Package: systemd Followup-For: Bug #1112535 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
Dear Maintainer, I hit this as well with the upgrade from 13.0 to 13.1. Downgrading systemd from 257.8-1~deb13u1 to 257.7-1 again fixed the problem. But this is very hard to do without networking.... Which I believe justifies increasing the severity of this bug even more. It completely breaks affected systems in hard to repair ways. I believe this bug might be relevant: https://github.com/systemd/systemd/issues/38515 The failing system has a complex setup with VLANs on top of a bridge. - -- Package-specific info: - -- System Information: Debian Release: 13.1 APT prefers stable-security APT policy: (700, 'stable-security'), (700, 'stable'), (699, 'stable-updates') Architecture: amd64 (x86_64) Kernel: Linux 6.12.43+deb13-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages systemd depends on: ii libacl1 2.3.2-2+b1 ii libapparmor1 4.1.0-1 ii libc6 2.41-12 ii libmount1 2.41-5 ii libpam0g 1.7.0-5 ii libseccomp2 2.6.0-2 ii libselinux1 3.8.1-1 ii libssl3t64 3.5.1-1 hi libsystemd-shared 257.7-1 hi libsystemd0 257.7-1 ii mount 2.41-5 Versions of packages systemd recommends: ii chrony [time-daemon] 4.6.1-3 ii dbus [default-dbus-system-bus] 1.16.2-2 ii linux-sysctl-defaults 4.12 pn systemd-cryptsetup <none> Versions of packages systemd suggests: pn libtss2-tcti-device0 <none> pn polkitd <none> pn systemd-boot <none> ii systemd-container 257.8-1~deb13u1 pn systemd-homed <none> pn systemd-repart <none> pn systemd-resolved <none> pn systemd-userdbd <none> Versions of packages systemd is related to: ii dbus-user-session 1.16.2-2 pn dracut <none> ii initramfs-tools 0.148.3 pn libnss-systemd <none> ii libpam-systemd 257.8-1~deb13u1 hu udev 257.7-1 - -- Configuration Files: /etc/systemd/journald.conf changed [not included] /etc/systemd/networkd.conf changed [not included] - -- no debconf information -----BEGIN PGP SIGNATURE----- iGwEAREKACwWIQR3fjfc8EF8nPbC0aDXSuqSjBsiyQUCaLwyWQ4cYmpvcm5AbW9y ay5ubwAKCRDXSuqSjBsiycnWAJ0RNnK4Khf3xmNxPcI/C2IbEEkDcACeLBOwc09e t0MrkXm/bfeaWahywcQ= =4V0M -----END PGP SIGNATURE-----
