https://bugzilla.novell.com/show_bug.cgi?id=552271 https://bugzilla.novell.com/show_bug.cgi?id=552271#c9 Ron Lusk <rlusk@actslife.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rlusk@actslife.org --- Comment #9 from Ron Lusk <rlusk@actslife.org> 2010-11-15 03:11:21 UTC --- (In reply to comment #7)
Obviously the issue is no longer reproducable. Otherwise please reopen
I can easily reproduce it (openSuSE v11.3): I have an Acer Aspire running the KDE Plasma Netbook workspace. 1. Unplug the AC adapter from a running system. The system displays a Power Management notification, and the KDE Window Manager displays the "Compositing has been suspended by another application, you can resume it by using the ALT-SHIFT-F12 shortcut" message. NOTE: After this point, "fancy" effects no longer work: if I click on the "Current Application Control" on the right of the taskbar, I get a fairly plain dropdown list instead of the usual display of all windows to choose from. 2. Suspend to RAM 3. Plug in the AC adapter 4. Press any key to resume from RAM. Wait 30 seconds or so. Instead of displaying a black screen with (eventually) an unlock dialog, I get the background image (the greenish bubbly theme). Since I am not logged in, Shift-Alt-F12 does nothing here. 5. Unplug the system. The background image disappears (along with "compositing", presumably), and a blank screen with an unlock dialog appears (or just a blank screen, and press a key to see the unlock dialog). 6. Unlock the system. The view visible just before suspending to RAM reappears. 7. Plug in the AC adapter. The background image appears (as compositing starts up, badly, apparently). 8. Press Shift-Alt-F12. The normal desktop appears, but all the whizzy effects are gone. What appears to happen is that compositing is never successfully turned on when AC power is restored. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.