Thanks. Answers to the three steps: 1) Attached journal-2026-10-30-redacted.txt: the boot containing both gnome-shell crashes on 2026-10-30 (11:46:36 and 12:10:52, "GNOME Shell crashed with signal 11"). journal-2026-10-30-crash-window-redacted.txt is the 11:40-12:15 excerpt.
2/3) I have the automatic reporting enabled, so ubuntu-bug sends the crash to errors.ubuntu.com rather than creating a Launchpad bug. But whoopsie never manages to upload it: errors.ubuntu.com/user/<id> shows nothing after 2026-09-25. Each attempt for the ~50 MB gnome-shell .crash runs 7-20 min and fails with "Stream error in the HTTP/2 framing layer" / "Failure when receiving data from the peer"; earlier attempts got HTTP 400/502/504. Same for _usr_bin_gjs-console.1000.crash. The symbolized backtrace from that core dump is in the previously attached gnome-shell-jsgc-crash.txt: SIGSEGV in JS_GC (libmozjs-140 140.8.0-4) called from gjs in the main loop. The gjs desktop-icons process (ding.js) segfaults at the same libmozjs-140 offset (ip ...b7370, fault addr 0x400000000010) repeatedly, latest 2026-11-03 08:43. Happy to run gdb commands on the core dump if you need more detail. ** Attachment added: "journal-2026-10-30-crash-window-redacted.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2172586/+attachment/6014619/+files/journal-2026-10-30-crash-window-redacted.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2172586 Title: gnome-shell 50.1 crashes with SIGSEGV in JS_GC (libmozjs-140 140.8.0-4), logging the user out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2172586/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
