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.
@feinom
I checked everything in /etc/acpi and there's nothing there.
@didier
I guess that would be temporary solution but I'd rather be able to control what happens with the lid and to retain software controlled power-off.
Is the /etc/acpi directory emtpy? My default installation has the acpi_handler script and a directory called "events" which contains a file named "default".
Sorry, I meant to say there is nothing there except the default files (acpi_handler.sh and events/default).
Through trial and error I found that choosing "Off" as the action for "Lid Switch Closed" in Klaptop is causing the crash. If I choose something like "logout" then I do not get a lock up. Is this possibly a klaptop problem?
Last edited by brixtoncalling; 03-30-2009 at 04:03 PM.
To update a bit, I can't seem to predictably prevent this locking up no matter how much I play with klaptop. Sometimes I can get it to log out on close but usually it is a crash. The same thing happens when I am logged in at the terminal (no X running).
Besides the files in /etc/acpi what should I be looking at? I can find nothing in /var/log/syslog except that acpi_helper.sh is correctly catching the lid close (I added a little logger message to test it).
I would avoid using KDE settings for ACPI. Personally I don't use it at all.
Go to Control Center/Power Control/Laptop Battery and disable everything in the ACPI tab.
Other than that I tried "rmmod button". In fact I still can shutdown through software (e.g. "shutdown -r now" or "halt"); the only difference is that when I hit the ON/OFF button nothing happens (usually it triggers the "halt" command).
Well I did not find the source of the problem per se, but an upgrade to kernel 2.6.29 has solved it. Things worked fine with the 12.1 default kernel but not with the one that shipped with 12.2.
At least I've learned to love pm-utils -- allend's setup works better than klaptop.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.