Bug 15667

Summary: Visual corruption after recent upgrades
Product: Mageia Reporter: Friedel Wolff <friedel>
Component: RPM PackagesAssignee: Mageia Bug Squad <bugsquad>
Status: RESOLVED OLD QA Contact:
Severity: normal    
Priority: Normal CC: tmb
Version: 4   
Target Milestone: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Source RPM: CVE:
Status comment:

Description Friedel Wolff 2015-04-09 19:36:21 CEST
After recent upgrades (I assume it is the kernel) and a reboot (earlier today) I have frequent visual corruption in GNOME shell. It manifests as content from other windows showing over clean, unused parts of the desktop. For example, when switching to an empty workspace (Ctrl+Alt+Down or through the workspace switcher in Activities view) some remnants of the window on the previous workspace is shown. With a second monitor connected, there is constant corruption on a part of the second monitor, unless there is a window open on that monitor. There is no corruption over "used" parts of the desktop (where a window is shown, or even when a preview window is shown in the Activities view).

Hardware: HP Probook with integrated Intel graphics.

I'm not sure which packages are useful to report on, but this is what I'm currently running that I guess might be useful to know:
3.14.32-desktop-1.mga4
lib64drm_intel1-2.4.51-1.mga4
libdrm_intel1-2.4.51-1.mga4
x11-driver-video-intel-2.99.909-1.2.mga4
x11-server-xorg-1.14.5-2.3.mga4
lib64clutter1.0_0-1.16.2-1.mga4
gnome-shell-3.10.2.1-7.1.mga4

some lines from lspci:
00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller (rev 09)
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)
Comment 1 Thomas Backlund 2015-04-10 10:51:46 CEST
Can you check if 3.14.37-desktop-2.mga4 currently in core updates_testing works any better ?

CC: (none) => tmb

Comment 2 Samuel Verschelde 2015-09-21 13:18:52 CEST
Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer 
maintained, which means that it will not receive any further security or bug 
fix updates.

Package Maintainer: If you wish for this bug to remain open because you plan to 
fix it in a currently maintained version, simply change the 'version' to a later 
Mageia version.

Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't 
able to fix it before Mageia 4's end of life. If you are able to reproduce it 
against a later version of Mageia, you are encouraged to click on "Version" and 
change it against that version of Mageia. If it's valid in several versions, 
select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.

Although we aim to fix as many bugs as possible during every release's lifetime, 
sometimes those efforts are overtaken by events. Often a more recent Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].

[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/
Comment 3 Marja Van Waes 2015-10-27 06:56:18 CET
As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates.

This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version)

If you are able to reproduce it against a maintained version of Mageia, you are encouraged to 
1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED"
2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.
3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page:
https://wiki.mageia.org/en/How_to_report_a_bug_properly

If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too). 


If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].
[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/

Status: NEW => RESOLVED
Resolution: (none) => OLD