FS#32281 - [systemd] overly aggresive logind

Attached to Project: Arch Linux
Opened by Ryan West (rdub53) - Monday, 29 October 2012, 16:16 GMT
Last edited by Dave Reisner (falconindy) - Thursday, 01 November 2012, 01:06 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Dave Reisner (falconindy)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: systemd overrides all user/DE settings, and will suspend even when you explicitly instruct it not to.


Additional info:
* package version(s): any version of
systemd, systemd-logind
* config and/or log files etc.
/etc/systemd/login.conf


Steps to reproduce:
1. Install Arch freshly
2. Install a DE
3. Change settings on Hibernate/Suspend/Power Off
4. Close laptop lid

Not sure how one goes about fixing something like this. Maybe changing the default behavior systemd comes with? I note this problem did not occur on a Fedora 17 install with systemd, nor rawhide. It's been isolated to Arch, as far as I can tell.

Additional information:
Hardware: eMachines e525 notebook
2GB RAM
Intel Celeron 900
Intel on-board Video
Intel on-board Audio
This task depends upon

Closed by  Dave Reisner (falconindy)
Thursday, 01 November 2012, 01:06 GMT
Reason for closing:  Not a bug
Additional comments about closing:  Fix your config. logind's defaults are defaults -- not mandated behavior.
Comment by Jan de Groot (JGC) - Monday, 29 October 2012, 16:40 GMT
AFAIK desktops need to inhibit suspend when they take over control from logind. GNOME 3.6 seems to do this, GNOME 3.4 doesn't. Guess some other desktops without native logind integration don't inhibit suspend either.
Comment by Greg (dolby) - Monday, 29 October 2012, 16:46 GMT
I would like to add that the fact doesnt happen elsewhere doesnt mean its exclusive to Arch as none of the other distributions package all systemd versions. And systemd is still changing rapidly.
Comment by Ryan West (rdub53) - Monday, 29 October 2012, 20:50 GMT
Alright, while those are given, forgive my ignorance, but wouldn't that affect a lot of people with laptops? Perhaps they don't want it to do perform that action on lid close, like say, hibernate or the like as opposed to sleep every time? This seems like a simple fix to me, perhaps it isn't. While able to use Arch, I know only a slight bit about the actual building of, say, a DE or like program/group of progs for Linux. I've only ever messed with Android before, and while similar in some ways, the majority are differences.
Comment by Hong Shick Pak (hspasta) - Monday, 29 October 2012, 21:17 GMT
Can you not edit the /etc/systemd/logind.conf file and edit the entries to ignore the actions?
Comment by Ryan West (rdub53) - Tuesday, 30 October 2012, 03:45 GMT
And I guess my next question is: why is GNOME 3.6 not the current pushed version?
Comment by Dave Reisner (falconindy) - Wednesday, 31 October 2012, 21:19 GMT
Gnome 3.6 IS the current version in extra. If you don't want systemd suspending on laptop lid close, then fix logind.conf. Nothing to see here.

Loading...