Ubuntu 22 crash when updating, broken network manager and cannot report bug

[Alexandru Buhnici]

A new day, a new struggle with Ubuntu 22.04.

So, I decided to get my daily updates and in the middle of the process the system just crashed, leaving me at the login page. When I got back, the wifi was no longer there and the network configuration was reporting an error about the network manager having problems.
I shut down and restarted, the wifi came back.

Went to the var/crash folder to report the bug with

    $:/var/crash$ ubuntu-bug _usr_bin_gnome-shell.1000.crash

and it started complaining about older packages that need to be upgraded. I run `apt upgrade`, one of the packages is `dbus`, I tried `apt install dbus` and another even uglier crash that left me with a black screen from which I could only come back with a forced shutdown and restart.

Now, how do I get out of this mess and report the bug?

[Alexandru Buhnici (alexmro)]

Ubuntu 22 crash when updating, broken network manager and cannot report bug.

The errors must be at the beginning because as soon as I logged in the first thing I did was updating

[Alexandru Buhnici (alexmro)]

I tried to update again, it asked me to restart, restarted and now looks like there are no newer updates. I still cannot send the report with ubuntu-bug.
When I hit send I get a popup with an error stating that there's a problem with gnome-shell and could be caused by the fact that I have older versions of some packages (accountsservice, bind9-host, bind9-libs, dbus, gir1.2-accountservice-1.0, gir1.2-nm-1.0, libaccountservice0, libsasl2-modules-db, libwhoopsie-preferences0, libwhoopsie0, libxml2, networkmanager, whoopsie-preferences)

But when I try to upgrade them with apt upgrade it says they are all fine

[Paul White (paulw2u)]

I also experienced a crash while performing a routine update and was thrown out of the desktop. I saw an error relating to canonical-livepatch which is installed but not enabled.

I switched to vt4 and rebooted with the command "sudo reboot now". In my case everything appears to be working normally including the ability to report bugs.

My /var/crash/ directory shows that files relating to gnome-shell, seahorse and cups-browsed were automatically uploaded at the time I experienced the crash. The times match entries found in /var/log/apt/history.log so the crash *was* related to the update process.

I'm not sure if this helps anyone trace the source of the problem but I thought I should respond as this is the first instance I have seen of such a crash since I began using Ubuntu in 2010.

Alexandru, I'm confirming the bug on the basis that *we* saw a similar crash while updating but not for the problems that you experienced afterwards.

[Alexandru Buhnici (alexmro)]

Updates work now but I continue to get the gnome-shell error when trying to report crashes with ubuntu-bug

[Timo Aaltonen (tjaalton)]

if gnome-shell crashes, you lose the session if it's using the wayland-based one

[Alexandru Buhnici (alexmro)]

Yes, it's wayland what it's using

[Paul White (paulw2u)]

Seems related to https://bugs.launchpad.net/bugs/1962036

[Daniel van Vugt (vanvugt)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
    ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself.

[Alex Murray (alexmurray)]

See https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1962127 for an ubuntu-bug of the gnome-shell crash file when this occurred for me yesterday.

[lotuspsychje (lotuspsychje)]

@Daniel #8 created a new bug as requested from the gnome crash see bug 1962149

[Daniel van Vugt (vanvugt)]

I can't access that yet so it's probably still private. If bug 1962149 hasn't seen any comment from me by tomorrow then please try making it public.

[Julian Andres Klode (juliank)]

I'm not sure it's worth going on wild goose chases tracking down the crashes, as the underlying cause is dbus stopping and there's no way to gracefully recover from that, as discussed in 1962036.

dbus is expected to be always running, so tons of crashes if it stops are to be expected.

[Daniel van Vugt (vanvugt)]

Sure bug 1962036 is about dbus. This bug is about whatever Alexandru Buhnici's issue really is and that seems unclear still. The bug description suggests it's a gnome-shell crash: _usr_bin_gnome-shell.1000.crash

[Alexandru Buhnici (alexmro)]

I no longer get crashes when updating (for the last 2 days it works) but I still cannot send bug reports when using `ubuntu-bug`. When I click Send I still see an error dialog with title `gnome-shell` and something about gnome older versions of some packages (accountsservice, bind9-host, bind9-libs, dbus, gir1.2-accountservice-1.0, gir1.2-nm-1.0, libaccountservice0, libsasl2-modules-db, libwhoopsie-preferences0, libwhoopsie0, libxml2, networkmanager, whoopsie-preferences)

It's the only problem I have now. So, I cannot do step 1 from comment #8 by Daniel. I can do step 2 and I get these 2 links for the dates around the occurring of this problem

- 2022-02-23 10:02 https://errors.ubuntu.com/oops/dfb7270b-9488-11ec-bdec-fa163e102db1 Crash(gnome-shell)
- 2022-02-22 13:02 https://errors.ubuntu.com/oops/00444da8-93d2-11ec-91a1-fa163e983629 Crash(xdg-desktop-portal-gtk)
- 2022-02-18 02:02 https://errors.ubuntu.com/oops/c01523ae-9318-11ec-8699-fa163ee63de6 Crash(xwayland)

[geole0 (geole0)]

Hello.

Hello
Not exactly the same. it processes a few files and the toshiba boot screen is offered.
I can only press the restart button on the lap

[Daniel van Vugt (vanvugt)]

> 2022-02-23 10:02 https://errors.ubuntu.com/oops/dfb7270b-9488-11ec-bdec-fa163e102db1 Crash(gnome-shell)

That's untraceable for now but it does match the most common gnome-shell crashes we see globally: https://errors.ubuntu.com/?release=Ubuntu%2022.04&package=gnome-shell&period=month

If you can provide a full system log from when it happened (Wed Feb 23 10:53:39 2022) then there might be some useful information there.

> 2022-02-18 02:02 https://errors.ubuntu.com/oops/c01523ae-9318-11ec-8699-fa163ee63de6 Crash(xwayland)

That's bug 1751508.

I'll close this bug since the original reporter says the crash is no longer happening.

[wolfgang (wolfgang-ztoeg)]

crash during full-upgrade: (that removed bunch of packages, see below...)
Start-Date: 2022-09-23 00:16:10
Commandline: apt full-upgrade

black screen, no network.

reboot.

configuring network: (from history)
1093 ip a add 192.168.178.100/24 dev enp37s0
1094 ip link set dev enp37s0 up
1095 ip route add default via 192.168.178.1

/etc/hosts: 129.143.116.10 ftp-stud.hs-esslingen.de (for my sources.list)

apt update
apt --fix-broken install
(problem remains: no gui no net)

apt install ubuntu-desktop .. gui is back.

found Removed packages from faulty full-upgrade. a bunch of. -> file atached: Removed

cat Removed | tr , \\n| awk -F: '{print $1}'|grep -v Remove|xargs apt install -y

did the job. online+working OK
End-Date: 2022-09-23 01:23:51

[Daniel van Vugt (vanvugt)]

This bug is closed. Please open new bugs for any crashes you experience.