Your message dated Tue, 28 Mar 2017 06:30:34 +0200
with message-id <[email protected]>
and subject line Re: Bug#858843: systemd: Default value of
LidSwitchIgnoreInhibited should be no
has caused the Debian Bug report #858843,
regarding systemd: Default value of LidSwitchIgnoreInhibited should be no
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
858843: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858843
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: systemd
Version: 232-19
Severity: minor
Dear Maintainer,
What's the problem?
systemd and xfce4-power-manager compete to handle event "lid closed", this
yields confusing behavior and error messages.
What's the solution?
ignore inhibited messages, as done for other events, the default value of
LidSwitchIgnoreInhibited should be "no"
-- Package-specific info:
-- System Information:
Debian Release: 9.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
Versions of packages systemd depends on:
ii adduser 3.115
ii libacl1 2.2.52-3+b1
ii libapparmor1 2.11.0-2
ii libaudit1 1:2.6.7-1
ii libblkid1 2.29.1-1
ii libc6 2.24-9
ii libcap2 1:2.25-1
ii libcryptsetup4 2:1.7.3-3
ii libgcrypt20 1.7.6-1
ii libgpg-error0 1.26-2
ii libidn11 1.33-1
ii libip4tc0 1.6.0+snapshot20161117-5
ii libkmod2 23-2
ii liblz4-1 0.0~r131-2+b1
ii liblzma5 5.2.2-1.2+b1
ii libmount1 2.29.1-1
ii libpam0g 1.1.8-3.5
ii libseccomp2 2.3.1-2.1
ii libselinux1 2.6-3+b1
ii libsystemd0 232-19
ii mount 2.29.1-1
ii util-linux 2.29.1-1
Versions of packages systemd recommends:
ii dbus 1.10.16-1
ii libpam-systemd 232-19
Versions of packages systemd suggests:
ii policykit-1 0.105-17
pn systemd-container <none>
pn systemd-ui <none>
Versions of packages systemd is related to:
pn dracut <none>
ii initramfs-tools 0.127
ii udev 232-19
-- Configuration Files:
/etc/systemd/logind.conf changed [not included]
-- no debconf information
--- End Message ---
--- Begin Message ---
Am 27.03.2017 um 23:37 schrieb Michael Biebl:
> Am 27.03.2017 um 21:27 schrieb Martin Monperrus:
>>> How exactly do they compete for the "lid closed" event?
>>
>> Both try to perform an action. If they are the same, say suspend, you just
>> have a warning. If they
>> are different, you don't really understand what and why one or the other
>> happens.
>>
>>> I was under the impression, that XFCE nowadays uses logind, does it not?
>>
>> Yes, but systemd does not honor by default the inhibition request for lid
>> events sent by XFCE.
>
>
> What's the output of systemd-inhibit
If you read the logind.conf man page carefully, you'll see that logind
does respect low-level block requests. So if xfce4-power-manager takes a
blocking lock on handle-lid-switch it can implement it's own policy.
I just tested in a VM and xfce4-power-manager does take a proper
inhibitor lock:
$ systemd-inhibit
Who: NetworkManager (UID 0/root, PID 586/NetworkManager)
What: sleep
Why: NetworkManager needs to turn off networks
Mode: delay
Who: xfce4-power-manager (UID 1001/test, PID 2138/xfce4-power-man)
What:
handle-power-key:handle-suspend-key:handle-hibernate-key:handle-lid-switch
Why: xfce4-power-manager handles these events
Mode: block
Who: ModemManager (UID 0/root, PID 561/ModemManager)
What: sleep
Why: ModemManager needs to reset devices
Mode: delay
3 inhibitors listed.
I've used xfce4-power-manager-settings to instruct it to do nothing on
lid-close. Closing the lid, nothing happened. So everything is working
as expected. For xfce4-power-manager to successfully take an inhibitor
lock, it needs to run in an active, local session. You can check that via
$ loginctl show-session $XDG_SESSION_ID
Id=5
User=1001
Name=test
Timestamp=Tue 2017-03-28 06:00:00 CEST
TimestampMonotonic=33951653
VTNr=7
Seat=seat0
Display=:0
Remote=no
Active=yes
State=active
Both logind and xfce4-power-manager work as expected. If you still have
something else reacting to power events, I would check if you have
something like acpid running which might interfere. This is no longer a
logind bug though, so closing this report.
Regards,
Michael
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
--- End Message ---
_______________________________________________
Pkg-systemd-maintainers mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
