Your message dated Fri, 13 Dec 2013 21:01:44 +0100 with message-id <[email protected]> and subject line Re: [Pkg-systemd-maintainers] Bug#731887: systemd: Lid close on laptop doesn't suspend has caused the Debian Bug report #731887, regarding systemd: Lid close on laptop doesn't suspend 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.) -- 731887: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731887 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: systemd Version: 204-5 Severity: normal Dear Maintainer, * What exactly did you do (or not do) that was effective (or ineffective)? Closed laptop lid * What was the outcome of this action? Nothing * What outcome did you expect instead? Suspend. I see in dmesg: [ 675.056857] ACPI: \_SB_.PCI0: Bus check notify on _handle_hotplug_event_root [ 675.057065] systemd-logind[3255]: Lid closed. [ 675.057209] systemd-logind[3255]: Suspending... [ 675.057380] systemd-logind[3255]: Removed session 1. [ 675.135870] systemd-logind[3255]: New session c1 of user john. [ 676.658958] systemd-logind[3255]: Removed session c1. [ 680.066006] systemd-logind[3255]: Delay lock is active but inhibitor timeout is reached. [ 680.070792] systemd-logind[3255]: Failed to send delayed message: Launch helper exited with unknown return code 1 [ 914.776413] ACPI: \_SB_.PCI0: Bus check notify on _handle_hotplug_event_root [ 914.776644] systemd-logind[3255]: Lid opened. This is on a Sony Vaio Z2 -- Package-specific info: -------------- systemd-delta: -------------- 0 overridden configuration files found. -------------- Contents of /var/lib/systemd/deb-systemd-helper-enabled: -------------- ==> /var/lib/systemd/deb-systemd-helper-enabled/pcscd.service.dsh-also <== /etc/systemd/system/sockets.target.wants/pcscd.socket ==> /var/lib/systemd/deb-systemd-helper-enabled/accounts-daemon.service.dsh-also <== /etc/systemd/system/graphical.target.wants/accounts-daemon.service ==> /var/lib/systemd/deb-systemd-helper-enabled/avahi-daemon.service.dsh-also <== /etc/systemd/system/multi-user.target.wants/avahi-daemon.service /etc/systemd/system/sockets.target.wants/avahi-daemon.socket /etc/systemd/system/dbus-org.freedesktop.Avahi.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/avahi-daemon.service <== ==> /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 ==> /var/lib/systemd/deb-systemd-helper-enabled/pcscd.socket.dsh-also <== /etc/systemd/system/sockets.target.wants/pcscd.socket ==> /var/lib/systemd/deb-systemd-helper-enabled/avahi-daemon.socket.dsh-also <== /etc/systemd/system/sockets.target.wants/avahi-daemon.socket ==> /var/lib/systemd/deb-systemd-helper-enabled/sockets.target.wants/avahi-daemon.socket <== ==> /var/lib/systemd/deb-systemd-helper-enabled/sockets.target.wants/pcscd.socket <== ==> /var/lib/systemd/deb-systemd-helper-enabled/syslog.service <== ==> /var/lib/systemd/deb-systemd-helper-enabled/dbus-org.freedesktop.Avahi.service <== ==> /var/lib/systemd/deb-systemd-helper-enabled/graphical.target.wants/accounts-daemon.service <== -- 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.11-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages systemd depends on: ii initscripts 2.88dsf-43 ii libacl1 2.2.52-1 ii libaudit1 1:2.3.2-2 ii libc6 2.17-97 ii libcap2 1:2.22-1.2 ii libcryptsetup4 2:1.6.1-1 ii libdbus-1-3 1.6.18-2 ii libgcrypt11 1.5.3-2 ii libkmod2 9-3 ii liblzma5 5.1.1alpha+20120614-2 ii libpam0g 1.1.3-10 ii libselinux1 2.2.1-1 ii libsystemd-daemon0 204-5 ii libsystemd-journal0 204-5 ii libsystemd-login0 204-5 ii libudev1 204-5 ii libwrap0 7.6.q-24 ii udev 204-5 ii util-linux 2.20.1-5.5 Versions of packages systemd recommends: ii libpam-systemd 204-5 Versions of packages systemd suggests: pn systemd-ui <none> -- no debconf information
--- End Message ---
--- Begin Message ---Hi John, John Hughes <[email protected]> writes: > On 12/11/2013 10:49 AM, Michael Biebl wrote: >> Have you booted with systemd being your PID 1 or do you still use >> sysvinit? > > Ok, with init=/bin/systemd it seems to work reliably. So this works as intendend, AFAICT. Or at least it’s not a bug in the systemd package. Closing this report. If you feel that there’s a need to reopen, please reopen against a more appropriate package :). -- Best regards, Michael
--- End Message ---
