Bug#883241: chrony: daemon doesn't automatically start

Seems like Conflicts= do not work reliably to ensure the systemd-timesyncd.service is not started during boot. See also the upstream bug report https://github.com/systemd/systemd/issues/7104 We've re-added the Conditions to systemd-timesyncd.service. # /lib/systemd/system/systemd-timesyncd.servic

Bug#933967: More information, testing using .link files to rename iface

>> Hm, you probably need to blacklist >> /lib/udev/rules.d/73-usb-net-by-mac.rules. You can do that by creating a >> file /etc/udev/rules.d/73-usb-net-by-mac.rules pointing at /dev/null >> >> After that (and running update-initramfs -u), 70-wifi.link should become >> active and you should be able

Processed: severity of 940840 is normal

Processing commands for cont...@bugs.debian.org: > severity 940840 normal Bug #940840 [systemd] systemd-time-wait-sync blocks indefinitely with alternative NTP Severity set to 'normal' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 940840: https

Processed: forcibly merging 931356 940971

Processing commands for cont...@bugs.debian.org: > forcemerge 931356 940971 Bug #931356 [libnss-systemd] libnss-systemd: 'systemd' entry in /etc/nsswitch.conf confuses daemons when systemd is not pid1 Bug #940971 [libnss-systemd] libnss-systemd: /etc/init.d/dbus blocks for 90 seconds when bootin

Bug#941758: systemd: StopWhenUnneeded has stopped working for a mount unit

Am 04.10.19 um 22:57 schrieb Jonathan Dowland: > Package: systemd > Version: 241-7~deb10u1 > Severity: normal > > I have a mount unit as follows > > [Unit] > Requires=systemd-cryptsetup@backup.service > StopWhenUnneeded=true > > [Mount] > What=/dev/phobos_backup/backup >

Bug#940021: systemd: socket activation leads to OOM situation due to slices not getting cleaned up

* Michael Biebl [191004 21:51]: > Am 11.09.19 um 15:54 schrieb Julian Hübenthal: > > Just discovered something that may help to debug: >   > > > > It does not happen with a simple “Hello World” bash script instead of > > the Check MK Agent. > > > > It does not happen when the Encryption of the

Bug#941239: systemd 241-7, poweroff+reboot stalls/freezes after "Reached target shutdown"

Am 04.10.19 um 13:34 schrieb Rado S: >> Please also follow the hints in >> /usr/share/doc/systemd/README.Debian.gz (Debugging boot/shutdown problems) >> >> See the section starting with "In situations where the debug shell is >> not available,..." > > I've attached the so produced log-file. > > D

Bug#941239: systemd 241-7, poweroff+reboot stalls/freezes after "Reached target shutdown"

Am 04.10.19 um 13:34 schrieb Rado S: > =- Michael Biebl wrote on Thu 3.Oct'19 at 13:51:28 +0200 -= > >>> How to find more information on this failure? >> >> Do you get any shutdown messages from systemd when you shut down? > > No, the screen is black all the time except for the initally > blinki

Bug#941239: systemd 241-7, poweroff+reboot stalls/freezes after "Reached target shutdown"

=- Michael Biebl wrote on Thu 3.Oct'19 at 13:51:28 +0200 -= > > How to find more information on this failure? > > Do you get any shutdown messages from systemd when you shut down? No, the screen is black all the time except for the initally blinking but eventually frozen cursor in top-left corn

Bug#940021: Re[2]: Bug#940021: systemd: socket activation leads to OOM situation due to slices not getting cleaned up

* Julian Hübenthal [Mon Sep 16, 2019 at 06:01:41PM +]: > here is your requested output: [...] You might want to take a look at https://checkmk.de/check_mk-werks.php?werk_id=10070 - I'm quoting from there: | We have seen cases in which the parameter "KillMode=process" of the | unit file "chec