Processed: severity of 783509 is important
Processing commands for cont...@bugs.debian.org: > severity 783509 important Bug #783509 [systemd] tmp.mount activated accidentally via bind mount Severity set to 'important' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 783509: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783509 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Processed: tagging 783509
Processing commands for cont...@bugs.debian.org: > tags 783509 + pending Bug #783509 [systemd] tmp.mount activated accidentally via bind mount Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 783509: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783509 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Processing of systemd_220-6_amd64.changes
systemd_220-6_amd64.changes uploaded successfully to localhost along with the files: systemd_220-6.dsc systemd_220-6.debian.tar.xz libnss-myhostname_220-6_amd64.deb libnss-mymachines_220-6_amd64.deb libpam-systemd_220-6_amd64.deb libsystemd-daemon-dev_220-6_amd64.deb libsystemd-dev_220-6_amd64.deb libsystemd-id128-dev_220-6_amd64.deb libsystemd-journal-dev_220-6_amd64.deb libsystemd-login-dev_220-6_amd64.deb libsystemd0_220-6_amd64.deb libudev-dev_220-6_amd64.deb libudev1-udeb_220-6_amd64.udeb libudev1_220-6_amd64.deb python3-systemd_220-6_amd64.deb systemd-dbg_220-6_amd64.deb systemd-sysv_220-6_amd64.deb systemd_220-6_amd64.deb udev-udeb_220-6_amd64.udeb udev_220-6_amd64.deb Greetings, Your Debian queue daemon (running on host franck.debian.org) ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#788400: systemd-logind only fires suspend on lid close once even though it sees the event
Control: tags -1 moreinfo Am 11.06.2015 um 02:13 schrieb jessie: > And the output of the systemd-logind.service, as you can see it fires > `suspend` on the first lid close but never on any after the very first lid > close, it is very odd, it clearly sees the event: > > ``` > -- Logs begin at Wed 2015-06-10 16:49:40 PDT, end at Wed 2015-06-10 17:05:35 > PDT. -- > Jun 10 16:49:41 debian systemd[1]: Starting Login Service... > Jun 10 16:49:41 debian systemd-logind[559]: New seat seat0. > Jun 10 16:49:41 debian systemd-logind[559]: Watching system buttons on > /dev/input/event4 (Power But > Jun 10 16:49:41 debian systemd-logind[559]: Watching system buttons on > /dev/input/event9 (Video Bus > Jun 10 16:49:41 debian systemd[1]: Started Login Service. > Jun 10 16:49:41 debian systemd-logind[559]: Watching system buttons on > /dev/input/event2 (Power But > Jun 10 16:49:41 debian systemd-logind[559]: Watching system buttons on > /dev/input/event1 (Lid Switc > Jun 10 16:49:41 debian systemd-logind[559]: Watching system buttons on > /dev/input/event3 (Sleep But > Jun 10 16:49:47 debian systemd-logind[559]: New session 1 of user jessie. > Jun 10 16:52:18 debian systemd-logind[559]: Lid closed. > Jun 10 16:52:18 debian systemd-logind[559]: Suspending... > Jun 10 16:52:31 debian systemd-logind[559]: Lid opened. > Jun 10 16:52:31 debian systemd-logind[559]: Operation finished. > Jun 10 16:54:44 debian systemd-logind[559]: Lid closed. > Jun 10 16:54:57 debian systemd-logind[559]: Lid opened. > Jun 10 16:56:48 debian systemd-logind[559]: Lid closed. > Jun 10 16:56:51 debian systemd-logind[559]: Lid opened. > Jun 10 16:56:57 debian systemd-logind[559]: Lid closed. > Jun 10 16:57:06 debian systemd-logind[559]: Lid opened. > Jun 10 16:58:33 debian systemd-logind[559]: Lid closed. > Jun 10 16:58:39 debian systemd-logind[559]: Lid opened. What's the output of systemd-inhibit? Maybe some application is block the suspend request. -- 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 ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Processed: Re: Bug#788400: systemd-logind only fires suspend on lid close once even though it sees the event
Processing control commands: > tags -1 moreinfo Bug #788400 [systemd] systemd-logind only fires suspend on lid close once even though it sees the event Added tag(s) moreinfo. -- 788400: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788400 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
systemd_220-6_amd64.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 11 Jun 2015 09:25:49 +0200 Source: systemd Binary: systemd systemd-sysv libpam-systemd libnss-myhostname libnss-mymachines libsystemd0 libsystemd-dev libsystemd-login-dev libsystemd-daemon-dev libsystemd-journal-dev libsystemd-id128-dev udev libudev1 libudev-dev udev-udeb libudev1-udeb python3-systemd systemd-dbg Architecture: source amd64 Version: 220-6 Distribution: unstable Urgency: medium Maintainer: Debian systemd Maintainers Changed-By: Martin Pitt Description: libnss-myhostname - nss module providing fallback resolution for the current hostname libnss-mymachines - nss module to resolve hostnames for local container instances libpam-systemd - system and service manager - PAM module libsystemd-daemon-dev - systemd utility library (transitional package) libsystemd-dev - systemd utility library - development files libsystemd-id128-dev - systemd 128 bit ID utility library (transitional package) libsystemd-journal-dev - systemd journal utility library (transitional package) libsystemd-login-dev - systemd login utility library (transitional package) libsystemd0 - systemd utility library libudev-dev - libudev development files libudev1 - libudev shared library libudev1-udeb - libudev shared library (udeb) python3-systemd - Python 3 bindings for systemd systemd- system and service manager systemd-dbg - system and service manager (debug symbols) systemd-sysv - system and service manager - SysV links udev - /dev/ and hotplug management daemon udev-udeb - /dev/ and hotplug management daemon (udeb) Closes: 760299 783509 787542 Changes: systemd (220-6) unstable; urgency=medium . * Enable seccomp support on the architectures that provide libseccomp. (Closes: #760299) * boot-and-services autopkgtest: Add SeccompTest for the above. * boot-and-services autopkgtest: Check that we don't get an unwanted tmp.mount unless /etc/fstab explicitly specifies it. * Bump libcap-dev build dep to the version that provides libcap2-udeb. (Closes: #787542) * Stop installing tmp.mount by default; there are still situations where it becomes active through dependencies from other units, which is surprising, hides existing data in /tmp during runtime, and it isn't safe to have a tmpfs /tmp on every install scenario. (Closes: #783509) - d/rules: Ship tmp.mount in /usr/share/systemd/ instead of /lib/systemd/systemd. - systemd.postinst: When tmp.mount already was enabled, install tmp.mount into /etc and keep it enabled. - systemd.postinst: When enabling tmp.mount because of RAMTMP=yes, copy it from /usr/share. - Drop Don-t-mount-tmp-as-tmpfs-by-default.patch and PrivateTmp-shouldn-t-require-tmpfs.patch, not necessary any more. Checksums-Sha1: 8ec778b1fc6cb90a0e237fbee7779eb0f6b35ae8 3742 systemd_220-6.dsc fa675727097b055fc20984bcf476902ed7f172df 158632 systemd_220-6.debian.tar.xz 88c7dcbff4d1c5e1f24afa3705526b464eb79b81 63066 libnss-myhostname_220-6_amd64.deb 273ff844bdd358db6279e1e1b01c4ba37ac2518b 143238 libnss-mymachines_220-6_amd64.deb 61cc1862b8135a23a4cb80a8e50d24581aa6dc70 147328 libpam-systemd_220-6_amd64.deb 71c64234bdbc0832c2ddc3559f54ae89fe97be47 42344 libsystemd-daemon-dev_220-6_amd64.deb b2287566bd921c7d5c46862bff52d05cacf9a114 108658 libsystemd-dev_220-6_amd64.deb 9f213cca02e9de73e59a347f19d33f6f5858259b 42320 libsystemd-id128-dev_220-6_amd64.deb c9fa5cbbc73fe0f27681f003e058cad14a65deb4 42324 libsystemd-journal-dev_220-6_amd64.deb 291e898d521cb94aea4e99ac7ca8a366b64d6fcd 42338 libsystemd-login-dev_220-6_amd64.deb 7d3ac5cf80d243592f1e3e223b15832bbb9060a3 108476 libsystemd0_220-6_amd64.deb f9bcb2511ed9cdf88d672a7591072041073de791 22996 libudev-dev_220-6_amd64.deb 7ffa5c81789a0d9b0dbd77290a9856e228464a86 46086 libudev1-udeb_220-6_amd64.udeb a218322dc3fb4c66cb53b3b3cb88143d2b6ab725 90456 libudev1_220-6_amd64.deb 29b18418d9ab3937115139b32112df6b78c2a343 74732 python3-systemd_220-6_amd64.deb 7f7d92e2ddbc1193a224e14e53eae8cf924e1c84 23656160 systemd-dbg_220-6_amd64.deb 8323f30c45a3a23ac9f73b2e8dc02fd18cc5c4dd 46946 systemd-sysv_220-6_amd64.deb 7c1c492f5e4d095485d2c49c98f2146f13e2153c 3552944 systemd_220-6_amd64.deb 7bd1dba8195270dbbe3a0018afbc2a20d6aa6841 248832 udev-udeb_220-6_amd64.udeb 7b799d6d8f53842727d0976e2d918a410e59c24e 982444 udev_220-6_amd64.deb Checksums-Sha256: a36967838bfbea0baf1f893f55e6124288f65facf53b989cd4f89779b84fd573 3742 systemd_220-6.dsc faf72111c8282432893bb6799231b58ee0b1cfb868d749a75171b05458d318af 158632 systemd_220-6.debian.tar.xz ffbdae53c8a882f7e4c65d8ec39c7a9df3ba6eaa4fcd5f76d33090e48a078275 63066 libnss-myhostname_220-6_amd64.deb 341702594eb483479c68534fb7a551fb0e53f288132999c6ce6e1aa27b3de4fc 143238 libnss-mymachines_220-6_amd64.deb c4f3b055e4ac1ed7bf231ea36dbeaf3ba67b3a4b2d4aee750ad0304dea872b74 147328 libpam-systemd_220-6_amd64.deb f4ed2052181d8a7
Bug#783509: marked as done (tmp.mount activated accidentally via bind mount)
Your message dated Thu, 11 Jun 2015 10:25:59 + with message-id and subject line Bug#783509: fixed in systemd 220-6 has caused the Debian Bug report #783509, regarding tmp.mount activated accidentally via bind mount 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.) -- 783509: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783509 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: systemd Version: 215-17 Severity: normal Hello, I am not sure for how long but I guess less than two months (jessie), systemd has started purging my /tmp on every reboot, although I have these settings: /etc/default/rcS: TMPTIME=2 which seems to have been migrated to /etc/tmpfiles.d/tmp.conf (attached, I have made a manual change from 5d to 2d iirc). I am a litle bit at loss what goes wrong here, any idea on how to debug this? thanks cu Andreas -- Package-specific info: -- System Information: Debian Release: 8.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable'), (1, 'experimental') Architecture: i386 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages systemd depends on: ii acl 2.2.52-2 ii adduser 3.113+nmu3 ii initscripts 2.88dsf-59 ii libacl1 2.2.52-2 ii libaudit1 1:2.4-1+b1 ii libblkid1 2.25.2-6 ii libc6 2.19-18 ii libcap2 1:2.24-8 ii libcap2-bin 1:2.24-8 ii libcryptsetup4 2:1.6.6-5 ii libgcrypt20 1.6.3-2 ii libkmod218-3 ii liblzma55.1.1alpha+20120614-2+b3 ii libpam0g1.1.8-3.1 ii libselinux1 2.3-2 ii libsystemd0 215-17 ii mount 2.25.2-6 ii sysv-rc 2.88dsf-59 ii udev215-17 ii util-linux 2.25.2-6 Versions of packages systemd recommends: ii dbus1.8.16-1 pn libpam-systemd Versions of packages systemd suggests: pn systemd-ui -- no debconf information -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure' # 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 tmpfiles.d(5) for details # Clear tmp directories separately, to make them easier to override d /tmp 1777 root root 2d #d /var/tmp 1777 root root 30d # Exclude namespace mountpoints created with PrivateTmp=yes x /tmp/systemd-private-* x /var/tmp/systemd-private-* X /tmp/systemd-private-*/tmp X /var/tmp/systemd-private-*/tmp --- End Message --- --- Begin Message --- Source: systemd Source-Version: 220-6 We believe that the bug you reported is fixed in the latest version of systemd, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 783...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Martin Pitt (supplier of updated systemd package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 11 Jun 2015 09:25:49 +0200 Source: systemd Binary: systemd systemd-sysv libpam-systemd libnss-myhostname libnss-mymachines libsystemd0 libsystemd-dev libsystemd-login-dev libsystemd-daemon-dev libsystemd-journal-dev libsystemd-id128-dev udev libudev1 libudev-dev udev-udeb libudev1-udeb python3-systemd systemd-dbg Architecture: source amd64 Version: 220-6 Distribution: unstable Urgency: medium Maintainer: Debian systemd Maintainers Changed-By: Martin Pitt Description: libnss-myhostname - nss module providing fallback resolution for the current hostname libnss-mymachines - nss module to resolve hostnames for local container instances libpam-systemd - system and service manager - PAM module libsystemd-daemon-dev - systemd utility library (transitional package) libsystemd-dev - systemd utility library - development files libsystemd-id128-dev - systemd 128 bit ID utility li
Bug#787542: marked as done (libudev1-udeb depends on missing libcap2)
Your message dated Thu, 11 Jun 2015 10:25:59 + with message-id and subject line Bug#787542: fixed in systemd 220-6 has caused the Debian Bug report #787542, regarding libudev1-udeb depends on missing libcap2 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.) -- 787542: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787542 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libudev1-udeb Version: 218-1 Severity: grave Tags: d-i Justification: renders package unusable (Please keep debian-b...@lists.debian.org cc'ed.) Hi, libudev1-udeb depends on missing libcap2. I suspect the easiest would be to drop libcap2 support from the udeb build. An alternative would be to try and add a udeb in libcap2. I'd rather have the former happen, so that we could think of releasing an alpha 1 for d-i soonish. The latter can happen afterwards if relevant/wished for etc. Would be better with a coffee, but iterating over debsnap's output for amd64 binaries, this dependency seems to have present since 218-1. Thanks for your time. Mraw, KiBi. --- End Message --- --- Begin Message --- Source: systemd Source-Version: 220-6 We believe that the bug you reported is fixed in the latest version of systemd, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 787...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Martin Pitt (supplier of updated systemd package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 11 Jun 2015 09:25:49 +0200 Source: systemd Binary: systemd systemd-sysv libpam-systemd libnss-myhostname libnss-mymachines libsystemd0 libsystemd-dev libsystemd-login-dev libsystemd-daemon-dev libsystemd-journal-dev libsystemd-id128-dev udev libudev1 libudev-dev udev-udeb libudev1-udeb python3-systemd systemd-dbg Architecture: source amd64 Version: 220-6 Distribution: unstable Urgency: medium Maintainer: Debian systemd Maintainers Changed-By: Martin Pitt Description: libnss-myhostname - nss module providing fallback resolution for the current hostname libnss-mymachines - nss module to resolve hostnames for local container instances libpam-systemd - system and service manager - PAM module libsystemd-daemon-dev - systemd utility library (transitional package) libsystemd-dev - systemd utility library - development files libsystemd-id128-dev - systemd 128 bit ID utility library (transitional package) libsystemd-journal-dev - systemd journal utility library (transitional package) libsystemd-login-dev - systemd login utility library (transitional package) libsystemd0 - systemd utility library libudev-dev - libudev development files libudev1 - libudev shared library libudev1-udeb - libudev shared library (udeb) python3-systemd - Python 3 bindings for systemd systemd- system and service manager systemd-dbg - system and service manager (debug symbols) systemd-sysv - system and service manager - SysV links udev - /dev/ and hotplug management daemon udev-udeb - /dev/ and hotplug management daemon (udeb) Closes: 760299 783509 787542 Changes: systemd (220-6) unstable; urgency=medium . * Enable seccomp support on the architectures that provide libseccomp. (Closes: #760299) * boot-and-services autopkgtest: Add SeccompTest for the above. * boot-and-services autopkgtest: Check that we don't get an unwanted tmp.mount unless /etc/fstab explicitly specifies it. * Bump libcap-dev build dep to the version that provides libcap2-udeb. (Closes: #787542) * Stop installing tmp.mount by default; there are still situations where it becomes active through dependencies from other units, which is surprising, hides existing data in /tmp during runtime, and it isn't safe to have a tmpfs /tmp on every install scenario. (Closes: #783509) - d/rules: Ship tmp.mount in /usr/share/systemd/ instead of /lib/systemd/systemd. - systemd.postinst: When tmp.mount already was enabled, install tmp.mount into /etc and keep it enabled. - systemd.postinst: When enabling tmp.mount because of RAMTMP=yes, copy it from /usr/share. - Drop Don-t-m
Bug#770135: systemd: ssh logins considerably delayed (until PAM timeout) when systemd is upgraded but the system not rebooted
After upgrade to Jessie 8.1 problem still exist ii systemd215-17+deb8u1 systemctl restart systemd-logind.service still have to manually restart the services ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#788400: systemd-logind only fires suspend on lid close once even though it sees the event
systemd-inhibit Who: NetworkManager (UID 0/root, PID 693/NetworkManager) What: sleep Why: NetworkManager needs to turn off networks Mode: delay 1 inhibitors listed. On Thu, Jun 11, 2015 at 3:16 AM, Michael Biebl wrote: > Control: tags -1 moreinfo > > Am 11.06.2015 um 02:13 schrieb jessie: > >> And the output of the systemd-logind.service, as you can see it fires >> `suspend` on the first lid close but never on any after the very first lid >> close, it is very odd, it clearly sees the event: >> >> ``` >> -- Logs begin at Wed 2015-06-10 16:49:40 PDT, end at Wed 2015-06-10 17:05:35 >> PDT. -- >> Jun 10 16:49:41 debian systemd[1]: Starting Login Service... >> Jun 10 16:49:41 debian systemd-logind[559]: New seat seat0. >> Jun 10 16:49:41 debian systemd-logind[559]: Watching system buttons on >> /dev/input/event4 (Power But >> Jun 10 16:49:41 debian systemd-logind[559]: Watching system buttons on >> /dev/input/event9 (Video Bus >> Jun 10 16:49:41 debian systemd[1]: Started Login Service. >> Jun 10 16:49:41 debian systemd-logind[559]: Watching system buttons on >> /dev/input/event2 (Power But >> Jun 10 16:49:41 debian systemd-logind[559]: Watching system buttons on >> /dev/input/event1 (Lid Switc >> Jun 10 16:49:41 debian systemd-logind[559]: Watching system buttons on >> /dev/input/event3 (Sleep But >> Jun 10 16:49:47 debian systemd-logind[559]: New session 1 of user jessie. >> Jun 10 16:52:18 debian systemd-logind[559]: Lid closed. >> Jun 10 16:52:18 debian systemd-logind[559]: Suspending... >> Jun 10 16:52:31 debian systemd-logind[559]: Lid opened. >> Jun 10 16:52:31 debian systemd-logind[559]: Operation finished. >> Jun 10 16:54:44 debian systemd-logind[559]: Lid closed. >> Jun 10 16:54:57 debian systemd-logind[559]: Lid opened. >> Jun 10 16:56:48 debian systemd-logind[559]: Lid closed. >> Jun 10 16:56:51 debian systemd-logind[559]: Lid opened. >> Jun 10 16:56:57 debian systemd-logind[559]: Lid closed. >> Jun 10 16:57:06 debian systemd-logind[559]: Lid opened. >> Jun 10 16:58:33 debian systemd-logind[559]: Lid closed. >> Jun 10 16:58:39 debian systemd-logind[559]: Lid opened. > > What's the output of systemd-inhibit? > > Maybe some application is block the suspend request. > > -- > Why is it that all of the instruments seeking intelligent life in the > universe are pointed away from Earth? > -- Jessie Frazelle 4096R / D4C4 DD60 0D66 F65A 8EFC 511E 18F3 685C 0022 BFF3 pgp.mit.edu ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#788400: systemd-logind only fires suspend on lid close once even though it sees the event
Here are the NetworkManager.service logs, it sees the first suspend and sleeps but it is not even getting the others -- Logs begin at Thu 2015-06-11 09:30:01 PDT, end at Thu 2015-06-11 09:47:32 PDT. -- Jun 11 09:30:02 debian systemd[1]: Starting Network Manager... -- Subject: Unit NetworkManager.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit NetworkManager.service has begun starting up. Jun 11 09:30:02 debian NetworkManager[693]: NetworkManager (version 1.0.2) is starting... Jun 11 09:30:02 debian NetworkManager[693]: Read config: /etc/NetworkManager/NetworkManager.conf Jun 11 09:30:02 debian NetworkManager[693]: WEXT support is enabled Jun 11 09:30:02 debian NetworkManager[693]: init! Jun 11 09:30:02 debian NetworkManager[693]: update_system_hostname Jun 11 09:30:02 debian NetworkManager[693]: interface-parser: parsing file /etc/network/interfaces Jun 11 09:30:02 debian NetworkManager[693]: interface-parser: source line includes interfaces file(s) /etc/network/interfaces.d/* Jun 11 09:30:02 debian NetworkManager[693]: interfaces file /etc/network/interfaces.d/* doesn't exist Jun 11 09:30:02 debian NetworkManager[693]: interface-parser: finished parsing file /etc/network/interfaces Jun 11 09:30:02 debian NetworkManager[693]: guessed connection type (eth0) = 802-3-ethernet Jun 11 09:30:02 debian NetworkManager[693]: update_connection_setting_from_if_block: name:eth0, type:802-3-ethernet, id:Ifupdown (eth0), uuid: 681b428f-beaf-8932-dce4-687ed5bae28e Jun 11 09:30:02 debian NetworkManager[693]: adding eth0 to connections Jun 11 09:30:02 debian NetworkManager[693]: adding iface eth0 to eni_ifaces Jun 11 09:30:02 debian NetworkManager[693]: autoconnect Jun 11 09:30:02 debian NetworkManager[693]: management mode: unmanaged Jun 11 09:30:02 debian NetworkManager[693]: devices added (path: /sys/devices/pci:00/:00:1c.3/:02:00.0/net/wlan0, iface: wlan0) Jun 11 09:30:02 debian NetworkManager[693]: device added (path: /sys/devices/pci:00/:00:1c.3/:02:00.0/net/wlan0, iface: wlan0): no ifupdown configuration found. Jun 11 09:30:02 debian NetworkManager[693]: devices added (path: /sys/devices/virtual/net/lo, iface: lo) Jun 11 09:30:02 debian NetworkManager[693]: device added (path: /sys/devices/virtual/net/lo, iface: lo): no ifupdown configuration found. Jun 11 09:30:02 debian NetworkManager[693]: end _init. Jun 11 09:30:02 debian NetworkManager[693]: Loaded plugin ifupdown: (C) 2008 Canonical Ltd. To report bugs please use the NetworkManager mailing list. Jun 11 09:30:02 debian NetworkManager[693]: Loaded plugin keyfile: (c) 2007 - 2015 Red Hat, Inc. To report bugs please use the NetworkManager mailing list. Jun 11 09:30:02 debian NetworkManager[693]: (11672832) ... get_connections. Jun 11 09:30:02 debian NetworkManager[693]: (11672832) ... get_connections (managed=false): return empty list. Jun 11 09:30:02 debian NetworkManager[693]: keyfile: new connection /etc/NetworkManager/system-connections/DockerEng_Slow (b562ec97-fec0-4b24-bf7a-8812fe97ee8b,"DockerEng_Slow") Jun 11 09:30:02 debian NetworkManager[693]: keyfile: new connection /etc/NetworkManager/system-connections/Not in Range (1436f8b2-524c-490c-9b4c-72b8cfd0005c,"Not in Range") Jun 11 09:30:02 debian NetworkManager[693]: get unmanaged devices count: 0 Jun 11 09:30:02 debian NetworkManager[693]: monitoring kernel firmware directory '/lib/firmware'. Jun 11 09:30:02 debian NetworkManager[693]: monitoring ifupdown state file '/run/network/ifstate'. Jun 11 09:30:02 debian NetworkManager[693]: rfkill1: found WiFi radio killswitch (at /sys/devices/pci:00/:00:1c.3/:02:00.0/ieee80211/phy0/rfkill1) (driver wl) Jun 11 09:30:02 debian NetworkManager[693]: WiFi hardware radio set enabled Jun 11 09:30:02 debian NetworkManager[693]: WWAN hardware radio set enabled Jun 11 09:30:02 debian NetworkManager[693]: Loaded device plugin: /usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-wifi.so Jun 11 09:30:02 debian NetworkManager[693]: Loaded device plugin: /usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-adsl.so Jun 11 09:30:02 debian NetworkManager[693]: Loaded device plugin: /usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-wwan.so Jun 11 09:30:02 debian NetworkManager[693]: Loaded device plugin: /usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so Jun 11 09:30:02 debian NetworkManager[693]: Loaded device plugin: /usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-team.so Jun 11 09:30:02 debian NetworkManager[693]: WiFi enabled by radio killswitch; enabled by state file Jun 11 09:30:02 debian NetworkManager[693]: WWAN enabled by radio killswitch; enabled by state file Jun 11 09:30:02 debian NetworkManager[693]: WiMAX enabled by radio killswitch; enabled by state file Jun 11 09:30:02 debian NetworkManager[693]: Networking is enabled by state file Jun 11 09:30:02 debian NetworkManager[693]: (lo): l
Bug#788400: systemd-logind only fires suspend on lid close once even though it sees the event
Am 11.06.2015 um 18:44 schrieb Jessica Frazelle: > systemd-inhibit > Who: NetworkManager (UID 0/root, PID 693/NetworkManager) > What: sleep > Why: NetworkManager needs to turn off networks > Mode: delay > > 1 inhibitors listed. Ok, that looks fine. Do you have an external monitor connected? What happens if you set the following in logind.conf HandleLidSwitchDocked=suspend and run systemctl restart systemd-logind ? -- 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 ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#788400: systemd-logind only fires suspend on lid close once even though it sees the event
No I don't have an external monitor, I also reproduced this on a ubuntu 15.04 machine and a machine with a commpletely fresh install of debian stretch with gnome. Also I see the same behavior when I change HandleLidSwitchDocked=suspend and run systemctl restart systemd-logind On Thu, Jun 11, 2015 at 9:59 AM, Michael Biebl wrote: > Am 11.06.2015 um 18:44 schrieb Jessica Frazelle: >> systemd-inhibit >> Who: NetworkManager (UID 0/root, PID 693/NetworkManager) >> What: sleep >> Why: NetworkManager needs to turn off networks >> Mode: delay >> >> 1 inhibitors listed. > > Ok, that looks fine. > > > > Do you have an external monitor connected? > What happens if you set the following in logind.conf > HandleLidSwitchDocked=suspend > and run systemctl restart systemd-logind ? > > -- > Why is it that all of the instruments seeking intelligent life in the > universe are pointed away from Earth? > -- Jessie Frazelle 4096R / D4C4 DD60 0D66 F65A 8EFC 511E 18F3 685C 0022 BFF3 pgp.mit.edu ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#788400: systemd-logind only fires suspend on lid close once even though it sees the event
Am 11.06.2015 um 19:06 schrieb Jessica Frazelle: > No I don't have an external monitor, I also reproduced this on a > ubuntu 15.04 machine and a machine with a commpletely fresh install of > debian stretch with gnome. I guess we need a more verbose debug log then. Please boot with systemd.log_level=debug on the kernel command line, and then attach the log from journalctl -u systemd-logind.service -- 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 ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#788400: systemd-logind only fires suspend on lid close once even though it sees the event
will do! On Thu, Jun 11, 2015 at 10:29 AM, Michael Biebl wrote: > Am 11.06.2015 um 19:06 schrieb Jessica Frazelle: >> No I don't have an external monitor, I also reproduced this on a >> ubuntu 15.04 machine and a machine with a commpletely fresh install of >> debian stretch with gnome. > > I guess we need a more verbose debug log then. > Please boot with systemd.log_level=debug on the kernel command line, and > then attach the log from journalctl -u systemd-logind.service > > > -- > Why is it that all of the instruments seeking intelligent life in the > universe are pointed away from Earth? > -- Jessie Frazelle 4096R / D4C4 DD60 0D66 F65A 8EFC 511E 18F3 685C 0022 BFF3 pgp.mit.edu ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#788400: systemd-logind only fires suspend on lid close once even though it sees the event
ok confirmed, it was HandleLidSwitchDocked=suspend, it just needed a system reboot to register the change i guess restarting logind doesnt do that On Thu, Jun 11, 2015 at 10:43 AM, Jessica Frazelle wrote: > so weird it is working now... and the debug is the only line I changed... > > > > On Thu, Jun 11, 2015 at 10:35 AM, Jessica Frazelle wrote: >> will do! >> >> On Thu, Jun 11, 2015 at 10:29 AM, Michael Biebl wrote: >>> Am 11.06.2015 um 19:06 schrieb Jessica Frazelle: No I don't have an external monitor, I also reproduced this on a ubuntu 15.04 machine and a machine with a commpletely fresh install of debian stretch with gnome. >>> >>> I guess we need a more verbose debug log then. >>> Please boot with systemd.log_level=debug on the kernel command line, and >>> then attach the log from journalctl -u systemd-logind.service >>> >>> >>> -- >>> Why is it that all of the instruments seeking intelligent life in the >>> universe are pointed away from Earth? >>> >> >> >> >> -- >> >> >> Jessie Frazelle >> 4096R / D4C4 DD60 0D66 F65A 8EFC 511E 18F3 685C 0022 BFF3 >> pgp.mit.edu > > > > -- > > > Jessie Frazelle > 4096R / D4C4 DD60 0D66 F65A 8EFC 511E 18F3 685C 0022 BFF3 > pgp.mit.edu -- Jessie Frazelle 4096R / D4C4 DD60 0D66 F65A 8EFC 511E 18F3 685C 0022 BFF3 pgp.mit.edu ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#788400: systemd-logind only fires suspend on lid close once even though it sees the event
Am 11.06.2015 um 19:49 schrieb Jessica Frazelle: > ok confirmed, it was HandleLidSwitchDocked=suspend, it just needed a > system reboot to register the change i guess restarting logind doesnt > do that So logind believes your system is docked, probably because it detected a second graphics device. Can you please still attach the debug log. -- 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 ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#788400: systemd-logind only fires suspend on lid close once even though it sees the event
Am 11.06.2015 um 20:04 schrieb Jessica Frazelle: > attached here Ok, two things: If you suspend/resume/suspend within 90secs, systemd will ignore the 2n suspend request. That's this line: > Jun 11 10:42:17 debian systemd-logind[706]: Ignoring lid switch request, system startup or resume too close. Second, logind indeed believes you have multiple graphics devices attached: > Jun 11 10:42:17 debian systemd-logind[706]: Multiple (3) displays connected. Can you reboot,run ls -la /sys/class/drm suspend/resume and run again ls -la /sys/class/drm -- 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 ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#788400: systemd-logind only fires suspend on lid close once even though it sees the event
jessie at debian in ~ $ ls -la /sys/class/drm total 0 drwxr-xr-x 2 root root0 Jun 11 11:39 . drwxr-xr-x 51 root root0 Jun 11 11:39 .. lrwxrwxrwx 1 root root0 Jun 11 11:39 card0 -> ../../devices/pci:00/:00:02.0/drm/card0 lrwxrwxrwx 1 root root0 Jun 11 11:39 card0-DP-1 -> ../../devices/pci:00/:00:02.0/drm/card0/card0-DP-1 lrwxrwxrwx 1 root root0 Jun 11 11:39 card0-eDP-1 -> ../../devices/pci:00/:00:02.0/drm/card0/card0-eDP-1 lrwxrwxrwx 1 root root0 Jun 11 11:39 card0-HDMI-A-1 -> ../../devices/pci:00/:00:02.0/drm/card0/card0-HDMI-A-1 lrwxrwxrwx 1 root root0 Jun 11 11:39 controlD64 -> ../../devices/pci:00/:00:02.0/drm/controlD64 lrwxrwxrwx 1 root root0 Jun 11 11:39 renderD128 -> ../../devices/pci:00/:00:02.0/drm/renderD128 -r--r--r-- 1 root root 4096 Jun 11 11:39 version CLOSE LID after resume... jessie at debian in ~ $ ls -la /sys/class/drm total 0 drwxr-xr-x 2 root root0 Jun 11 11:39 . drwxr-xr-x 51 root root0 Jun 11 11:39 .. lrwxrwxrwx 1 root root0 Jun 11 11:39 card0 -> ../../devices/pci:00/:00:02.0/drm/card0 lrwxrwxrwx 1 root root0 Jun 11 11:39 card0-DP-1 -> ../../devices/pci:00/:00:02.0/drm/card0/card0-DP-1 lrwxrwxrwx 1 root root0 Jun 11 11:39 card0-eDP-1 -> ../../devices/pci:00/:00:02.0/drm/card0/card0-eDP-1 lrwxrwxrwx 1 root root0 Jun 11 11:39 card0-HDMI-A-1 -> ../../devices/pci:00/:00:02.0/drm/card0/card0-HDMI-A-1 lrwxrwxrwx 1 root root0 Jun 11 11:39 controlD64 -> ../../devices/pci:00/:00:02.0/drm/controlD64 lrwxrwxrwx 1 root root0 Jun 11 11:39 renderD128 -> ../../devices/pci:00/:00:02.0/drm/renderD128 -r--r--r-- 1 root root 4096 Jun 11 11:39 version On Thu, Jun 11, 2015 at 11:30 AM, Michael Biebl wrote: > Am 11.06.2015 um 20:04 schrieb Jessica Frazelle: >> attached here > > Ok, two things: > > If you suspend/resume/suspend within 90secs, systemd will ignore the 2n > suspend request. That's this line: > >> Jun 11 10:42:17 debian systemd-logind[706]: Ignoring lid switch > request, system startup or resume too close. > > > Second, logind indeed believes you have multiple graphics devices attached: > >> Jun 11 10:42:17 debian systemd-logind[706]: Multiple (3) displays > connected. > > > Can you reboot,run > ls -la /sys/class/drm > suspend/resume and run again > ls -la /sys/class/drm > > > -- > Why is it that all of the instruments seeking intelligent life in the > universe are pointed away from Earth? > -- Jessie Frazelle 4096R / D4C4 DD60 0D66 F65A 8EFC 511E 18F3 685C 0022 BFF3 pgp.mit.edu ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
[bts-link] source package systemd
# # bts-link upstream status pull for source package systemd # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org # remote status report for #746151 (http://bugs.debian.org/746151) # Bug title: systemd: daemon-reload+reload kills a daemon with a BusName # * https://bugs.freedesktop.org/show_bug.cgi?id=78311 # * remote status changed: NEW -> RESOLVED # * remote resolution changed: (?) -> FIXED # * closed upstream tags 746151 + fixed-upstream usertags 746151 - status-NEW usertags 746151 + status-RESOLVED resolution-FIXED # remote status report for #785525 (http://bugs.debian.org/785525) # Bug title: systemd fails to boot if non-essential block device is missing # * https://github.com/systemd/systemd/pull/91 # * remote status changed: (?) -> closed # * closed upstream tags 785525 + fixed-upstream usertags 785525 + status-closed thanks ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Processed: [bts-link] source package systemd
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package systemd > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # > user bts-link-upstr...@lists.alioth.debian.org Setting user to bts-link-upstr...@lists.alioth.debian.org (was bts-link-de...@lists.alioth.debian.org). > # remote status report for #746151 (http://bugs.debian.org/746151) > # Bug title: systemd: daemon-reload+reload kills a daemon with a BusName > # * https://bugs.freedesktop.org/show_bug.cgi?id=78311 > # * remote status changed: NEW -> RESOLVED > # * remote resolution changed: (?) -> FIXED > # * closed upstream > tags 746151 + fixed-upstream Bug #746151 [systemd] systemd: daemon-reload+reload kills a daemon with a BusName Added tag(s) fixed-upstream. > usertags 746151 - status-NEW Usertags were: status-NEW. Usertags are now: . > usertags 746151 + status-RESOLVED resolution-FIXED There were no usertags set. Usertags are now: status-RESOLVED resolution-FIXED. > # remote status report for #785525 (http://bugs.debian.org/785525) > # Bug title: systemd fails to boot if non-essential block device is missing > # * https://github.com/systemd/systemd/pull/91 > # * remote status changed: (?) -> closed > # * closed upstream > tags 785525 + fixed-upstream Bug #785525 [systemd] systemd fails to boot if non-essential block device is missing Added tag(s) fixed-upstream. > usertags 785525 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 746151: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746151 785525: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785525 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#787731: adds google nameserver without being asked to
Am 10.06.2015 um 11:37 schrieb Michael Biebl: > Am 09.06.2015 um 13:14 schrieb Marc Haber: >> On Sat, Jun 06, 2015 at 09:42:37PM +0200, Michael Biebl wrote: >>> This change is imho too invasive for being backported to the stable v215 >>> in jessie. The first Debian version carrying that fix is 217-1, so I'm >>> closing it for this version. >> >> How about shipping a /etc/systemd/resolved.conf with a not commented >> out "DNS=" line? > > Compiling with ---with-dns-servers="" is better. > It doesn't require us to patch the conf file, it also changes the > builtin list, and the resulting resolved.conf will actually look pretty > similar: > > [Resolve] > #DNS= I committed this change now for the jessie branch: https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=jessie&id=fc04df5fc3adedb990318a34d69a261521d4d57d So this change will be part of the next stable upload. -- 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 ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
