Your message dated Mon, 21 Dec 2020 17:52:40 +0100
with message-id <[email protected]>
and subject line Re: Bug#976659: Kernel panic while upgrading systemd
has caused the Debian Bug report #976659,
regarding Kernel panic while upgrading systemd
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 [email protected]
immediately.)
--
976659: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976659
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: systemd
Version: 246.6-4
Dear maintainer,
I'm trying to upgrade systemd (along with libnss-systemd libpam-systemd
libsystemd0 libudev1 systemd systemd-sysv systemd-timesyncd udev) from
version 246-2 to version 246.6-4, but I'm encountering a kernel panic
during systemd's package configuration. Please find as attchment the
secreenshot with logs.
Regards,
Guillaume
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 5.9.0-4-686-pae (SMP w/2 CPU threads)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE
not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages systemd depends on:
ii adduser 3.118
ii libacl1 2.2.53-8
ii libapparmor1 2.13.5-1+b1
ii libaudit1 1:2.8.5-3.1
ii libblkid1 2.36.1-2
ii libc6 2.31-5
ii libcap2 1:2.44-1
ii libcrypt1 1:4.4.17-1
ii libcryptsetup12 2:2.3.4-1
ii libgcrypt20 1.8.7-2
ii libgnutls30 3.6.15-4
ii libgpg-error0 1.38-2
ii libidn2-0 2.3.0-4
ii libip4tc2 1.8.6-1
ii libkmod2 27+20200310-2
ii liblz4-1 1.9.2-2
ii liblzma5 5.2.4-1+b1
ii libmount1 2.36.1-2
ii libpam0g 1.3.1-5
ii libpcre2-8-0 10.34-7
ii libseccomp2 2.5.0-3
ii libselinux1 3.1-2+b1
ii libsystemd0 246-2
ii libzstd1 1.4.5+dfsg-4
ii mount 2.36.1-2
ii systemd-timesyncd [time-daemon] 246-2
ii util-linux 2.36.1-2
Versions of packages systemd recommends:
ii dbus 1.12.20-1
Versions of packages systemd suggests:
pn policykit-1 <none>
pn systemd-container <none>
Versions of packages systemd is related to:
pn dracut <none>
ii initramfs-tools 0.139
ii libnss-systemd 246-2
ii libpam-systemd 246-2
ii udev 246-2
--- End Message ---
--- Begin Message ---
Hi
On Tue, 15 Dec 2020 09:28:55 +0100 Guillaume Brocker
<[email protected]> wrote:
> Although all upgrade attempts fail, I agree to close this bug. The
> system was installed for more than 15 years now, and is running and
> regulary upgraded since. So I guess there must be a kind of old thing in
> my computer's file system that leeds to this bug.
Have you checked if you have any libraries in /usr/local/lib which
might be interfering? You can use `ldd /lib/systemd/systemd`
Anyway, I'm closing this bug report now. Should you manage to gather a
backtrace [1], just let us know and we will reopen this bug report.
Regards,
Michael
[1] https://wiki.debian.org/HowToGetABacktrace
Install the dbgsym packages for systemd and systemd-coredump
signature.asc
Description: This is a digitally signed message part
--- End Message ---
