Your message dated Sat, 28 Jun 2014 03:09:05 +0200
with message-id <53ae15b1.10...@debian.org>
and subject line systemd: closing lid suddenly suspends the machine
has caused the Debian Bug report #747749,
regarding systemd: closing lid suddenly suspends the machine
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 ow...@bugs.debian.org
immediately.)


-- 
747749: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747749
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd
Version: 204-10
Severity: normal

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Dear Maintainer,

I switched from sysvinit to systemd and now, if I close the lid, my machine
suddenly suspends. For me this means, that the data of my current session is
lost, since there are some problems with suspend with my machine.

This is unspected behaviour, that at least I would not expect from just
changing the init system, since the init system should not have to do anything
with events like closing the lid.

I was able to restore the old behaviour (doing nothing) by editing the
HandleLidSwitch entry in /etc/systemd/logind.conf but I think, that should not
be necessary. I also have a keybinding, so that pressing the XF86Sleep key,
hibernates the machine to disk, but now it first suspends and after waking up
from the suspend, the machine is hibernated (to disk) since systemd also
silently takes over control over that key event. This is also not behaviour I
would expect from changing the init systemd.

Therefore, please consider changing the default to doing nothing when doing
this actions, so that others do not get this unexpected behaviour and
experience data loss like I did.


With best regards,
Julian Wollrath

- -- Package-specific info:

- -- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.15.0-rc5 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages systemd depends on:
ii  acl                  2.2.52-1
ii  adduser              3.113+nmu3
ii  initscripts          2.88dsf-53
ii  libacl1              2.2.52-1
ii  libaudit1            1:2.3.6-1
ii  libc6                2.18-5
ii  libcap2              1:2.22-1.2
ii  libcap2-bin          1:2.22-1.2
ii  libcryptsetup4       2:1.6.4-4
ii  libdbus-1-3          1.8.2-1
ii  libgcrypt11          1.5.3-4
ii  libkmod2             17-2
ii  liblzma5             5.1.1alpha+20120614-2
ii  libpam0g             1.1.8-3
ii  libselinux1          2.2.2-2
ii  libsystemd-daemon0   204-10
ii  libsystemd-journal0  204-10
ii  libsystemd-login0    204-10
ii  libudev1             204-10
ii  libwrap0             7.6.q-25
ii  sysv-rc              2.88dsf-53
ii  udev                 204-10
ii  util-linux           2.20.1-5.7

Versions of packages systemd recommends:
pn  libpam-systemd  <none>

Versions of packages systemd suggests:
pn  systemd-ui  <none>

- -- no debconf information

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBCAAGBQJTb4ZqAAoJEFl2dmpRMS8zW58H/j3M9KZn7MOcoA9re9M+v1LR
ivkmv7ElFGPWtxmKX+S9XyaVHhG/OLz1REqgwAZSaYvNT8vpEMkJ+RHirxbZS+ec
gi6d8wXqDdmgBicVjjylEerI2LddsiosiawvTarsyf5m+t1F212Cr/i7mM4l8Bge
+Lobh9aDRz1L4a2f6arAXIFqSOlFsJj2C2j8uBngzewaz1Zp4kn1nVuR7xsw+hQ/
NMnyJQmHyDCJndItLdPhVSRhgx/hDwRc3BQNDFesw+Pg8uRs7dPSzhA6aHXXVR/F
2E6++G2X57P0e85rGuLOfMA+bvnXlpDDLMtMvC7nuKIOCdfTWdyNDuXnFuA29J0=
=2P4/
-----END PGP SIGNATURE-----
[OVERRIDDEN] /etc/systemd/system/sockets.target.wants → 
/lib/systemd/system/sockets.target.wants

Only in /etc/systemd/system/sockets.target.wants: acpid.socket
Only in /etc/systemd/system/sockets.target.wants: cups.socket
Only in /lib/systemd/system/sockets.target.wants: dbus.socket
Only in /etc/systemd/system/sockets.target.wants: lvm2-lvmetad.socket
Only in /lib/systemd/system/sockets.target.wants: systemd-initctl.socket
Only in /lib/systemd/system/sockets.target.wants: systemd-journald.socket
Only in /lib/systemd/system/sockets.target.wants: systemd-shutdownd.socket
Only in /lib/systemd/system/sockets.target.wants: systemd-udevd-control.socket
Only in /lib/systemd/system/sockets.target.wants: systemd-udevd-kernel.socket

[OVERRIDDEN] /etc/systemd/system/multi-user.target.wants → 
/lib/systemd/system/multi-user.target.wants

