Bug 1218480 - logind.conf suspend setting ignored when using Gnome and Nvidia drivers
Summary: logind.conf suspend setting ignored when using Gnome and Nvidia drivers
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gdm
Version: 21
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-05-05 03:58 UTC by Jeff Pullen
Modified: 2015-12-02 19:55 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-12-02 19:55:39 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Jeff Pullen 2015-05-05 03:58:14 UTC
Description of problem:

When using the nvidia drivers and Gnome 3.14 the system will not suspend on lid close despite modifying /etc/systemd/logind.conf. Gnome believes that there are multiple displays attached. Systemd incorporates a way to force the suspend even with multiple displays (LidSwitchIgnoreInhibited=yes), but this does not work while using Gnome. 

Switching to the KDE desktop the system correctly suspends.
Initiating a suspend from the terminal  works find 'systemctl suspend'

Version-Release number of selected component (if applicable):

# rpm -qa | grep -e ^gdm -e nvidia -e intel
nvidia-driver-349.16-2.fc21.x86_64
nvidia-settings-349.16-1.fc21.x86_64
gdm-3.14.2-1.fc21.x86_64
nvidia-driver-libs-349.16-2.fc21.x86_64
xorg-x11-drv-intel-2.99.916-3.20141117.fc21.x86_64
nvidia-libXNVCtrl-349.16-1.fc21.x86_64
kmod-nvidia-3.19.5-200.fc21.x86_64-349.16-1.fc21.x86_64
akmod-nvidia-349.16-1.fc21.x86_64


How reproducible:
Install the Nvidia drivers, close the lid, reopen and see that it is still running.

Steps to Reproduce:
1. Install nvidia drivers 
2. run 'systemd-inhibit --list' and see the block for "Multiple displays attached"
3. Modify the following lines in /etc/systemd/logind.conf
HandleLidSwitch=suspend
HandleLidSwitchDocked=suspend
LidSwitchIgnoreInhibited=yes

4. Close lid and see that it did not suspend

Actual results:
System continues to run despite the fact that it registered a lid close event, the LidSwitchIgnoreInhibited=yes setting is not honored and the system continues to run.

The only way to get the system to suspend with the lid closed is the following workaround.
journalctl -f -n0  | awk '/Lid closed./ { system("systemctl suspend") }'

Expected results:
The system should suspend with a lid close as it does when using KDE without the workaround. 

Additional info:
# journalctl -r
-- Logs begin at Wed 2014-11-26 09:26:02 EST, end at Mon 2015-05-04 23:45:32 EDT. --
May 04 23:45:32 fedwks21 systemd-logind[818]: Lid opened.
May 04 23:45:29 fedwks21 systemd-logind[818]: Lid closed.



# xrandr
Screen 0: minimum 8 x 8, current 2880 x 1800, maximum 16384 x 16384
DP-0 disconnected (normal left inverted right x axis y axis)
DP-1 disconnected (normal left inverted right x axis y axis)
HDMI-0 disconnected (normal left inverted right x axis y axis)
DP-2 connected primary 2880x1800+0+0 (normal left inverted right x axis y axis) 331mm x 207mm
   2880x1800     59.99*+
DP-3 disconnected (normal left inverted right x axis y axis)
DP-4 disconnected (normal left inverted right x axis y axis)


# systemd-inhibit --list
     Who: jpullen (UID 1000/jpullen, PID 5253/gnome-settings-)
    What: handle-power-key:handle-suspend-key:handle-hibernate-key
     Why: GNOME handling keypresses
    Mode: block

     Who: jpullen (UID 1000/jpullen, PID 5253/gnome-settings-)
    What: handle-lid-switch
     Why: Multiple displays attached
    Mode: block

     Who: NetworkManager (UID 0/root, PID 955/NetworkManager)
    What: sleep
     Why: NetworkManager needs to turn off networks
    Mode: delay

     Who: Telepathy (UID 1000/jpullen, PID 5372/mission-control)
    What: shutdown:sleep
     Why: Disconnecting IM accounts before suspend/shutdown...
    Mode: delay

     Who: jpullen (UID 1000/jpullen, PID 5253/gnome-settings-)
    What: sleep
     Why: GNOME needs to lock the screen
    Mode: delay

     Who: GNOME Shell (UID 1000/jpullen, PID 5324/gnome-shell)
    What: sleep
     Why: GNOME needs to lock the screen
    Mode: delay

6 inhibitors listed.


# cat /etc/systemd/logind.conf 
#  This file is part of systemd.
#
#  systemd is free software; you can redistribute it and/or modify it
#  under the terms of the GNU Lesser General Public License as published by
#  the Free Software Foundation; either version 2.1 of the License, or
#  (at your option) any later version.
#
# See logind.conf(5) for details

[Login]
#NAutoVTs=6
#ReserveVT=6
#KillUserProcesses=no
#KillOnlyUsers=
#KillExcludeUsers=root
#InhibitDelayMaxSec=5
#HandlePowerKey=poweroff
#HandleSuspendKey=suspend
#HandleHibernateKey=hibernate
HandleLidSwitch=suspend
HandleLidSwitchDocked=suspend
#PowerKeyIgnoreInhibited=no
#SuspendKeyIgnoreInhibited=no
#HibernateKeyIgnoreInhibited=no
LidSwitchIgnoreInhibited=yes
#IdleAction=ignore
#IdleActionSec=30min
#RuntimeDirectorySize=10%
#RemoveIPC=yes


# lspci | grep -i vga
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)
01:00.0 VGA compatible controller: NVIDIA Corporation GK107M [GeForce GT 650M Mac Edition] (rev a1)

Comment 1 Fedora End Of Life 2015-11-04 12:10:16 UTC
This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '21'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 21 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 2 Jan Kurik 2015-12-02 19:55:42 UTC
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.