After a fresh hald start, acpi and hal agree on the lid state of my laptop [root@trillian lowe]# lshal -l | grep button.state button.state.value = false (bool) [root@trillian lowe]# cat /proc/acpi/button/lid/LID/state state: open However, after hibernating (by closing the lid) and resuming, they disagree [root@trillian lowe]# lshal -l | grep button.state button.state.value = true (bool) [root@trillian lowe]# cat /proc/acpi/button/lid/LID/state state: open I am using hal version 0.5.7 plus the patch for hal-system-power-hibernate that rescans the button on resume. So rescanning isn't setting the correct state. Restarting hald on resume returns the values to normal. This is related to gnome-power-manager bug http://bugzilla.gnome.org/show_bug.cgi?id=334220
I'm seing the exact same thing on my system and I know of a few other systems that are hit by this bug as well (i don't know of any system that's not). 3rd party tools, like gnome-power-manager, that relies on this information from hal can't help making bad decicions. So, whenever i unplug AC from my laptop to move to another desk, my system is suspended because it thinks the lid is shut.
2006-04-24 Richard Hughes <richard@hughsie.com> * tools/hal-system-power-hibernate, tools/hal-system-power-suspend: Add --print-reply to dbus-send else the Rescan does not work. This should fix a whole load of bugs related to ACPI values on resume.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.