Your message dated Thu, 16 Nov 2023 08:52:16 +0000
with message-id <d061f1e753b5e63321ecbd90b68e1643ea8d98c0.ca...@debian.org>
and subject line Re: systemd: some services don't start after systemd update
has caused the Debian Bug report #1056034,
regarding systemd: some services don't start after systemd update
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.)
--
1056034: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056034
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd
Version: 255~rc2-1
Severity: normal
X-Debbugs-Cc: antde...@gmail.com
Dear Maintainer,
after updating "systemd" to version "255~rc2-1" some services do not start:
- systemd-resolved.service:
nov 16 08:57:37 SAT (resolved)[1183]: systemd-resolved.service: Failed to set
up special execution directory in /run: Invalid argument
- systemd-timesyncd.service:
nov 16 08:57:37 SAT systemd[1]: Failed to start systemd-timesyncd.service -
Network Time Synchronization.
nov 16 08:57:37 SAT (imesyncd)[1249]: systemd-timesyncd.service: Failed to set
up special execution directory in /run: Invalid argument
- wpa_supplicant.service:
nov 16 08:57:38 SAT (pplicant)[1943]: wpa_supplicant.service: Failed to set up
special execution directory in /run: Invalid argument
nov 16 08:57:38 SAT systemd[1]: Failed to start wpa_supplicant.service
nov 16 08:58:46 SAT NetworkManager[1453]: <error> [1700121526.2236] device
(wlan0): Couldn't initialize supplicant interface: Failed to D-Bus activate
wpa_supplicant service
- systemd-tmpfiles
nov 16 08:57:36 SAT systemd-tmpfiles[661]: fchmod() of /dev/snd/seq failed:
Invalid argument
nov 16 08:57:36 SAT systemd-tmpfiles[661]: fchmod() of /dev/snd/timer failed:
Invalid argument
nov 16 08:57:36 SAT systemd-tmpfiles[661]: fchmod() of /dev/loop-control
failed: Invalid argument
nov 16 08:57:36 SAT systemd-tmpfiles[661]: fchmod() of /dev/net/tun failed:
Invalid argument
nov 16 08:57:36 SAT systemd-tmpfiles[661]: fchmod() of /dev/fuse failed:
Invalid argument
nov 16 08:57:36 SAT systemd-tmpfiles[661]: fchmod() of /dev/vfio/vfio failed:
Invalid argument
nov 16 08:57:36 SAT systemd-tmpfiles[661]: fchmod() of /dev/vhost-net failed:
Invalid argument
nov 16 08:57:36 SAT systemd-tmpfiles[661]: fchmod() of /dev/vhost-vsock failed:
Invalid argument
nov 16 08:57:36 SAT systemd-tmpfiles[670]: fchmod() of /dev/snd/seq failed:
Invalid argument
nov 16 08:57:36 SAT systemd-tmpfiles[670]: fchmod() of /dev/snd/timer failed:
Invalid argument
nov 16 08:57:36 SAT systemd-tmpfiles[670]: fchmod() of /dev/loop-control
failed: Invalid argument
nov 16 08:57:36 SAT systemd-tmpfiles[670]: fchmod() of /dev/net/tun failed:
Invalid argument
nov 16 08:57:36 SAT systemd-tmpfiles[670]: fchmod() of /dev/fuse failed:
Invalid argument
nov 16 08:57:36 SAT systemd-tmpfiles[670]: fchmod() of /dev/vfio/vfio failed:
Invalid argument
nov 16 08:57:36 SAT systemd-tmpfiles[670]: fchmod() of /dev/vhost-net failed:
Invalid argument
nov 16 08:57:36 SAT systemd-tmpfiles[670]: fchmod() of /dev/vhost-vsock failed:
Invalid argument
nov 16 08:57:37 SAT systemd-tmpfiles[1096]: fchmod() of /run/dbus/containers
failed: Invalid argument
nov 16 08:57:37 SAT systemd-tmpfiles[1096]: fchmod() of /run/php failed:
Invalid argument
nov 16 08:57:37 SAT systemd-tmpfiles[1096]: fchmod() of /run/rpcbind failed:
Invalid argument
nov 16 08:57:37 SAT systemd-tmpfiles[1096]: fchmod() of /run/screen failed:
Invalid argument
nov 16 08:57:37 SAT systemd-tmpfiles[1096]: fchmod() of /run/systemd/netif
failed: Invalid argument
nov 16 08:57:37 SAT systemd-tmpfiles[1096]: fchmod() of
/run/systemd/netif/links failed: Invalid argument
nov 16 08:57:37 SAT systemd-tmpfiles[1096]: fchmod() of
/run/systemd/netif/leases failed: Invalid argument
nov 16 08:57:37 SAT systemd-tmpfiles[1096]: fchmod() of /run/systemd/netif/lldp
failed: Invalid argument
nov 16 08:57:37 SAT systemd-tmpfiles[1096]: fchmod() of /run/utmp failed:
Invalid argument
nov 16 08:57:37 SAT systemd-tmpfiles[1096]: fchmod() of /run/tpm2-tss/eventlog
failed: Invalid argument
nov 16 08:57:37 SAT systemd-tmpfiles[1096]: fchmod() of /run/log/journal
failed: Invalid argument
nov 16 08:57:37 SAT systemd-tmpfiles[1096]: fchmod() of
/sys/kernel/security/tpm0/binary_bios_measurements failed: Invalid argument
nov 16 08:57:37 SAT systemd-tmpfiles[1096]: fchmod() of
/sys/kernel/security/ima/binary_runtime_measurements failed: Invalid argument
---
also note the truncated keywords "(pplicant)", "(imesyncd)"
what has changed?
Thanks,
Antonio
-- Package-specific info:
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (700, 'unstable'), (500, 'stable-updates'), (500,
'stable-security'), (500, 'stable'), (100, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.5.11-4-liquorix-amd64 (SMP w/24 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=it
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages systemd depends on:
ii libacl1 2.3.1-3
ii libapparmor1 3.0.12-1
ii libaudit1 1:3.1.1-1
ii libblkid1 2.39.2-6
ii libc6 2.37-12
ii libcap2 1:2.66-4
ii libcryptsetup12 2:2.6.1-5
ii libfdisk1 2.39.2-6
ii libgcrypt20 1.10.2-3
ii libkmod2 30+20230601-2
ii liblz4-1 1.9.4-1
ii liblzma5 5.4.4-0.1
ii libmount1 2.39.2-6
ii libpam0g 1.5.2-9.1
ii libseccomp2 2.5.4-2
ii libselinux1 3.5-1
ii libssl3 3.0.12-2
ii libsystemd-shared 255~rc2-1
ii libsystemd0 255~rc2-1
ii libzstd1 1.5.5+dfsg2-2
ii mount 2.39.2-6
ii systemd-dev 255~rc2-1
Versions of packages systemd recommends:
ii dbus [default-dbus-system-bus] 1.14.10-3
ii systemd-timesyncd [time-daemon] 255~rc2-1
Versions of packages systemd suggests:
ii libfido2-1 1.13.0-1+b1
ii libip4tc2 1.8.9-2
ii libp11-kit0 0.25.0-5
ii libqrencode4 4.1.1-1
ii libtss2-esys-3.0.2-0 4.0.1-3
ii libtss2-mu0 4.0.1-3
ii libtss2-rc0 4.0.1-3
ii polkitd 123-3
ii python3 3.11.4-5+b1
pn python3-pefile <none>
ii systemd-boot 255~rc2-1
ii systemd-container 255~rc2-1
pn systemd-homed <none>
ii systemd-resolved 255~rc2-1
ii systemd-userdbd 255~rc2-1
Versions of packages systemd is related to:
ii dbus-user-session 1.14.10-3
pn dracut <none>
ii initramfs-tools 0.142
ii libnss-systemd 255~rc2-1
ii libpam-systemd 255~rc2-1
ii udev 255~rc2-1
-- Configuration Files:
/etc/systemd/system.conf changed [not included]
/etc/systemd/user.conf changed [not included]
-- no debconf information
--- End Message ---
--- Begin Message ---
Control: tags 1056034 wontfix
On Thu, 16 Nov 2023 09:14:30 +0100 antonio <antde...@gmail.com> wrote:
> Package: systemd
> Version: 255~rc2-1
> Severity: normal
> X-Debbugs-Cc: antde...@gmail.com
>
> Dear Maintainer,
> after updating "systemd" to version "255~rc2-1" some services do not
start:
...
> Kernel: Linux 6.5.11-4-liquorix-amd64 (SMP w/24 CPU threads; PREEMPT)
You are not using a Debian kernel, so we cannot offer you support.
Someone with the same broken kernel reported a similar issue upstream,
and was redirected to the kernel supplier:
https://github.com/damentz/liquorix-package/issues/147
--
Kind regards,
Luca Boccassi
signature.asc
Description: This is a digitally signed message part
--- End Message ---
