|
Bugzilla – Full Text Bug Listing |
| Summary: | Suspend to disk/ram no longer an option in the KDE shutdown dialog | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.0 | Reporter: | Ulrich Derenthal <uli.2001> |
| Component: | KDE3 | Assignee: | E-mail List <kde-maintainers> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P2 - High | CC: | andrew, daniele, dspolleke, forgotten_qMyteedNxa, mcphrsp, mlemos, pablo, zajec5 |
| Version: | Beta 1 | ||
| Target Milestone: | --- | ||
| Hardware: | x86 | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | lshal output | ||
|
Description
Ulrich Derenthal
2007-07-10 22:01:06 UTC
that means that liblazy returned false for power_management.can_suspend. I believe one of the reasons for that is powersave not running. does that run for you? powersaved seems to be running: rcpowersaved status Checking for service powersaved running holger, any idea? It only depends on HAL whether the power_management.can_suspend key is set or not. Ulrich, please post the output of $ lshal | grep power_management Does suspend work when used from kpowersave or with pm-suspend? After another reboot, it works again. I don't know why it didn't work before. For completeness, I should mention that when it did not work when being login in into KDE, it worked after logging out again and selecting shutdown in the graphical login screen. I had to type in the root password, and then suspend worked. lshal | grep power_management power_management.can_suspend_to_disk = true (bool) power_management.acpi.linux.version = '20060707' (string) power_management.can_hibernate = true (bool) power_management.can_suspend_to_ram = true (bool) power_management.can_standby = false (bool) power_management.can_suspend = true (bool) power_management.type = 'acpi' (string) closing as worksforme then. feel free to reopen when it is happening reproducible. I just tried opensuse 10.3 and this problem still happens. Actually I did exactly as Ulrich Derenthal mentioned, selected shutdown in the graphical login screen and the suspend to disk/ram options started appearing in kpowersave menu. Previously I was asking to shutdown without logging out the user and the suspend to disk/ram would never appear in kpowersave after rebooting. So, I assume there may be something different depending on how you ask to shutdown. Since I lost hours figuring this out until I found this report, I thought I should reopen the bug report because I suspect many other users may be annoyed until they figure it too. $ lshal | grep power_management Created attachment 188760 [details]
lshal output
Information was provided. *** Bug 383179 has been marked as a duplicate of this bug. *** Dirk: thanks for deciding and marking. Developers: you may find interesting information also in report (bug 383179) ─ if more info needed, let me know. *** Bug 402479 has been marked as a duplicate of this bug. *** Adding myself to the cc list to maintain status. I can provdive additional information (beside those in bug #402479 ) When logged in as root the suspend option is present. *** Bug 358389 has been marked as a duplicate of this bug. *** fixed for 11.1. Anja, would you assign a swamp for this issue? it is a regression in 11.0 due to hal changing in a backward incompatible way (one liner fix). I can collect some other kde3 related fixes into the swamp. *** Bug 397882 has been marked as a duplicate of this bug. *** *** Bug 405187 has been marked as a duplicate of this bug. *** closing for further processing *** Bug 402479 has been marked as a duplicate of this bug. *** If this is a simple patch why can't it be applied against 11.0? All the 11.0 installs I have done irregardless of architecture exhibit this problem. It is unacceptable for suspend not to work (well it does work if you login as root but giving out root passwords is not a viable workaround). The environmental impact is atrocious. The fact this bug was reported in Beta 1 of 11.0 makes it a bit of a stretch to justify pushing it out to 11.1 the patch is already queued for 11.0 update. released I ran an update and I see the suspend option. Thank you. As I didn't open this bug, I won't close it. Hm. After installing the fix, after wakeup from suspend I get a errormessage (kde-dialog): "Fehler - KDE-Kontrolleiste" "Suspend fehlgeschlagen" (Error - KDE-controlpanel - Failed suspend). A new bug? I reopened this one. Hi, FWIW, I do not get the above message when I suspend to RAM. comment #28: you've found bug 382364 on one of twp machines i have updated (the third will follow shortly) the update has worked.. However, when clicking suspend it it suspends to disk rather than giving me the option to suspend to RAM aswell.. just a minor glitch. on my current machine still no suspend option.. |