[SOLVED] Guidance won't remember my choices on KDE 4.4.3 (-current)
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Guidance won't remember my choices on KDE 4.4.3 (-current)
I can not get Guidance to remember my choices past the first suspend. I open Guidance from the battery icon on my screen and select "Suspend" from the "lid closed" option list. I click OK (or apply then OK) and my choice is remember right until I close the lid and restart. If I don't go through the process again random events occur when I resume the second time. I am a member of the power group, this was working perfectly on 4.4.2 and previous. Is there a text file I can edit to fix this properly instead of all the clicky-clicky I'm not listening nonsense?
Multiple Lenovo ThinkPad models with Intel Core i5/i7 CPUs can
successfully suspend/resume once, and then hang on the second s/r
cycle.
We got confirmation that this was due to a BIOS defect. The BIOS
did not properly set SCI_EN coming out of S3. The BIOS guys
hinted that The Other Leading OS ignores the fact that hardware
owns the bit and sets it manually.
In any case, an existing DMI table exists for machines where this
defect is a known problem. Lenovo promise to fix their BIOS, but
for folks who either won't or can't upgrade their BIOS, allow
Linux to workaround the issue.
Confirmed by numerous testers in the launchpad bug that using
acpi_sleep=sci_force_enable fixes the issue. We add the machines
to acpisleep_dmi_table[] to automatically enable this workaround.
Cc: Colin King <colin.king@canonical.com>
Signed-off-by: Alex Chiang <achiang@canonical.com>
Signed-off-by: Len Brown <len.brown@intel.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Try the "acpi_sleep=sci_force_enable" kernel option.
I am having a similar problem with the Guidance Power manager. It does not remember my settings, either, but in any case it ignores the settings I make anyway. My laptop suffers from the "cannot resume a second time" bug (it is a Compaq Presario 700), so I do not want it to suspend when I close the lid. Unfortunately it insists on doing so when my power cable is not plugged in. Setting the "When Laptop Lid Is Closed" option in Guidance has no effect on this behavior.
Have you tried going through System Settings -> Advanced -> Power Management and setting your profiles as you wish?
I actually have the "When laptop lid closed" set to Do Nothing. The action on lid close is handled by pm-utils, through a line in /etc/acpi/acpi_handler.sh, so that it is general across all environments.
Code:
#!/bin/sh
# Default acpi script that takes an entry for all actions
IFS=${IFS}/
set $@
case "$1" in
button)
case "$2" in
power) /sbin/init 0
;;
lid) /usr/sbin/pm-hibernate
;;
*) logger "ACPI action $2 is not defined"
;;
esac
;;
*)
logger "ACPI group $1 / action $2 is not defined"
;;
esac
Thanks, allend. I made the change to the script and told KDE to do nothing when the lid is closed. I'll see if that helps after I'm done building 2.6.34 (asynchronous suspend/resume )
OK, so after a minor revision to the script I am much happier with the response to suspend and resume. I no longer have lock on resume, but maybe a little digging will answer that.
Code:
#!/bin/sh
# Default acpi script that takes an entry for all actions
IFS=${IFS}/
set $@
case "$1" in
button)
case "$2" in
power) /usr/sbin/pm-hibernate
;;
lid) /usr/sbin/pm-suspend
;;
*) logger "ACPI action $2 is not defined"
;;
esac
;;
*)
logger "ACPI group $1 / action $2 is not defined"
;;
esac
Last edited by em21701; 05-20-2010 at 03:52 PM.
Reason: fixed script error
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.