Only manual suspend-to-ram possible?

After rebooting I checked the lid state again, closed the display -> entered suspend mode without problems -> reopened display -> checked state again:
Code:

cywhale@ubuntu:~$ cat /proc/acpi/button/lid/*/state state: open cywhale@ubuntu:~$ cat /proc/acpi/button/lid/*/state state: closed

So the lid state remains "closed" after reopening the display, therefore suspending won't work any more ?

Maybe the remaining lid state "closed" is caused by a missing lid-open event ?

sudo acpi_listen
Password: ...
<closing>
<waiting 10-20 sec.>
<opening>
button/lid LID 00000080 00000001

Shouldn't there be 2 events, one for closing the lid and one for opening ?

Can you please provide a the output from:

  lshal -m

when doing the lid close+open.

2 times close - wait - open:

Start monitoring devicelist:
-------------------------------------------------
acpi_LID condition ButtonPressed = lid
acpi_LID condition ButtonPressed = lid

The bug is still there. On my Fujitsu-Siemens Amilo M7400 running Ubuntu 6.10 suspending after 20 minutes of inactivity (as set in gnome-power-manager) does not happen.

[Expired for gnome-power-manager (Ubuntu) because there has been no activity for 60 days.]

I seem to have this same bug. I'm on an HP Pavilion dv1111AV. acpi_listen shows that acpi is getting the events. However, gnome-power-manager --verbose does not show gnome-power-manager handling the events.

Ugly as it is, I've worked around the problem by including commenting out the CheckPolicy line of the lid and including the following, which simulates the settings I tried to set up with gnome-power-manager.

#if [ `CheckPolicy` = 0 ]; then exit; fi

grep -q closed /proc/acpi/button/lid/*/state
if [ $? = 0 ]
then
    echo "lid closed"
    grep -q off-line /proc/acpi/ac_adapter/*/state
    if [ $? = 0 ]
    then
        echo "sleep with gnome-power-cmd"
        su tom
        gnome-power-cmd.sh suspend

Yeah, that's ugly.

Let me know if I can give you some more output to help with this.

I'm still experiencing this bug with intrepid.

Oddly, I register the close event with acpi_listen...
tom@hydrophax:~/Desktop$ acpi_listen
button/lid LID 00000080 00000010

And I can register it with cat /proc/acpi/

tom@hydrophax:~/Desktop$ cat /proc/acpi/button/lid/LID/state; echo close lid for 2 seconds; sleep 2; cat /proc/acpi/button/lid/LID/state; sleep 3; cat /proc/acpi/button/lid/LID/state
state: open
close lid for 2 seconds
state: closed
state: open

But it does not show up with lshal -m

tom@hydrophax:~/Desktop$ lshal -m

Start monitoring devicelist:
-------------------------------------------------
21:47:29.015: computer_power_supply_battery_BAT0 property battery.remaining_time = 4082 (0xff2)
21:47:29.018: computer_power_supply_battery_BAT0 property battery.charge_level.percentage = 43 (0x2b)
21:47:29.020: computer_power_supply_battery_BAT0 property battery.charge_level.design = 71022 (0x1156e)
21:47:29.021: computer_power_supply_battery_BAT0 property battery.charge_level.last_full = 82196 (0x14114)
21:47:29.022: computer_power_supply_battery_BAT0 property battery.charge_level.current = 35605 (0x8b15)
21:47:29.023: computer_power_supply_battery_BAT0 property battery.reporting.current = 3008 (0xbc0)
21:47:29.024: computer_power_supply_battery_BAT0 property battery.voltage.current = 11837 (0x2e3d)