Comment 10 for bug 2055012

Revision history for this message
Danilo Egea Gondolfo (danilogondolfo) wrote :

I can confirm this is an issue, although it's not caused by Network Manager so I'll go ahead and set it as invalid.

After trying to do a "do-release-upgrade -d" from a brand new installation of Jammy 22.04.4, gnome-shell crashed and interrupted the upgrade.

After that, this is what "dpkg --list | grep systemd" looks like:

ii dbus-user-session 1.14.10-4ubuntu4 amd64 simple interprocess messaging system (systemd --user integration)
ii gnome-logs 42.0-1 amd64 viewer for the systemd journal
ii libnss-systemd:amd64 249.11-0ubuntu3.12 amd64 nss module providing dynamic user and group name resolution
ii libpam-systemd:amd64 249.11-0ubuntu3.12 amd64 system and service manager - PAM module
ii libsystemd-shared:amd64 255.4-1ubuntu8 amd64 systemd shared private library
ii libsystemd0:amd64 255.4-1ubuntu8 amd64 systemd utility library
ii networkd-dispatcher 2.1-2ubuntu0.22.04.2 all Dispatcher service for systemd-networkd connection status changes
ii python3-systemd 235-1build4 amd64 Python 3 bindings for systemd
ii systemd 255.4-1ubuntu8 amd64 system and service manager
ii systemd-dev 255.4-1ubuntu8 all systemd development files
ii systemd-hwe-hwdb 249.11.5 all udev rules for hardware enablement (HWE)
ii systemd-oomd 249.11-0ubuntu3.12 amd64 Userspace out-of-memory (OOM) killer
ii systemd-sysv 249.11-0ubuntu3.12 amd64 system and service manager - SysV links
ii systemd-timesyncd 255.4-1ubuntu8 amd64 minimalistic service to synchronize local time with NTP servers

and /etc/resolv.conf is a broken link as systemd-resolved is not installed and /run/systemd/resolve doesn't exist:

/etc/resolv.conf -> ../run/systemd/resolve/stub-resolv.conf