0008921: Errors for systemd while installing sudo

ID	Project	Category	View Status	Date Submitted	Last Update

0008921	Kali Linux	Kali Package Bug	public	2024-09-18 02:41	2024-10-14 03:36

Reporter	Vampire	Assigned To	arnaudr
Priority	normal	Severity	minor	Reproducibility	have not tried
Status	resolved	Resolution	won't fix

Summary	0008921: Errors for systemd while installing sudo
Description	When I install kali-linux in WSL (1) on GitHub Actions virtual machine and then do `apt-get update` followed by `apt-get install --yes --no-install-recommends sudo`, the operation fails. This worked fine yesterday. Here the install log: Reading package lists... Building dependency tree... Reading state information... The following additional packages will be installed: libc-bin libc-l10n libc6 libssl3t64 libsystemd-shared libsystemd0 libudev1 libzstd1 locales-all openssl openssl-provider-legacy systemd systemd-sysv udev Suggested packages: glibc-doc locales libnss-nis libnss-nisplus libarchive13t64 libbpf1 libdw1t64 libelf1t64 libfido2-1 libpwquality1 libqrencode4 libtss2-rc0t64 systemd-container systemd-homed systemd-userdbd systemd-boot systemd-resolved systemd-repart libtss2-tcti-device0 polkitd Recommended packages: manpages default-dbus-system-bus \| dbus-system-bus linux-sysctl-defaults systemd-timesyncd \| time-daemon systemd-cryptsetup libpam-systemd libnss-systemd The following packages will be REMOVED: libssl3 The following NEW packages will be installed: libssl3t64 openssl-provider-legacy The following packages will be upgraded: libc-bin libc-l10n libc6 libsystemd-shared libsystemd0 libudev1 libzstd1 locales-all openssl sudo systemd systemd-sysv udev 13 upgraded, 2 newly installed, 1 to remove and 168 not upgraded. Need to get 29.6 MB of archives. After this operation, 13.6 MB of additional disk space will be used. Get:11 http://mirror.accuris.ca/kali kali-rolling/main amd64 libc-bin amd64 2.40-2 [613 kB] Get:3 http://kali.download/kali kali-rolling/main amd64 openssl-provider-legacy amd64 3.3.2-1 [298 kB] Get:4 http://kali.download/kali kali-rolling/main amd64 libssl3t64 amd64 3.3.2-1 [2,271 kB] Get:5 http://kali.download/kali kali-rolling/main amd64 libsystemd-shared amd64 256.5-1 [2,060 kB] Get:6 http://kali.download/kali kali-rolling/main amd64 libc6 amd64 2.40-2 [2,791 kB] Get:8 http://kali.download/kali kali-rolling/main amd64 systemd amd64 256.5-1 [3,489 kB] Get:9 http://http.kali.org/kali kali-rolling/main amd64 libzstd1 amd64 1.5.6+dfsg-1 [303 kB] Get:10 http://kali.download/kali kali-rolling/main amd64 openssl amd64 3.3.2-1 [1,381 kB] Get:12 http://kali.download/kali kali-rolling/main amd64 systemd-sysv amd64 256.5-1 [57.7 kB] Get:13 http://http.kali.org/kali kali-rolling/main amd64 sudo amd64 1.9.15p5-3+b1 [2,043 kB] Get:15 http://kali.download/kali kali-rolling/main amd64 libudev1 amd64 256.5-1 [144 kB] Get:1 http://kali.mirror.rafal.ca/kali kali-rolling/main amd64 libc-l10n all 2.40-2 [725 kB] Get:2 http://kali.mirror.rafal.ca/kali kali-rolling/main amd64 locales-all amd64 2.40-2 [11.1 MB] Get:7 http://kali.mirror.rafal.ca/kali kali-rolling/main amd64 libsystemd0 amd64 256.5-1 [381 kB] Get:14 http://kali.mirror.rafal.ca/kali kali-rolling/main amd64 udev amd64 256.5-1 [1,897 kB] Preconfiguring packages ... Fetched 29.6 MB in 5s (6,083 kB/s) (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 17300 files and directories currently installed.) Preparing to unpack .../libc-l10n_2.40-2_all.deb ... Unpacking libc-l10n (2.40-2) over (2.33-8) ... Preparing to unpack .../locales-all_2.40-2_amd64.deb ... Unpacking locales-all (2.40-2) over (2.33-8) ... dpkg: libssl3:amd64: dependency problems, but removing anyway as you requested: systemd depends on libssl3 (>= 3.0.0). openssl depends on libssl3 (>= 3.0.3). libsystemd-shared:amd64 depends on libssl3 (>= 3.0.0). libssh2-1:amd64 depends on libssl3 (>= 3.0.0). libsasl2-modules:amd64 depends on libssl3 (>= 3.0.0). libkrb5-3:amd64 depends on libssl3 (>= 3.0.0). libkmod2:amd64 depends on libssl3 (>= 3.0.0). libcurl4:amd64 depends on libssl3 (>= 3.0.0). libcryptsetup12:amd64 depends on libssl3 (>= 3.0.0). kmod depends on libssl3 (>= 3.0.0). bind9-libs:amd64 depends on libssl3 (>= 3.0.0). (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 17455 files and directories currently installed.) Removing libssl3:amd64 (3.0.4-2) ... Selecting previously unselected package openssl-provider-legacy. (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 17443 files and directories currently installed.) Preparing to unpack .../openssl-provider-legacy_3.3.2-1_amd64.deb ... Unpacking openssl-provider-legacy (3.3.2-1) ... Selecting previously unselected package libssl3t64:amd64. Preparing to unpack .../libssl3t64_3.3.2-1_amd64.deb ... Unpacking libssl3t64:amd64 (3.3.2-1) ... Preparing to unpack .../libsystemd-shared_256.5-1_amd64.deb ... Unpacking libsystemd-shared:amd64 (256.5-1) over (251.2-7) ... dpkg: considering deconfiguration of systemd, which would be broken by installation of libc6:amd64 ... dpkg: yes, will deconfigure systemd (broken by libc6:amd64) Preparing to unpack .../libc6_2.40-2_amd64.deb ... De-configuring systemd (251.2-7), to allow installation of libc6:amd64 (2.40-2) ... Checking for services that may need to be restarted... Checking init scripts... Unpacking libc6:amd64 (2.40-2) over (2.33-8) ... Setting up libc6:amd64 (2.40-2) ... Checking for services that may need to be restarted... Checking init scripts... Nothing to restart. (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 17452 files and directories currently installed.) Preparing to unpack .../libsystemd0_256.5-1_amd64.deb ... Unpacking libsystemd0:amd64 (256.5-1) over (251.2-7) ... Setting up libsystemd0:amd64 (256.5-1) ... (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 17453 files and directories currently installed.) Preparing to unpack .../libzstd1_1.5.6+dfsg-1_amd64.deb ... Unpacking libzstd1:amd64 (1.5.6+dfsg-1) over (1.5.2+dfsg-1) ... Setting up libzstd1:amd64 (1.5.6+dfsg-1) ... Setting up openssl-provider-legacy (3.3.2-1) ... Setting up libssl3t64:amd64 (3.3.2-1) ... (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 17453 files and directories currently installed.) Preparing to unpack .../systemd_256.5-1_amd64.deb ... Unpacking systemd (256.5-1) over (251.2-7) ... dpkg: warning: unable to delete old directory '/lib/systemd/system-generators': Directory not empty dpkg: warning: unable to delete old directory '/lib/systemd/system/user-.slice.d': Directory not empty dpkg: warning: unable to delete old directory '/lib/systemd/system/timers.target.wants': Directory not empty dpkg: warning: unable to delete old directory '/lib/systemd/system/systemd-localed.service.d': Directory not empty dpkg: warning: unable to delete old directory '/lib/systemd/system/rescue.target.wants': Directory not empty dpkg: warning: unable to delete old directory '/lib/systemd/system/rc-local.service.d': Directory not empty dpkg: warning: unable to delete old directory '/lib/systemd/system/multi-user.target.wants': Directory not empty dpkg: warning: unable to delete old directory '/lib/systemd/system/local-fs.target.wants': Directory not empty dpkg: warning: unable to delete old directory '/lib/systemd/system/graphical.target.wants': Directory not empty dpkg: warning: unable to delete old directory '/lib/systemd/system/getty.target.wants': Directory not empty Preparing to unpack .../openssl_3.3.2-1_amd64.deb ... Unpacking openssl (3.3.2-1) over (3.0.4-2) ... Preparing to unpack .../libc-bin_2.40-2_amd64.deb ... Unpacking libc-bin (2.40-2) over (2.33-8) ... Setting up libc-bin (2.40-2) ... Setting up libsystemd-shared:amd64 (256.5-1) ... Setting up systemd (256.5-1) ... Installing new version of config file /etc/systemd/journald.conf ... Installing new version of config file /etc/systemd/logind.conf ... Installing new version of config file /etc/systemd/networkd.conf ... Installing new version of config file /etc/systemd/pstore.conf ... Installing new version of config file /etc/systemd/sleep.conf ... Installing new version of config file /etc/systemd/system.conf ... Installing new version of config file /etc/systemd/user.conf ... Failed to take /etc/passwd lock: Invalid argument dpkg: error processing package systemd (--configure): installed systemd package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: systemd E: Sub-process /usr/bin/dpkg returned an error code (1)

