Bug 402479

Summary: Suspend to disk/ram no longer an option in KDE3 after upgrade to 11.0
Product: [openSUSE] openSUSE 11.0 Reporter: Ulrich Derenthal <uli.2001>
Component: KDE3Assignee: E-mail List <kde-maintainers>
Status: RESOLVED DUPLICATE QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P3 - Medium CC: andrew, cgoncalves
Version: Final   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Ulrich Derenthal 2008-06-21 08:54:38 UTC
I am using KDE 3 in openSUSE 11.0, and suspend to disk/ram does no longer appear in the shutdown dialog of KDE 3. It worked perfectly in 10.3 before the upgrade.

Calling pm-suspend from the command line as root seems to work.
Comment 1 Carlos Gonçalves 2008-06-21 10:27:25 UTC
I can confirm this, though when I want to suspend I always do it by right-clicking on the kpowersave systray icon which works.

Ulrich, anyway you can suspend with user permissions by running 'powersave -U' (disk), 'powersave -u' (ram), or 'powersave -m' (standby)
Comment 2 Ulrich Derenthal 2008-06-21 11:43:18 UTC
The two methods you describe (kpowersave systray icon and command line) work here, so this is no longer a serious problem for me.
Comment 3 Dirk Mueller 2008-06-23 15:53:54 UTC
lshal | grep power_man

please
Comment 4 Ulrich Derenthal 2008-06-23 17:50:18 UTC
> lshal | grep power_man
  power_management.acpi.linux.version = '20070126'  (string)
  power_management.can_hibernate = true  (bool)
  power_management.can_standby = false  (bool)
  power_management.can_suspend = true  (bool)
  power_management.can_suspend_hybrid = false  (bool)
  power_management.is_powersave_set = true  (bool)
  power_management.quirk.s3_bios = true  (bool)
  power_management.quirk.s3_mode = true  (bool)
  power_management.type = 'acpi'  (string)
Comment 5 Carlos Gonçalves 2008-06-26 10:47:42 UTC
*** Bug 404040 has been marked as a duplicate of this bug. ***
Comment 6 Klaus Singvogel 2008-06-26 11:20:41 UTC
I'm also noticing this issue.

Additional information from my site:
- The menu entry was present in openSUSE-10.3, and openSUSE-10.2 on my machine.
- "powersave -U" works fine.
- "cat /sys/power/state" shows "mem disk".
- kpowersave applet has options "Suspend to Disk" and "Suspend to RAM"
- YaST PowerSave module is no longer avail in distribution to change anything
via it.
- It doesn't matter if using KDE-Menu or Logout Applet: the entry is missing in
any case.
- "lshal | grep power_man"
  power_management.acpi.linux.version = '20070126'  (string)
  power_management.can_hibernate = true  (bool)
  power_management.can_standby = false  (bool)
  power_management.can_suspend = true  (bool)
  power_management.can_suspend_hybrid = false  (bool)
  power_management.is_powersave_set = false  (bool)
  power_management.quirk.no_fb = true  (bool)
  power_management.quirk.vbestate_restore = true  (bool)
  power_management.type = 'acpi'  (string)
Comment 7 Lubos Lunak 2008-06-27 13:08:45 UTC

*** This bug has been marked as a duplicate of bug 290917 ***
Comment 8 Andrew Joakimsen 2008-07-28 05:13:49 UTC
I have the same issue... suspend option simply is not present in KDE3. But if you login as root the suspend option is there. Confirmed on two systems one is x86_64 and the other i686. 

Why can't this be a simple patch for 11.0?
Comment 9 Dirk Mueller 2008-07-28 11:41:44 UTC
it is a simple patch, and the patch is submitted. please also do not reopen bugreports that are marked as duplicate of another unless you think it is not really a duplicate. 

*** This bug has been marked as a duplicate of bug 290917 ***
Comment 10 Andrew Joakimsen 2008-07-28 19:28:33 UTC
If this is a simple patch why can't it be applied against 11.0?
Comment 11 Andrew Joakimsen 2008-07-28 19:30:06 UTC
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.