Bug 113175

Summary: YaST powersave module fails to read current system state for "Suspend to Disk"
Product: [openSUSE] SUSE LINUX 10.0 Reporter: Gerald Pfeifer <gp>
Component: YaST2Assignee: E-mail List <bnc-team-screening>
Status: RESOLVED DUPLICATE QA Contact: Klaus Kämpf <kkaempf>
Severity: Normal    
Priority: P5 - None    
Version: Beta 3   
Target Milestone: ---   
Hardware: i386   
OS: All   
Whiteboard:
Found By: Other Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: hwinfo output
y2log
y2log-1

Description Gerald Pfeifer 2005-08-25 22:07:24 UTC 
After installing 10.0 Beta3 on my notebook (T41p) with KDE as the desktop
kpowersave was automatically started and I could successfully suspend to 
disk as a user (selecting the according item from the kpowersave menu).

When running YaST to configure powersave, then, the dialog called "Modes
Permitted for Users" had _both_ "Suspend to Disk" and "Suspend to RAM"
disabled.  After just hitting OK, without making any change, "Suspend
to disk" indeed was not available in the kpowersave menu any longer.

In other words, YaST's powersave module does not correctly read the current
state of the active system configuration when invoked first (and/or the
defaults in YaST and powersave are not consistent).
Comment 1 Gerald Pfeifer 2005-08-25 22:08:24 UTC 
Created attachment 47681 [details]
hwinfo output
Comment 2 Gerald Pfeifer 2005-08-25 22:09:34 UTC 
Created attachment 47682 [details]
y2log
Comment 3 Gerald Pfeifer 2005-08-25 22:09:49 UTC 
Created attachment 47683 [details]
y2log-1
Comment 4 Danny Al-Gaaf 2005-08-26 08:01:08 UTC 

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