Vampire 2024-10-09 17:36 reporter ~0019885	Any updates? :-(

kali-bugreport 2024-10-09 19:03 reporter ~0019886	Tried google :-)? https://superuser.com/a/1805742 seems to indicate that the systemd packages (AFAICT) doesn't support WSL1

Vampire 2024-10-10 15:56 reporter ~0019887	Well, even if that is the case, I'd still hope for kali project taking care. Because kali is compatible with WSL 1 and it has that version of systemd in its repository now. Some potential options (that can also be combined): make upstream fix it if it is an upstream problem make a work-around in kali that fixes the problem (seems there are work-arounds) downgrade systemd in the repository to a version that does not have that problem ...?

kali-bugreport 2024-10-10 16:33 reporter ~0019888	Report an issue to Debian as the maintainer of the systemd packages :-)

Vampire 2024-10-10 16:40 reporter ~0019889	!?! I'm not using Debian, I'm using kali. Thus I'm reporting to kali. If kali uses the Debian packages, then please you talk to Debian about it. My tests also run against Debian and there I had not yet a problem so far.

kali-bugreport 2024-10-10 18:43 reporter ~0019890 Last edited: 2024-10-10 20:43	I can't talk to Debian in any way as i'm no Kali team member. But Kali is largely based on Debian and shipping many packages directly from Debian testing and the Kali team has posted many times that they don't have the people to do own fixes for such packages pulled directly from Debian. For such cases Debian needs to fix the packages which then will land in Kali afterwards.

