https://bugzilla.novell.com/show_bug.cgi?id=264692 dkukawka@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hmacht@novell.com, seife@novell.com, | |dkukawka@novell.com Status|NEW |NEEDINFO Info Provider| |ammulder@chariotsolutions.com ------- Comment #1 from dkukawka@novell.com 2007-04-16 15:04 MST ------- (In reply to comment #0)

Also, I would be pretty happy if both KPowersave and KDEBase patches were rolled back, because suspend worked properly back then (through early March).

We don't rollback updates because of problems that are machine specific. This make absolutely no sense, also because you can rollback this on your machine if you think you need this. The problem you descriped are may kernel problems and not KPowersave specific. do this: - go to konsole and call 'lshal -m' - suspend and resume via KPowersave, attach the output from konsole -- 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, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=264692 ------- Comment #2 from seife@novell.com 2007-04-17 06:09 MST ------- to work around your problem, you can just stop powersaved with /etc/init.d/powersaved stop and ensure that it is not started during boot with "insserv -r powersaved". Then everything should work fine. This is a thinkpad specific bug. -- 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, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=264692 ------- Comment #7 from ammulder@chariotsolutions.com 2007-04-17 11:42 MST ------- The update fixed my problem. I had not realized it was a ThinkPad specific problem. Thanks. I had the same problem on openSUSE 10.3 alpha 2 (bug #259666) and I hope this fix will be applied there too. -- 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, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=264692 ------- Comment #8 from ammulder@chariotsolutions.com 2007-04-18 08:31 MST ------- Well, having used this a bit more... With the update, when my machine resumes from suspend to RAM, the image on the screen is pretty mangled. It shows a legible login box on top of that, and if I log in then it clears up and the desktop looks fine. But it doesn't seem to recover without a login. I only mention this because it didn't happen before -- it used to come up with the screen all black IIRC, but not corrupted. -- 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, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=264692 ammulder@chariotsolutions.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|ammulder@chariotsolutions.co| |m | ------- Comment #10 from ammulder@chariotsolutions.com 2007-04-18 08:52 MST ------- Well... my screen saver is set to "GLMatrix" in KDE. For what it's worth, the post-resume image most recently was primarily white (like my proper desktop itself, which was dominated by mainly white Firefox and Konsole windows), while the screen saver was mainly black with some green. I don't think the screen saver had engaged when I suspended (I just closed the lid), so it seems more like some mangled version of the desktop rather than something relating to the screen saver. I guess it's possible that xlock does something different than the main KDE screen saver (I'm not too sure of the mechanics). But it really looked more like random junk in the graphics card buffer or whatever than a screen saver. I think this is similar to what used to happen long ago when using previous releases and suspend with s3_bios. It seemed that on the recent hardware and OS platforms, when resuming, either it went straight back to the desktop or came up with a black screen that I could then unlock. But as I said it seems to have changed since this latest update. -- 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, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=264692 hmacht@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aj@novell.com Status|ASSIGNED |RESOLVED Resolution| |FIXED ------- Comment #12 from hmacht@novell.com 2007-04-19 05:48 MST ------- Fixed powersave package which doesn't handle the IBM hotkeys anymore submitted to internal build system. Fixed. -- 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, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=264692 seife@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gp@novell.com ------- Comment #14 from seife@novell.com 2007-04-26 09:48 MST ------- *** Bug 268630 has been marked as a duplicate of this bug. *** -- 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, or are watching someone who is.