https://bugzilla.novell.com/show_bug.cgi?id=230717 ------- Comment #22 from jan.sekal@volny.cz 2007-01-14 10:04 MST ------- Created an attachment (id=112914) --> (https://bugzilla.novell.com/attachment.cgi?id=112914&action=view) one suspend, that failed here is one suspend to ram, that "failed" - it was triggered via the start menu - on resume, a text file that was under cursor in krusader on suspending to ram was loaded approx 120 times (see the next attachment) (krusader was the application directly behind the start menu on suspending the computer to ram) when i was killing the approx. 120 times launched text file (with application Kwrite) using ksysguard, a spontaneous logoff occured - after logging in, all was ok and computer worked properly in the next next comment, there is the var/log/pm-suspend.log It seems to me, that the main problem is ksysguard - now when I want my machine suspend to ram, i always close ksysguard before that, and this really helps! With this workaround (closing ksysguard before suspend to ram), resume after suspend to ram is possible: 1. if triggered via kpowersave dock icon, restart of x does not occur by itself, you have to pres win key and hold it for approx 5 sec (only password protection is ignored, although explicitly required by the user - in kpowersave settings/general settings/lock screen) 2. if triggered via start menu, pressing the win key several times to switch to x window is often necessary (and in this case password protection is ignored, although explicitly required by the user - in kpowersave settings/general settings/lock screen), sometimes x window is started automatically and then password is required -- 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.