Bug 590165

I can confirm the problem on a dell e6400.
Closing lid does not suspend, however I don't have issues with the mouse.
Suspending via System->shutdown->suspend works and closing and re-opening the lid resumes from suspend.
I'm not sure when this stopped working.

Just for clarity, in my case:

Steps to Reproduce:
1. Close lid, the computer does not suspend
2. system->shutdown->suspend, and the screen fades to black and the computer suspends to RAM
3. Open the lid and the computer resumes, with visible mouse pointer

Same thing on my DELL E6400. In /var/log/messages:

localhost kernel: dell-wmi: Received unknown WMI event (0x11)

I also have the lid-closing problem (but no mouse pointer problem) on a Dell XPS M1330 and Inspiron 640m, eg same as Comment 1.
I don't see any messages in /var/log/messages.
We're running 2.6.33.3-85.fc13 (one x86_64, one i686).

Same issue for me on eee pc 1005pe.  Closing lid suspended fine when I was using kernel-2.6.33.3-79.fc13.i686 (not sure of pm utils).  After yum update on May 9th, it stopped working once it booted to kernel-2.6.33.3-85.fc13.i686.

When I close lid, my backlight is turned off but suspend doesn't happen.  Opening lid correctly turns on backlight but you can tell system was running the whole time lid was closed (disk light would occasionally blink for example).

Output of /proc/acpi/event shows events are working:

button/lid LID 00000080 00000009
button/lid LID 00000080 0000000a

Run dbus-monitor --system shows something related to lid but not sure its correct values:

signal sender=:1.6 -> dest=(null destination) serial=552 path=/org/freedesktop/Hal/devices/computer_logicaldev_input_4; interface=org.freedesktop.Hal.Device; member=PropertyModified
   int32 1
   array [
      struct {
         string "button.state.value"
         boolean false
         boolean false
      }
   ]
signal sender=:1.6 -> dest=(null destination) serial=553 path=/org/freedesktop/Hal/devices/computer_logicaldev_input_4; interface=org.freedesktop.Hal.Device; member=Condition
   string "ButtonPressed"
   string "lid"
signal sender=:1.6 -> dest=(null destination) serial=554 path=/org/freedesktop/Hal/devices/computer_logicaldev_input_4; interface=org.freedesktop.Hal.Device; member=PropertyModified
   int32 1
   array [
      struct {
         string "button.state.value"
         boolean false
         boolean false
      }
   ]
signal sender=:1.6 -> dest=(null destination) serial=555 path=/org/freedesktop/Hal/devices/computer_logicaldev_input_4; interface=org.freedesktop.Hal.Device; member=Condition
   string "ButtonPressed"
   string "lid"


Suspend does work if I select it from Gnome's Shut Down prompt.

I now suspect this is an issue with an upgrade to gnome-power-manager or resources it uses.  The rational is because gnome-power-manager is were you set the preference that closing lid should invoke Suspend.

Also, I noticed today that when I remove power cord the gnome-power-manager job of dimming the display did not occur.  I believe I'm also now missing some battery related notification messages as well.

As a side note, I have an unrelated app I wrote that monitors dbus for org.freedesktop.UPower and signal Changed and that is no longer being detected after this same upgrade.  I didn't think UPower monitored lid's but perhaps that is real source of issue.

I noticed Fedora 13 updates-testing email mentioned an update to upower and a bug description about failing to suspend/hibernate when lid closed.  For me, it turned out a duplicate of bugzilla #590090 .

A "yum --enablerepo updates-testing update upower" and then rebooting fixed the issue for me.

upower-0.9.4-1 from updates-testing has also fixed the same issue on XPS M1330.

*** This bug has been marked as a duplicate of bug 590090 ***