When I upgraded from 22.04 to 24.04, DNS resolution went wrong.

[Zalán Hári]

I was an unpatient idiot, and I upgraded from 22.04 to 24.04. Near to the end of the upgrade, I got an „Oh, no! Something has gone wrong and the system cannot recover. Call the system administrator” message after a red FAILED in the terminal. The system administrator is myself, because my computer is a personal one. Hard reset, same error, Ctrl+Alt+F3, sudo apt reinstall gdm3. Obviously. I needed to finish the update with dpkg. While dpkg was upgrading, it printed an error message for every WiFi connection:

„[Failed] Failed to migrate [I do not remember, something with /etc/netplan]”

It took at least one and a half hour to find the solution on Ask Ubuntu. The problem was: /etc/resolv.conf became a broken link, along with systemd-resolve.service. I needed to remove both of them and write a new resolv.conf to fix the error.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: network-manager 1.45.90-1ubuntu1
ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
Uname: Linux 6.6.0-14-generic x86_64
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Feb 26 08:21:02 2024
InstallationDate: Installed on 2023-07-05 (236 days ago)
InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316)
IpRoute:
 default via 192.168.0.1 dev wlp3s0 proto dhcp src 192.168.0.100 metric 600
 192.168.0.0/24 dev wlp3s0 proto kernel scope link src 192.168.0.100 metric 600
 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=<set>
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: network-manager
UpgradeStatus: Upgraded to noble on 2024-02-24 (2 days ago)
modified.conffile..etc.init.d.apport: [modified]
mtime.conffile..etc.init.d.apport: 2024-02-22T15:20:00
nmcli-nm:
 RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN
 running 1.45.90 connected started full enabled enabled enabled missing enabled

[Eliseo Martínez (elmart)]

My case was exactly the same. And I also did the same as you at first (fixing /etc/resolv.conf by hand). After that I've realized that doing `sudo apt install systemd-resolved` seems to fix the situation better (/etc/resolv.conf is a link again, but now it's not broken). Also, `netplan status` reported to be offline before and says it's online now. `resolvectl status` lets you see your dhcp configured dns servers.

So, maybe failure in migrating network configurations prevented systemd-resolved to be installed, for some reason. BTW, in my case, the network I am currently connected to was migrated ok (I had a netplan file for it in /etc/netplan). The ones giving problems were other ones referring to other locations (my parents' home and such) that were not reachable at the moment of doing the migration.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Zalán Hári (zalanhari)]

I did not try that and I hope that I will not need to, but sudo apt install systemd-resolved seems to be much better.

[Md. Raisul Islam (rochi88)]

I have also faced the issue ... Same manner.

[Skashmeri (skashmeri)]

this affected me as well

[pmeerw (pmeerw)]

same, at least it's easy to fix

what's worse is that snap applications (firefox, chromium, slack) fail to resolve hostnames, see e.g. https://askubuntu.com/questions/1510668/network-problems-with-snap-apps

[Anurag (anurag1008)]

While upgrading, i noticed the whole screen became white and it has the error "Oh, no! Something has gone wrong and the system cannot recover. Call the system administrator”.
Now it cannot boot at all.

Rebooted in Recovery mode. User repair broken packages. It updated the packages.
Rebooted, could login. But had problems with the web browser.
Installed systemd-resolved, Command 'sudo apt install systemd-resolved'

Now working.

[Danilo Egea Gondolfo (danilogondolfo)]

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

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Nick Rosbrook (enr0n)]

I attempted an upgrade from a clean Jammy install to Noble so that I could gather upgrade logs. I have attached them here.

[Nick Rosbrook (enr0n)]

Adding my journal from the crash.

[Nick Rosbrook (enr0n)]

The problem is that gnome-shell crashes during the upgrade, so packages including systemd-resolved never finish getting installed. Marking as a duplicate of bug 2054761.

[Beowulf (s-highlander)]

I have the same issue.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Jason Ernst (compscidr)]

Same issue upgrading from 22.04 to 24.04, confirmed the fix of `sudo apt install systemd-resolved` fixes the issue.

Had a crash partway through the upgrade where I was left with the UI showing "something went wrong", which was partially fixed by dropping into a terminal and commadning `sudo dpkg --configure -a`, but it was left in this state afterwards.

[gianfilippo (gianfi)]

I confirm fixing of the issue with sudo apt install systemd-resolved
after broken update from 22.04

[Mahboob Karimian (mahboobkarimian)]

I had UI crash during upgrade from jammy. I had to go to recovery mode and run dpkg.
I confirm sudo apt install systemd-resolved resolves the problem.
But the upgrade is not recommended as you may encounter unfinished upgrade and gnome shell crash.

[Leo Didier (leobaba)]

Same for me, the upgrade went horribly also wrong...

But i could get everything on track again from the terminal with a complete update and upgrade the missing packages.
Did not have to do install systemd-resolved as i already had the latest installed.

Then in Ubuntu 24 desktop i had troubles with long minutes hanging on a grey screen, firefox freeze at start up and other desktop freezes..
A snap store refresh did the job with 'sudo snap refresh snap-store' and everything is working fine now !