Description of Problem: In KDE, if Desktop Effects are enabled, using any fullscreen OpenGL based application or screensaver (tested with XBMC Media Center, as well as screensavers - Eurphoria GL and Flux GL) while "Suspend desktop effects for fullscreen windows" is enabled causes image flickering and after-imaging followed by severe, lingering, graphically instability upon exiting the application (or waking from screensaver) usually in the form of a black screen or imprint of last frame drawn for the duration of the session. This instability is only remedied, fully, by rebooting the system until it triggers again. NOTE: This might be video card specific (Intel N10 Family Integrated Graphics Controller), not sure. Version-Release number of selected component (if applicable): Mageia 2 Cauldron Beta 2 (fully updated as of 4/13/2012 12:01AM EDT) How reproducible: Always in KDE if both Desktop Effects and "Suspend desktop effects for fullscreen windows" are enabled while a fullscreen opengl based application or screensaver is active. Tested and confirmed with XBMC Media Center, Eurphoria GL and Flux GL. Steps to Reproduce: 1. Log into KDE (an Intel N10 Family chipset might be needed to trigger) 2. Enable Desktop Effects (if not enabled already) and under the Advanced tab, enabled ""Suspend desktop effects for fullscreen windows" 3. Launch XBMC or any OpenGL Screensaver (try this with Eurphoria GL for best results) 3A. (If testing with an opengl screensaver) Wait for screensaver to activate (doesn't always trigger if "Test" is used) 4. Graphical instability should be noted at this point. If not, go to step 5. 6. Wake from screensaver (or exit application) and notice instability. If desktop still appears normal, go to last step. 7. Open and close any window then do it again (such as Dolphin)
Hi, This bug was filed against cauldron, but we do not have cauldron at the moment. Please report whether this bug is still valid for Mageia 2. Thanks :) Cheers, marja
Keywords: (none) => NEEDINFO
@ Andrew, This bug was filed agains old cauldron, from before Mageia 2 release It is very important for us to know whether this bug is valid for Mageia 2 and/or for *current* cauldron. Please tell us within two weeks from now. If you don't reply again, we'll have to close this bug as old.
CC: (none) => marja11
2x no reply, closing as old Feel free to reopen if needed and tell in which fully updated Mageia version(s) you still have this issue
Status: NEW => RESOLVEDResolution: (none) => OLD