You are not logged in.
Pages: 1
Topic closed
Hi,
To my understanding, systemd should suspend the laptop itself when I tell powerdevil (KDE 4.9.5) to ignore the lid switch. This is my logind.conf:
[ericd@vaiopro13 ~]$ 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
#Controllers=
#ResetControllers=cpu
#InhibitDelayMaxSec=5
#HandlePowerKey=poweroff
#HandleSuspendKey=suspend
#HandleHibernateKey=hibernate
#HandleLidSwitch=suspend
#PowerKeyIgnoreInhibited=no
#SuspendKeyIgnoreInhibited=no
#HibernateKeyIgnoreInhibited=no
#LidSwitchIgnoreInhibited=yes
#IdleAction=ignore
#IdleActionSec=30min
However, this is not the case. When I close the lid of the laptop, nothing happens except the screen switches off.
I'd like to hand over the suspend stuff to systemd, because I think suspending will go much faster and I hope I will get rid of the "double suspend" issue.
The systemd journal tells me:
feb 05 14:00:45 vaiopro13 systemd-logind[407]: Lid closed.
feb 05 14:00:56 vaiopro13 systemd-logind[407]: Lid opened.
What am I missing here?
EDIT: running
systemctl suspend
works fine, although on resume the screen is not locked, but I guess that is expected behaviour.
Last edited by LordChaos73 (2013-02-15 09:25:34)
Offline
... everything in logind.conf is commented out.
Offline
... everything in logind.conf is commented out.
Are those not just the default values?
Offline
Un-comment the one you'd like.
#InhibitDelayMaxSec=5
#HandlePowerKey=poweroff
#HandleSuspendKey=suspend
#HandleHibernateKey=hibernate
HandleLidSwitch=suspend
#PowerKeyIgnoreInhibited=no
#SuspendKeyIgnoreInhibited=no
#HibernateKeyIgnoreInhibited=no
#LidSwitchIgnoreInhibited=yes
#IdleAction=ignore
#IdleActionSec=30min
Also read https://wiki.archlinux.org/index.php/Sy … management
Last edited by doug piston (2013-02-05 16:19:24)
Offline
Uncommenting the following options:
HandleLidSwitch=suspend
LidSwitchIgnoreInhibited=yes
and restarting the logind service makes no difference at all.
[ericd@vaiopro13 ~]$ systemd-inhibit --list
WHAT WHO WHY MODE UID PID
handle-power-key:handle-suspend-key:handle-hibernate-key:handle-lid-switch PowerDevil KDE handles p...ents block 1000 6460
sleep root inhibited delay 0 389
2 inhibitors listed.
Maybe systemd isn't ignoring all inhibitors when the lid is closed although it is supposed to?
Offline
You're trying this with a fresh boot?
Offline
You're trying this with a fresh boot?
Yes, I've tried this after rebooting as well.
Offline
i think i've read that in kde 4.10 powerdevil has much better support to systemd.. maybe just wait few hours and see if the kde upgrade will do well.
cheers
Offline
i think i've read that in kde 4.10 powerdevil has much better support to systemd.. maybe just wait few hours and see if the kde upgrade will do well.
cheers
Do you think it will be in the stable repo's so soon?
Off topic, this seems like an annoying bug of which I hope they will fix soon:
https://bugs.kde.org/show_bug.cgi?id=314559
Last edited by LordChaos73 (2013-02-07 19:34:05)
Offline
I've upgraded KDE, problem still persists. Also, I now get the double suspend even when the laptop is connected to AC. This wasn't the case when I was running KDE 4.9.x.
Offline
Looks like the double suspend bug is fixed
Offline
Maybe systemd isn't ignoring all inhibitors when the lid is closed although it is supposed to?
If I understand it correctly, this will only ignore real inhibitors. The handle-... inhibitors are always working and stop systemd from responding. You'll have to use the app which requested the lock, in your case powerdevil.
| alias CUTF='LANG=en_XX.UTF-8@POSIX ' |
Online
LordChaos73 wrote:Maybe systemd isn't ignoring all inhibitors when the lid is closed although it is supposed to?
If I understand it correctly, this will only ignore real inhibitors. The handle-... inhibitors are always working and stop systemd from responding. You'll have to use the app which requested the lock, in your case powerdevil.
Thank you for clarifying!
Offline
How was this problem actually solved?
Offline
It's part of the Power Management settings.
Go to the setting 'Energy Saving'. There's a bullet point 'Button events handling' where you'll find 'When laptop lid closed'. The options include [Hibernate, Suspend, Do nothing] etc. Set it to Do nothing and apply.
See also: KDE Power Management https://docs.kde.org/stable5/en/kde-wor … index.html
Offline
Please look at the dates, the problem was originally solved already and it's quite likely that the OP has already noticed this. Don't necrobump 6 year old threads.
Closing.
Offline
Pages: 1
Topic closed