Bug#895239: marked as done ([systemd] suspend works 1st time)
Your message dated Mon, 9 Apr 2018 23:43:33 +0200 with message-id <79f72234-8c6f-83d8-4e5d-9af265969...@debian.org> and subject line Re: Bug#895239: [systemd] suspend works 1st time has caused the Debian Bug report #895239, regarding [systemd] suspend works 1st time 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.) -- 895239: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895239 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: systemd Version: 232-25+deb9u3 Severity: important --- Please enter the report below this line. --- Suspend only works first time. It worked fine on an ancient Acer Aspire One. Now on an Acer S7 392, suspend works on its first try but afterwards fails. Currently running the backports kernel but didn't work with stable either. $ sudo journalctl -u suspend.target [sudo] password for tct: -- Logs begin at Sun 2018-04-08 12:17:50 EDT, end at Sun 2018-04-08 13:49:23 EDT. -- Apr 08 12:48:07 okeeffe systemd[1]: Reached target Suspend. Apr 08 12:48:07 okeeffe systemd[1]: suspend.target: Unit is bound to inactive unit systemd-suspend.service Apr 08 12:48:07 okeeffe systemd[1]: Stopped target Suspend. Apr 08 12:48:09 okeeffe systemd[1]: Reached target Suspend. Apr 08 12:48:09 okeeffe systemd[1]: suspend.target: Unit is bound to inactive unit systemd-suspend.service Apr 08 12:48:09 okeeffe systemd[1]: Stopped target Suspend. Apr 08 13:02:36 okeeffe systemd[1]: Reached target Suspend. Apr 08 13:02:36 okeeffe systemd[1]: suspend.target: Unit is bound to inactive unit systemd-suspend.service Apr 08 13:02:36 okeeffe systemd[1]: Stopped target Suspend. Apr 08 13:28:28 okeeffe systemd[1]: Reached target Suspend. Apr 08 13:28:28 okeeffe systemd[1]: suspend.target: Unit is bound to inactive unit systemd-suspend.service Apr 08 13:28:28 okeeffe systemd[1]: Stopped target Suspend. Apr 08 13:29:24 okeeffe systemd[1]: Reached target Suspend. Apr 08 13:29:24 okeeffe systemd[1]: suspend.target: Unit is bound to inactive unit systemd-suspend.service Apr 08 13:29:24 okeeffe systemd[1]: Stopped target Suspend. and relevant portions of syslog: Apr 8 13:50:09 debian NetworkManager[533]: [1523209809.4718] manager: sleep requested (sleeping: no enabled: yes) Apr 8 13:50:09 debian NetworkManager[533]: [1523209809.4719] manager: sleeping... Apr 8 13:50:09 debian NetworkManager[533]: [1523209809.4720] manager: NetworkManager state is now ASLEEP Apr 8 13:50:09 debian NetworkManager[533]: [1523209809.4724] device (wlp1s0): state change: activated -> deactivating (reason 'sleeping') [100 110 37] Apr 8 13:50:09 debian dbus[521]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' Apr 8 13:50:09 debian NetworkManager[533]: [1523209809.4770] device (wlp1s0): state change: deactivating -> disconnected (reason 'sleeping') [110 30 37] Apr 8 13:50:09 debian systemd[1]: Starting Network Manager Script Dispatcher Service... Apr 8 13:50:09 debian avahi-daemon[519]: Withdrawing address record for fd21:9228:e650::b2e on wlp1s0. Apr 8 13:50:09 debian avahi-daemon[519]: Withdrawing address record for 2601:14d:4101:380b::b2e on wlp1s0. Apr 8 13:50:09 debian avahi-daemon[519]: Withdrawing address record for fd21:9228:e650:0:889d:b57e:e0cc:c4b2 on wlp1s0. Apr 8 13:50:09 debian avahi-daemon[519]: Withdrawing address record for fd21:9228:e650:0:5e51:4fff:fef2:d5b9 on wlp1s0. Apr 8 13:50:09 debian avahi-daemon[519]: Leaving mDNS multicast group on interface wlp1s0.IPv6 with address fd21:9228:e650:0:5e51:4fff:fef2:d5b9. Apr 8 13:50:09 debian avahi-daemon[519]: Joining mDNS multicast group on interface wlp1s0.IPv6 with address 2601:14d:4101:380b:889d:b57e:e0cc:c4b2. Apr 8 13:50:09 debian avahi-daemon[519]: Withdrawing address record for 2601:14d:4101:380b:889d:b57e:e0cc:c4b2 on wlp1s0. Apr 8 13:50:09 debian avahi-daemon[519]: Leaving mDNS multicast group on interface wlp1s0.IPv6 with address 2601:14d:4101:380b:889d:b57e:e0cc:c4b2. Apr 8 13:50:09 debian avahi-daemon[519]: Joining mDNS multicast group on interface wlp1s0.IPv6 with address 2601:14d:4101:380b:5e51:4fff:fef2:d5b9. Apr 8 13:50:09 debian avahi-daemon[519]: Withdrawing address record for 2601:14d:4101:380b:5e51:4fff:fef2:d5b9 on wlp1s0. Apr 8 13:50:09 debian avahi-daemon[519]: Leaving mDNS multicast group on interface wlp1s0.IPv6 with address 2601:14d:4101:380b:5e51:4fff:fef2:d5b9. Apr 8 13:50:09 debian avahi-daemon[519]: Joining mDNS multicast group on interface wlp1s0.IPv6 with address fe80::5e51:4fff:fef2:d5b9. Apr 8 13:50:09
Processed: Re: Restart, Suspend, Hibernate, Shut Down all greyed out in lightdm
Processing control commands: > severity -1 normal Bug #895292 [systemd] Restart, Suspend, Hibernate, Shut Down all greyed out in lightdm Severity set to 'normal' from 'important' > tags -1 moreinfo unreproducible Bug #895292 [systemd] Restart, Suspend, Hibernate, Shut Down all greyed out in lightdm Added tag(s) moreinfo and unreproducible. -- 895292: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895292 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: Restart, Suspend, Hibernate, Shut Down all greyed out in lightdm
Processing control commands: > reassign -1 systemd 238-4 Bug #895292 [policykit-1] policykit-1: Restart, Suspend, Hibernate, Shut Down all greyed out in lightdm Bug reassigned from package 'policykit-1' to 'systemd'. No longer marked as found in versions policykit-1/0.105-20. Ignoring request to alter fixed versions of bug #895292 to the same values previously set Bug #895292 [systemd] policykit-1: Restart, Suspend, Hibernate, Shut Down all greyed out in lightdm Marked as found in versions systemd/238-4. > retitle -1 Restart, Suspend, Hibernate, Shut Down all greyed out in lightdm Bug #895292 [systemd] policykit-1: Restart, Suspend, Hibernate, Shut Down all greyed out in lightdm Changed Bug title to 'Restart, Suspend, Hibernate, Shut Down all greyed out in lightdm' from 'policykit-1: Restart, Suspend, Hibernate, Shut Down all greyed out in lightdm'. -- 895292: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895292 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: Re: Bug#894605: systemd: System fails to suspend.
Processing control commands: > tags -1 + moreinfo Bug #894605 [systemd] systemd: System fails to suspend. Added tag(s) moreinfo. -- 894605: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894605 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: bug 810247 is forwarded to https://github.com/systemd/systemd/issues/8652
Processing commands for cont...@bugs.debian.org: > forwarded 810247 https://github.com/systemd/systemd/issues/8652 Bug #810247 [udev] Hyper-V network adapters are mapped to a different interface (ethN) on every boot Set Bug forwarded-to-address to 'https://github.com/systemd/systemd/issues/8652'. > thanks Stopping processing here. Please contact me if you need assistance. -- 810247: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810247 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: Re: Processed (with 1 error): Re: [Pkg-samba-maint] Bug#886897: Acknowledgement (samba: samba cannot export LUKs encrypted disks mounted manually after systemd boot)
Processing commands for cont...@bugs.debian.org:
> unarchive 885325
Bug #885325 {Done: Michael Biebl <bi...@debian.org>} [systemd] systemd: Daemon
start with systemctl start daemon can not find mount point not mounted by boot
Bug #886811 {Done: Michael Biebl <bi...@debian.org>} [systemd] Can't do
system-wide mounts/unmounts in a ssh sessions
Bug #886908 {Done: Michael Biebl <bi...@debian.org>} [systemd] systemd enabled
services unable to access shares
Unarchived Bug 885325
Unarchived Bug 886811
Unarchived Bug 886908
> forcemerge 885325 886897
Bug #885325 {Done: Michael Biebl <bi...@debian.org>} [systemd] systemd: Daemon
start with systemctl start daemon can not find mount point not mounted by boot
Bug #886811 {Done: Michael Biebl <bi...@debian.org>} [systemd] Can't do
system-wide mounts/unmounts in a ssh sessions
Bug #886908 {Done: Michael Biebl <bi...@debian.org>} [systemd] systemd enabled
services unable to access shares
Bug #886897 [systemd] samba: samba cannot export LUKs encrypted disks mounted
manually after systemd boot
Set Bug forwarded-to-address to
'https://github.com/systemd/systemd/issues/7761'.
Marked Bug as done
Marked as fixed in versions systemd/236-3.
Marked as found in versions systemd/236-2.
Added tag(s) fixed-upstream.
Bug #886811 {Done: Michael Biebl <bi...@debian.org>} [systemd] Can't do
system-wide mounts/unmounts in a ssh sessions
Bug #886908 {Done: Michael Biebl <bi...@debian.org>} [systemd] systemd enabled
services unable to access shares
Merged 885325 886811 886897 886908
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
885325: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885325
886811: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886811
886897: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886897
886908: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886908
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 (with 1 error): Re: [Pkg-samba-maint] Bug#886897: Acknowledgement (samba: samba cannot export LUKs encrypted disks mounted manually after systemd boot)
Processing control commands: > reassign -1 systemd 236-1 Bug #886897 [samba] samba: samba cannot export LUKs encrypted disks mounted manually after systemd boot Bug reassigned from package 'samba' to 'systemd'. No longer marked as found in versions samba/2:4.7.3+dfsg-1. Ignoring request to alter fixed versions of bug #886897 to the same values previously set Bug #886897 [systemd] samba: samba cannot export LUKs encrypted disks mounted manually after systemd boot Marked as found in versions systemd/236-1. > forcemerge 885325 -1 Failed to forcibly merge 885325: Not altering archived bugs; see unarchive. -- 886897: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886897 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: Re: Bug#867368: systemd-udevd: delays boot for 2+ minutes when LVM PV is inside a LV
Processing control commands: > reassign -1 lvm2 Bug #867368 [udev] systemd-udevd: delays boot for 2+ minutes when LVM PV is inside a LV Bug reassigned from package 'udev' to 'lvm2'. No longer marked as found in versions systemd/232-25. Ignoring request to alter fixed versions of bug #867368 to the same values previously set -- 867368: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867368 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#883877: marked as done (systemd segfaults in manager_unref_uid_internal)
Your message dated Mon, 2 Apr 2018 23:16:27 +0200 with message-id <dd9c5cd6-07d1-b44c-1241-39b0bd9d0...@debian.org> and subject line Re: Bug#883877: rsyslog: fails to configure, dpkg --configure exits with error has caused the Debian Bug report #883877, regarding systemd segfaults in manager_unref_uid_internal 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.) -- 883877: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883877 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: rsyslog Version: 8.31.0-1 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 $ sudo LC_ALL=C dpkg --configure --pending Setting up rsyslog (8.31.0-1) ... Failed to reload daemon: Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms) Failed to reload daemon: Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms) Failed to retrieve unit: Connection timed out Failed to restart rsyslog.service: Connection timed out See system logs and 'systemctl status rsyslog.service' for details. invoke-rc.d: initscript rsyslog, action "restart" failed. Failed to get properties: Connection timed out dpkg: error processing package rsyslog (--configure): installed rsyslog package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: rsyslog $ sudo LC_ALL=C systemctl status rsyslog.service Failed to get properties: Connection timed out Dec 8 18:55:47 geode rsyslogd: action '*' treated as ':omusrmsg:*' - please use ':omusrmsg:*' syntax instead, '*' will not be supported in the future [v8.31.0 try http://www.rsyslog.com/e/2184 ] Dec 8 18:55:47 geode rsyslogd: error during parsing file /etc/rsyslog.d/50-default.conf, on or before line 46: warnings occured in file '/etc/rsyslog.d/50-default.conf' around line 46 [v8.31.0 try http://www.rsyslog.com/e/2207 ] Dec 8 18:55:47 geode rsyslogd: [origin software="rsyslogd" swVersion="8.31.0" x-pid="368" x-info="http://www.rsyslog.com;] start Dec 8 18:55:47 geode rsyslogd: action '*' treated as ':omusrmsg:*' - please use ':omusrmsg:*' syntax instead, '*' will not be supported in the future [v8.31.0 try http://www.rsyslog.com/e/2184 ] Dec 8 18:55:47 geode rsyslogd: error during parsing file /etc/rsyslog.d/50-default.conf, on or before line 46: warnings occured in file '/etc/rsyslog.d/50-default.conf' around line 46 [v8.31.0 try http://www.rsyslog.com/e/2207 ] Dec 8 18:55:47 geode rsyslogd: [origin software="rsyslogd" swVersion="8.31.0" x-pid="368" x-info="http://www.rsyslog.com;] start Dec 8 18:55:47 geode rsyslogd: Could not open output pipe '/dev/xconsole':: No such file or directory [v8.31.0 try http://www.rsyslog.com/e/2039 ] Dec 8 18:55:47 geode rsyslogd: action 'action 9' suspended (module 'builtin:ompipe'), retry 0. There should be messages before this one giving the reason for suspension. [v8.31.0 try http://www.rsyslog.com/e/2007 ] Dec 8 18:55:47 geode rsyslogd: action 'action 9' suspended (module 'builtin:ompipe'), next retry is Fri Dec 8 18:56:17 2017, retry nbr 0. There should be messages before this one giving the reason for suspension. [v8.31.0 try http://www.rsyslog.com/e/2007 ] Dec 8 18:55:47 geode rsyslogd: Could not open output pipe '/dev/xconsole':: No such file or directory [v8.31.0 try http://www.rsyslog.com/e/2039 ] Dec 8 18:55:47 geode rsyslogd: action 'action 9' suspended (module 'builtin:ompipe'), retry 0. There should be messages before this one giving the reason for suspension. [v8.31.0 try http://www.rsyslog.com/e/2007 ] Dec 8 18:55:47 geode rsyslogd: action 'action 9' suspended (module 'builtin:ompipe'), next retry is Fri Dec 8 18:56:17 2017, retry nbr 0. There should be messages before this one giving the reason for suspension. [v8.31.0 try http://www.rsyslog.com/e/2007 ] Please see also ( https://q-funk.blogspot.fi/2017/12/dbus-rsyslogd-systemd-which-one-is.html ) Thanks! Martin-Éric - -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (, 'testing'), (1101, 'stable'), (1011, 'oldstable'), (1001, 'oldoldstable'), (500, 'testing-debug') Architecture: i386 (i586) Kernel: Linux 4.13.0-1-686 (SMP w/1 CPU core) Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), LANGUAGE=fi:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages rsyslog depends on: ii init-syste
Processed: forcibly merging 858211 845186
Processing commands for cont...@bugs.debian.org: > forcemerge 858211 845186 Bug #858211 [systemd] please allow console operator to abort waiting for TimeoutStart/Stop Bug #858211 [systemd] please allow console operator to abort waiting for TimeoutStart/Stop Marked as found in versions systemd/232-5. Bug #845186 [systemd] systemd: does not respect ctrl-c running into timeout when starting or stopping services Set Bug forwarded-to-address to 'https://github.com/systemd/systemd/issues/838'. Severity set to 'wishlist' from 'normal' Marked as found in versions systemd/232-19. Merged 845186 858211 > thanks Stopping processing here. Please contact me if you need assistance. -- 845186: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845186 858211: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858211 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#793116: marked as done (systemd: journald randomly exits with USR1, leaving /dev/log unusable)
Your message dated Mon, 2 Apr 2018 00:36:31 +0200 with message-id <8482a91c-cb35-7c96-9d87-f92649a0c...@debian.org> and subject line Re: systemd: journald randomly exits with USR1, leaving /dev/log unusable has caused the Debian Bug report #793116, regarding systemd: journald randomly exits with USR1, leaving /dev/log unusable 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.) -- 793116: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793116 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: systemd Version: 215-17+deb8u1 Severity: normal Dear Maintainer, systemd-journald randomly exits sometimes, about once every 2-3 weeks. I cannot say what leads to the situation, and I'm not sufficiently familiar with systemd to do the neccesary digging on my own. I forgot to make a systemd-analyze dump before restarting the service, so I won't be able to attach it here until this happens again. Let me know what else I can do to help solve this. The highly critical side-effect from this bug is that /dev/log becomes unusable, # logger -u /dev/log FOO logger: socket /dev/log: Connection refused which, among others, makes postfix-policyd-spf-perl crash upon startup, which results in Postfix (temporarily) rejecting _all_ incoming mails. systemctl reports <<<snip<<< # systemctl status systemd-journald systemd-journald.service - Journal Service Loaded: loaded (/lib/systemd/system/systemd-journald.service; static) Active: failed (Result: start-limit) since Mo 2015-07-13 01:21:13 CEST; 14h ago Docs: man:systemd-journald.service(8) man:journald.conf(5) Process: 24406 ExecStart=/lib/systemd/systemd-journald (code=killed, signal=USR1) Main PID: 24406 (code=killed, signal=USR1) # systemctl status systemd-journald-dev-log.socket systemd-journald-dev-log.socket - Journal Socket (/dev/log) Loaded: loaded (/lib/systemd/system/systemd-journald-dev-log.socket; static) Active: failed (Result: service-failed-permanent) since Mo 2015-07-13 01:21:13 CEST; 14h ago Docs: man:systemd-journald.service(8) man:journald.conf(5) Listen: /run/systemd/journal/dev-log (Datagram) Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable. <>>>snap>>> - Phillip Berndt -- Package-specific info: -- System Information: Debian Release: 8.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.41-042stab106.6 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.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+deb8u1 ii mount 2.25.2-6 ii sysv-rc 2.88dsf-59 ii udev215-17+deb8u1 ii util-linux 2.25.2-6 Versions of packages systemd recommends: ii dbus1.8.18-0+deb8u1 ii libpam-systemd 215-17+deb8u1 Versions of packages systemd suggests: pn systemd-ui -- no debconf information --- End Message --- --- Begin Message --- We never heard back from Philipp after the bug was tagged moreinfo and more information has been requested. I'm thus closing this bug report, also keeping in mind, that a lot has changed in journald, so the original crash is most likely no longer an issue. If the issue still persists though, please reopen or file a new bug report. -- 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 Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#883569: marked as done (libpam-systemd: Prefer systemd-sysv over systemd-shim)
Your message dated Mon, 2 Apr 2018 00:23:51 +0200 with message-id <9300ceda-2d7c-174c-b092-ac5f73f9f...@debian.org> and subject line Re: Bug#883569: libpam-systemd: Prefer systemd-sysv over systemd-shim has caused the Debian Bug report #883569, regarding libpam-systemd: Prefer systemd-sysv over systemd-shim 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.) -- 883569: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883569 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libpam-systemd Version: 235-3 Severity: important libpam-systemd depending on systemd-shim first causes severe trouble with resolving dependencies, as APT picks systemd-shim but then later sees a package which needs systemd-sysv and fails. I understand the order was necessary for preventing upgrades to stretch from migrating to systemd, but with the packages now widely installed, this should not be a problem anymore, as the dependencies are satisfied already, so APT won't switch them. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (900, 'testing'), (800, 'unstable'), (500, 'unstable-debug'), (500, 'testing-debug'), (100, 'experimental'), (1, 'experimental-debug') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.13.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8), LANGUAGE=en_IE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages libpam-systemd depends on: ii dbus1.12.2-1 ii libc6 2.25-2 ii libpam-runtime 1.1.8-3.6 ii libpam0g1.1.8-3.6 ii libselinux1 2.7-2 ii systemd 235-3 ii systemd-sysv235-3 libpam-systemd recommends no packages. libpam-systemd suggests no packages. -- no debconf information -- debian developer - deb.li/jak | jak-linux.org - free software dev ubuntu core developer i speak de, en --- End Message --- --- Begin Message --- On Fri, 23 Mar 2018 09:03:06 +0100 Martin Pitt <mp...@debian.org> wrote: > Hello Michael, > > Michael Biebl [2018-03-19 6:44 +0100]: > > So, what are we going to do now then? > > "Nothing" I supppose. I don't think it's actually broken right now, it just > feels a little odd to prefer SysV in the dependencies. But with systemd being > installed by default, I suppose it's okay. I guess it doesn't make sense then to keep this bug report open. So I'll close it. Julian, if you want to get confirmation from the CTTE that actually switching the dependencies is ok, then I'm fine to comply accordingly. The decision in #883573 is actually not that helpful to decide this particular bug 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 Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Processed: tagging 768178, closing 768178
Processing commands for cont...@bugs.debian.org: > tags 768178 + wontfix Bug #768178 [systemd] LSB/SysV service incorrectly marked as active under certain conditions Bug #763401 [systemd] LSB/SysV service incorrectly marked as active under certain conditions Bug #817892 [systemd] systemd: sysv wrapper breaks LSB exit codes Added tag(s) wontfix. Added tag(s) wontfix. Added tag(s) wontfix. > close 768178 Bug #768178 [systemd] LSB/SysV service incorrectly marked as active under certain conditions Bug #763401 [systemd] LSB/SysV service incorrectly marked as active under certain conditions Bug #817892 [systemd] systemd: sysv wrapper breaks LSB exit codes Marked Bug as done Marked Bug as done Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 763401: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763401 768178: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768178 817892: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817892 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: [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 #868159 (http://bugs.debian.org/868159) > # Bug title: systemd-setup-tmpfiles startup error when /srv is on read-only fs > # * https://github.com/systemd/systemd/issues/8566 > # * remote status changed: (?) -> closed > # * closed upstream > tags 868159 + fixed-upstream Bug #868159 [systemd] systemd-setup-tmpfiles startup error when /srv is on read-only fs Added tag(s) fixed-upstream. > usertags 868159 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 868159: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868159 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#887847: marked as done (Extra quoting needed for the job description)
Your message dated Wed, 28 Mar 2018 21:40:37 + with message-id <e1f1io9-000hdt...@fasolo.debian.org> and subject line Bug#887847: fixed in systemd-cron 1.5.13-1 has caused the Debian Bug report #887847, regarding Extra quoting needed for the job description 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.) -- 887847: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887847 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: systemd-cron Version: 1.5.12-2 Severity: normal Found this in the wild: zfsutils-linux package has the following cron.d entry: # Scrub the second Sunday of every month. 24 0 8-14 * * root [ $(date +\%w) -eq 0 ] && [ -x /usr/lib/zfs-linux/scrub ] && /usr/lib/zfs-linux/scrub generating this timer unit: [Unit] Description=[Timer] "24 0 8-14 * * root [ $(date +\%w) -eq 0 ] && [ -x /usr/lib/zfs-linux/scrub ] && /usr/lib/zfs-linux/scrub" which yields: /run/systemd/generator/cron-zfsutils-linux-root-0.timer:2: Failed to resolve unit specifiers on [Timer] "24 0 8-14 * * root [ $(date +\%w) -eq 0 ] && [ -x /usr/lib/zfs-linux/scrub ] && /usr/lib/zfs-linux/scrub", ignoring: Invalid slot The % should be escaped in Description as well using %%. -- Package-specific info: -- output of systemd-delta -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (900, 'unstable'), (800, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.14.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages systemd-cron depends on: ii libc6 2.26-4 ii python3 3.6.4-1 ii systemd-sysv 236-3 Versions of packages systemd-cron recommends: ii exim4-daemon-light [mail-transport-agent] 4.90-3 systemd-cron suggests no packages. --- End Message --- --- Begin Message --- Source: systemd-cron Source-Version: 1.5.13-1 We believe that the bug you reported is fixed in the latest version of systemd-cron, 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 887...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alexandre Detiste <alexandre.deti...@gmail.com> (supplier of updated systemd-cron 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: SHA512 Format: 1.8 Date: Wed, 28 Mar 2018 22:58:07 +0200 Source: systemd-cron Binary: systemd-cron Architecture: source amd64 Version: 1.5.13-1 Distribution: unstable Urgency: medium Maintainer: Debian Systemd Maintainers <pkg-systemd-maintainers@lists.alioth.debian.org> Changed-By: Alexandre Detiste <alexandre.deti...@gmail.com> Description: systemd-cron - systemd units to provide cron daemon & anacron functionality Closes: 887847 Changes: systemd-cron (1.5.13-1) unstable; urgency=medium . * remove obsolete hack of $$(bindir) in Makefile * escape '%' in unit description (Closes: #887847) Checksums-Sha1: 8a47982b7bed9892bb2757a9c0a599af4e08a131 2077 systemd-cron_1.5.13-1.dsc 66f6f4f5b8e2e328a63c7a4f46c24908b9f4975e 31533 systemd-cron_1.5.13.orig.tar.gz b7cf25c6e600b473032b0e77931f83c9543fa99e 6500 systemd-cron_1.5.13-1.debian.tar.xz 1a19efe3f8fe22b067c17d934fd6d0bb207fbcc0 6472 systemd-cron-dbgsym_1.5.13-1_amd64.deb fd7af454c35a3e4c78a8c418220aec8443379218 6572 systemd-cron_1.5.13-1_amd64.buildinfo d57cc6cebcfafa32a02c0f60417ac5cc6612c755 34332 systemd-cron_1.5.13-1_amd64.deb Checksums-Sha256: c3989fb40d91f469fd6830dc84aa79c8c7957a579e7f7250c1a16f4898b16d6a 2077 systemd-cron_1.5.13-1.dsc e14143bff01a1c74ee0f8776bc142310f1e165a6ebbee37ed670ff9a24c1cb26 31533 systemd-cron_1.5.13.orig.tar.gz 9a89b8ce53e5fe4fe7b81eb741bd2dd2fafb6a4782bab594ab519a6188b31fc8 6500 systemd-cron_1.5.13-1.debian.tar.xz d55613e65d343c7581deda1cfc21d9d92ccd6a1e6e43e22c75151c7be902c067 6472 systemd-cron-dbgsym_1.5.13-1_amd64.deb 3d65c2f3a5a8cf9d24adbfff9d5f83a5aeea00677cd6af08928111375940ab88 6572 systemd-cron_1.5.13-1_amd64.buildinfo 489e2d6143f2e
Processed: tagging 792045
Processing commands for cont...@bugs.debian.org: > tags 792045 + wontfix Bug #792045 [systemd] SHould handle failed stop action in lsb initscript Added tag(s) wontfix. > thanks Stopping processing here. Please contact me if you need assistance. -- 792045: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792045 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: Re: logind sometimes blocks input to X after VT switch
Processing control commands: > tags -1 + moreinfo Bug #809069 [systemd] logind sometimes blocks input to X after VT switch Added tag(s) moreinfo. -- 809069: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809069 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: bug 792045 is forwarded to https://github.com/systemd/systemd/issues/8601
Processing commands for cont...@bugs.debian.org: > forwarded 792045 https://github.com/systemd/systemd/issues/8601 Bug #792045 [systemd] SHould handle failed stop action in lsb initscript Set Bug forwarded-to-address to 'https://github.com/systemd/systemd/issues/8601'. > thanks Stopping processing here. Please contact me if you need assistance. -- 792045: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792045 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: Re: Bug#893574: closed by Simon McVittie <s...@debian.org> (Re: Bug#893574: gnome-shell: Suspends after 20 minutes even if there is activity on a seat)
Processing control commands:
> reopen -1
Bug #893574 {Done: Simon McVittie <s...@debian.org>} [systemd] gnome-shell:
Suspend after 20 minutes even there is activity on a seat
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 238-3.
> reassign -1 gnome-settings-daemon
Bug #893574 [systemd] gnome-shell: Suspend after 20 minutes even there is
activity on a seat
Bug reassigned from package 'systemd' to 'gnome-settings-daemon'.
No longer marked as found in versions systemd/238-2.
Ignoring request to alter fixed versions of bug #893574 to the same values
previously set
> found -1 3.28.0-1
Bug #893574 [gnome-settings-daemon] gnome-shell: Suspend after 20 minutes even
there is activity on a seat
Marked as found in versions gnome-settings-daemon/3.28.0-1.
--
893574: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893574
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#882630: marked as done (systemd-bootchart: debian/copyright refers to CC0 by URL)
Your message dated Sun, 25 Mar 2018 22:21:55 + with message-id <e1f0e1t-0001dx...@fasolo.debian.org> and subject line Bug#882630: fixed in systemd-bootchart 233-2 has caused the Debian Bug report #882630, regarding systemd-bootchart: debian/copyright refers to CC0 by URL 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.) -- 882630: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882630 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: systemd-bootchart Severity: normal Control: tag -1 + stretch buster Control: block -1 by 882628 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer, This package refers to the text of the Creative Commons Zero license by its URL on creativecommons.org; as far as I understand, the Debian policy requires that we ship the actual text of the license [0]. I requested (in #882628) that CC0 be shipped in /usr/share/common-licences, so it might become possible to refer to that file if you do not wish to include the whole text in debian/copyright. Best, nicoo -BEGIN PGP SIGNATURE- iQJNBAEBCgA3FiEEiWEbFKE2h/s1SpJPnU+IAQz+GeMFAloYvLAZHG5pY29sYXNA YnJhdWQtc2FudG9uaS5ldQAKCRCdT4gBDP4Z46ptD/4htt8y2sskTGj9gEqrS6cB ccvvPYkKqJ7an6p7BaEpA/EoAwMPJ67dFfgSw/e0s2a6Ne8asQCGH1prRtOkmXXx bW7ZvuGzeQSbSXopGHVWHAMH7cByo5nFPZDSpqaRFaNFLSl9PTIQCrfd/TOlHXZd iQujk/iKYyXEs41drTQKF1wxqI7twMtE9dT2osnTwNkcj3bhaOj9x6eWe0yzMCL6 zhIMkzS0ipsT5BEx6Y1Ifweu3D4dwc6Z0k0UgeueLkkzU0MitjRxBEZv1kB/qKp+ ceT+2LooMqJ/0ouhFedUqzGTn4gM8jC9bxfN3uQfwO1kXFc1eNX3IaeZY1YqZBnj ml/yMCS0ZQ/8BTZMpLysLH7cNC6Z2AlhVLsnhk47ts75P+YFrgFbC9X2XCQ4e/LW CakG0JvLjroHOZFxzNgc3KPUNriUifW6DSu8CMjK96dr9AzmBvzLiuE29NZj4gg/ 5JokPgBXrs5g6gnleO/F+Ogrif79QVCsSxackj1ci06jW/yi1yXvUike1N8bqC7S oXNg2TuLgTOO4yPsDcjcpL2pNiDYDCY2AMFvwC/e3PKEeNFAHhwphlz48WNXAvJe Jz6YC+hTYLQPAy+Rh43FWEV4asYQpUII9ESnD8q3wZex5dWlJ5jqdKi+yIIZARNz JTKkXvFo8CsCYXmiNClEQw== =mVQK -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Source: systemd-bootchart Source-Version: 233-2 We believe that the bug you reported is fixed in the latest version of systemd-bootchart, 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 882...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Martin Pitt <mp...@debian.org> (supplier of updated systemd-bootchart 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: Sun, 25 Mar 2018 23:53:27 +0200 Source: systemd-bootchart Binary: systemd-bootchart Architecture: source amd64 Version: 233-2 Distribution: unstable Urgency: medium Maintainer: Debian systemd Maintainers <pkg-systemd-maintainers@lists.alioth.debian.org> Changed-By: Martin Pitt <mp...@debian.org> Description: systemd-bootchart - boot performance graphing tool Closes: 882630 Changes: systemd-bootchart (233-2) unstable; urgency=medium . [ Michael Biebl ] * Update Vcs-* to point to https://salsa.debian.org * Set Rules-Requires-Root to no . [ Nicolas Braud-Santoni ] * debian/copyright: Point to CC-1.0 license in /usr/share/common-licenses/ (Closes: #882630) . [ Martin Pitt ] * debian/copyright: Use https URL for Format: * Bump Standards-Version to 4.1.3 * debian/copyright: Move global wildcard section to the top. Fixes lintian warning global-files-wildcard-not-first-paragraph-in-dep5-copyright. Checksums-Sha1: 96df85503a101b0afe7a4ba0bd457feaa423a3d3 2224 systemd-bootchart_233-2.dsc 37748e1c6472abcf19cc6c6ba96a42b16b48f721 3976 systemd-bootchart_233-2.debian.tar.xz 8f236eff095456c16bb6f15afeff1cba98063514 91952 systemd-bootchart-dbgsym_233-2_amd64.deb a2d2d40285bac93bff3c16d25129df981de0ad4e 6795 systemd-bootchart_233-2_amd64.buildinfo 640025e212cfb2f043f6cb4aa4aeff4918c95044 45276 systemd-bootchart_233-2_amd64.deb Checksums-Sha256: 2426ccda61307578d882376b0566343e0fd7769b3b200fd6b31b8511fa84da1d 2224 systemd-bootchart_233-2.dsc d86959f527bd0c99dc552a251acf11e3c6d9c00cf250fa34bff294e10e7f1e9f 3976 systemd-bootchart_233-2.debian.tar.xz 64abff7c02b55031df0a5336d0ea02e6064ce1fe71a42886c48330449ce35856 91952 systemd-bootchar
Bug#783618: marked as done (systemd: journald ignores MaxLevelKMsg=warning)
Your message dated Sat, 24 Mar 2018 22:36:10 +0100 with message-id <6dfcea2f-7b74-aa9a-e8d3-1a06149a8...@debian.org> and subject line Re: systemd: journald ignores MaxLevelKMsg=warning has caused the Debian Bug report #783618, regarding systemd: journald ignores MaxLevelKMsg=warning 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.) -- 783618: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783618 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: systemd Version: 215-17 Severity: normal Dear Maintainer, * After noticing that journald fills dmesg with irrelevant messages such as: > syslog:info : [2730378.422878] systemd-journald[4060]: Deleted empty journal > /var/log/journal/c2544241fd44405fba80ed9cf7fe0f29/user-31146@c21ba3b937144879a1feba0ae91775ae--.journal > (8388608 bytes). * I read the documentation and tried to suppress those messages (since they are loglevel info) by adding MaxLevelKMsg=warning to journald.conf * I would have expected said messages to be no longer logged to dmesg/kmsg. * Yet those messages still appear in dmesg. -- Package-specific info: -- System Information: Debian Release: 8.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.18.9-cip-amd64 (SMP w/16 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.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 ii libpam-systemd 215-17 Versions of packages systemd suggests: pn systemd-ui -- Configuration Files: /etc/pam.d/systemd-user changed: @include cip-login /etc/systemd/journald.conf changed: [Journal] Storage=persistent SystemMaxUse=200M MaxRetentionSec=1week MaxLevelKMsg=warning /etc/systemd/logind.conf changed: [Login] HandlePowerKey=ignore HandleSuspendKey=ignore HandleHibernateKey=ignore HandleLidSwitch=ignore -- no debconf information --- End Message --- --- Begin Message --- On Fri, 16 Dec 2016 06:06:29 +0100 Michael Biebl <bi...@debian.org> wrote: > Control: tags -1 + moreinfo > > On Tue, 28 Apr 2015 14:36:26 +0200 Alexander Wuerstlein > <snalw...@cip.informatik.uni-erlangen.de> wrote: > > Package: systemd > > Version: 215-17 > > Severity: normal > > > > Dear Maintainer, > > > >* After noticing that journald fills dmesg with irrelevant messages > > such as: > > > syslog:info : [2730378.422878] systemd-journald[4060]: Deleted empty > > > journal > > > /var/log/journal/c2544241fd44405fba80ed9cf7fe0f29/user-31146@c21ba3b937144879a1feba0ae91775ae--.journal > > > (8388608 bytes). > >* I read the documentation and tried to suppress those messages > > (since they are loglevel info) by adding MaxLevelKMsg=warning to > > journald.conf > >* I would have expected said messages to be no longer logged to > > dmesg/kmsg. > >* Yet those messages still appear in dmesg. > > I think this is fixed in newer systemd versions. > > Can you please try to reproduce the problem with systemd v232 from > unstable/stretch. Closing, ttbomk this is fixed in recent versions and no feedback was provided which would indicate the contrary. 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 Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#799922: marked as done (systemd-machined: error: error from service: CreateMachine: Activation of org.freedesktop.machine1 timed out)
Your message dated Sat, 24 Mar 2018 22:44:21 +0100 with message-id <3a7169f2-aa23-2f81-0733-e2437bc4f...@debian.org> and subject line Re: systemd-machined: error: error from service: CreateMachine: Activation of org.freedesktop.machine1 timed out has caused the Debian Bug report #799922, regarding systemd-machined: error: error from service: CreateMachine: Activation of org.freedesktop.machine1 timed out 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.) -- 799922: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799922 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: systemd Version: 215-17+deb8u2 Severity: normal File: systemd-machined Dear Maintainer, when trying to re-start a guest machine (doing virsh shutdown to use new library files in the qemu process), startup via "virsh start " failed: error: Failed to start domain error: error from service: CreateMachine: Activation of org.freedesktop.machine1 timed out The host in question is up for around 40 days. It seems as if libvirt needs some dbus connection and systemd-machined for guest startup. Restarting systemd-machined via "service systemd-machined restart" cleared the situation. So obviously, some sort of communication between systemd and dbus was lost unnoticed - maybe by recent library upgrades and daemon restarts by needrestart? Maybe some restart dependency is broken? Yours sincerely Matthias Merz -- Package-specific info: -- System Information: Debian Release: 8.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/48 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.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+deb8u1 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+deb8u2 ii mount 2.25.2-6 ii sysv-rc 2.88dsf-59 ii udev215-17+deb8u2 ii util-linux 2.25.2-6 Versions of packages systemd recommends: ii dbus1.8.20-0+deb8u1 ii libpam-systemd 215-17+deb8u2 Versions of packages systemd suggests: pn systemd-ui -- Configuration Files: /etc/systemd/system.conf changed: [Manager] ShowStatus=yes -- no debconf information --- End Message --- --- Begin Message --- On Fri, 2 Jun 2017 03:01:22 +0200 Michael Biebl <bi...@debian.org> wrote: > Control: tags -1 + moreinfo > > Hi Matthias > > On Thu, 24 Sep 2015 11:11:23 +0200 Matthias Merz <deb...@merz-ka.de> wrote: > > Package: systemd > > Version: 215-17+deb8u2 > > Severity: normal > > File: systemd-machined > > > > Dear Maintainer, > > > > when trying to re-start a guest machine (doing virsh shutdown to use > > new library files in the qemu process), startup via > > "virsh start " failed: > > > > error: Failed to start domain > > error: error from service: CreateMachine: Activation of > > org.freedesktop.machine1 timed out > > > > > > The host in question is up for around 40 days. It seems as if libvirt > > needs some dbus connection and systemd-machined for guest > > startup. Restarting systemd-machined via "service systemd-machined > > restart" cleared the situation. > > > > So obviously, some sort of communication between systemd and dbus was > > lost unnoticed - maybe by recent library upgrades and daemon restarts > > by needrestart? Maybe some restart dependency is broken? > > Sorry for not getting back to you earlier. > Is this still a problem you can reproduce? If so, I'd send you further > instructions how to debug this. I revisited this old bug report and with the given information I was unable to reproduce the issue. So I'm going to close it. Please report back, if you still run into this issue with an up-to-date stretch system. We can then reopen the bug report. Regards, Michael -- Why is it that all of the instruments seeking intelligent life
Bug#893574: marked as done (gnome-shell: Suspend after 20 minutes even there is activity on a seat)
Your message dated Sat, 24 Mar 2018 21:39:19 + with message-id <20180324213900.ga29...@espresso.pseudorandom.co.uk> and subject line Re: Bug#893574: gnome-shell: Suspends after 20 minutes even if there is activity on a seat has caused the Debian Bug report #893574, regarding gnome-shell: Suspend after 20 minutes even there is activity on a seat 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.) -- 893574: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893574 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gnome-shell Version: 3.28.0-1 Severity: important Dear Maintainer, Since version 3.27.90 the default action is to suspend after 20 minutes of inactivity. Unfortunately, the system also suspend when there is activity on a seat while the other is idle. * What led up to the situation? create a multiseat setup with the "loginctl attach seat1" command * What exactly did you do (or not do) that was effective (or ineffective)? Leave seat1 on the gdm3 login screen and go away. Login on seat0 and play. * What was the outcome of this action? The system go to sleep after 20 minutes * What outcome did you expect instead? The system stays awake When both seats are active the system doesn't go to sleep. journalctl mrt 20 00:42:21 Jessica gnome-shell[1403]: Screen lock is locked down, not locking mrt 20 00:42:21 Jessica kernel: PM: suspend entry (deep) mrt 20 00:42:21 Jessica gnome-shell[3700]: Screen lock is locked down, not locking mrt 20 00:42:21 Jessica NetworkManager[896]: [1521502941.3440] manager: sleep: sleep requested (sleeping: no enabled: yes) mrt 20 00:42:21 Jessica NetworkManager[896]: [1521502941.3440] manager: NetworkManager state is now ASLEEP mrt 20 00:42:21 Jessica systemd[1]: Reached target Sleep. mrt 20 00:42:21 Jessica systemd[1]: Starting Suspend... mrt 20 00:42:21 Jessica systemd-sleep[6914]: Suspending system... See also Gnome bug 681869 https://bugzilla.gnome.org/show_bug.cgi?id=681869 -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.15.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=nl_NL.utf8, LC_CTYPE=nl_NL.utf8 (charmap=UTF-8), LANGUAGE=nl_NL.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gnome-shell depends on: ii dconf-gsettings-backend [gsettings-backend] 0.26.1-3 ii evolution-data-server3.26.5-2 ii gir1.2-accountsservice-1.0 0.6.45-1 ii gir1.2-atspi-2.0 2.28.0-1 ii gir1.2-freedesktop 1.56.0-1 ii gir1.2-gcr-3 3.28.0-1 ii gir1.2-gdesktopenums-3.0 3.28.0-1 ii gir1.2-gdm-1.0 3.28.0-1 ii gir1.2-geoclue-2.0 2.4.7-1 ii gir1.2-glib-2.0 1.56.0-1 ii gir1.2-gnomebluetooth-1.03.28.0-2 ii gir1.2-gnomedesktop-3.0 3.28.0-1 ii gir1.2-gtk-3.0 3.22.29-1 ii gir1.2-gweather-3.0 3.28.0-2 ii gir1.2-ibus-1.0 1.5.17-3 ii gir1.2-mutter-2 3.28.0-2 ii gir1.2-nm-1.01.10.6-2 ii gir1.2-nma-1.0 1.8.10-2 ii gir1.2-pango-1.0 1.40.14-1 ii gir1.2-polkit-1.00.105-18 ii gir1.2-rsvg-2.0 2.40.20-2 ii gir1.2-soup-2.4 2.62.0-1 ii gir1.2-upowerglib-1.00.99.7-2 ii gjs 1.52.0-1 ii gnome-backgrounds3.28.0-1 ii gnome-settings-daemon3.28.0-1 ii gnome-shell-common 3.28.0-1 ii gsettings-desktop-schemas3.28.0-1 ii libatk-bridge2.0-0 2.26.2-1 ii libatk1.0-0 2.28.1-1 ii libc62.27-2 ii libcairo21.15.10-2 ii libcanberra-gtk3-0 0.30-6 ii libcanberra0 0.30-6 ii libcroco30.6.12-2 ii libecal-1.2-19
Bug#779612: marked as done (systemd-sysv,cryptsetup: systemd-sysv, cryptsetup should recommend plymouth; without plymouth cryptsetup prompts are unusable)
Your message dated Sat, 24 Mar 2018 22:51:51 +0100 with message-id <16dfe332-607b-d6f7-165e-0d2b630aa...@debian.org> and subject line Re: Bug#764555: systemd: cryptsetup password overwritten/hidden by status messages has caused the Debian Bug report #764555, regarding systemd-sysv,cryptsetup: systemd-sysv, cryptsetup should recommend plymouth; without plymouth cryptsetup prompts are unusable 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.) -- 764555: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764555 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: systemd-sysv,cryptsetup Severity: important Dear Maintainer, Booting in jessie is currently nearly impossible with multiple cryptsetup volumes which are mounted at boot time. systemd spews messages over the prompt and there's a 90-second timeout while typing blind. Please see the bug report[1] and discussion on debian-qa[2]. The bug appears to be "fixed" by installing plymouth, so it's proposed that systemd-sysv and cryptsetup should at least recommend plymouth. This is a major usability problem for users with multiple required cryptsetup volumes, e.g. on /var and /usr. I do not believe jessie should ship as "stable" with it unresolved. 1. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768314 2. https://lists.debian.org/debian-qa/2015/02/msg00051.html -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (900, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.16-2-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) --- End Message --- --- Begin Message --- On Wed, 08 Oct 2014 18:39:11 -0700 Nikolaus Rath <nikol...@rath.org> wrote: > On 10/08/2014 06:17 PM, Michael Biebl wrote: > > Am 09.10.2014 um 02:51 schrieb Nikolaus Rath: > >> On 10/08/2014 05:47 PM, Michael Biebl wrote: > >>> Am 09.10.2014 um 02:43 schrieb Nikolaus Rath: > >>>> Package: systemd > >>>> Version: 215-5+b1 > >>>> Severity: normal > >>>> > >>>> Hello, > >>>> > >>>> I'm running Debian testing. After the last dist-upgrade, systemd has > >>>> started showing status messages during boot (sort of like sysvinit used > >>>> to do). This is certainly much prettier and more informative than the > >>>> blank screen that I had before, but it has the unfortunate side-effect > >>>> of interfering with the cryptsetup password prompt. Sometimes the prompt > >>>> is several lines before the cursor with other messsages in between, and > >>>> sometimes it's actually overwritten completely. > >>>> > >>>> It'd be nice if status output would be suppressed/delayed while a > >>>> password prompty is active. > >>> > >>> You'll need something like plymouth to multiplex the input/output. > >>> > >>> http://web.dodds.net/~vorlon/wiki/blog/Plymouth_is_not_a_bootsplash/ > >> > >> In that case it'd be great if the systemd or the cryptsetup package > >> could recommend or suggest the appropriate package (plymouth?). > > > > Could you verify that plymouth solves your problem? > > Yes it did. Thank you! > I think systemd handles this case more gracefully nowadays, so having plymouth installed is no longer a necessity. I'm thus closing this bug report. A Recommends in systemd wouldn't actually help in any case, as systemd is installed during the initial bootstrap phase, where recommends are not considered and a hard Depends doesn't seem warranted. If we wanted to install plymouth by default, we should use another mechanism then having systemd recommend it. 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 Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#764555: marked as done (Please add Recommends: plymouth)
Your message dated Sat, 24 Mar 2018 22:51:51 +0100 with message-id <16dfe332-607b-d6f7-165e-0d2b630aa...@debian.org> and subject line Re: Bug#764555: systemd: cryptsetup password overwritten/hidden by status messages has caused the Debian Bug report #764555, regarding Please add Recommends: plymouth 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.) -- 764555: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764555 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: systemd Version: 215-5+b1 Severity: normal Hello, I'm running Debian testing. After the last dist-upgrade, systemd has started showing status messages during boot (sort of like sysvinit used to do). This is certainly much prettier and more informative than the blank screen that I had before, but it has the unfortunate side-effect of interfering with the cryptsetup password prompt. Sometimes the prompt is several lines before the cursor with other messsages in between, and sometimes it's actually overwritten completely. It'd be nice if status output would be suppressed/delayed while a password prompty is active. -- Package-specific info: -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-2-amd64 (SMP w/8 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 acl 2.2.52-2 ii adduser 3.113+nmu3 ii initscripts 2.88dsf-53.4 ii libacl1 2.2.52-2 ii libaudit1 1:2.4-1 ii libblkid1 2.20.1-5.11 ii libc6 2.19-11 ii libcap2 1:2.24-6 ii libcap2-bin 1:2.24-6 ii libcryptsetup4 2:1.6.6-1 ii libgcrypt20 1.6.2-3 ii libkmod218-3 ii liblzma55.1.1alpha+20120614-2 ii libpam0g1.1.8-3.1 ii libselinux1 2.3-2 ii libsystemd0 215-5+b1 ii sysv-rc 2.88dsf-53.4 ii udev215-5+b1 ii util-linux 2.20.1-5.11 Versions of packages systemd recommends: ii dbus1.8.8-1+b1 ii libpam-systemd 215-5+b1 Versions of packages systemd suggests: pn systemd-ui -- no debconf information --- End Message --- --- Begin Message --- On Wed, 08 Oct 2014 18:39:11 -0700 Nikolaus Rath <nikol...@rath.org> wrote: > On 10/08/2014 06:17 PM, Michael Biebl wrote: > > Am 09.10.2014 um 02:51 schrieb Nikolaus Rath: > >> On 10/08/2014 05:47 PM, Michael Biebl wrote: > >>> Am 09.10.2014 um 02:43 schrieb Nikolaus Rath: > >>>> Package: systemd > >>>> Version: 215-5+b1 > >>>> Severity: normal > >>>> > >>>> Hello, > >>>> > >>>> I'm running Debian testing. After the last dist-upgrade, systemd has > >>>> started showing status messages during boot (sort of like sysvinit used > >>>> to do). This is certainly much prettier and more informative than the > >>>> blank screen that I had before, but it has the unfortunate side-effect > >>>> of interfering with the cryptsetup password prompt. Sometimes the prompt > >>>> is several lines before the cursor with other messsages in between, and > >>>> sometimes it's actually overwritten completely. > >>>> > >>>> It'd be nice if status output would be suppressed/delayed while a > >>>> password prompty is active. > >>> > >>> You'll need something like plymouth to multiplex the input/output. > >>> > >>> http://web.dodds.net/~vorlon/wiki/blog/Plymouth_is_not_a_bootsplash/ > >> > >> In that case it'd be great if the systemd or the cryptsetup package > >> could recommend or suggest the appropriate package (plymouth?). > > > > Could you verify that plymouth solves your problem? > > Yes it did. Thank you! > I think systemd handles this case more gracefully nowadays, so having plymouth installed is no longer a necessity. I'm thus closing this bug report. A Recommends in systemd wouldn't actually help in any case, as systemd is installed during the initial bootstrap phase, where recommends are not considered and a hard Depends doesn't seem warranted. If we wanted to install plymouth by default, we should use another mechanism then having systemd recommend it. 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 Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Processed: found 793198 in 215-17+deb8u1
Processing commands for cont...@bugs.debian.org: > found 793198 215-17+deb8u1 Bug #793198 [src:systemd] systemd: poweroff, reboot without stopping services and unmounting Marked as found in versions systemd/215-17+deb8u1. > thanks Stopping processing here. Please contact me if you need assistance. -- 793198: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793198 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: Re: Bug#893054: systemd: System failed to boot after upgrade/install systemd from systemd:i386
Processing control commands: > tags -1 + moreinfo Bug #893054 [systemd] systemd: System failed to boot after upgrade/install systemd from systemd:i386 Added tag(s) moreinfo. -- 893054: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893054 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#775613: marked as done (systemd: why is /run/systemd/inhibit/1.ref inherited?)
Your message dated Sat, 24 Mar 2018 22:33:17 +0100
with message-id <61e51f6f-157c-63e1-b20a-bea2884ad...@debian.org>
and subject line Re: systemd: why is /run/systemd/inhibit/1.ref inherited?
has caused the Debian Bug report #775613,
regarding systemd: why is /run/systemd/inhibit/1.ref inherited?
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.)
--
775613: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775613
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd
Version: 215-9
Severity: normal
type=AVC msg=audit(1421538903.417:232): avc: denied { use } for pid=23546
comm="kded4" path="/run/systemd/inhibit/1.ref" dev="tmpfs" ino=91124
scontext=rjc:user_r:user_t:s0-s0:c0.c1023
tcontext=system_u:system_r:systemd_logind_t:s0 tclass=fd permissive=0
When I login via kdm the KDE user processes (and presumably user processes
from any other desktop environment) inherit /run/systemd/inhibit/1.ref.
Is this desired? If so why? I have SE Linux preventing it and everything
works.
-- Package-specific info:
-- System Information:
Debian Release: 8.0
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
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-58
ii libacl1 2.2.52-2
ii libaudit1 1:2.4-1+b1
ii libblkid1 2.25.2-4
ii libc6 2.19-13
ii libcap2 1:2.24-6
ii libcap2-bin 1:2.24-6
ii libcryptsetup4 2:1.6.6-4
ii libgcrypt20 1.6.2-4+b1
ii libkmod218-3
ii liblzma55.1.1alpha+20120614-2+b3
ii libpam0g1.1.8-3.1
ii libselinux1 2.3-2
ii libsystemd0 215-9
ii mount 2.25.2-4
ii sysv-rc 2.88dsf-58
ii udev215-9
ii util-linux 2.25.2-4
Versions of packages systemd recommends:
ii dbus1.8.14-1
ii libpam-systemd 215-9
Versions of packages systemd suggests:
pn systemd-ui
-- Configuration Files:
/etc/systemd/journald.conf changed:
[Journal]
SystemMaxUse=25M
-- no debconf information
--- End Message ---
--- Begin Message ---
On Thu, 1 Oct 2015 15:59:52 +1000 Russell Coker <russ...@coker.com.au>
wrote:
> On Thu, 1 Oct 2015 08:00:45 AM Michael Biebl wrote:
> > On Sun, 18 Jan 2015 11:07:40 +1100 Russell Coker <russ...@coker.com.au>
> > wrote:
> > > Package: systemd
> > > Version: 215-9
> > > Severity: normal
> > >
> > >
> > > type=AVC msg=audit(1421538903.417:232): avc: denied { use } for
> > > pid=23546 comm="kded4" path="/run/systemd/inhibit/1.ref" dev="tmpfs"
> > > ino=91124 scontext=rjc:user_r:user_t:s0-s0:c0.c1023
> > > tcontext=system_u:system_r:systemd_logind_t:s0 tclass=fd permissive=0
> > >
> > > When I login via kdm the KDE user processes (and presumably user
> > > processes from any other desktop environment) inherit
> > > /run/systemd/inhibit/1.ref.
> > >
> > > Is this desired? If so why? I have SE Linux preventing it and
> > > everything works.
> >
> > I'm not sure what the problem is here.
> > Can you elaborate?
>
> If a socket or pipe is inherited from a system process to a process running
> as
> a user there is a possibility of a security problem. Generally if there is
> no
> reason for such access to be granted then it should not be granted. The file
> handle could be closed before exec or it could be set to close on exec.
Please raise this issue upstream at
https://github.com/systemd/systemd/issues if it still persists in stretch.
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
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#876103: marked as done (systemd-nspawn: --read-only is broken)
Your message dated Sat, 24 Mar 2018 21:47:51 +0100 with message-id <5a21ca04-4b83-62a0-86d0-eb3c7b55e...@debian.org> and subject line Re: Bug#876103: systemd-nspawn: --read-only is broken has caused the Debian Bug report #876103, regarding systemd-nspawn: --read-only is broken 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.) -- 876103: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876103 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: systemd-container Version: 232-25+deb9u1 Severity: normal Dear Maintainer, on stretch, 'systemd-nspawn --read-only' fails to start the container entirely. Trivial test case: # machinectl pull-tar https://cloud-images.ubuntu.com/xenial/current/xenial-server-cloudimg-amd64-root.tar.gz [ output omitted ] # systemd-nspawn -M xenial-server-cloudimg-amd64-root -- true # systemd-nspawn -M xenial-server-cloudimg-amd64-root --read-only -- true Spawning container xenial-server-cloudimg-amd64-root on /var/lib/machines/xenial-server-cloudimg-amd64-root. Press ^] three times within 1s to kill container. Failed to create directory /var/lib/machines/xenial-server-cloudimg-amd64-root/sys: Read-only file system (the first systemd-nspawn call is there to implicitly create some directories inside the container root that must exist for read-only to work) The expected behavior is that 'true' is executed in container and exit status 0 is returned; however, the container is not started and the exit status is 1. There is an upstream fix for this in https://github.com/systemd/systemd/pull/4693 -- acbbf69b718260755a5dff60dd68ba239ac0d61b is the commit that actually fixes read-only containers, but it requires two other commits to apply cleanly. I applied the following sequence to systemd-container on stretch: https://github.com/systemd/systemd/commit/bdb4e0cb646ff33ecbb1cf4b502870f84bf4016d https://github.com/systemd/systemd/commit/4f086aab52812472a24c9b8b627589880a38696e https://github.com/systemd/systemd/commit/acbbf69b718260755a5dff60dd68ba239ac0d61b and it solved my problem. Could you backport these patches to stretch? -- System Information: Debian Release: 9.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-3-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages systemd-container depends on: ii dbus 1.10.18-1 ii libacl1 2.2.52-3+b1 ii libblkid12.29.2-1 ii libbz2-1.0 1.0.6-8.1 ii libc62.24-11+deb9u1 ii libcurl3-gnutls 7.52.1-5 ii libgcrypt20 1.7.6-2+deb9u2 ii libip4tc01.6.0+snapshot20161117-6 ii liblzma5 5.2.2-1.2+b1 ii libseccomp2 2.3.1-2.1 ii libselinux1 2.6-3+b1 ii systemd 232-25+deb9u1 ii zlib1g 1:1.2.8.dfsg-5 Versions of packages systemd-container recommends: ii btrfs-progs4.7.3-1 ii libnss-mymachines 232-25+deb9u1 systemd-container suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Hi Lauri, On Mon, 4 Dec 2017 09:29:17 +0200 Lauri Tirkkonen <la...@tuxera.com> wrote: > Hi, > > On Sun, Dec 03 2017 13:47:29 +0100, Michael Biebl wrote: > > > There is an upstream fix for this in > > > https://github.com/systemd/systemd/pull/4693 -- > > > acbbf69b718260755a5dff60dd68ba239ac0d61b is the commit that actually > > > fixes read-only containers, but it requires two other commits to apply > > > cleanly. I applied the following sequence to systemd-container on > > > stretch: > > > > > > https://github.com/systemd/systemd/commit/bdb4e0cb646ff33ecbb1cf4b502870f84bf4016d > > > https://github.com/systemd/systemd/commit/4f086aab52812472a24c9b8b627589880a38696e > > > https://github.com/systemd/systemd/commit/acbbf69b718260755a5dff60dd68ba239ac0d61b > > > > > > and it solved my problem. Could you backport these patches to stretch? > > > > > > > Those patches looks a bit invasive for a stretch stable upload. > > But we do provide updated systemd versions with this fix via > > stretch-backports: > > https://packages.debian.org/source/stable-backports/systemd > > > > Would that be sufficient for your case? > > It turned out that we nee
Processed: Re: Bug#893574: gnome-shell: Suspends after 20 minutes even if there is activity on a seat
Processing control commands: > reassign -1 systemd 238-2 Bug #893574 [gnome-shell] gnome-shell: Suspend after 20 minutes even there is activity on a seat Bug reassigned from package 'gnome-shell' to 'systemd'. No longer marked as found in versions gnome-shell/3.28.0-1. Ignoring request to alter fixed versions of bug #893574 to the same values previously set Bug #893574 [systemd] gnome-shell: Suspend after 20 minutes even there is activity on a seat Marked as found in versions systemd/238-2. -- 893574: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893574 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#831414: marked as done (systemd: learns IPv6 prefix from its own RAs and configures IP address on wrong interface)
Your message dated Fri, 23 Mar 2018 17:24:02 +0100
with message-id <d224da26-a84c-6aa7-2843-53a9aac69...@debian.org>
and subject line Re: Bug#831414: systemd: learns IPv6 prefix from its own RAs
and configures IP address on wrong interface
has caused the Debian Bug report #831414,
regarding systemd: learns IPv6 prefix from its own RAs and configures IP
address on wrong interface
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.)
--
831414: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831414
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd
Version: 230-5pitti1
Severity: minor
Tags: ipv6
Hi,
I am filing this as severity minor because this bug is in a version
that is not officially in Debian. I am filing it nevertheless because
systemd with this IPv6 user space code active should not be in Debian.
If this were an official version, this would be an important bug, with
the potential for "serious" at maintainer discretion.
While following up Martin's requests for #815793 and #815884, I have
found new misbehsvior regarding IPv6.
Given a host that also acts as a router, with the following network
setup:
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP
link/ether 54:04:a6:82:21:00 brd ff:ff:ff:ff:ff:ff
inet 192.168.182.250/32 brd 192.168.182.250 scope global eth0
valid_lft forever preferred_lft forever
inet 192.168.182.29/24 brd 192.168.182.255 scope global dynamic eth0
valid_lft 12650sec preferred_lft 12650sec
inet6 2001:db8:0:3282:5604:a6ff:fe82:2100/64 scope global mngtmpaddr
noprefixroute dynamic
valid_lft 86309sec preferred_lft 14309sec
inet6 2001:db8:0:3282::1d:250/128 scope global
valid_lft forever preferred_lft forever
inet6 2001:db8:0:3282::1d:100/64 scope global
valid_lft forever preferred_lft forever
inet6 fe80::5604:a6ff:fe82:2100/64 scope link
valid_lft forever preferred_lft forever
3: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group
default qlen 1000
link/ether c6:f4:98:dc:5e:21 brd ff:ff:ff:ff:ff:ff
inet 192.168.29.254/24 brd 192.168.29.255 scope global br0
valid_lft forever preferred_lft forever
inet6 2001:db8:0:328d::1d:153/64 scope global
valid_lft forever preferred_lft forever
inet6 2001:db8:0:328d::1d:100/64 scope global
valid_lft forever preferred_lft forever
inet6 fec0:0:0:::3/128 scope site
valid_lft forever preferred_lft forever
inet6 fec0:0:0:::2/128 scope site
valid_lft forever preferred_lft forever
inet6 fec0:0:0:::1/128 scope site
valid_lft forever preferred_lft forever
inet6 fe80::c4f4:98ff:fedc:5e21/64 scope link
valid_lft forever preferred_lft forever
On br0, there is a radvd, advertising a prefix on br0:
interface br0 {
AdvSendAdvert on;
MinRtrAdvInterval 600;
MaxRtrAdvInterval 1200;
prefix 2001:db8:0:328d::/64 {
DeprecatePrefix on;
};
RDNSS 2001:db8:0:328d::1d:153 {
AdvRDNSSLifetime 1200;
};
};
When the radvd is started, the local host seems to learn the prefix
from the locally running radvd and _configures_ _it_ _on_ _eth0_,
which is plain wrong:
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP gr
oup default qlen 1000
link/ether 54:04:a6:82:21:00 brd ff:ff:ff:ff:ff:ff
inet 192.168.182.250/32 brd 192.168.182.250 scope global eth0
valid_lft forever preferred_lft forever
inet 192.168.182.29/24 brd 192.168.182.255 scope global dynamic eth0
valid_lft 12530sec preferred_lft 12530sec
inet6 2001:db8:0:328d:5604:a6ff:fe82:2100/64 scope global mngtmpaddr
noprefixroute dynamic
valid_lft 86390sec preferred_lft 14390sec
inet6 2001:db8:0:3282:5604:a6ff:fe82:2100/64 scope global mngtmpaddr
noprefixroute dynamic
valid_lft 86189sec preferred_lft 14189sec
inet6 2001:db8:0:3282::1d:250/128 scope global
valid_lft forever preferred_lft forever
inet6 2001:db8:0:3282::1d:100/64 scope global
valid_lft forever preferred_lft forever
inet6 fe80::5604:a6ff:fe82:2100/64 scope link
valid_lft forever preferred_lft forever
It also learns a default route pointing to its own link local IP
address on br0:
[2/502]mh@fan:~$ ip -6 r
2001:db8:0:3282::1d:250 dev eth0 proto kernel metric 256 pref medium
2001:db8:0:3282::/64 dev eth0 proto kernel metric 256 pref medium
2001:db8:0:3282::/64 dev eth0 proto ra metric 1024 pref medium
2001:db8:0:328d::/64 dev b
Processed: bug 868159 is forwarded to https://github.com/systemd/systemd/issues/8566
Processing commands for cont...@bugs.debian.org: > forwarded 868159 https://github.com/systemd/systemd/issues/8566 Bug #868159 [systemd] systemd-setup-tmpfiles startup error when /srv is on read-only fs Set Bug forwarded-to-address to 'https://github.com/systemd/systemd/issues/8566'. > thanks Stopping processing here. Please contact me if you need assistance. -- 868159: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868159 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: Re: Bug#875557: systemd: service mark as enabled but not in reality
Processing control commands: > tags -1 + moreinfo Bug #875557 [systemd] systemd: service mark as enabled but not in reality Added tag(s) moreinfo. -- 875557: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875557 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#863710: marked as done (journald's most recent entries)
Your message dated Fri, 23 Mar 2018 17:03:19 +0100 with message-id <917a9097-0c17-577d-d435-f4154b9fc...@debian.org> and subject line Re: Bug#863710: journald's most recent entries has caused the Debian Bug report #863710, regarding journald's most recent entries 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.) -- 863710: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863710 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: systemd Version: 215-17+deb8u6 Severity: normal Dear Maintainer, I have tried to retrieve recent journal entries (with matching fields), but the retrieved entries were not the most recent ones: $ journalctl OBJECT_ID=50483 -n 15 | tail -n 1 | cut -c 1-15 May 29 23:05:13 $ journalctl OBJECT_ID=50483 -n 14 | tail -n 1 | cut -c 1-15 May 29 23:05:13 $ journalctl OBJECT_ID=50483 -n 13 | tail -n 1 | cut -c 1-15 May 30 03:04:57 $ journalctl OBJECT_ID=50483 -n 12 | tail -n 1 | cut -c 1-15 May 30 07:05:03 $ journalctl OBJECT_ID=50483 -n 11 | tail -n 1 | cut -c 1-15 May 30 07:05:03 $ journalctl OBJECT_ID=50483 -n 12 | tail -n 1 | cut -c 1-15 May 30 07:05:03 $ journalctl OBJECT_ID=50483 -n 13 | tail -n 1 | cut -c 1-15 May 30 03:04:57 $ journalctl OBJECT_ID=50483 -n 14 | tail -n 1 | cut -c 1-15 May 29 23:05:13 $ journalctl OBJECT_ID=50483 -n 15 | tail -n 1 | cut -c 1-15 May 29 23:05:13 Here is another example, a bit redacted (any is identical to another : the same few messages get inserted there roughly every 4 hours): $ journalctl OBJECT_ID=50482 -n 1 -- Logs begin at Sat 2017-05-27 15:00:01 MSK, end at Tue 2017-05-30 11:09:13 MSK. -- May 30 07:03:49 mars mmdb[131728]: $ journalctl OBJECT_ID=50482 -n 2 -- Logs begin at Sat 2017-05-27 15:00:01 MSK, end at Tue 2017-05-30 11:09:14 MSK. -- May 30 03:04:11 mars mmdb[131728]: May 30 03:04:11 mars mmsocks[946]: $ journalctl OBJECT_ID=50482 -n 3 -- Logs begin at Sat 2017-05-27 15:00:01 MSK, end at Tue 2017-05-30 11:09:22 MSK. -- May 29 23:04:18 mars mmdb[131728]: May 29 23:04:19 mars mmsocks[946]: May 29 23:05:19 mars rtms4[35053]: $ journalctl OBJECT_ID=50482 -n 4 -- Logs begin at Sat 2017-05-27 15:00:01 MSK, end at Tue 2017-05-30 11:09:26 MSK. -- May 29 19:06:03 mars mmdb[131728]: May 29 19:06:03 mars mmsocks[946]: May 29 19:07:03 mars rtms4[27816]: May 29 19:07:03 mars mmsocks[946]: Repeating the same commands led to same results, as in the first example. After that, new messages were inserted, and it got shifted: $ journalctl OBJECT_ID=50482 -n 1 -- Logs begin at Sat 2017-05-27 15:00:01 MSK, end at Tue 2017-05-30 11:20:31 MSK. -- May 30 11:10:06 mars mmdb[131728]: $ journalctl OBJECT_ID=50482 -n 2 -- Logs begin at Sat 2017-05-27 15:00:01 MSK, end at Tue 2017-05-30 11:21:14 MSK. -- May 30 07:03:49 mars mmdb[131728]: May 30 07:03:51 mars mmsocks[946]: It doesn't seem to happen with OBJECT_ID's where the messages are not as repetitive. And it works fine if the `-n` option is not specified, or if its argument is greater than the amount of messages for a given OBJECT_ID. Looks like a similar behaviour can be reproduced using systemd units and shell scripts (just printing the same messages), with no custom fields or programs, but I wasn't able to get a clean example (got a few attempts mixed together the only time when it worked that way, and then it got fixed on its own -- unlike the above examples). The default /etc/systemd/journald.conf was used. -- Package-specific info: -- System Information: Debian Release: 8.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/32 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.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+deb8u7 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+deb8u2 ii libkmod218-3 ii liblzma55.1.1alpha+20120614-2+b3 ii libpam0g1.1.8-3.1+deb8u2 ii libselinux1 2.3-2 ii libsystemd0 215-17+deb8u6 ii mount 2.25.2-6 ii sysv-rc 2.88dsf-59 ii udev215-17+deb8u6 ii util-linux 2.25.2-6 Versions of packages systemd recommends: ii dbus1.8.22-0+deb8u1 pn libpam-systemd Versions of packages s
Processed: Re: journalctl too slow
Processing control commands: > tags -1 + moreinfo Bug #803524 [systemd] journalctl too slow Added tag(s) moreinfo. -- 803524: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803524 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: Re: Bug#893605: warning: #warning "Consider adding the right mmap() syscall definitions here!" [-Wcpp]
Processing control commands: > notforwarded -1 Bug #893605 [src:systemd] warning: #warning "Consider adding the right mmap() syscall definitions here!" [-Wcpp] Unset Bug forwarded-to-address -- 893605: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893605 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: Bug #892794 in systemd marked as pending
Processing control commands: > tag -1 pending Bug #892794 [systemd] systemd-networkd fails to configure IPv6 without MTU from RA Bug #892651 [systemd] networkd: no IPv6 default route after point release Added tag(s) pending. Added tag(s) pending. -- 892651: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892651 892794: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892794 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: [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 #883690 (http://bugs.debian.org/883690)
> # Bug title: systemd Caught , "Freezing execution", __libc_fatal("***
> %n in writable segment detected ***\n") after execute asprintf(,
> "U\002%c%s%n"... in src/core/manager.c:2404
> # * https://github.com/systemd/systemd/issues/8483
> # * remote status changed: (?) -> closed
> # * closed upstream
> tags 883690 + fixed-upstream
Bug #883690 [systemd] systemd Caught , "Freezing execution",
__libc_fatal("*** %n in writable segment detected ***\n") after execute
asprintf(, "U\002%c%s%n"... in src/core/manager.c:2404
Added tag(s) fixed-upstream.
> usertags 883690 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
883690: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883690
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#893602: marked as done (macro.h:423:18: error: expected ')' before '__attribute__')
Your message dated Tue, 20 Mar 2018 23:21:59 + with message-id <e1eyqzr-000ikk...@fasolo.debian.org> and subject line Bug#893426: fixed in systemd 238-3 has caused the Debian Bug report #893426, regarding macro.h:423:18: error: expected ')' before '__attribute__' 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.) -- 893426: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893426 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: systemd Version: 238-2 Severity: important User: debian-m...@lists.debian.org Usertags: mipsel For some reason I cannot build systemd on a sid/mipsel system (sid schroot on eller.d.o): [7/1280] Compiling C object 'src/journal/journal-client@sta/sd-journal.c.o'. FAILED: src/journal/journal-client@sta/sd-journal.c.o cc -Isrc/journal/journal-client@sta -Isrc/journal -I../src/journal -I. -I../ -Isrc/libsystemd-network -I../src/libsystemd-network -I../src/libsystemd/sd-network -I../src/libsystemd/sd-netlink -I../src/libsystemd/sd-id128 -I../src/libsystemd/sd-hwdb -I../src/libsystemd/sd-device -I../src/libsystemd/sd-bus -Isrc/core -I../src/core -Isrc/libudev -I../src/libudev -Isrc/udev -I../src/udev -Isrc/login -I../src/login -Isrc/timesync -I../src/timesync -Isrc/resolve -I../src/resolve -Isrc/systemd -I../src/systemd -Isrc/shared -I../src/shared -Isrc/basic -I../src/basic -flto -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -std=gnu99 -Wextra -Werror=undef -Wlogical-op -Wmissing-include-dirs -Wold-style-definition -Wpointer-arith -Winit-self -Wdeclaration-after-statement -Wfloat-equal -Wsuggest-attribute=noreturn -Werror=missing-prototypes -Werror=implicit-function-declaration -Werror=missing-declarations -Werror=return-type -Werror=incompatible-pointer-types -Werror=format=2 -Wstrict-prototypes -Wredundant-decls -Wmissing-noreturn -Wimplicit-fallthrough=5 -Wshadow -Wendif-labels -Wstrict-aliasing=2 -Wwrite-strings -Werror=overflow -Wdate-time -Wnested-externs -ffast-math -fno-common -fdiagnostics-show-option -fno-strict-aliasing -fvisibility=hidden -fstack-protector -fstack-protector-strong --param=ssp-buffer-size=4 -fPIE -Wno-unused-parameter -Wno-missing-field-initializers -Wno-unused-result -Wno-format-signedness -Wno-error=nonnull -Werror=shadow -ffunction-sections -fdata-sections -include config.h -g -O2 -fdebug-prefix-map=/home/malat/systemd-238=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -fvisibility=default -MD -MQ 'src/journal/journal-client@sta/sd-journal.c.o' -MF 'src/journal/journal-client@sta/sd-journal.c.o.d' -o 'src/journal/journal-client@sta/sd-journal.c.o' -c ../src/journal/sd-journal.c In file included from ../src/basic/alloc-util.h:28:0, from ../src/journal/sd-journal.c:33: ../src/basic/macro.h:423:18: error: expected ')' before '__attribute__' #define noreturn __attribute__((noreturn)) ^ In file included from /usr/include/gcrypt.h:30:0, from ../src/journal/journal-file.h:26, from ../src/journal/sd-journal.c:46: /usr/include/mipsel-linux-gnu/gpg-error.h:1545:46: error: expected ',' or ';' before ')' token void gpgrt_log_bug (const char *fmt, ...)GPGRT_ATTR_NR_PRINTF(1,2); ^ In file included from ../src/basic/alloc-util.h:28:0, from ../src/journal/sd-journal.c:33: ../src/basic/macro.h:423:18: error: expected ')' before '__attribute__' #define noreturn __attribute__((noreturn)) ^ In file included from /usr/include/gcrypt.h:30:0, from ../src/journal/journal-file.h:26, from ../src/journal/sd-journal.c:46: /usr/include/mipsel-linux-gnu/gpg-error.h:1546:46: error: expected ',' or ';' before ')' token void gpgrt_log_fatal (const char *fmt, ...) GPGRT_ATTR_NR_PRINTF(1,2); ^ In file included from ../src/basic/alloc-util.h:28:0, from ../src/journal/sd-journal.c:33: ../src/basic/macro.h:423:18: error: expected ')' before '__attribute__' #define noreturn __attribute__((noreturn)) ^ In file included from /usr/include/gcrypt.h:30:0, from ../src/journal/journal-file.h:26, from ../src/journal/sd-journal.c:46: /usr/include/mipsel-linux-gnu/gpg-error.h:1558:43: error: expected ',' or ';' before ')' token const char *func) GPGRT_ATTR_NORETURN; ^ ninja: build stopped: subcommand failed. --- End Message --- --- Begin M
Bug#881769: marked as done (udev: Docs on upgrading to predictable network interface names don't work)
Your message dated Tue, 20 Mar 2018 23:21:59 + with message-id <e1eyqzr-000ik2...@fasolo.debian.org> and subject line Bug#881769: fixed in systemd 238-3 has caused the Debian Bug report #881769, regarding udev: Docs on upgrading to predictable network interface names don't work 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.) -- 881769: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881769 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: udev Version: 232-25+deb9u1 Severity: normal Tags: patch Hi, The stretch README.Debian.gz for udev omits mention that update-initramfs -u must be run after changing configuration files when converting to the new "predictable network interface names". Attached is a patch which clarifies the README.Debian. Note also that the upgrade process would be greatly simplified if there was a tool which reported the default "predictable network interface name"s, along with their MAC address for mapping to existing network interface names. Regards, Karl -- Package-specific info: -- System Information: Debian Release: 9.0 APT prefers stable APT policy: (500, 'stable'), (500, 'oldstable') Architecture: amd64 (x86_64) P: /devices/LNXSYSTM:00 E: DEVPATH=/devices/LNXSYSTM:00 E: MODALIAS=acpi:LNXSYSTM: E: SUBSYSTEM=acpi P: /devices/LNXSYSTM:00/LNXCPU:00 E: DEVPATH=/devices/LNXSYSTM:00/LNXCPU:00 E: MODALIAS=acpi:LNXCPU: E: SUBSYSTEM=acpi P: /devices/LNXSYSTM:00/LNXCPU:01 E: DEVPATH=/devices/LNXSYSTM:00/LNXCPU:01 E: MODALIAS=acpi:LNXCPU: E: SUBSYSTEM=acpi P: /devices/LNXSYSTM:00/LNXCPU:02 E: DEVPATH=/devices/LNXSYSTM:00/LNXCPU:02 E: MODALIAS=acpi:LNXCPU: E: SUBSYSTEM=acpi P: /devices/LNXSYSTM:00/LNXCPU:03 E: DEVPATH=/devices/LNXSYSTM:00/LNXCPU:03 E: MODALIAS=acpi:LNXCPU: E: SUBSYSTEM=acpi P: /devices/LNXSYSTM:00/LNXPWRBN:00 E: DEVPATH=/devices/LNXSYSTM:00/LNXPWRBN:00 E: DRIVER=button E: MODALIAS=acpi:LNXPWRBN: E: SUBSYSTEM=acpi P: /devices/LNXSYSTM:00/LNXPWRBN:00/input/input6 E: DEVPATH=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input6 E: EV=3 E: ID_FOR_SEAT=input-acpi-LNXPWRBN_00 E: ID_INPUT=1 E: ID_INPUT_KEY=1 E: ID_PATH=acpi-LNXPWRBN:00 E: ID_PATH_TAG=acpi-LNXPWRBN_00 E: KEY=10 0 E: MODALIAS=input:b0019vp0001e-e0,1,k74,ramlsfw E: NAME="Power Button" E: PHYS="LNXPWRBN/button/input0" E: PRODUCT=19/0/1/0 E: PROP=0 E: SUBSYSTEM=input E: TAGS=:seat: E: USEC_INITIALIZED=938931 P: /devices/LNXSYSTM:00/LNXPWRBN:00/input/input6/event3 N: input/event3 E: BACKSPACE=guess E: DEVNAME=/dev/input/event3 E: DEVPATH=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input6/event3 E: ID_INPUT=1 E: ID_INPUT_KEY=1 E: ID_PATH=acpi-LNXPWRBN:00 E: ID_PATH_TAG=acpi-LNXPWRBN_00 E: MAJOR=13 E: MINOR=67 E: SUBSYSTEM=input E: TAGS=:power-switch: E: USEC_INITIALIZED=879724 E: XKBLAYOUT=us E: XKBMODEL=pc105 E: XKBOPTIONS=terminate:ctrl_alt_bksp P: /devices/LNXSYSTM:00/LNXSYBUS:00 E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00 E: MODALIAS=acpi:LNXSYBUS: E: SUBSYSTEM=acpi P: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0103:00 E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0103:00 E: MODALIAS=acpi:PNP0103: E: SUBSYSTEM=acpi P: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00 E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00 E: MODALIAS=acpi:PNP0A03: E: SUBSYSTEM=acpi P: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:00 E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:00 E: SUBSYSTEM=acpi P: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:01 E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:01 E: SUBSYSTEM=acpi P: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:02 E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:02 E: SUBSYSTEM=acpi P: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:03 E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:03 E: SUBSYSTEM=acpi P: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:04 E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:04 E: SUBSYSTEM=acpi P: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:05 E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:05 E: SUBSYSTEM=acpi P: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:06 E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:06 E: SUBSYSTEM=acpi P: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:07 E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:07 E: SUBSYSTEM=acpi P: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:07/PNP:00 E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:07/PNP:00 E: MODALIA
Bug#888126: marked as done ([patch] Please enable systemd-sysusers unit)
Your message dated Tue, 20 Mar 2018 23:21:59 + with message-id <e1eyqzr-000ik8...@fasolo.debian.org> and subject line Bug#888126: fixed in systemd 238-3 has caused the Debian Bug report #888126, regarding [patch] Please enable systemd-sysusers unit 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.) -- 888126: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888126 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- package: systemd version: 236-3 Dear systemd team, please enable the systemd-sysuser.service unit. The rational is that users who want to use this inside their containers/deployments can do so. Attached is a (trivial) patch to enable the unit. It is also documented widely and the fact that it does not work on Debian (and Ubuntu) is slightly surprising. There is no downside (AFAICS), the unit is conditiional on ConditionNeedsUpdate=/etc so it will never run on default Debian systems. I also looked into providing debian specific basic.conf that would re-generate the base-passwd passwd.master (and group) file. However it looks like the systemd-sysusers file format is not expressive enough for this (which is slightly unfortunate). I.e. we have entries like sync:*:4:65534:sync:/bin:/bin/sync which cannot be represented because you cannot specify a different primary gid in the sysusers file (or a login shell). So extra work is required for this but (personally) I would love to this is. Thanks for your consideration! Michael >From 69af77164ce2eb9bdddfce1c397b9b0c1ae7da55 Mon Sep 17 00:00:00 2001 From: Michael Vogt <m...@ubuntu.com> Date: Tue, 23 Jan 2018 15:55:38 +0100 Subject: [PATCH] Enable sysusers service units This allows users who want to use /usr/lib/sysusers.d/* to use it together with an empty /etc. Note that this PR does not ship any sysuser.d files. It is up to the user to provide those. --- debian/rules | 1 - 1 file changed, 1 deletion(-) diff --git a/debian/rules b/debian/rules index 0389867ec..0cc4b85ec 100755 --- a/debian/rules +++ b/debian/rules @@ -216,7 +216,6 @@ override_dh_install: find debian/install/*/etc/systemd/system/ -type l -delete # FIXME: generate proper sysusers.d/basic.conf for Debian, and add autopkgtest rm -rf debian/install/*/usr/lib/sysusers.d/* - rm -f debian/install/*/lib/systemd/system/*sysusers*.service debian/install/*/lib/systemd/system/*/*sysusers*.service ifeq (, $(filter noudeb, $(DEB_BUILD_PROFILES))) dh_install -pudev-udeb -plibudev1-udeb --sourcedir=debian/install/udeb endif -- 2.14.1 --- End Message --- --- Begin Message --- Source: systemd Source-Version: 238-3 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 888...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Biebl <bi...@debian.org> (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: Tue, 20 Mar 2018 23:22:57 +0100 Source: systemd Binary: systemd systemd-sysv systemd-container systemd-journal-remote systemd-coredump systemd-tests libpam-systemd libnss-myhostname libnss-mymachines libnss-resolve libnss-systemd libsystemd0 libsystemd-dev udev libudev1 libudev-dev udev-udeb libudev1-udeb Architecture: source Version: 238-3 Distribution: unstable Urgency: medium Maintainer: Debian systemd Maintainers <pkg-systemd-maintainers@lists.alioth.debian.org> Changed-By: Michael Biebl <bi...@debian.org> Description: libnss-myhostname - nss module providing fallback resolution for the current hostname libnss-mymachines - nss module to resolve hostnames for local container instances libnss-resolve - nss module to resolve names via systemd-resolved libnss-systemd - nss module providing dynamic user and group name resolution libpam-systemd - system and service manager - PAM module libsystemd-dev - systemd utility library - development files libsystemd0 - systemd utility library libudev-dev - libudev development files libudev1 - libudev shared library libudev1-udeb - libudev shared library (udeb) systemd- sy
Processed: severity of 893605 is normal
Processing commands for cont...@bugs.debian.org: > severity 893605 normal Bug #893605 [src:systemd] warning: #warning "Consider adding the right mmap() syscall definitions here!" [-Wcpp] Severity set to 'normal' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 893605: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893605 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: reassign 893426 to src:systemd, forcibly merging 893426 893602
Processing commands for cont...@bugs.debian.org: > reassign 893426 src:systemd Bug #893426 [systemd] systemd FTBFS: syntax error close to GPGRT_ATTR_NORETURN Bug reassigned from package 'systemd' to 'src:systemd'. No longer marked as found in versions systemd/238-1. Ignoring request to alter fixed versions of bug #893426 to the same values previously set > forcemerge 893426 893602 Bug #893426 [src:systemd] systemd FTBFS: syntax error close to GPGRT_ATTR_NORETURN Bug #893602 [src:systemd] macro.h:423:18: error: expected ')' before '__attribute__' Set Bug forwarded-to-address to 'https://github.com/systemd/systemd/pull/8456'. Severity set to 'serious' from 'important' Added indication that 893602 affects systemd Added tag(s) pending and patch. Bug #893426 [src:systemd] systemd FTBFS: syntax error close to GPGRT_ATTR_NORETURN Marked as found in versions systemd/238-2. Added tag(s) confirmed. Merged 893426 893602 > thanks Stopping processing here. Please contact me if you need assistance. -- 893426: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893426 893602: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893602 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 (with 1 error): Re: macro.h:423:18: error: expected ')' before '__attribute__'
Processing control commands: > forcemerge 893426 -1 Bug #893426 [systemd] systemd FTBFS: syntax error close to GPGRT_ATTR_NORETURN Unable to merge bugs because: package of #893602 is 'src:systemd' not 'systemd' Failed to forcibly merge 893426: Did not alter merged bugs. -- 893426: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893426 893602: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893602 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: Re: Bug#893602: Acknowledgement (macro.h:423:18: error: expected ')' before '__attribute__')
Processing control commands: > tags -1 confirmed fixed-upstream Bug #893602 [src:systemd] macro.h:423:18: error: expected ')' before '__attribute__' Added tag(s) fixed-upstream and confirmed. -- 893602: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893602 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: Re: Buck-passing
Processing control commands:
> tags -1 moreinfo
Bug #883690 [systemd] systemd Caught , "Freezing execution",
__libc_fatal("*** %n in writable segment detected ***\n") after execute
asprintf(, "U\002%c%s%n"... in src/core/manager.c:2404
Added tag(s) moreinfo.
--
883690: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883690
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: bug 883690 is forwarded to https://github.com/systemd/systemd/issues/8483
Processing commands for cont...@bugs.debian.org:
> forwarded 883690 https://github.com/systemd/systemd/issues/8483
Bug #883690 [systemd] systemd Caught , "Freezing execution",
__libc_fatal("*** %n in writable segment detected ***\n") after execute
asprintf(, "U\002%c%s%n"... in src/core/manager.c:2404
Set Bug forwarded-to-address to
'https://github.com/systemd/systemd/issues/8483'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
883690: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883690
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 884788
Processing commands for cont...@bugs.debian.org: > tags 884788 + wontfix Bug #884788 [systemd] systemd-ask-password echos password as stars (*) while decrypting LUKS partition Added tag(s) wontfix. > thanks Stopping processing here. Please contact me if you need assistance. -- 884788: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884788 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: Bug #893426 in systemd marked as pending
Processing control commands: > tag -1 pending Bug #893426 [systemd] systemd FTBFS: syntax error close to GPGRT_ATTR_NORETURN Added tag(s) pending. -- 893426: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893426 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: Bug #893282 in systemd marked as pending
Processing control commands: > tag -1 pending Bug #893282 [systemd] systemd: SuccessAction=reboot in wrong stanza in /lib/systemd/system/system-update-cleanup.service Added tag(s) pending. -- 893282: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893282 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: Re: Processed: Re: Processed: Re: Bug#893426: systemd FTBFS: syntax error close to GPGRT_ATTR_NORETURN
Processing control commands: > tags -1 fixed-upstream patch Bug #893426 [systemd] systemd FTBFS: syntax error close to GPGRT_ATTR_NORETURN Added tag(s) fixed-upstream and patch. > forwarded -1 https://github.com/systemd/systemd/pull/8456 Bug #893426 [systemd] systemd FTBFS: syntax error close to GPGRT_ATTR_NORETURN Set Bug forwarded-to-address to 'https://github.com/systemd/systemd/pull/8456'. -- 893426: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893426 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: severity of 893369 is important
Processing commands for cont...@bugs.debian.org: > severity 893369 important Bug #893369 [systemd] systemd-udevd is killed at startup Severity set to 'important' from 'critical' > thanks Stopping processing here. Please contact me if you need assistance. -- 893369: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893369 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: Re: Processed: Re: Bug#893426: systemd FTBFS: syntax error close to GPGRT_ATTR_NORETURN
Processing control commands: > reassign -1 systemd Bug #893426 [libgpg-error-dev] systemd FTBFS: syntax error close to GPGRT_ATTR_NORETURN Bug reassigned from package 'libgpg-error-dev' to 'systemd'. No longer marked as found in versions libgpg-error/1.28-1. Ignoring request to alter fixed versions of bug #893426 to the same values previously set > found -1 238-1 Bug #893426 [systemd] systemd FTBFS: syntax error close to GPGRT_ATTR_NORETURN Marked as found in versions systemd/238-1. -- 893426: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893426 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: Re: Bug#893426: systemd FTBFS: syntax error close to GPGRT_ATTR_NORETURN
Processing control commands: > reassign -1 libgpg-error-dev Bug #893426 [systemd] systemd FTBFS: syntax error close to GPGRT_ATTR_NORETURN Bug reassigned from package 'systemd' to 'libgpg-error-dev'. No longer marked as found in versions systemd/238-2. Ignoring request to alter fixed versions of bug #893426 to the same values previously set > found -1 1.28-1 Bug #893426 [libgpg-error-dev] systemd FTBFS: syntax error close to GPGRT_ATTR_NORETURN Marked as found in versions libgpg-error/1.28-1. > affects -1 + systemd Bug #893426 [libgpg-error-dev] systemd FTBFS: syntax error close to GPGRT_ATTR_NORETURN Added indication that 893426 affects systemd -- 893426: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893426 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: Bug #881769 in systemd marked as pending
Processing control commands: > tag -1 pending Bug #881769 [udev] udev: Docs on upgrading to predictable network interface names don't work Added tag(s) pending. -- 881769: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881769 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: bug 893282 is forwarded to https://github.com/systemd/systemd/issues/8477
Processing commands for cont...@bugs.debian.org: > forwarded 893282 https://github.com/systemd/systemd/issues/8477 Bug #893282 [systemd] systemd: SuccessAction=reboot in wrong stanza in /lib/systemd/system/system-update-cleanup.service Set Bug forwarded-to-address to 'https://github.com/systemd/systemd/issues/8477'. > thanks Stopping processing here. Please contact me if you need assistance. -- 893282: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893282 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#852461: marked as done (systemd: Creating scopes with systemd-run unreliable)
Your message dated Sat, 17 Mar 2018 14:59:30 +0100 with message-id <3ce1c79f-2816-d46b-9867-2bdc66d84...@debian.org> and subject line Re: Bug#852461: systemd: Creating scopes with systemd-run unreliable has caused the Debian Bug report #852461, regarding systemd: Creating scopes with systemd-run unreliable 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.) -- 852461: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852461 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: systemd Version: 215-17+deb8u5 Severity: normal Dear Maintainer, The creation of scopes with systemd-run --scope is unreliable. It seems to depend on system "load" or some other factors affected by system "load". On production systems we've seen an error rate of up to 20%. It feels the same like the often needed patches for software to reliable connect to unix sockets under high-load. It would be nice if systemd-run --scope would retry the dbus/unix-socket connect a few times as the error is only temporary. % for i in `seq 50`; do (systemd-run --scope -- sleep 5 2>&1 ) & done 2>&1 |grep -ni failed # First execution 3:Failed to create message: Input/output error 22:Failed to create message: Input/output error 49:Failed to create message: Input/output error # Second execution 14:Failed to create message: Input/output error 28:Failed to create message: Input/output error 41:Failed to create message: Input/output error % systemd-run --scope -- sleep 1; echo $? Failed to create message: Input/output error 1 ps.: i had to manually corrected the system information because reportbug is not possible on our production servers. gebi -- System Information: Debian Release: 8.6 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.36-1+deb8u2 (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 Init: systemd --- End Message --- --- Begin Message --- Version: 230-1 On Mon, 30 Jan 2017 12:41:25 +0100 Michael Biebl <bi...@debian.org> wrote: > Am 28.01.2017 um 00:02 schrieb Michael Biebl: > > > > > > Am 27. Januar 2017 21:16:52 MEZ schrieb Michael Gebetsroither > > <mich...@mgeb.org>: > >> On 2017-01-27 20:50, Michael Biebl wrote: > >> > >>>> The error sent from systemd back to systemd-run seems to be: > >>>> "Unit run-24908.scope already exists." > >>> > >>> > >>> Could you check if you have many scope units in /run which could slow > >> down systemd > >> > >> # find /run/systemd/system/ -type f -iname '*.scope' |wc -l > >> 1440 > > > > Does the problem go away if you clean up stale scope units? > > > > This might be related to https://github.com/systemd/systemd/issues/1961 > > I fear though that https://github.com/systemd/systemd/pull/3191 might be > too invasive for a backport to jessie stable. I'm pretty sure, the issue Michael was seeing is fixed by PR 3191 which landed in v230. I'm thus closing it for this version. 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 Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Processed: fixed 876103 in 233-1
Processing commands for cont...@bugs.debian.org: > fixed 876103 233-1 Bug #876103 [systemd-container] systemd-nspawn: --read-only is broken There is no source info for the package 'systemd-container' at version '233-1' with architecture '' Unable to make a source version for version '233-1' Marked as fixed in versions 233-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 876103: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876103 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: reopening 876103
Processing commands for cont...@bugs.debian.org:
> reopen 876103
Bug #876103 {Done: Michael Biebl <bi...@debian.org>} [systemd-container]
systemd-nspawn: --read-only is broken
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 233-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
876103: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876103
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: closing 876103
Processing commands for cont...@bugs.debian.org: > close 876103 Bug #876103 [systemd-container] systemd-nspawn: --read-only is broken Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 876103: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876103 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#888955: marked as done (open-vm-tools.service 10.2.0 does not start on boot on jessie/stretch/etc)
Your message dated Sat, 17 Mar 2018 03:12:26 +0100 with message-id <b2329588-25b9-b7f5-d4a4-9e1d3e56e...@debian.org> and subject line Re: Bug#888955: open-vm-tools.service 10.2.0 does not start on boot on jessie/stretch/etc has caused the Debian Bug report #888955, regarding open-vm-tools.service 10.2.0 does not start on boot on jessie/stretch/etc 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.) -- 888955: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888955 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: open-vm-tools Version: 2:10.2.0-2 Severity: important Dear Maintainer, here all systems on vSphere 6.0/6.5 fail to start open-vm-tools.service on boot. The only thing I see is: # systemctl status open-vm-tools.service ● open-vm-tools.service - Service for virtual machines hosted on VMware Loaded: loaded (/lib/systemd/system/open-vm-tools.service; enabled) Active: failed (Result: resources) Docs: http://open-vm-tools.sourceforge.net/about.php This happens on jessie and stretch: Stretch: Works: 2:10.1.5-5055683-4+deb9u1 Fails: 2:10.2.0-2~bpo9+1 Jessie: Works: 2:9.4.6-1770165-8 Works: 2:10.1.5-5055683-4+deb9u1~bpo8+1 Fails: 2:10.2.0-2~bpo8+1 (jessie-bpo-sloppy) -- System Information: Debian Release: 9.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-5-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages open-vm-tools depends on: ii iproute2 4.9.0-1+deb9u1 ii libc6 2.24-11+deb9u1 ii libdrm2 2.4.74-1 ii libdumbnet1 1.12-7+b1 ii libfuse2 2.9.7-1 ii libgcc1 1:6.3.0-18 ii libglib2.0-0 2.50.3-2 ii libicu57 57.1-6+deb9u1 ii libmspack0 0.5-1+deb9u1 ii libssl1.1 1.1.0f-3+deb9u1 ii libstdc++6 6.3.0-18 ii libudev1 232-25+deb9u1 ii libxml2 2.9.4+dfsg1-2.2+deb9u2 ii libxmlsec1 1.2.23-0.1 ii libxmlsec1-openssl 1.2.23-0.1 ii libxslt1.1 1.1.29-2.1 ii pciutils 1:3.5.2-1 Versions of packages open-vm-tools recommends: ii ethtool 1:4.8-1+b1 pn fuse ii lsb-release 9.20161125 pn zerofree Versions of packages open-vm-tools suggests: pn cloud-init pn open-vm-tools-desktop -- Configuration Files: /etc/vmware-tools/tools.conf changed: -- no debconf information -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */ -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */ --- End Message --- --- Begin Message --- Version: 238-1 On Sat, 10 Mar 2018 09:29:46 +0100 Bernd Zeimetz <be...@bzed.de> wrote: > > Why does it need to run before cloud-init i.e. why does cloud-init need > > open-vm-tools? > > because cloud-init pulls the configuration it should apply from vmtoolsd. > > But that is not the bug here and nothing that needs to be changed. > > If you would finally read > https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1750780 > > you would learn that there is a race condition that when PrivateTmp is > being used the necessary mounts are not always available. > > The workaround for now is After=local-fs.target - which will result in a > dependency loop at some point, which is discussed in > > https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1750780/comments/11 > > basically all information is in that bug. Please read it. Actually this bug report it doesn't contain any actual information what this supposed race condition in systemd should be. It's mostly speculation on their part. Anyway, they said they can no longer reproduce it anyway on bionic which ships the same version as unstable, so let's close this bug report. -- 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 Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#893014: marked as done (systemd: journalctl -g and --grep fail (in different ways))
Your message dated Thu, 15 Mar 2018 18:09:25 +0100 with message-id <630c41a4-828b-4796-a8c5-c3a5d4813...@debian.org> and subject line Re: Bug#893014: systemd: journalctl -g and --grep fail (in different ways) has caused the Debian Bug report #893014, regarding systemd: journalctl -g and --grep fail (in different ways) 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.) -- 893014: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893014 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: systemd Version: 237-4 Severity: normal journalctl(1) says: -g, --grep= Filter output to entries where the MESSAGE= field matches the specified regular expression. PERL-compatible regular expressions are used, see pcre2pattern(3) for a detailed description of the syntax. If the pattern is all lowercase, matching is case insensitive. Otherwise, matching is case sensitive. This can be overridden with the --case-sensitive option, see below. however: 0 dkg@alice:~$ journalctl --grep=hello Compiled without pattern matching support 0 dkg@alice:~$ journalctl -g hello journalctl: invalid option -- 'g' 1 dkg@alice:~$ note that --grep=hello returns 0 and provides a user-comprehensible warning about why it didn't work. but -g hello returns 1 and just gives an incomprehensible error message that doesn't indicate why it's failing. I think the right approach would be to return a non-zero error code in both cases, and to print the same reasonable explanation in both cases. --dkg -- Package-specific info: -- System Information: Debian Release: buster/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'testing'), (500, 'oldstable'), (200, 'unstable-debug'), (200, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.14.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.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 adduser 3.117 ii libacl1 2.2.52-3+b1 ii libapparmor1 2.12-3 ii libaudit11:2.8.2-1 ii libblkid12.31.1-0.4 ii libc62.27-1 ii libcap2 1:2.25-1.2 ii libcryptsetup12 2:2.0.1-1 ii libgcrypt20 1.8.1-4 ii libgpg-error01.27-6 ii libidn11 1.33-2.1 ii libip4tc01.6.2-1 ii libkmod2 25-1 ii liblz4-1 0.0~r131-2+b1 ii liblzma5 5.2.2-1.3 ii libmount12.31.1-0.4 ii libpam0g 1.1.8-3.7 ii libseccomp2 2.3.1-2.1 ii libselinux1 2.7-2+b1 ii libsystemd0 237-4 ii mount2.31.1-0.4 ii procps 2:3.3.12-4 ii util-linux 2.31.1-0.4 Versions of packages systemd recommends: ii dbus1.12.6-2 ii libpam-systemd 237-4 Versions of packages systemd suggests: ii policykit-10.105-18 ii systemd-container 237-4 Versions of packages systemd is related to: ii dracut 047-2 pn initramfs-tools ii udev 237-4 -- Configuration Files: /etc/systemd/resolved.conf changed [not included] -- no debconf information --- End Message --- --- Begin Message --- Version: 238-1 Am 15.03.2018 um 15:39 schrieb Daniel Kahn Gillmor: > Package: systemd > Version: 237-4 > Severity: normal > > journalctl(1) says: > >-g, --grep= >Filter output to entries where the MESSAGE= field matches the >specified regular expression. PERL-compatible regular expressions >are used, see pcre2pattern(3) for a detailed description of the >syntax. > >If the pattern is all lowercase, matching is case insensitive. >Otherwise, matching is case sensitive. This can be overridden with >the --case-sensitive option, see below. > > > however: > > 0 dkg@alice:~$ journalctl --grep=hello > Compiled without pattern matching support > 0 dkg@alice:~$ journalctl -g hello > journalctl: invalid option -- 'g' > 1 dkg@alice:~$ > > > note that --grep=hello returns 0 and provides a user-comprehensible > warning about why it didn't work. > > but -g hello returns 1 and just gives an incomprehensible error > message that doesn't indicate why it's failing. > > I think the right approach would be to return a
Processed: Re: Bug#892989: weird chars found in dpkg output
Processing control commands: > reassign -1 systemd Bug #892989 [dpkg] weird chars found in dpkg output Bug reassigned from package 'dpkg' to 'systemd'. No longer marked as found in versions dpkg/1.18.24. Ignoring request to alter fixed versions of bug #892989 to the same values previously set -- 892989: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892989 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: affects 892651
Processing commands for cont...@bugs.debian.org: > affects 892651 release.debian.org Bug #892651 [systemd] networkd: no IPv6 default route after point release Bug #892794 [systemd] systemd-networkd fails to configure IPv6 without MTU from RA Added indication that 892651 affects release.debian.org Added indication that 892794 affects release.debian.org > thanks Stopping processing here. Please contact me if you need assistance. -- 892651: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892651 892794: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892794 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: fixed 892829 in 236-1
Processing commands for cont...@bugs.debian.org: > fixed 892829 236-1 Bug #892829 [systemd] systemd: RemoveIPC directive is half-supported in stretch Marked as fixed in versions systemd/236-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 892829: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892829 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: forcibly merging 892651 892794
Processing commands for cont...@bugs.debian.org: > forcemerge 892651 892794 Bug #892651 [systemd] networkd: no IPv6 default route after point release Bug #892794 [systemd] systemd-networkd fails to configure IPv6 without MTU from RA Merged 892651 892794 > thanks Stopping processing here. Please contact me if you need assistance. -- 892651: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892651 892794: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892794 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#892736: marked as done (udev: systemd-udevd.service include is wrong)
Your message dated Mon, 12 Mar 2018 13:14:11 +0100 with message-id <f755b6b7-cb56-d620-eb70-7eedef068...@debian.org> and subject line Re: Bug#892736: udev: systemd-udevd.service include is wrong has caused the Debian Bug report #892736, regarding udev: systemd-udevd.service include is wrong 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.) -- 892736: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892736 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: udev Version: 232-25+deb9u2 Severity: grave Justification: renders package unusable Dear Maintainer, After upgrading, systemd reports udev errors. The problem is a wrong include in /etc/systemd/system/systemd-udevd.service: #.include /usr/lib/systemd/system/systemd-udevd.service .include /lib/systemd/system/systemd-udevd.service [Service] MountFlags=shared After changing '/usr/lib/...' in '/lib/...' udev starts normally. Kind regards, Jaap van Wingerde. -- Package-specific info: -- System Information: Debian Release: 9.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-0.bpo.4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages udev depends on: ii adduser 3.115 ii dpkg 1.18.24 ii libacl1 2.2.52-3+b1 ii libblkid12.29.2-1+deb9u1 ii libc62.24-11+deb9u3 ii libkmod2 23-2 ii libselinux1 2.6-3+b3 ii libudev1 232-25+deb9u2 ii lsb-base 9.20161125 ii procps 2:3.3.12-3 ii util-linux 2.29.2-1+deb9u1 udev recommends no packages. udev suggests no packages. Versions of packages udev is related to: ii systemd 232-25+deb9u2 -- Configuration Files: /etc/udev/udev.conf changed: udev_log="info" -- debconf information: udev/sysfs_deprecated_incompatibility: udev/new_kernel_needed: false udev/reboot_needed: udev/title/upgrade: P: /devices/LNXSYSTM:00 E: DEVPATH=/devices/LNXSYSTM:00 E: ID_VENDOR_FROM_DATABASE=The Linux Foundation E: MODALIAS=acpi:LNXSYSTM: E: SUBSYSTEM=acpi E: USEC_INITIALIZED=8104336 P: /devices/LNXSYSTM:00/LNXCPU:00 E: DEVPATH=/devices/LNXSYSTM:00/LNXCPU:00 E: ID_VENDOR_FROM_DATABASE=The Linux Foundation E: MODALIAS=acpi:LNXCPU: E: SUBSYSTEM=acpi E: USEC_INITIALIZED=8106545 P: /devices/LNXSYSTM:00/LNXCPU:01 E: DEVPATH=/devices/LNXSYSTM:00/LNXCPU:01 E: ID_VENDOR_FROM_DATABASE=The Linux Foundation E: MODALIAS=acpi:LNXCPU: E: SUBSYSTEM=acpi E: USEC_INITIALIZED=8108966 P: /devices/LNXSYSTM:00/LNXCPU:02 E: DEVPATH=/devices/LNXSYSTM:00/LNXCPU:02 E: ID_VENDOR_FROM_DATABASE=The Linux Foundation E: MODALIAS=acpi:LNXCPU: E: SUBSYSTEM=acpi E: USEC_INITIALIZED=8108966 P: /devices/LNXSYSTM:00/LNXCPU:03 E: DEVPATH=/devices/LNXSYSTM:00/LNXCPU:03 E: ID_VENDOR_FROM_DATABASE=The Linux Foundation E: MODALIAS=acpi:LNXCPU: E: SUBSYSTEM=acpi E: USEC_INITIALIZED=8113152 P: /devices/LNXSYSTM:00/LNXPWRBN:00 E: DEVPATH=/devices/LNXSYSTM:00/LNXPWRBN:00 E: DRIVER=button E: ID_VENDOR_FROM_DATABASE=The Linux Foundation E: MODALIAS=acpi:LNXPWRBN: E: SUBSYSTEM=acpi E: USEC_INITIALIZED=8111617 P: /devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 E: DEVPATH=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 E: EV=3 E: ID_FOR_SEAT=input-acpi-LNXPWRBN_00 E: ID_INPUT=1 E: ID_INPUT_KEY=1 E: ID_PATH=acpi-LNXPWRBN:00 E: ID_PATH_TAG=acpi-LNXPWRBN_00 E: KEY=10 0 E: MODALIAS=input:b0019vp0001e-e0,1,k74,ramlsfw E: NAME="Power Button" E: PHYS="LNXPWRBN/button/input0" E: PRODUCT=19/0/1/0 E: PROP=0 E: SUBSYSTEM=input E: TAGS=:seat: E: USEC_INITIALIZED=8886907 P: /devices/LNXSYSTM:00/LNXPWRBN:00/input/input2/event2 N: input/event2 E: DEVNAME=/dev/input/event2 E: DEVPATH=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2/event2 E: ID_INPUT=1 E: ID_INPUT_KEY=1 E: ID_PATH=acpi-LNXPWRBN:00 E: ID_PATH_TAG=acpi-LNXPWRBN_00 E: MAJOR=13 E: MINOR=66 E: SUBSYSTEM=input E: TAGS=:power-switch: E: USEC_INITIALIZED=9014351 P: /devices/LNXSYSTM:00/LNXSYBUS:00 E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00 E: ID_VENDOR_FROM_DATABASE=The Linux Foundation E: MODALIAS=acpi:LNXSYBUS: E: SUBSYSTEM=acpi E: USEC_INITIALIZED=8127828 P: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00 E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00 E: ID_VENDOR_FROM_DATABASE=The Linux Foundation E: MODALIAS=acpi:PNP0A03: E: SUBSYSTEM=acpi E: USEC_INITIALIZED=8137677 P: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/PNP0003:00 E: DEVP
Processed: severity of 892736 is normal
Processing commands for cont...@bugs.debian.org: > severity 892736 normal Bug #892736 [udev] udev: systemd-udevd.service include is wrong Severity set to 'normal' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 892736: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892736 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: Bug #888126 in systemd marked as pending
Processing control commands: > tag -1 pending Bug #888126 [systemd] [patch] Please enable systemd-sysusers unit Added tag(s) pending. -- 888126: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888126 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: Re: Bug#892585: systemd: can not create user.slice/user session, after upgrade systemd from 237-4 to 238-1/2
Processing control commands: > tags -1 moreinfo Bug #892585 [systemd] systemd: can not create user.slice/user session, after upgrade systemd from 237-4 to 238-1/2 Added tag(s) moreinfo. -- 892585: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892585 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 (with 1 error): Still present in stretch versions, patch attached
Processing commands for cont...@bugs.debian.org:
> unarchive #869995
> found #869995 232-25+deb9u1
Bug #869995 {Done: Michael Biebl <bi...@debian.org>} [systemd] interface stuck
in "configuring" if SLAAC prefix announced with preferred lifetime zero
Ignoring request to alter found versions of bug #869995 to the same values
previously set
> found #869995 232-25+deb9u2
Bug #869995 {Done: Michael Biebl <bi...@debian.org>} [systemd] interface stuck
in "configuring" if SLAAC prefix announced with preferred lifetime zero
Ignoring request to alter found versions of bug #869995 to the same values
previously set
> tags #869995 patch stretch
Bug #869995 {Done: Michael Biebl <bi...@debian.org>} [systemd] interface stuck
in "configuring" if SLAAC prefix announced with preferred lifetime zero
Ignoring request to alter tags of bug #869995 to the same tags previously set
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
869995: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869995
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: Re: Bug#869995: fixed in systemd 235-1
Processing commands for cont...@bugs.debian.org:
> unarchive #869995
Bug #869995 {Done: Michael Biebl <bi...@debian.org>} [systemd] interface stuck
in "configuring" if SLAAC prefix announced with preferred lifetime zero
Unarchived Bug 869995
> found #869995 232-25+deb9u1
Bug #869995 {Done: Michael Biebl <bi...@debian.org>} [systemd] interface stuck
in "configuring" if SLAAC prefix announced with preferred lifetime zero
Marked as found in versions systemd/232-25+deb9u1.
> found #869995 232-25+deb9u2
Bug #869995 {Done: Michael Biebl <bi...@debian.org>} [systemd] interface stuck
in "configuring" if SLAAC prefix announced with preferred lifetime zero
Marked as found in versions systemd/232-25+deb9u2.
> tags #869995 patch stretch
Bug #869995 {Done: Michael Biebl <bi...@debian.org>} [systemd] interface stuck
in "configuring" if SLAAC prefix announced with preferred lifetime zero
Added tag(s) stretch.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
869995: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869995
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: Re: Bug#806256: libpam-systemd: log out from a TTY and your X input devices get lost!
Processing control commands: > found -1 systemd/237-4 Bug #806256 [libpam-systemd] libpam-systemd: log out from a TTY and your X input devices get lost! Bug #867745 [libpam-systemd] libpam-systemd: log out from a TTY and your X input devices get lost! Bug #877571 [libpam-systemd] xserver-xorg-core: lockup on exiting another virtual terminal Marked as found in versions systemd/237-4. Marked as found in versions systemd/237-4. Marked as found in versions systemd/237-4. -- 806256: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806256 867745: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867745 877571: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877571 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: Bug #892360 in systemd marked as pending
Processing control commands: > tag -1 pending Bug #892360 [systemd] systemd pid 1 freezes at startup on x86 systems Added tag(s) pending. -- 892360: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892360 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: PrivateTmp Race with local file systems
Processing commands for cont...@bugs.debian.org: > reassign 888955 systemd Bug #888955 [open-vm-tools] open-vm-tools.service 10.2.0 does not start on boot on jessie/stretch/etc Bug reassigned from package 'open-vm-tools' to 'systemd'. No longer marked as found in versions open-vm-tools/2:10.2.0-2. Ignoring request to alter fixed versions of bug #888955 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 888955: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888955 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: Re: Bug#892360: core: do not free stack-allocated strings
Processing control commands: > tags -1 patch Bug #892360 [systemd] systemd pid 1 freezes at startup on x86 systems Added tag(s) patch. -- 892360: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892360 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: Re: Bug#892360: systemd: Breaks also all my tested amd64 machines
Processing control commands: > tags -1 moreinfo Bug #892360 [systemd] systemd pid 1 freezes at startup on x86 systems Added tag(s) moreinfo. -- 892360: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892360 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#890779: marked as done (systemd: CVE-2018-6954: Mishandled sysmlinks in systemd-tmpfiles allows local users to obtain ownership of arbitrary files)
Your message dated Wed, 07 Mar 2018 23:05:23 + with message-id <e1eti7f-000cxl...@fasolo.debian.org> and subject line Bug#890779: fixed in systemd 238-1 has caused the Debian Bug report #890779, regarding systemd: CVE-2018-6954: Mishandled sysmlinks in systemd-tmpfiles allows local users to obtain ownership of arbitrary files 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.) -- 890779: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890779 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: systemd Version: 236-1 Severity: important Tags: security upstream Forwarded: https://github.com/systemd/systemd/issues/7986 Hi, the following vulnerability was published for systemd, filling this bug to keep track of the bug in the Debian BTS. CVE-2018-6954[0]: | systemd-tmpfiles in systemd through 237 mishandles symlinks present in | non-terminal path components, which allows local users to obtain | ownership of arbitrary files via vectors involving creation of a | directory and a file under that directory, and later replacing that | directory with a symlink. This occurs even if the fs.protected_symlinks | sysctl is turned on. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2018-6954 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6954 [1] https://github.com/systemd/systemd/issues/7986 Please adjust the affected versions in the BTS as needed (all earlier versions should be affected). Regards, Salvatore --- End Message --- --- Begin Message --- Source: systemd Source-Version: 238-1 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 890...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Biebl <bi...@debian.org> (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: Wed, 07 Mar 2018 23:21:53 +0100 Source: systemd Binary: systemd systemd-sysv systemd-container systemd-journal-remote systemd-coredump systemd-tests libpam-systemd libnss-myhostname libnss-mymachines libnss-resolve libnss-systemd libsystemd0 libsystemd-dev udev libudev1 libudev-dev udev-udeb libudev1-udeb Architecture: source Version: 238-1 Distribution: unstable Urgency: medium Maintainer: Debian systemd Maintainers <pkg-systemd-maintainers@lists.alioth.debian.org> Changed-By: Michael Biebl <bi...@debian.org> Description: libnss-myhostname - nss module providing fallback resolution for the current hostname libnss-mymachines - nss module to resolve hostnames for local container instances libnss-resolve - nss module to resolve names via systemd-resolved libnss-systemd - nss module providing dynamic user and group name resolution libpam-systemd - system and service manager - PAM module libsystemd-dev - systemd utility library - development files libsystemd0 - systemd utility library libudev-dev - libudev development files libudev1 - libudev shared library libudev1-udeb - libudev shared library (udeb) systemd- system and service manager systemd-container - systemd container/nspawn tools systemd-coredump - tools for storing and retrieving coredumps systemd-journal-remote - tools for sending and receiving remote journal logs systemd-sysv - system and service manager - SysV links systemd-tests - tests for systemd udev - /dev/ and hotplug management daemon udev-udeb - /dev/ and hotplug management daemon (udeb) Closes: 890779 Changes: systemd (238-1) unstable; urgency=medium . [ Michael Biebl ] * New upstream version 238 - Fixes systemd-tmpfiles to correctly handle symlinks present in non-terminal path components. (CVE-2018-6954, Closes: #890779) * Rebase patches * Use compat symlinks as provided by upstream. As the upstream build system now creates those symlinks for us, we no longer have to create them manually. * Update symbols file for libsystemd0
Processed: severity of 890265 is wishlist
Processing commands for cont...@bugs.debian.org: > severity 890265 wishlist Bug #890265 [systemd] systemd: journalctl compiled without pattern matching support Severity set to 'wishlist' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 890265: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890265 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: Re: Bug#891836: systemd: systemctl start/stop/restart valid-template@invalid-instance doesn't cause errors
Processing control commands: > reassign -1 postgresql Bug #891836 [systemd] systemd: systemctl start/stop/restart valid-template@invalid-instance doesn't cause errors Bug reassigned from package 'systemd' to 'postgresql'. No longer marked as found in versions systemd/232-25+deb9u1. Ignoring request to alter fixed versions of bug #891836 to the same values previously set -- 891836: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891836 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 891836
Processing commands for cont...@bugs.debian.org: > tags 891836 + unreproducible Bug #891836 [systemd] systemd: systemctl start/stop/restart valid-template@invalid-instance doesn't cause errors Ignoring request to alter tags of bug #891836 to the same tags previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 891836: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891836 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: Re: Bug#891836: systemd: systemctl start/stop/restart valid-template@invalid-instance doesn't cause errors
Processing control commands: > tags -1 moreinfo unreproducible Bug #891836 [systemd] systemd: systemctl start/stop/restart valid-template@invalid-instance doesn't cause errors Ignoring request to alter tags of bug #891836 to the same tags previously set -- 891836: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891836 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: Re: Bug#891836: systemd: systemctl start/stop/restart valid-template@invalid-instance doesn't cause errors
Processing control commands: > tags -1 + moreinfo unreproducible Bug #891836 [systemd] systemd: systemctl start/stop/restart valid-template@invalid-instance doesn't cause errors Added tag(s) moreinfo and unreproducible. -- 891836: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891836 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: Re: Bug#891558: Checking in progress on ... message improvement ideas
Processing commands for cont...@bugs.debian.org: > reassign 891558 systemd 237 Bug #891558 [e2fsprogs] Checking in progress on ... message improvement ideas Bug reassigned from package 'e2fsprogs' to 'systemd'. No longer marked as found in versions e2fsprogs/1.43.9-2. Ignoring request to alter fixed versions of bug #891558 to the same values previously set Bug #891558 [systemd] Checking in progress on ... message improvement ideas There is no source info for the package 'systemd' at version '237' with architecture '' Unable to make a source version for version '237' Marked as found in versions 237. > thanks Stopping processing here. Please contact me if you need assistance. -- 891558: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891558 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: Re: Bug#891477: udev: MemoryDenyWriteExecute breaks gzip on i386
Processing control commands: > reassign -1 gzip Bug #891477 [udev] udev: MemoryDenyWriteExecute breaks gzip on i386 Bug reassigned from package 'udev' to 'gzip'. No longer marked as found in versions systemd/232-25+deb9u1. Ignoring request to alter fixed versions of bug #891477 to the same values previously set > forcemerge 890279 -1 Bug #890279 [gzip] gzip (x86) uses TEXTRELs, compiled without -fPIC? Bug #891477 [gzip] udev: MemoryDenyWriteExecute breaks gzip on i386 Marked as found in versions gzip/1.6-5. Merged 890279 891477 -- 890279: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890279 891477: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891477 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: forcibly merging 887343 890095
Processing commands for cont...@bugs.debian.org:
> forcemerge 887343 890095
Bug #887343 {Done: Michael Biebl <bi...@debian.org>} [systemd]
systemd-timesyncd does not start with DynamicUser=yes
Bug #50 {Done: Michael Biebl <bi...@debian.org>} [systemd]
systemd-timesyncd fails to start
Bug #50 {Done: Michael Biebl <bi...@debian.org>} [systemd]
systemd-timesyncd fails to start
Added tag(s) moreinfo.
Added tag(s) moreinfo.
Bug #890095 [systemd] systemd: Failed to start network time synchronization
Set Bug forwarded-to-address to
'https://github.com/systemd/systemd/issues/7883'.
Marked Bug as done
Marked as fixed in versions systemd/236-4.
There is no source info for the package 'systemd' at version '236-6' with
architecture ''
Unable to make a source version for version '236-6'
Marked as found in versions 236-6.
Added tag(s) fixed-upstream and patch.
Merged 887343 50 890095
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
887343: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887343
50: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=50
890095: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890095
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#880158: marked as done (systemd-container: machinectl incorrectly reports "No machines." when using --no-legend)
Your message dated Sun, 25 Feb 2018 15:02:18 + with message-id <e1epxog-0004ej...@fasolo.debian.org> and subject line Bug#880158: fixed in systemd 232-25+deb9u2 has caused the Debian Bug report #880158, regarding systemd-container: machinectl incorrectly reports "No machines." when using --no-legend 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.) -- 880158: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880158 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: systemd-container Version: 232-25+deb9u1 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? I am running containers launched with systemd-nspawn. They show up in 'machinectl' just fine. * What exactly did you do (or not do) that was effective (or ineffective)? Running machinectl with the --no-legend flag causes it to report "No machines." *after* the actual list of machines. * What was the outcome of this action? admin@ip-172-31-15-145:~$ machinectl MACHINECLASS SERVICEOS VERSION ADDRESSES ctr-emVnH3DhH3rStx3g78sGyh container systemd-nspawn alpine 3.6.2 10.1.16.204... 1 machines listed. admin@ip-172-31-15-145:~$ machinectl --no-legend ctr-emVnH3DhH3rStx3g78sGyh container systemd-nspawn alpine 3.6.2 10.1.16.204... No machines. * What outcome did you expect instead? That "No machines." would not be orinted. *** End of the template - remove these template lines *** -- System Information: Debian Release: 9.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-4-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages systemd-container depends on: ii dbus 1.10.22-0+deb9u1 ii libacl1 2.2.52-3+b1 ii libblkid12.29.2-1 ii libbz2-1.0 1.0.6-8.1 ii libc62.24-11+deb9u1 ii libcurl3-gnutls 7.52.1-5+deb9u2 ii libgcrypt20 1.7.6-2+deb9u2 ii libip4tc01.6.0+snapshot20161117-6 ii liblzma5 5.2.2-1.2+b1 ii libseccomp2 2.3.1-2.1 ii libselinux1 2.6-3+b3 ii systemd 232-25+deb9u1 ii zlib1g 1:1.2.8.dfsg-5 Versions of packages systemd-container recommends: ii btrfs-progs4.7.3-1 ii libnss-mymachines 232-25+deb9u1 systemd-container suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: systemd Source-Version: 232-25+deb9u2 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 880...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Biebl <bi...@debian.org> (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: Sun, 03 Dec 2017 15:03:50 +0100 Source: systemd Binary: systemd systemd-sysv systemd-container systemd-journal-remote systemd-coredump libpam-systemd libnss-myhostname libnss-mymachines libnss-resolve libnss-systemd libsystemd0 libsystemd-dev udev libudev1 libudev-dev udev-udeb libudev1-udeb Architecture: source Version: 232-25+deb9u2 Distribution: stretch Urgency: medium Maintainer: Debian systemd Maintainers <pkg-systemd-maintainers@lists.alioth.debian.org> Changed-By: Michael Biebl <bi...@debian.org> Description: libnss-myhostname - nss module providing fallback resolution for the current hostname libnss-mymachines - nss module to resolve hostnames for local container instances libnss-resolve - nss module to resolve names via systemd-resolved libnss-systemd - nss module providing dynamic user and group name resolution libpam-systemd - system and service manager - PAM module libsystemd-dev - systemd utility library - development files libsystemd0 - systemd utility library libudev-dev - libudev
Processed: Bug #880158 in systemd marked as pending
Processing control commands: > tag -1 pending Bug #880158 [systemd-container] systemd-container: machinectl incorrectly reports "No machines." when using --no-legend Added tag(s) pending. -- 880158: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880158 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#890986: marked as done (BIOS upgrade change main ethernet device name / regression from previous debian versions)
Your message dated Wed, 21 Feb 2018 16:21:53 +0100 with message-id <1d407861-de48-2a54-5d66-3082b91a7...@debian.org> and subject line Re: Bug#890986: BIOS upgrade change main ethernet device name / regression from previous debian versions has caused the Debian Bug report #890986, regarding BIOS upgrade change main ethernet device name / regression from previous debian versions 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.) -- 890986: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890986 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: udev Version: 232-25+deb9u1 Severity: normal On a Asrock AB350 Gaming K4 motherboard based machine running debian stretch we upgraded BIOS from P3.00 to P4.60 and this changed the integrated motherboard ethernet device name from enp10s0 to enp37s0. As a consequence we lost network connectivty and had to edit configuration files. Initial BIOS: r8169 :0a:00.0 enp10s0: renamed from eth0 New BIOS: r8169 :25:00.0 enp37s0: renamed from eth0 On older versions debian /etc/udev/rules.d/70-persistent-net.rules would have made the ethernet device name constant and we would not have lost network connectivity, so the current state of udev is an unfortunate regression. Is there a way to force generation of 70-persistent-net.rules? Thanks in advance, Sincerely, Laurent --- End Message --- --- Begin Message --- Am 21.02.2018 um 11:13 schrieb Laurent GUERBY: > Package: udev > Version: 232-25+deb9u1 > Severity: normal > > On a Asrock AB350 Gaming K4 motherboard based machine > running debian stretch we upgraded BIOS from P3.00 to P4.60 and this > changed the integrated motherboard ethernet device name from enp10s0 to > enp37s0. As a consequence we lost network connectivty and had to edit > configuration files. > > Initial BIOS: > r8169 :0a:00.0 enp10s0: renamed from eth0 > > New BIOS: > r8169 :25:00.0 enp37s0: renamed from eth0 That's very unfortunate, unfortunately we can't really fix that in systemd. > On older versions debian /etc/udev/rules.d/70-persistent-net.rules > would have made the ethernet device name constant and we would > not have lost network connectivity, so the current state of udev is an > unfortunate regression. > > Is there a way to force generation of 70-persistent-net.rules? No, but you can setup your own naming scheme, matching on whatever you see fit, including the MAC address. Say I wanted to name my ethernet device net0, then you could setup something like $ cat /etc/systemd/network/70-net.link [Match] MACAddress=00:11:22:33:44:55:66 [Link] Name=net0 If you are going to rename network interfaces, don't reuse the kernel provided names, i.e. ethX and wlanX, as this is inherently racy. See man systemd.link for more information on this. If you are sure, that your system will only ever have a single network interface, you can also disable the new default network interface naming scheme and use the kernel provided names. See /usr/share/doc/udev/README.Debian.gz → "Network interface naming" Let me repeat: Using the kernel provided names is probably only a good idea if you have a single network interface. With multiple interfaces, you have no guarantee in which order they are enumerated and named. I'm closing this bug report, as unfortunately there is nothing really that systemd/udev can do, if your bios update has such effects. 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 Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Processed: bug 890641 is forwarded to https://github.com/systemd/systemd/issues/8221
Processing commands for cont...@bugs.debian.org: > forwarded 890641 https://github.com/systemd/systemd/issues/8221 Bug #890641 [udev] udev: fragile handling of uevent actions breaks with kernel 4.12+ Set Bug forwarded-to-address to 'https://github.com/systemd/systemd/issues/8221'. > thanks Stopping processing here. Please contact me if you need assistance. -- 890641: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890641 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: Re: systemd: Failed to start network time synchronization
Processing control commands: > tags -1 + moreinfo Bug #890095 [systemd] systemd: Failed to start network time synchronization Added tag(s) moreinfo. -- 890095: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890095 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: bug 890445 is forwarded to https://github.com/systemd/systemd/issues/8216
Processing commands for cont...@bugs.debian.org: > forwarded 890445 https://github.com/systemd/systemd/issues/8216 Bug #890445 [systemd] systemd: systemctl tab-auto-completion freezes the terminal and causes 100% CPU utilization Set Bug forwarded-to-address to 'https://github.com/systemd/systemd/issues/8216'. > thanks Stopping processing here. Please contact me if you need assistance. -- 890445: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890445 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: unarchiving 873708, forcibly merging 873708 890659, archiving 873708
Processing commands for cont...@bugs.debian.org:
> unarchive 873708
Bug #873708 {Done: Michael Biebl <bi...@debian.org>} [systemd]
libsystemd-shared: symbol collisions
Unarchived Bug 873708
> forcemerge 873708 890659
Bug #873708 {Done: Michael Biebl <bi...@debian.org>} [systemd]
libsystemd-shared: symbol collisions
Bug #890659 [systemd] systemd segfault in libsystemd-shared-232.so
Set Bug forwarded-to-address to
'https://github.com/systemd/systemd/issues/6624'.
Marked Bug as done
Marked as fixed in versions systemd/234-3.
Added tag(s) fixed-upstream.
Bug #873708 {Done: Michael Biebl <bi...@debian.org>} [systemd]
libsystemd-shared: symbol collisions
Added tag(s) patch.
Merged 873708 890659
> archive 873708
Bug #873708 {Done: Michael Biebl <bi...@debian.org>} [systemd]
libsystemd-shared: symbol collisions
Bug #890659 {Done: Michael Biebl <bi...@debian.org>} [systemd] systemd segfault
in libsystemd-shared-232.so
archived 873708 to archive/08 (from 873708)
archived 890659 to archive/59 (from 873708)
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
873708: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873708
890659: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890659
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#890436: marked as done (systemd-sysv-install uses ROOT variable from environment for chrooting)
Your message dated Wed, 14 Feb 2018 22:22:53 + with message-id <e1em5s1-0005ru...@fasolo.debian.org> and subject line Bug#890436: fixed in systemd 237-3 has caused the Debian Bug report #890436, regarding systemd-sysv-install uses ROOT variable from environment for chrooting 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.) -- 890436: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890436 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: systemd Version: 232-25+deb9u1 Severity: normal systemd-sysv-install uses `ROOT` variable from environment when not set via `-r` and tries to execute update-rc.d chrooted to the content of this variable. I'm am a bit unsure whether or not this really is a bug, but since it was a total surprise for me when I found the cause of the issue and I did not find any documentation about this behaviour, I think this is a bug. *Expected behaviour I didn't see* root@Klappspaten:/# systemctl enable ssh Synchronizing state of ssh.service with SysV service script with /lib/systemd/systemd-sysv-install. Executing: /lib/systemd/systemd-sysv-install enable ssh Created symlink /etc/systemd/system/sshd.service → /lib/systemd/system/ssh.service. *Unexpected behaviour I saw* When ROOT is e.g. set to /dev/sda1, this issue occurs: root@Klappspaten:/# systemctl enable ssh Synchronizing state of ssh.service with SysV service script with /lib/systemd/systemd-sysv-install. Executing: /lib/systemd/systemd-sysv-install enable ssh chroot: cannot change root directory to "'/dev/sda1'": No such file or directory *Steps to reproduce the problem* Simply set the environment variable and try to enable a service that is also available as SysV-Init-Script root@Klappspaten:/# export ROOT=/dev/sda1 root@Klappspaten:/# systemctl enable ssh Synchronizing state of ssh.service with SysV service script with /lib/systemd/systemd-sysv-install. Executing: /lib/systemd/systemd-sysv-install enable ssh chroot: cannot change root directory to "'/dev/sda1'": No such file or directory *Possible solution* ROOT should be initialized with an empty value before reading command line options. *References* https://github.com/systemd/systemd/issues/8180 https://salsa.debian.org/systemd-team/systemd/blob/master/debian/extra/systemd-sysv-install -- Package-specific info: -- System Information: Debian Release: 9.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-5-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.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 adduser 3.115 ii libacl1 2.2.52-3+b1 ii libapparmor12.11.0-3 ii libaudit1 1:2.6.7-2 ii libblkid1 2.29.2-1 ii libc6 2.24-11+deb9u1 ii libcap2 1:2.25-1 ii libcryptsetup4 2:1.7.3-4 ii libgcrypt20 1.7.6-2+deb9u2 ii libgpg-error0 1.26-2 ii libidn111.33-1 ii libip4tc0 1.6.0+snapshot20161117-6 ii libkmod223-2 ii liblz4-10.0~r131-2+b1 ii liblzma55.2.2-1.2+b1 ii libmount1 2.29.2-1 ii libpam0g1.1.8-3.6 ii libseccomp2 2.3.1-2.1 ii libselinux1 2.6-3+b3 ii libsystemd0 232-25+deb9u1 ii mount 2.29.2-1 ii procps 2:3.3.12-3 ii util-linux 2.29.2-1 Versions of packages systemd recommends: ii dbus1.10.24-0+deb9u1 ii libpam-systemd 232-25+deb9u1 Versions of packages systemd suggests: pn policykit-1 pn systemd-container pn systemd-ui Versions of packages systemd is related to: pn dracut ii initramfs-tools 0.130 ii udev 232-25+deb9u1 -- Configuration Files: /etc/systemd/logind.conf changed [not included] -- no debconf information --- End Message --- --- Begin Message --- Source: systemd Source-Version: 237-3 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 890...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Biebl <bi...@debian.org> (supplier of updated systemd package) (This message was generate
Processed: Re: Bug#890436: systemd-sysv-install uses ROOT variable from environment for chrooting
Processing control commands: > tag -1 pending Bug #890436 [systemd] systemd-sysv-install uses ROOT variable from environment for chrooting Ignoring request to alter tags of bug #890436 to the same tags previously set -- 890436: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890436 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: Bug #890436 in systemd marked as pending
Processing control commands: > tag -1 pending Bug #890436 [systemd] systemd-sysv-install uses ROOT variable from environment for chrooting Added tag(s) pending. -- 890436: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890436 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: Bug #890423 in systemd marked as pending
Processing control commands: > tag -1 pending Bug #890423 [systemd] systemd getpeergroups break rsync Added tag(s) pending. -- 890423: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890423 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: reassign 890343 linux
Processing commands for cont...@bugs.debian.org: > reassign 890343 linux Bug #890343 [systemd] systemd: Debian could use the fq_codel network queuing algorithm by default Bug reassigned from package 'systemd' to 'linux'. No longer marked as found in versions systemd/237-2. Ignoring request to alter fixed versions of bug #890343 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 890343: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890343 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#890008: marked as done (init(8): Some corrections to the manual)
Your message dated Sat, 10 Feb 2018 03:11:54 +0100
with message-id <06d81777-180d-df59-b4de-310478079...@debian.org>
and subject line Re: Bug#890008: init(8): Some corrections to the manual
has caused the Debian Bug report #890008,
regarding init(8): Some corrections to the manual
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.)
--
890008: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890008
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: init
Version: 1.51
Severity: minor
Tags: patch
Dear Maintainer,
Test nr. 1: Remove space at end of lines.
122:it is signaled by \fBtelinit\fP to change the system's runlevel.
177:tell \fBinit\fP to re-execute itself (preserving the state). No
re-examining of
#
Test nr. 2: Fix warning from man/groff
:330 (macro BR): only 1 argument, but more are expected
#
Test nr. 5: Change - to \(en if it is
a numeric range
83:Runlevels 7-9 are also valid, though not really documented. This is
226:.B 1-5
#
Test nr. 8: Protect . if not end of sentence
59:\fB0\(en6\fP and \fBS\fP (a.k.a. \fBs\fP). The runlevel is
246:line a bit, so that it takes some more space on the stack. \fBInit\fP
#
Test nr. 25: Change a HYPHEN-MINUS (code 0x55, 2D) to a dash (minus) if it
matches " -[:alpha:]" or \(aq-[:alpha:] (for options)
184:is 5 seconds, but this can be changed with the \fB-t\fP option.
186:\fBtelinit -e\fP tells \fBinit\fP to change the environment
188:The argument of \fB-e\fP is either of the form \fIVAR\fP=\fIVAL\fP
245:The argument to \fB-z\fP is ignored. You can use this to expand the command
#
Additionally:
Sentences in the first created patch, that showed a wrong amount of
space between them, were separated ("man-pages(7)"), and a new patch
created.
Patch:
--- init.8 2017-09-08 19:18:37.0 +
+++ init.8.new 2018-02-09 01:44:20.0 +
@@ -56,7 +56,7 @@ A \fIrunlevel\fP is a software configura
only a selected group of processes to exist. The processes spawned by
\fBinit\fP for each of these runlevels are defined in the
\fB/etc/inittab\fP file. \fBInit\fP can be in one of eight runlevels:
-\fB0\(en6\fP and \fBS\fP (a.k.a. \fBs\fP). The runlevel is
+\fB0\(en6\fP and \fBS\fP (a.k.a.\& \fBs\fP). The runlevel is
changed by having a privileged user run \fBtelinit\fP, which sends
appropriate signals to \fBinit\fP, telling it which runlevel to change
to.
@@ -80,8 +80,8 @@ the administrator performs maintenance a
For more information,
see the manpages for \fBshutdown\fP(8) and \fBinittab\fP(5).
.PP
-Runlevels 7-9 are also valid, though not really documented. This is
-because "traditional" Unix variants don't use them.
+Runlevels 7\(en9 are also valid, though not really documented.
+This is because "traditional" Unix variants don't use them.
.PP
Runlevels \fIS\fP and \fIs\fP are the same.
Internally they are aliases for the same runlevel.
@@ -119,7 +119,7 @@ provided that these files exist.
.SH CHANGING RUNLEVELS
After it has spawned all of the processes specified, \fBinit\fP waits
for one of its descendant processes to die, a powerfail signal, or until
-it is signaled by \fBtelinit\fP to change the system's runlevel.
+it is signaled by \fBtelinit\fP to change the system's runlevel.
When one of the above three conditions occurs, it re-examines
the \fB/etc/inittab\fP file. New entries can be added to this file at
any time. However, \fBinit\fP still waits for one of the above three
@@ -174,18 +174,18 @@ tell \fBinit\fP to re-examine the \fB/et
.IP "\fBS\fP or \fBs\fP"
tell \fBinit\fP to switch to single user mode.
.IP "\fBU\fP or \fBu\fP"
-tell \fBinit\fP to re-execute itself (preserving the state). No re-examining
of
-\fB/etc/inittab\fP file happens. Run level should be one of
-\fBSs0123456\fP
-otherwise request would be silently ignored.
+tell \fBinit\fP to re-execute itself (preserving the state).
+No re-examining of \fB/etc/inittab\fP file happens.
+Run level should be one of \fBSs0123456\fP otherwise request would be
+silently ignored.
.PP
\fBtelinit\fP can tell \fBinit\fP how long it should wait
between sending processes the SIGTERM and SIGKILL signals. The default
-is 5 seconds, but this can be changed with the \fB-t\fP option.
+is 5 seconds, but this can be changed with the \fB\-t\fP option.
.PP
-\fBtelinit -e\fP tells \fBinit\fP to change the environment
+\fBtelinit \-e\fP tells \fBinit\fP to change the environment
for processes it spawns.
-The argument of \fB-e\fP is eithe
Bug#889144: marked as done (stricter PIDfile handling breaks several daemons)
Your message dated Fri, 09 Feb 2018 22:52:12 + with message-id <e1ekhwe-000evo...@fasolo.debian.org> and subject line Bug#889144: fixed in systemd 237-2 has caused the Debian Bug report #889144, regarding stricter PIDfile handling breaks several daemons 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.) -- 889144: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889144 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: systemd Version: 237-1 Severity: important Tags: upstream Hi! The upstream commit db256aab13d8a89d583ecd2bacf0aca87c66effc "core: be stricter when handling PID files and MAINPID sd_notify() messages" breaks several daemons in Debian. Known issues exist for - munin-node https://bugs.debian.org/889073 - ulogd2 - dnsmasq https://lists.debian.org/debian-user/2018/01/msg01331.html and possibly others. Symptom is a timeout during service start, constant service restarts (if configured) and log messages like: Feb 2 14:22:49 HOST systemd[1]: ulogd2.service: Permission denied while opening PID file or unsafe symlink chain: /run/ulog/ulogd.pid Feb 2 14:23:54 HOST systemd[1]: munin-node.service: Permission denied while opening PID file or unsafe symlink chain: /run/munin/munin-node.pid Problem lies, as far as I understand the change, in the permissions of the directory in which the PIDfile is created by the daemon. In all cases it does not belong root:root but the respective service user: HOST:/run# ls -ld ulog munin drwxr-xr-x 2 munin root 100 Feb 2 14:50 munin drwxr-xr-x 2 ulog ulog 40 Feb 2 14:24 ulog My quick'n'dirty workaround for munin was to change the PIDfile path to just "/run" in both the systemd unit and the configuration file and for ulogd2 I converted the unit from Type=forking to Type=simple, omitting the PIDfile completely. But this can only be a workaround in my opinion, because the upstream change changes an assumption on how and where PIDfiles can work without any prior notice. This needs to be changed to a non-fatal warning and not an error, IMHO. Grüße, Sven. -- Package-specific info: -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (200, 'experimental'), (1, 'experimental-debug') Architecture: i386 (x86_64) Foreign Architectures: amd64 Kernel: Linux 4.14.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages systemd depends on: ii adduser 3.116 ii libacl1 2.2.52-3+b1 ii libapparmor1 2.12-2 ii libaudit11:2.8.2-1 ii libblkid12.30.2-0.3 ii libc62.26-6 ii libcap2 1:2.25-1.2 ii libcryptsetup12 2:2.0.0-1 ii libgcrypt20 1.8.1-4 ii libgpg-error01.27-5 ii libidn11 1.33-2.1 ii libip4tc01.6.1-2+b1 ii libkmod2 25-1 ii liblz4-1 0.0~r131-2+b1 ii liblzma5 5.2.2-1.3 ii libmount12.30.2-0.3 ii libpam0g 1.1.8-3.6 ii libseccomp2 2.3.1-2.1 ii libselinux1 2.7-2 ii libsystemd0 237-1 ii mount2.30.2-0.3 ii procps 2:3.3.12-3 ii util-linux 2.30.2-0.3 Versions of packages systemd recommends: ii dbus1.12.2-1 ii libpam-systemd 237-1 Versions of packages systemd suggests: ii policykit-10.105-18 pn systemd-container Versions of packages systemd is related to: pn dracut ii initramfs-tools 0.130 ii udev 237-1 -- Configuration Files: /etc/systemd/journald.conf changed [not included] /etc/systemd/logind.conf changed [not included] /etc/systemd/system.conf changed [not included] -- debconf-show failed --- End Message --- --- Begin Message --- Source: systemd Source-Version: 237-2 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 889...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Biebl <bi...@debian.org> (supplier of updated systemd package) (This message was generated automatically at their request; if you believe that t
