Closing Laptop Lid does not suspend in Gnome

smchadwell · 2014-07-26 02:58:05

Anyone else still having problems with this? I'm on a fresh install, here, and none of the solutions is working.

In fact, the gnome power manager seems not to be little regarding the screen -- it dims but never blanks (unless I close the lid . . . but then blanking is all it does).

No external monitor or dock is involved, and I've changed the gsettings as suggested. No proprietary drivers or anything, either. This is on a pretty straightforward Thinkpad X230.

Last edited by smchadwell (2014-07-26 04:07:12)

Sara · 2014-08-05 05:39:52

Yeah, I'm having the issue on a Fujitsu T904 myself, all Intel drivers. Suspend on lid close originally didn't work, then it worked again, and after my last update I'm back to it not working... dismal state of affairs. If I'd upgraded more frequently I could cite the exact systemd version numbers, alas. Currently running the latest version, 215-4.

My logs clearly show the lid close/open is being registered:

systemd-logind[4482]: Lid closed.
systemd-logind[4482]: Lid opened.

And I have these lines uncommented in my logind.conf:

HandlePowerKey=poweroff
HandleLidSwitch=suspend

The power button works as it should, only the lid still doesn't respond. Tried uncommenting the LidSwitchIgnoreInhibited=yes, but to no avail.

Running a pretty simple setup in dwm, so gnome isn't the issue for me. (Was running gnome before though, and it didn't work there either, but it had worked for awhile before some recent update...)

Also, my xrandr, just in case:

Screen 0: minimum 8 x 8, current 2560 x 1440, maximum 32767 x 32767
eDP1 connected 2560x1440+0+0 (normal left inverted right x axis y axis) 294mm x 165mm
   2560x1440     59.97*+  47.92    40.00  
   1920x1440     60.00  
   1856x1392     60.01  
   1792x1344     60.01  
   1600x1200     60.00  
   1400x1050     59.98  
   1280x1024     60.02  
   1280x960      60.00  
   1024x768      60.00  
   800x600       60.32    56.25  
   640x480       59.94  
HDMI1 disconnected (normal left inverted right x axis y axis)
DP1 disconnected (normal left inverted right x axis y axis)
HDMI2 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)

Hope this helps!

Edit: Appears to now be working after all:

systemd-logind[260]: Lid closed.
systemd-logind[260]: Suspending...
systemd-logind[260]: Lid opened.

Maybe another update fixed it?

Last edited by Sara (2014-08-08 01:05:19)

msx · 2014-08-18 03:16:26

Bump!

Journal is detecting the lid closing and opening but the system never suspends (power button works as expected though).
Will keep researching and if found anything useful post it back.

EDIT
After some research and thanks to the help of @moymoy, @grawity and @sztanpet at #systemd on Freenode I found what's happening here, my laptop has a hybrid video system and the DRM is incorrectly showing up that both GPUs are turned on when in fact the discrete one (ATi in my case) is turned off:

# for f in /sys/class/drm/*/status; do echo $f = $(< $f); done
/sys/class/drm/card0-LVDS-1/status = connected
/sys/class/drm/card0-VGA-1/status = disconnected
/sys/class/drm/card1-HDMI-A-1/status = disconnected
/sys/class/drm/card1-LVDS-2/status = connected
/sys/class/drm/card1-VGA-2/status = disconnected

# cat /sys/kernel/debug/vgaswitcheroo/switch
0:IGD:+:Pwr:0000:00:02.0
1:DIS-Audio: :Off:0000:01:00.1
2:DIS: :DynOff:0000:01:00.0

OTOH systemd won't allow the system to suspend as it believes an external screen is connected to the laptop[0]:

~> systemctl status systemd-logind.service
...
systemd-logind[2213]: Lid closed.
systemd-logind[2213]: Ignoring lid switch request, 2 displays connected.
systemd-logind[2213]: Ignoring lid switch request, 2 displays connected.
systemd-logind[2213]: Lid opened. 
...

[0] As suggested by @moymoy it would be nice though that systemd let the user override this control.

To check what's happening in your case follow these steps:
1. # cp /usr/lib/systemd/system/systemd-logind.service /etc/systemd/system ;so you can safely play with the service without touching a system file;
2. Temporarily enable detailed debug by adding Environment=SYSTEMD_LOG_LEVEL=debug in the newly created file /etc/systemd/system/systemd-logind.service inside de [Service] section;
3. # systemctl daemon-reload (in order to reload systemd's configuration);
4. Log out and in again, alternatively you can try running # systemctl restart systemd-logind.service;
5. Once you're logged again try closing your laptop's lid and then opening it again and check what the heck is impeding your system from suspend: $ systemctl status systemd-logind.service

