GNOME Bugzilla – Bug 674821
Gnome 3.4 is not suspending when the lid is closed.
Last modified: 2012-06-19 16:48:49 UTC
Since upgrading to gnome 3.4.1, my laptop does not suspend when the lid is closed. I have checked the setting in gnome tweak tool, and they are both set to "Suspend" The laptop has no problem suspending if I choose the option from the menu to the right. Please tell me what logs you will need, and I will supply them..
/proc/acpi/button/lid/LID/state is updated to "state: closed" when the lid is closed.
#upower --monitor-detail [21:13:59.218] daemon changed: daemon-version: 0.9.15 can-suspend: yes can-hibernate yes on-battery: no on-low-battery: no lid-is-closed: yes lid-is-present: yes is-docked: no [21:14:01.571] daemon changed: daemon-version: 0.9.15 can-suspend: yes can-hibernate yes on-battery: no on-low-battery: no lid-is-closed: no lid-is-present: yes is-docked: no
#uname -a Linux arch 3.3.3-1-ARCH #1 SMP PREEMPT Mon Apr 23 09:41:07 CEST 2012 x86_64 Intel(R) Core(TM)2 Duo CPU T7300 @ 2.00GHz GenuineIntel GNU/Linux
this is now handled by the power plugin in gnome-settings-daemon
I see the same problem here using gnome 3.4.1 in fallback mode. Also, the battery icon does not update correctly as things change: battery is drained/charged, AC is plugged/unplugged. These problems occur with: gnome-settings-daemon-3.4.1 They go away when I revert to: gnome-settings-daemon-3.2.2
I can confirm this.. Suspend problem is gone when I revert to gnome-settings-daemon-3.2.2 however I do not see the battery issue, maybe that is a separate bug... ?
(In reply to comment #5) > I see the same problem here using gnome 3.4.1 in fallback mode. Also, the > battery icon does not update correctly as things change: battery is > drained/charged, AC is plugged/unplugged. This sounds like gnome-settings-daemon is crashing or the power plugin is failing to load. What does: killall gnome-settings-daemon killall gnome-settings-daemon (press alt-f4 to clear the fail-whale if it comes up) /usr/libexec/gnome-settings-daemon --debug print? Can you attach it to this bug as an attachment please. If you also shut the lid and re-open it we can see if the event is being ignored for some reason. Thanks.
Created attachment 212891 [details] /usr/lib/gnome-settings-daemon/gnome-settings-daemon --debug I closed the lid on line 336
On line 338: (gnome-settings-daemon:2544): power-plugin-DEBUG: lid is closed; not suspending nor hibernating since some external monitor outputs are still active. I do have an external monitor configured but it is not active..
#xrandr -q xrandr: Failed to get size of gamma for output default Screen 0: minimum 320 x 175, current 1280 x 800, maximum 1280 x 800 default connected 1280x800+0+0 0mm x 0mm 1280x800 50.0* 1024x768 51.0 52.0 832x624 53.0 800x600 54.0 55.0 56.0 57.0 58.0 720x400 59.0 700x525 60.0 640x512 61.0 62.0 640x480 63.0 64.0 65.0 66.0 67.0 640x400 68.0 640x350 69.0 576x432 70.0 512x384 71.0 72.0 73.0 74.0 75.0 416x312 76.0 400x300 77.0 78.0 79.0 80.0 81.0 360x200 82.0 320x240 83.0 84.0 85.0 86.0 320x200 87.0 320x175 88.0
same problem here: --- (gnome-settings-daemon:25856): power-plugin-DEBUG: lid is closed; not suspending nor hibernating since some external monitor outputs are still active --- but there is not any external monitor connected. it is a hp dc3550eg and i am using the propertary nvidia driver.
The issue is fixed with the latest nvidia driver ( 302.17). My guess is that the following change did the trick. Quote from nvidia changelog(http://www.nvidia.com/object/linux-display-amd64-302.17-driver.html) Added an "EDID" property to RandR 1.2 outputs. This property contains the binary contents of the connected monitor's extended display identification data, which allows applications such as the GNOME display properties dialog to query information about it.