https://bugzilla.novell.com/show_bug.cgi?id=257451 hmacht@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED ------- Comment #7 from hmacht@novell.com 2007-04-02 02:17 MST ------- (In reply to comment #6)
Hurray! :-D It works. Thank you very much.
Sorry about the xlock-xclock :-) It was it, but how it get to suspend to ram, I don't know. I didn't change anything except LID CLOSE & OPEN.
I am not closing this report, since I don't know if this xlock was intentional (imho there should be no such think, but that's just my 2 cents).
From a security point of view, you need at least _something_. Otherwise the system would be completely vulnerable after waking up. And because of the fact that you don't use a graphical frontend like kpowersave or gnome-power-manager, we are trying to find the least common denominator, which is xlock.
-- 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.