I will let the Radeon and Intel teams now about this issue and post any worthy information back.

Last edited by msx (2014-12-12 04:45:45)

nwallace · 2014-08-30 14:16:19

msx wrote:

After some research and thanks to the help of @moymoy, @grawity and @sztanpet at #systemd on Freenode I found what's happening here, my laptop has a hybrid video system and the DRM is incorrectly showing that both GPUs are turned on when in fact the discrete one (ATi in my case) is turned off...

Thanks for the post. This seems to be my issue as well - both my integrated (i915) and discrete graphics (Radeon) cards are connected and powered on all the time. So it seems my battery life issue and my lid-close suspend issue are related.

bobbaluba · 2014-12-11 23:57:40

To fix the issue with nvidia blob driver and the missing DRM interfaces in /sys, add

HandleLidSwitchDocked=suspend

to your /etc/systemd/logind.conf

Last edited by bobbaluba (2014-12-11 23:58:03)

msx · 2014-12-13 12:27:21

bobbaluba wrote:

To fix the issue with nvidia blob driver and the missing DRM interfaces in /sys, add
HandleLidSwitchDocked=suspend
to your /etc/systemd/logind.conf

Awww... finally!
Thanks

@nwallace: is your Radeon still turned on at boot? Mine is automatically disable - thus I can enable it at will. Also you might want to check PowerTop, a useful tool for diagnosing the power-hungry devices on your hardware.

Last edited by msx (2014-12-13 12:30:23)

d3Xt3r · 2015-01-11 21:33:57

Just chipping in as this might be helpful to someone. Suspend on lid broke for me since systemd 217. I was hoping that updating to 218 would fix it but it didn't. Also, none of the solutions posted above worked for me. journalctl didn't even detect the laptop lid event, and I couldn't even watch /proc/acpi/button/lid/LID0/state because I kept getting permission denied errors (even as root).

What did help though, was changing the following values in logind.conf:

HandleSuspendKey=suspend
HandleLidSwitch=suspend
LidSwitchIgnoreInhibited=yes

What is weird that these values contradict kyr0's, but that's what did the trick for me.
Restarted systemd-logind and it all went well. journalctl is now logging the lid events too.

My configuration, for reference:

- Dell XPS 13 (Haswell CPU)
- No external monitor
- Intel graphics / Mesa 10.4.1
- No acpid or Laptop Mode Tools installed
- DE: Gnome 3 -> Note: Gnome 3 still doesn't have an option for the laptop lid.

Last edited by d3Xt3r (2015-01-11 21:38:04)

Danixu86 · 2015-12-25 20:44:17

Thanks to all. It helped me to get the solution.

I had the same problem, the lid close is detected but the system won't suspend. Was working fine on Manjaro KDE and started to fail on Manjaro Gnome.
For me the solution was simple, comment the line:

HandleLidSwitch=ignore

on /etc/systemd/logind.conf and restart.

Is strange because in gnome-tweak-tools i've the "Don't suspend on lid close" option disabled, and now still disabled.

Last edited by Danixu86 (2015-12-25 20:46:33)

luso58 · 2016-01-11 20:47:10

Don't know if you still need help, but I think I know the solution.

It seems that all of you have either

#LidSwitchIgnoreInhibited=???

or

LidSwitchIgnoreInhibited=yes

And neither will work because by yes it means for systemd to ignore the event and and the default of this option is yes. You have to set it to no if you want it to respect the

HandleLidSwitch=?????

For me it works with any argument for the handler (after reboot).

PS: The lid ignore option is the only ignore option that has yes as default. All other ignore options have no as default and that's why they are commented and yet the events trigger some actions. And BTW all this info is in "man logind.conf".

Arch Linux

#26 2014-07-26 02:58:05

Re: Closing Laptop Lid does not suspend in Gnome

#27 2014-08-05 05:39:52

Re: Closing Laptop Lid does not suspend in Gnome

#28 2014-08-18 03:16:26

Re: Closing Laptop Lid does not suspend in Gnome

#29 2014-08-30 14:16:19

Re: Closing Laptop Lid does not suspend in Gnome

#30 2014-12-11 23:57:40

Re: Closing Laptop Lid does not suspend in Gnome

#31 2014-12-13 12:27:21

Re: Closing Laptop Lid does not suspend in Gnome

#32 2015-01-11 21:33:57

Re: Closing Laptop Lid does not suspend in Gnome

#33 2015-12-25 20:44:17

Re: Closing Laptop Lid does not suspend in Gnome

#34 2016-01-11 20:47:10

Re: Closing Laptop Lid does not suspend in Gnome

Board footer