kali-bugreport 2024-10-10 18:45 reporter ~0019891	See eg. 0008926:0019812

kali-bugreport 2024-10-10 18:53 reporter ~0019892	https://pkg.kali.org/pkg/systemd also lists this as responsible maintainer / contact point: maintainer: Debian systemd Maintainers (mailto:[email protected])

kali-bugreport 2024-10-10 19:01 reporter ~0019893	Won't fix in Debian https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053749: WSL1 is de-facto deprecated, just switch to WSL2. This is basic filesystem functionality and it just needs to work. If you don't want to switch to WSL2 for any reason, then just use Debian oldstable instead of unstable.

arnaudr 2024-10-14 03:35 manager ~0019905	Hello ! At a quick look, it seems indeed to be reported in Debian, at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053749, that was back in October 2023. Thx for doing the research @kali-bugreport. The person who answered the Debian bug (Luca Boccassi) is a Debian Developer and works for Microsoft, he must be knowledgeable on the matter. I've seen (following the Debian bug report), that it's been reported to upstream systemd: https://github.com/systemd/systemd/issues/29512. The answer is the same: WSL1 is not supported. There's nothing we (Kali) can do about that, apart from updating our doc to say that Kali doesn't work on WSL1 anymore. @Vampire Sorry but there's nothing we can do.

Date Modified	Username	Field	Change
2024-09-18 02:41	Vampire	New Issue
2024-10-09 17:36	Vampire	Note Added: 0019885
2024-10-09 19:03	kali-bugreport	Note Added: 0019886
2024-10-10 15:56	Vampire	Note Added: 0019887
2024-10-10 16:33	kali-bugreport	Note Added: 0019888
2024-10-10 16:40	Vampire	Note Added: 0019889
2024-10-10 18:43	kali-bugreport	Note Added: 0019890
2024-10-10 18:45	kali-bugreport	Note Added: 0019891
2024-10-10 18:53	kali-bugreport	Note Added: 0019892
2024-10-10 19:01	kali-bugreport	Note Added: 0019893
2024-10-10 20:43	kali-bugreport	Note Edited: 0019890
2024-10-14 03:35	arnaudr	Note Added: 0019905
2024-10-14 03:36	arnaudr	Assigned To	=> arnaudr
2024-10-14 03:36	arnaudr	Status	new => assigned
2024-10-14 03:36	arnaudr	Status	assigned => resolved
2024-10-14 03:36	arnaudr	Resolution	open => won't fix

View Issue Details

Activities

Issue History