gnome-shell crash (signal 11)

Bug #2069048 reported by Heiko Scheit
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gnome-shell (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

See

   https://github.com/xournalpp/xournalpp/issues/5719

for a full description.

While the bug can be triggered or caused by xournalpp, gnome-shell should not crash, but hand it gracefully.

Short excerpt from 'journalctl':

Jun 11 10:51:10 my-hostname gnome-shell[7110]: GNOME Shell crashed with signal 11
Jun 11 10:51:10 my-hostname gnome-shell[7110]: == Stack trace for context 0x6369da089b80 ==
Jun 11 10:51:10 my-hostname gnome-shell[7110]: #0 6369da154b68 i resource:///org/gnome/shell/ui/init.js:21 (256ffc870bf0 @ 48)

More details at the above URL.

> lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 24.04 LTS
Release: 24.04
Codename: noble

Bug showed up immediately after upgrade to noble (from mantic).

> apt-cache policy gnome-shell xournalpp
gnome-shell:
  Installed: 46.0-0ubuntu5.1
  Candidate: 46.0-0ubuntu5.1
  Version table:
 *** 46.0-0ubuntu5.1 500
        500 https://linux.mathematik.tu-darmstadt.de/pub/linux/distributions/ubuntu/ubuntu noble-updates/main amd64 Packages
        500 https://linux.mathematik.tu-darmstadt.de/pub/linux/distributions/ubuntu/ubuntu noble-security/main amd64 Packages
        500 http://security.ubuntu.com/ubuntu noble-security/main amd64 Packages
        100 /var/lib/dpkg/status
     46.0-0ubuntu5 500
        500 https://linux.mathematik.tu-darmstadt.de/pub/linux/distributions/ubuntu/ubuntu noble/main amd64 Packages
xournalpp:
  Installed: 1.2.3-1~ubuntu23.10.1
  Candidate: 1.2.3-1~ubuntu23.10.1
  Version table:
 *** 1.2.3-1~ubuntu23.10.1 100
        100 /var/lib/dpkg/status
     1.2.2-2build3 500
        500 https://linux.mathematik.tu-darmstadt.de/pub/linux/distributions/ubuntu/ubuntu noble/universe amd64 Packages

Tags: noble
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

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. Run these commands:
    journalctl -b0 > journal.txt
    journalctl -b-1 > prevjournal.txt
and attach the resulting text files here.

2. 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.

3. If step 2 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.

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.

tags: added: noble
Changed in gnome-shell (Ubuntu):
status: New → Incomplete
Revision history for this message
Heiko Scheit (h-scheit) wrote :

Hi there,

thanks for your reply. In the meantime I found this bug report

    https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7587

and this

    https://gitlab.gnome.org/GNOME/mutter/-/issues/3372

which address the issue.

For now I downloaded the new mutter packages from

    http://archive.ubuntu.com/ubuntu/ubuntu/pool/main/m/mutter/

All deb-files with '46.1-2ubuntu1' on this page and installed them with 'dpkg -i...'.

This solves the problem and so far no other side effects.

It would be good, if these packages are updated in noble (24.04) soon.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Assuming this is https://gitlab.gnome.org/GNOME/mutter/-/issues/3372, then it's really in upstream release 46.2. So see bug 2068598.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Actually the fix for https://gitlab.gnome.org/GNOME/mutter/-/issues/3372 is not in 46.1-2ubuntu1, so that's not the right upstream link.

There are some other crashes fixed in 46.1 so please follow the steps in comment #1 to identify which crash it is.

no longer affects: mutter
Revision history for this message
Heiko Scheit (h-scheit) wrote :

Thanks for following up on this.

I have to get some work done with xournal and matter working. As soon as I find some time, I will follow the steps in comment #1, but it might be only on or after the weekend...

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.