https://bugzilla.novell.com/show_bug.cgi?id=326814#c11
Adam Martinson
battery.alarm.design = 5827 (0x16c3) (int) 151c151 < battery.voltage.current = 16749 (0x416d) (int)
battery.voltage.current = 16725 (0x4155) (int) 202c202 < button.state.value = false (bool)
button.state.value = true (bool)
The last part I think is the relevant one. After lid close, suspend-to-ram, lid open, and resume, the button.state.value for the lid doesn't get set back to false. After this auto-suspend on lid close fails. Manually initiating suspend-to-ram, and then closing the lid works, and it will automatically resume when you open the lid again, and afterward it will suspend when you close the lid (once). Either that or I can close the lid, open it, and close it again, and then it will work. So for me auto-suspend on lid close works every other time. I don't think it's a hal problem though, because using hal-set-property to manually change button.state.value back to false doesn't help! I really think this is an ACPI issue, because here's the output from acpi_listen during first a successful lid close->suspend->open->resume and then an unsuccessful one: ibm/hotkey HKEY 00000080 00005001 button/lid LID 00000080 00000007 processor CPU 00000081 00000000 ibm/hotkey HKEY 00000080 00005001 button/lid LID 00000080 00000008 ibm/hotkey HKEY 00000080 00005002 button/lid LID 00000080 00000009 After the successful one, the ACPI events for the lid opening are missing. ~Loki -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.