Mailinglist Archive: opensuse-bugs (10046 mails)
| < Previous | Next > |
[Bug 230717] s2ram -f -a 3 worked under suse 10.1 final, under suse 10.2 final does not work any more
- From: bugzilla_noreply@xxxxxxxxxx
- Date: Sun, 14 Jan 2007 15:35:19 -0700 (MST)
- Message-id: <20070114223519.1F502FAB@xxxxxxxxxxxxxxxxxxxxxx>
https://bugzilla.novell.com/show_bug.cgi?id=230717
------- Comment #25 from seife@xxxxxxxxxx 2007-01-14 15:35 MST -------
That logfile looks perfectly good.
Note that the "suspend failed" popup is an error in kpowersave / the start menu
/ DBus. The suspend does not really fail, it is just signalled that it fails.
The screen not being locked after suspending from the start menu is a KDE bug,
not a suspend bug.
What i meant was "the logfile after a suspend that did not switch back to X
without interaction (hitting the win key or simply alt-f7".
Just ignore that "suspend failed" popup until a fixed kpowersave package is
available.
--
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.
------- Comment #25 from seife@xxxxxxxxxx 2007-01-14 15:35 MST -------
That logfile looks perfectly good.
Note that the "suspend failed" popup is an error in kpowersave / the start menu
/ DBus. The suspend does not really fail, it is just signalled that it fails.
The screen not being locked after suspending from the start menu is a KDE bug,
not a suspend bug.
What i meant was "the logfile after a suspend that did not switch back to X
without interaction (hitting the win key or simply alt-f7".
Just ignore that "suspend failed" popup until a fixed kpowersave package is
available.
--
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.
| < Previous | Next > |