You are not logged in.
Since gnome 3.4 my laptop is not suspending when I close the lid.
The problem is that gnome-settings-daemon believe there is an external monitor connected.
All my attempts to understand how gnome-settings-daemon is dreaming up this non existing external monitor has failed.
The problem is also described in this thread.. The tread is marked as solved, but it really does not solve the problem.
I have reported the problem to the bugtracker. But nothing happens, and the bug is listed as NEEDINFO..
Does anyone has some expertise, or knowledge that could help solve this. ?
Last edited by Munken (2012-06-19 16:44:39)
Offline
Have you installed pm-utils?
Offline
Have you installed pm-utils?
Yes.
[root@arch munken]# pacman -Qs pm-utils
local/pm-quirks 0.20100619-2
Quirks data for pm-utils
local/pm-utils 1.4.1-5
Utilities and scripts for suspend and hibernate power managementOffline
gnome-settings-daemon supply the following message when i kill it and run.
/usr/lib/gnome-settings-daemon/gnome-settings-daemon --debug.(gnome-settings-daemon:2544): power-plugin-DEBUG: lid is closed; not suspending
nor hibernating since some external monitor outputs are still active.
Last edited by Munken (2012-06-12 15:42:51)
Offline
Exact same problem for me:
(gnome-settings-daemon:1289): power-plugin-DEBUG: lid is closed; not suspending nor hibernating since some external monitor outputs are still activeIt worked before Gnome 3.4 and is probably related to the gnome-settings-daemon since reverting it to version 3.2 "fixes" the problem.
It is probably caused by this Feature: ( from release notes ):
Better handling of docking stations and external monitors, so that a laptop will now stay running (and not suspend) when it is connected to an external monitor, even if the lid is closed.UPDATE:
So. Probably with the last update of the nvidia driver the problem changed. Suspend on lid close is now "working" (as in: it suspends). But sadly the computer won't recover from suspention anymore. The computer starts running (ventilator noise) the screen is glowing but it keeps being black.
So for now it sound like a normal not recovering from suspension after update problem.
Last edited by Archdove (2012-06-18 19:53:57)
Offline
So. Probably with the last update of the nvidia driver the problem changed. Suspend on lid close is now "working" (as in: it suspends). But sadly the computer won't recover from suspention anymore. The computer starts running (ventilator noise) the screen is glowing but it keeps being black.
So for now it sound like a normal not recovering from suspension after update problem.
Exact same experience here.. The upgrade from nvidia 295.59-1 to 302.17-1 fixes my suspend problem. But my recovery is problematic as well. Sometimes it works and sometimes it just gives me a black screen.
Don't know but i found this in the changelog of nvidia 302.17 ( Source)
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.
As a small bonus the screen settings in gnome control panel is active now..
I think the problematic recovery, from suspend is another problem, i will mark this as solved.
Offline
So resuming from suspend sometimes works for you? It doesn't for me. I always have to force reboot.
Will you open a new Thread for the resume issue?
Offline
It is really messy and the screen is flickering a lot, but in the end it resumes more often than not.
Think i will wait a bit. Maybe the discussion in one of these threads present an answer to the problem.
Offline
Fixed for me with nvidia 304.32-1. Damn i'm happy.
Maybe the new suspend to both kernes feature will solve this for good.
Offline