[Bug 2055012] Re: When I upgraded from 22.04 to 24.04, DNS resolution went wrong.
*** This bug is a duplicate of bug 2054761 *** https://bugs.launchpad.net/bugs/2054761 I have the same issue on multiple hosts, including my laptop, with intermittent DNS failures depending on the command used, after upgrading to 24.04. The fix is rather unclear. For a laptop which connects and reconnects to different networks, this is a pain. For a server, this is also a pain. I understand that `cloud-init` recorded Notably, it seems (?!) the DNS configuration do not match DHCP settings, so it is unclear from where cloud init got it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055012 Title: When I upgraded from 22.04 to 24.04, DNS resolution went wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2055012/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055012] Re: When I upgraded from 22.04 to 24.04, DNS resolution went wrong.
*** This bug is a duplicate of bug 2054761 *** https://bugs.launchpad.net/bugs/2054761 @mchelen Please open a new bug report by running `ubuntu-bug ubuntu- release-upgrader-core` on the affected system. This will attach the necessary logs to investigate your upgrade issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055012 Title: When I upgraded from 22.04 to 24.04, DNS resolution went wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2055012/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055012] Re: When I upgraded from 22.04 to 24.04, DNS resolution went wrong.
*** This bug is a duplicate of bug 2054761 *** https://bugs.launchpad.net/bugs/2054761 Same issue occurred for me today on upgrade from 22.04 to 24.04. There was some error during the initial upgrade, causing it to exit and it had to be resumed. After the upgrade completed, `/etc/resolv.conf/` was linked to `/run/systemd/resolve/stub-resolv.conf` however this file did not exist. The package `systemd-resolved` was not installed or marked for installation. To fix this, I installed the package resulting in `/run/systemd/resolve/stub-resolv.conf` being generated, and after a `sudo systemctl restart NetworkManager.service` DNS resolution worked again. Here is what I see in the relevant `main.log`: ``` 2024-09-19 19:15:49,942 DEBUG Disabling systemd-resolved stub resolver during upgrade 2024-09-19 19:15:50,112 DEBUG apt btrfs snapshots supported: False 2024-09-19 19:15:50,112 INFO cache.commit() 2024-09-20 15:46:53,054 ERROR got an error from dpkg for pkg: '/tmp/apt-dpkg-install-hysakR/32-firefox_1%3a1snap1-0ubuntu5_amd64.deb': 'new firefox package pre-installation script subprocess returned error exit status 1' 2024-09-20 15:46:53,055 DEBUG running apport_pkgfailure() firefox: new firefox package pre-installation script subprocess returned error exit status 1 2024-09-20 15:46:58,303 ERROR Exception during pm.DoInstall() Traceback (most recent call last): File "/tmp/ubuntu-release-upgrader-mkvb_fzo/DistUpgrade/DistUpgradeView.py", line 220, in run res = pm.do_install(self.writefd) apt_pkg.Error: E:Sub-process /usr/bin/dpkg returned an error code (1) 2024-09-20 15:46:58,333 ERROR SystemError from cache.commit(): installArchives() failed 2024-09-20 15:46:58,333 ERROR found exception: 'E:Sub-process /usr/bin/dpkg returned an error code (1)' 2024-09-20 15:47:00,255 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' 2024-09-20 15:47:00,286 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/convert_list_to_deb822.py' 2024-09-20 15:47:00,502 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' ``` So it seems like there was an unrelated error with the Firefox snap installer. Perhaps the underlying problem is that `systemd-resolved` is not properly reconfigured after upgrade errors? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055012 Title: When I upgraded from 22.04 to 24.04, DNS resolution went wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2055012/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055012] Re: When I upgraded from 22.04 to 24.04, DNS resolution went wrong.
*** This bug is a duplicate of bug 2054761 *** https://bugs.launchpad.net/bugs/2054761 Not sure if it is related or not. I have a name server VM that was running dnsmasq on 22.04.4. Upgraded it today with "do-release-upgrade -d" (impatient) to 24.04.1. Upgrade went fine except that dnsmasq could not start because something had triggered starting systemd.resolved ... and of course I had no name resolution on my network. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055012 Title: When I upgraded from 22.04 to 24.04, DNS resolution went wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2055012/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055012] Re: When I upgraded from 22.04 to 24.04, DNS resolution went wrong.
*** This bug is a duplicate of bug 2054761 *** https://bugs.launchpad.net/bugs/2054761 I tried to upgrade from Ubuntu 22.04.04 LTS to 24.04.1 (GUI). Unexpectedly the upgrade was cancelled on the last 20 packages to be downloaded (download failed). Turned out, DNS resolution failed completely and was not recoverable. After a reboot into 22.04, DNS resolution worked as expected again. A few unsuccessful upgrade attempts later (same problem), I gave up and reverted everything to the previous state. Staying with Ubuntu 22.04 LTS for the moment. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055012 Title: When I upgraded from 22.04 to 24.04, DNS resolution went wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2055012/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055012] Re: When I upgraded from 22.04 to 24.04, DNS resolution went wrong.
*** This bug is a duplicate of bug 2054761 *** https://bugs.launchpad.net/bugs/2054761 I ran into this problem recently while upgrading from Ubuntu 22.04.04 LTS to 24.04, although mine is little more severe. I'm missing /etc/resolv.conf (which typically links to /run/systemd/resolve/stub- resolv.conf) and the systemd-resolved package was not installed or failed to install. Therefore, I have to manually download the package, along with dependencies, and install them on the server. What a mess! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055012 Title: When I upgraded from 22.04 to 24.04, DNS resolution went wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2055012/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055012] Re: When I upgraded from 22.04 to 24.04, DNS resolution went wrong.
*** This bug is a duplicate of bug 2054761 *** https://bugs.launchpad.net/bugs/2054761 I still ran into this issue today during an upgrade from 22.04 to 24.04. So I actually think this is not a duplicate of bug #2054761, as that one is marked as 'fix released'. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055012 Title: When I upgraded from 22.04 to 24.04, DNS resolution went wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2055012/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055012] Re: When I upgraded from 22.04 to 24.04, DNS resolution went wrong.
*** This bug is a duplicate of bug 2054761 *** https://bugs.launchpad.net/bugs/2054761 can not find local pc's since Ubuntu 22.0.4 to 24.04 sudo nano /etc/nsswitch.conf sudo nano /etc/mdns.allow aio@aio:~$ service systemd-resolved restart Failed to restart systemd-resolved.service: Unit var-tmp.mount is masked. aio@aio:~$ ls -l /etc/systemd/system/systemd-resolved.service ls: cannot access '/etc/systemd/system/systemd-resolved.service': No such file or directory aio@aio:~$ sudo systemctl unmask systemd-resolved aio@aio:~$ service systemd-resolved restart Failed to restart systemd-resolved.service: Unit var-tmp.mount is masked. aio@aio:~$ sudo dpkg-reconfigure resolvconf dpkg-query: package 'resolvconf' is not installed and no information is available Use dpkg --info (= dpkg-deb --info) to examine archive files. /usr/sbin/dpkg-reconfigure: resolvconf is not installed aio@aio:~$ sudo apt install systemd-resolved Reading package lists... Done Building dependency tree... Done Reading state information... Done systemd-resolved is already the newest version (255.4-1ubuntu8.1). systemd-resolved set to manually installed. 0 upgraded, 0 newly installed, 0 to remove and 33 not upgraded. aio@aio:~$ sudo dpkg-reconfigure resolvconf dpkg-query: package 'resolvconf' is not installed and no information is available Use dpkg --info (= dpkg-deb --info) to examine archive files. /usr/sbin/dpkg-reconfigure: resolvconf is not installed aio@aio:~$ service systemd-resolved restart Failed to restart systemd-resolved.service: Unit var-tmp.mount is masked. aio@aio:~$ sudo apt install systemd-resolved Reading package lists... Done Building dependency tree... Done Reading state information... Done systemd-resolved is already the newest version (255.4-1ubuntu8.1). 0 upgraded, 0 newly installed, 0 to remove and 33 not upgraded. aio@aio:~$ sudo apt install --reinstall systemd-resolved Reading package lists... Done Building dependency tree... Done Reading state information... Done 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 33 not upgraded. Need to get 0 B/296 kB of archives. After this operation, 0 B of additional disk space will be used. (Reading database ... 838554 files and directories currently installed.) Preparing to unpack .../systemd-resolved_255.4-1ubuntu8.1_amd64.deb ... Unpacking systemd-resolved (255.4-1ubuntu8.1) over (255.4-1ubuntu8.1) ... Setting up systemd-resolved (255.4-1ubuntu8.1) ... Failed to restart systemd-resolved.service: Unit var-tmp.mount is masked. Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 148. Processing triggers for dbus (1.14.10-4ubuntu4) ... Processing triggers for man-db (2.12.0-4build2) ... Config is in use. Scanning processes... Scanning candidates... Scanning processor microcode... Scanning linux images... Running kernel seems to be up-to-date. The processor microcode seems to be up-to-date. Restarting services... systemctl restart systemd-resolved.service Failed to restart systemd-resolved.service: Unit var-tmp.mount is masked. No containers need to be restarted. User sessions running outdated binaries: aio @ user manager service: chrome[174774,174791,174792,174794,891445,891462,891463,891465], gnome-session-b[169989], gnome-shell[170020], surfshark[170400,170719,170720,170767], systemd[169581] No VM guests are running outdated hypervisor (qemu) binaries on this host. aio@aio:~$ service systemd-resolved restart Failed to restart systemd-resolved.service: Unit var-tmp.mount is masked. aio@aio:~$ service systemd-resolved start Failed to start systemd-resolved.service: Unit var-tmp.mount is masked. aio@aio:~$ ls -l /etc/systemd/system/systemd-resolved.service ls: cannot access '/etc/systemd/system/systemd-resolved.service': No such file or directory aio@aio:~$ sudo ls -l /etc/systemd/system/systemd-resolved.service ls: cannot access '/etc/systemd/system/systemd-resolved.service': No such file or directory aio@aio:~$ sudo systemctl daemon-reload aio@aio:~$ sudo systemctl start systemd-resolved Failed to start systemd-resolved.service: Unit var-tmp.mount is masked. aio@aio:~$ sudo systemctl enable systemd-resolved aio@aio:~$ sudo systemctl start systemd-resolved Failed to start systemd-resolved.service: Unit var-tmp.mount is masked. aio@aio:~$ sudo dpkg-reconfigure resolvconf dpkg-query: package 'resolvconf' is not installed and no information is available Use dpkg --info (= dpkg-deb --info) to examine archive files. /usr/sbin/dpkg-reconfigure: resolvconf i
[Bug 2055012] Re: When I upgraded from 22.04 to 24.04, DNS resolution went wrong.
*** This bug is a duplicate of bug 2054761 *** https://bugs.launchpad.net/bugs/2054761 I also upgraded server from Jammy to Noble, name resolution was busted, it looks systemd-resolved didn't complete the stub file where resolv.conf was symlinked to, but symlink was there -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055012 Title: When I upgraded from 22.04 to 24.04, DNS resolution went wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2055012/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055012] Re: When I upgraded from 22.04 to 24.04, DNS resolution went wrong.
*** This bug is a duplicate of bug 2054761 *** https://bugs.launchpad.net/bugs/2054761 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 ! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055012 Title: When I upgraded from 22.04 to 24.04, DNS resolution went wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2055012/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055012] Re: When I upgraded from 22.04 to 24.04, DNS resolution went wrong.
*** This bug is a duplicate of bug 2054761 *** https://bugs.launchpad.net/bugs/2054761 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. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055012 Title: When I upgraded from 22.04 to 24.04, DNS resolution went wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2055012/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055012] Re: When I upgraded from 22.04 to 24.04, DNS resolution went wrong.
*** This bug is a duplicate of bug 2054761 *** https://bugs.launchpad.net/bugs/2054761 I confirm fixing of the issue with sudo apt install systemd-resolved after broken update from 22.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055012 Title: When I upgraded from 22.04 to 24.04, DNS resolution went wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2055012/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055012] Re: When I upgraded from 22.04 to 24.04, DNS resolution went wrong.
*** This bug is a duplicate of bug 2054761 *** https://bugs.launchpad.net/bugs/2054761 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. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055012 Title: When I upgraded from 22.04 to 24.04, DNS resolution went wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2055012/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055012] Re: When I upgraded from 22.04 to 24.04, DNS resolution went wrong.
*** This bug is a duplicate of bug 2054761 *** https://bugs.launchpad.net/bugs/2054761 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055012 Title: When I upgraded from 22.04 to 24.04, DNS resolution went wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2055012/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055012] Re: When I upgraded from 22.04 to 24.04, DNS resolution went wrong.
*** This bug is a duplicate of bug 2054761 *** https://bugs.launchpad.net/bugs/2054761 I have the same issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055012 Title: When I upgraded from 22.04 to 24.04, DNS resolution went wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2055012/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055012] Re: When I upgraded from 22.04 to 24.04, DNS resolution went wrong.
*** This bug is a duplicate of bug 2054761 *** https://bugs.launchpad.net/bugs/2054761 Adding my journal from the crash. ** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2055012/+attachment/5769751/+files/journal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055012 Title: When I upgraded from 22.04 to 24.04, DNS resolution went wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2055012/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055012] Re: When I upgraded from 22.04 to 24.04, DNS resolution went wrong.
*** This bug is a duplicate of bug 2054761 *** https://bugs.launchpad.net/bugs/2054761 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. ** This bug has been marked a duplicate of bug 2054761 gnome-shell crashed with signal 5: Settings schema 'org.gnome.mutter.wayland' does not contain a key named 'xwayland-allow-byte-swapped-clients' -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055012 Title: When I upgraded from 22.04 to 24.04, DNS resolution went wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2055012/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055012] Re: When I upgraded from 22.04 to 24.04, DNS resolution went wrong.
** Changed in: ubuntu-release-upgrader (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055012 Title: When I upgraded from 22.04 to 24.04, DNS resolution went wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2055012/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055012] Re: When I upgraded from 22.04 to 24.04, DNS resolution went wrong.
I attempted an upgrade from a clean Jammy install to Noble so that I could gather upgrade logs. I have attached them here. ** Attachment added: "dist-upgrade.tar.gz" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2055012/+attachment/5769726/+files/dist-upgrade.tar.gz ** Also affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055012 Title: When I upgraded from 22.04 to 24.04, DNS resolution went wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2055012/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055012] Re: When I upgraded from 22.04 to 24.04, DNS resolution went wrong.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055012 Title: When I upgraded from 22.04 to 24.04, DNS resolution went wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2055012/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055012] Re: When I upgraded from 22.04 to 24.04, DNS resolution went wrong.
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 amd64simple interprocess messaging system (systemd --user integration) ii gnome-logs42.0-1 amd64viewer for the systemd journal ii libnss-systemd:amd64 249.11-0ubuntu3.12 amd64nss module providing dynamic user and group name resolution ii libpam-systemd:amd64 249.11-0ubuntu3.12 amd64system and service manager - PAM module ii libsystemd-shared:amd64 255.4-1ubuntu8 amd64systemd shared private library ii libsystemd0:amd64 255.4-1ubuntu8 amd64systemd 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 amd64Python 3 bindings for systemd ii systemd 255.4-1ubuntu8 amd64system 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 amd64Userspace out-of-memory (OOM) killer ii systemd-sysv 249.11-0ubuntu3.12 amd64system and service manager - SysV links ii systemd-timesyncd 255.4-1ubuntu8 amd64minimalistic 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 ** Changed in: network-manager (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055012 Title: When I upgraded from 22.04 to 24.04, DNS resolution went wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2055012/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055012] Re: When I upgraded from 22.04 to 24.04, DNS resolution went wrong.
** Also affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055012 Title: When I upgraded from 22.04 to 24.04, DNS resolution went wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2055012/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055012] Re: When I upgraded from 22.04 to 24.04, DNS resolution went wrong.
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. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055012 Title: When I upgraded from 22.04 to 24.04, DNS resolution went wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2055012/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055012] Re: When I upgraded from 22.04 to 24.04, DNS resolution went wrong.
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 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055012 Title: When I upgraded from 22.04 to 24.04, DNS resolution went wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2055012/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055012] Re: When I upgraded from 22.04 to 24.04, DNS resolution went wrong.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055012 Title: When I upgraded from 22.04 to 24.04, DNS resolution went wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2055012/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055012] Re: When I upgraded from 22.04 to 24.04, DNS resolution went wrong.
this affected me as well -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055012 Title: When I upgraded from 22.04 to 24.04, DNS resolution went wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2055012/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055012] Re: When I upgraded from 22.04 to 24.04, DNS resolution went wrong.
** Description changed: 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 our to find the solution on Ask Ubuntu. + 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= 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 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055012 Title: When I upgraded from 22.04 to 24.04, DNS resolution went wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2055012/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055012] Re: When I upgraded from 22.04 to 24.04, DNS resolution went wrong.
I have also faced the issue ... Same manner. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055012 Title: When I upgraded from 22.04 to 24.04, DNS resolution went wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2055012/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055012] Re: When I upgraded from 22.04 to 24.04, DNS resolution went wrong.
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. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055012 Title: When I upgraded from 22.04 to 24.04, DNS resolution went wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2055012/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055012] Re: When I upgraded from 22.04 to 24.04, DNS resolution went wrong.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055012 Title: When I upgraded from 22.04 to 24.04, DNS resolution went wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2055012/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055012] Re: When I upgraded from 22.04 to 24.04, DNS resolution went wrong.
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. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055012 Title: When I upgraded from 22.04 to 24.04, DNS resolution went wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2055012/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055012] Re: When I upgraded from 22.04 to 24.04, DNS resolution went wrong.
** Description changed: 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, I do not remember] - and the system cannot recover. Call the system administrator” message - after a red FAILED in the terminal. The system administrator is myself, + 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 our 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 + 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= + LANG=en_US.UTF-8 + PATH=(custom, no user) + SHELL=/bin/bash + TERM=xterm-256color + XDG_RUNTIME_DIR= RfKill: - 0: phy0: Wireless LAN - Soft blocked: no - Hard blocked: no + 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 + RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN + running 1.45.90 connected started full enabled enabled enabled missing enabled ** Tags added: network-manager -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055012 Title: When I upgraded from 22.04 to 24.04, DNS resolution went wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2055012/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs