*** This bug is a duplicate of bug 2054761 ***
https://bugs.launchpad.net/bugs/2054761
Somebody should re-open this thread.
The bug is confirmed in here, but nobody said it is fixed, so why is it
closed?
I have exactly this described bug.
--
You received this bug notification because you a
*** This bug is a duplicate of bug 2054761 ***
https://bugs.launchpad.net/bugs/2054761
This bug is also closed so please open a new one.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055012
Titl
*** This bug is a duplicate of bug 2054761 ***
https://bugs.launchpad.net/bugs/2054761
I have also a computer that is still affected by this in 2025. Why it is
so difficult to fix this problem?
During the Update 22.04 > 24.04 i loose the connection to the internet,
so the update can not finis
*** This bug is a duplicate of bug 2054761 ***
https://bugs.launchpad.net/bugs/2054761
~joeldjohnston -- My system was acting like described in this ticket,
but it is an AppArmor issue. I had to disable AppArmor entirely in GRUB,
disabling it via systemd wasn't enough. After upgrade from 20.04
*** This bug is a duplicate of bug 2054761 ***
https://bugs.launchpad.net/bugs/2054761
I can affirm that systemd-resolved is not getting its config from
netplan, nor does adding the nameserver in /etc/systemd/resolved.conf
have any affect. The only temporary fix is modification of
/etc/resolv.
*** This bug is a duplicate of bug 2054761 ***
https://bugs.launchpad.net/bugs/2054761
Same problem here, except a new install of 24.04.1 but using the previous /home
from 22.04. I can only get DNS working by manually adding a DNS entry (e.g.
9.9.9.9) in /etc/systemd/resolved.conf. I've trie
*** 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 a
*** 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 th
*** 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/`
*** 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
*** 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 a
*** 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-
res
*** 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 notif
*** 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
*** 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 thi
*** 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-
*** 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
*** 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 Ubu
*** 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 we
*** 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
*** 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 2
*** 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 receiv
*** 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 duplic
** 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
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 a
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:
Wh
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 |
** 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 wr
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 subsc
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 su
--
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/
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:
h
** 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 administrato
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 abo
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 fro
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
Tit
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` repo
** 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 admini
38 matches
Mail list logo
