Bug 216317 - No option to configure suspending
Summary: No option to configure suspending
Status: RESOLVED DUPLICATE of bug 221715
Alias: None
Product: openSUSE 10.3
Classification: openSUSE
Component: Mobile Devices (show other bugs)
Version: Alpha 1
Hardware: i686 SUSE Other
: P5 - None : Enhancement (vote)
Target Milestone: ---
Assignee: Danny Al-Gaaf
QA Contact: Jiri Srain
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-10-30 17:18 UTC by James Ogley
Modified: 2006-11-24 17:26 UTC (History)
0 users

See Also:
Found By: Beta-Customer
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description James Ogley 2006-10-30 17:18:33 UTC 
I've filed this under YaST, but it's not just a YaST issue - see below.

There's no option in the power management part of YaST to configure ACPI settings such as how to respond to closing a laptop lid (I would normally configure this to suspend-to-disk as, I suspect, would many others) - by default this just activates xlock.

It also applies in GNOME where the shutdown dialog no long gives the option to Hibernate.
Comment 2 Holger Macht 2006-11-06 17:30:21 UTC 
This has to be configured by a desktop applet such as g-p-m or kpowersave. This time picking Danny as assignee....

James, can you please create another bug for the GNOME logout dialog? Maybe Rodrigo can tell you to whom to assign this...
Comment 3 Danny Al-Gaaf 2006-11-06 23:31:56 UTC 
I work on this for KPowersave, but not sure if this is doable for 10.2 

Btw. There is the same problem for the KDE logout dialog if you use the logout button from the control panel.
Comment 4 Danny Al-Gaaf 2006-11-22 16:45:59 UTC 
This is currently only possible at 10.2 via the config file and not via the GUI. I write in the next days something how to configure this via the config file of KPowersave. I work on the GUI changes after 10.2 and we release maybe later a update for 10.2, but it should be fixed in 10.3
Comment 5 Danny Al-Gaaf 2006-11-24 17:26:22 UTC 

*** This bug has been marked as a duplicate of bug 221715 ***