*** 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
*** 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
*** 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
Desktop Bugs, which is
*** 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
*** 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
Desktop Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2055012
Title:
When
*** 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
*** 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
** Changed in: ubuntu-release-upgrader (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2055012
Title:
When I upgraded from 22.04 to
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
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
Desktop Bugs, which is subscribed to the bug report.
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
Desktop Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2055012
Title:
When I upgraded from 22.04 to 24.04, DNS
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
Desktop Bugs, which
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to the bug report.
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:
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
Desktop Bugs,
this affected me as well
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2055012
Title:
When I upgraded from 22.04 to 24.04, DNS resolution went wrong.
To manage notifications about
** 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
I have also faced the issue ... Same manner.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2055012
Title:
When I upgraded from 22.04 to 24.04, DNS resolution went wrong.
To manage
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
Desktop Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2055012
Title:
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
Desktop Bugs, which is subscribed to the bug report.
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`
22 matches
Mail list logo