https://bugzilla.novell.com/show_bug.cgi?id=230717 ------- Comment #15 from jan.sekal@volny.cz 2007-01-09 14:31 MST ------- (In reply to comment #14)
It actually seems to hang somewhere in s2ram for quite some time. If you do not press the Win key but wait for some time, does it eventually resume back to X?
Can you attach /var/log/pm-suspend.log after a resume? Maybe we can see something in there.
below I attach the the file I noticed following (I use suspend to ram very often): 1. it seems to me, that ksysguard inhibits somehow the restart of x - if i start suspend to ram via start menu (CTRL + ESC, TAB, 4 times arrow-left-key, 3 times arrow-up-key, ENTER) and ksysguard is running, it is very probable, that the restart of x does not occur after resume if ksysguard is not running, and suspend to ram is triggered the same way, i was able to repeat this up to approx. 7 times without problem, even the restart of x occurs spontaneously and almost immediately after resuming triggering the suspend to ram via start menu (as described above - via keyboard) sooner or later ended the way that network was inaccessible (as documented in comment 16) - what helps, is to start yast/network devices/network card - click next, edit, next and finish - then network is accessible again if the suspend to ram is triggered via start menu and ksysguard is not running, then restart occurs spontaneously usually almost immediately after resume, but the user is not asked for password, although it should do so 2. if suspend to ram is triggered via dock icon of kpowersave, and ksysguard is not running, everything works fine and user is asked for password except one detail - one has to press the win key three times until switched to the correct x window -- 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.