Only in /etc/systemd/system/multi-user.target.wants: cups.path
Only in /lib/systemd/system/multi-user.target.wants: dbus.service
Only in /lib/systemd/system/multi-user.target.wants: getty.target
Only in /etc/systemd/system/multi-user.target.wants: remote-fs.target
Only in /etc/systemd/system/multi-user.target.wants: rsyslog.service
Only in /etc/systemd/system/multi-user.target.wants: ssh.service
Only in /lib/systemd/system/multi-user.target.wants: 
systemd-ask-password-wall.path
Only in /lib/systemd/system/multi-user.target.wants: systemd-logind.service
Only in /lib/systemd/system/multi-user.target.wants: 
systemd-user-sessions.service

[OVERRIDDEN] /etc/systemd/system/local-fs.target.wants → 
/lib/systemd/system/local-fs.target.wants

Only in /etc/systemd/system/local-fs.target.wants: lvm2-activation-early.service
Only in /etc/systemd/system/local-fs.target.wants: lvm2-activation.service
Only in /lib/systemd/system/local-fs.target.wants: run-lock.mount
Only in /lib/systemd/system/local-fs.target.wants: run-user.mount
Only in /lib/systemd/system/local-fs.target.wants: systemd-fsck-root.service
Only in /lib/systemd/system/local-fs.target.wants: systemd-remount-fs.service


3 overridden configuration files found.
==> /var/lib/systemd/deb-systemd-helper-enabled/rsyslog.service.dsh-also <==
/etc/systemd/system/multi-user.target.wants/rsyslog.service
/etc/systemd/system/syslog.service
/etc/systemd/system/multi-user.target.wants/rsyslog.service
/etc/systemd/system/syslog.service
/etc/systemd/system/multi-user.target.wants/rsyslog.service
/etc/systemd/system/syslog.service

==> 
/var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/rsyslog.service
 <==

==> 
/var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/ssh.service 
<==

==> 
/var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/cups.path 
<==

==> /var/lib/systemd/deb-systemd-helper-enabled/syslog.service <==

==> 
/var/lib/systemd/deb-systemd-helper-enabled/lvm2-activation.service.dsh-also <==
/etc/systemd/system/local-fs.target.wants/lvm2-activation.service

==> 
/var/lib/systemd/deb-systemd-helper-enabled/local-fs.target.wants/lvm2-activation.service
 <==

==> 
/var/lib/systemd/deb-systemd-helper-enabled/local-fs.target.wants/lvm2-activation-early.service
 <==

==> 
/var/lib/systemd/deb-systemd-helper-enabled/lvm2-activation-early.service.dsh-also
 <==
/etc/systemd/system/local-fs.target.wants/lvm2-activation-early.service

==> /var/lib/systemd/deb-systemd-helper-enabled/ssh.socket.dsh-also <==
/etc/systemd/system/sockets.target.wants/ssh.socket

==> /var/lib/systemd/deb-systemd-helper-enabled/ssh.service.dsh-also <==
/etc/systemd/system/multi-user.target.wants/ssh.service
/etc/systemd/system/sshd.service

==> /var/lib/systemd/deb-systemd-helper-enabled/lvm2-lvmetad.socket.dsh-also <==
/etc/systemd/system/sockets.target.wants/lvm2-lvmetad.socket

==> 
/var/lib/systemd/deb-systemd-helper-enabled/sockets.target.wants/lvm2-lvmetad.socket
 <==

==> 
/var/lib/systemd/deb-systemd-helper-enabled/sockets.target.wants/cups.socket <==

==> /var/lib/systemd/deb-systemd-helper-enabled/cups.service.dsh-also <==
/etc/systemd/system/sockets.target.wants/cups.socket
/etc/systemd/system/multi-user.target.wants/cups.path
/etc/systemd/system/printer.target.wants/cups.service

==> 
/var/lib/systemd/deb-systemd-helper-enabled/printer.target.wants/cups.service 
<==

==> /var/lib/systemd/deb-systemd-helper-enabled/cups.path.dsh-also <==
/etc/systemd/system/multi-user.target.wants/cups.path

==> /var/lib/systemd/deb-systemd-helper-enabled/cups.socket.dsh-also <==
/etc/systemd/system/sockets.target.wants/cups.socket

==> /var/lib/systemd/deb-systemd-helper-enabled/bluetooth.service.dsh-also <==
/etc/systemd/system/bluetooth.target.wants/bluetooth.service
/etc/systemd/system/dbus-org.bluez.service

==> 
/var/lib/systemd/deb-systemd-helper-enabled/bluetooth.target.wants/bluetooth.service
 <==

==> /var/lib/systemd/deb-systemd-helper-enabled/dbus-org.bluez.service <==

==> /var/lib/systemd/deb-systemd-helper-enabled/sshd.service <==

--- End Message ---
--- Begin Message ---
Closing this bug report.

acpi-support has been fixed to deal with logind being active [1] and
handling suspend and not doing anything in that case.

Michael

[1] http://packages.qa.debian.org/a/acpi-support/news/20140619T213404Z.html
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---
_______________________________________________
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Reply via email to