gnome-shell crash (signal 11)
This bug report will be marked for expiration in 21 days if no further activity occurs. (find out why)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-shell (Ubuntu) |
Incomplete
|
Undecided
|
Unassigned |
Bug Description
See
https:/
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:
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:/
500 https:/
500 http://
100 /var/lib/
46.0-0ubuntu5 500
500 https:/
xournalpp:
Installed: 1.2.3-1~
Candidate: 1.2.3-1~
Version table:
*** 1.2.3-1~
100 /var/lib/
1.2.2-2build3 500
500 https:/
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.