Bugzilla – Bug 113175
YaST powersave module fails to read current system state for "Suspend to Disk"
Last modified: 2005-08-26 08:01:08 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).
Created attachment 47681 [details] hwinfo output
Created attachment 47682 [details] y2log
Created attachment 47683 [details] y2log-1
*** This bug has been marked as a duplicate of 105301 ***