gnome-shell crashes with SIGSEGV in meta_wayland_compositor_get_context()

Bug #2015691 reported by Bruce Elrick
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gnome-shell (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Output of gdb backtrace full:

#0 __pthread_kill_implementation (no_tid=0, signo=11, threadid=<optimized out>) at ./nptl/pthread_kill.c:44
        tid = <optimized out>
        ret = 0
        pd = <optimized out>
        old_mask = {__val = {0}}
        ret = <optimized out>
#1 __pthread_kill_internal (signo=11, threadid=<optimized out>) at ./nptl/pthread_kill.c:78
#2 __GI___pthread_kill (threadid=<optimized out>, signo=signo@entry=11) at ./nptl/pthread_kill.c:89
#3 0x00007fd23e83c406 in __GI_raise (sig=sig@entry=11) at ../sysdeps/posix/raise.c:26
        ret = <optimized out>
#4 0x0000564413f87aea in dump_gjs_stack_on_signal_handler (signo=11) at ../src/main.c:495
        sa = {__sigaction_handler = {sa_handler = 0x564413f87730 <dump_gjs_stack_alarm_sigaction>, sa_sigaction = 0x564413f87730 <dump_gjs_stack_alarm_sigaction>}, sa_mask = {__val = {0 <repeats 16 times>}}, sa_flags = 0, sa_restorer = 0x0}
        i = <optimized out>
#5 0x00007fd23e83c4b0 in <signal handler called> () at /lib/x86_64-linux-gnu/libc.so.6
#6 0x00007fd23ed2ce04 in meta_wayland_compositor_get_context () at /lib/x86_64-linux-gnu/libmutter-12.so.0
#7 0x00007fd23ed3046f in () at /lib/x86_64-linux-gnu/libmutter-12.so.0
#8 0x00007fd23bf0dfaf in () at /lib/x86_64-linux-gnu/libwayland-server.so.0
#9 0x00007fd23bf0fe0e in wl_resource_destroy () at /lib/x86_64-linux-gnu/libwayland-server.so.0
#10 0x00007fd23e3758b6 in () at /lib/x86_64-linux-gnu/libffi.so.8
#11 0x00007fd23e37234d in () at /lib/x86_64-linux-gnu/libffi.so.8
#12 0x00007fd23e374f33 in ffi_call () at /lib/x86_64-linux-gnu/libffi.so.8
#13 0x00007fd23bf0b2a0 in () at /lib/x86_64-linux-gnu/libwayland-server.so.0
#14 0x00007fd23bf0f694 in () at /lib/x86_64-linux-gnu/libwayland-server.so.0
#15 0x00007fd23bf0e0fa in wl_event_loop_dispatch () at /lib/x86_64-linux-gnu/libwayland-server.so.0
#16 0x00007fd23ed2a73b in () at /lib/x86_64-linux-gnu/libmutter-12.so.0
#17 0x00007fd23f2b349d in g_main_dispatch (context=0x56441550e3b0) at ../../../glib/gmain.c:3460
        dispatch = 0x7fd23ed2a720
        prev_source = 0x0
        begin_time_nsec = 0
        was_in_call = 0
        user_data = 0x0
        callback = 0x0
        cb_funcs = <optimized out>
        cb_data = <optimized out>
        need_destroy = <optimized out>
        source = 0x5644155c50e0
        current = 0x5644154ec5b0
        i = 0
#18 g_main_context_dispatch (context=0x56441550e3b0) at ../../../glib/gmain.c:4200
#19 0x00007fd23f30e178 in g_main_context_iterate.constprop.0 (context=0x56441550e3b0, block=<optimized out>, dispatch=1, self=<optimized out>) at ../../../glib/gmain.c:4276
        max_priority = 2147483647
        timeout = 134
        some_ready = 1
        nfds = <optimized out>
        allocated_nfds = 28
        fds = 0x5644226315d0
#20 0x00007fd23f2b2bdf in g_main_loop_run (loop=0x5644186fe790) at ../../../glib/gmain.c:4479
        __func__ = "g_main_loop_run"
#21 0x00007fd23ecbddf9 in meta_context_run_main_loop () at /lib/x86_64-linux-gnu/libmutter-12.so.0
#22 0x0000564413f86fa1 in main (argc=<optimized out>, argv=<optimized out>) at ../src/main.c:765
        context = 0x56441550c780
        debug_flags_string = 0x5644157fa640 "backtrace-aborts:backtrace-math-errors:backtrace-crashes-all:backtrace-all"
        error = 0x0
        shell_debug = <optimized out>
        ecode = 0

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: gnome-shell 44.0-2ubuntu3
ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6
Uname: Linux 6.2.0-19-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia
ApportVersion: 2.26.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sun Apr 9 10:49:04 2023
DisplayManager: gdm3
InstallationDate: Installed on 2023-01-15 (83 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221209)
RelatedPackageVersions: mutter-common 44.0-2ubuntu3
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Bruce Elrick (virtuous-sloth) wrote :
Revision history for this message
Bruce Elrick (virtuous-sloth) wrote :

Attaching gdb backtrace full output since paste looks line-wrapped.

Revision history for this message
Bruce Elrick (virtuous-sloth) wrote :
Download full text (3.9 KiB)

This has been happening every few days to week for the last couple months. I've installed lunar from scratch on January 15. I upgraded from kernel 5.19.0-19 to 6.1.0-14 late January. I have been regularly updating.

I have text copies of journald logs going back to March 1, so I think this covers the dates:
root@neil:~
# grep -i gnome-shell j.Wed\ 22\ Mar\ 2023\ 10\:39\:15\ AM\ MDT | grep -i crashed
Mar 17 17:22:59 neil gnome-shell[9530]: GNOME Shell crashed with signal 11
Mar 20 13:53:41 neil gnome-shell[16559]: GNOME Shell crashed with signal 11
Mar 20 13:55:27 neil gnome-shell[242217]: GNOME Shell crashed with signal 11
Mar 21 13:40:42 neil gnome-shell[9042]: GNOME Shell crashed with signal 11
Mar 22 10:11:09 neil gnome-shell[6556]: GNOME Shell crashed with signal 11
root@neil:~
# grep -i gnome-shell j.Sun\ 09\ Apr\ 2023\ 10\:29\:27\ AM\ MDT | grep -i crashed
Mar 28 11:21:54 neil gnome-shell[14173]: GNOME Shell crashed with signal 11
Mar 29 12:38:02 neil gnome-shell[6334]: GNOME Shell crashed with signal 11
Mar 29 16:01:21 neil gnome-shell[6575]: GNOME Shell crashed with signal 11
Apr 03 15:54:18 neil gnome-shell[246110]: GNOME Shell crashed with signal 11
Apr 06 09:33:04 neil gnome-shell[6814]: GNOME Shell crashed with signal 11
Apr 09 10:25:49 neil gnome-shell[13108]: GNOME Shell crashed with signal 11

Here is the latest apt upgrade prior to the first crash:
Start-Date: 2023-03-17 15:52:16
Commandline: apt upgrade
Requested-By: bme (1000)
Upgrade: libcanberra-gtk3-0:amd64 (0.30-10ubuntu2, 0.30-10ubuntu4), yaru-theme-icon:amd64 (22.10.3-1, 23.04.1-0ubuntu1), libext2fs2:amd64 (1.46.6~rc1-1ubuntu1, 1.47.0-1ubuntu1), aspnetcore-runtime-6.0:amd64 (6.0.114-0ubuntu1, 6.0.115-0ubuntu1), sosreport:amd64 (4.4-1ubuntu2, 4.5-1ubuntu0), gnome-control-center-faces:amd64 (1:44~rc-1ubuntu1, 1:44~rc-1ubuntu2), libcanberra-gtk3-module:amd64 (0.30-10ubuntu2, 0.30-10ubuntu4), ibus-gtk3:amd64 (1.5.28-1, 1.5.28-2), ibus-gtk4:amd64 (1.5.28-1, 1.5.28-2), liblzma5:amd64 (5.4.1-0.0, 5.4.1-0.2), liblzma5:i386 (5.4.1-0.0, 5.4.1-0.2), dotnet-hostfxr-6.0:amd64 (6.0.114-0ubuntu1, 6.0.115-0ubuntu1), python3-ibus-1.0:amd64 (1.5.28-1, 1.5.28-2), libostree-1-1:amd64 (2022.7-2, 2022.7-2ubuntu1), dotnet-sdk-6.0:amd64 (6.0.114-0ubuntu1, 6.0.115-0ubuntu1), dotnet-targeting-pack-6.0:amd64 (6.0.114-0ubuntu1, 6.0.115-0ubuntu1), poppler-data:amd64 (0.4.11-1, 0.4.12-1), xz-utils:amd64 (5.4.1-0.0, 5.4.1-0.2), libcom-err2:amd64 (1.46.6~rc1-1ubuntu1, 1.47.0-1ubuntu1), libcom-err2:i386 (1.46.6~rc1-1ubuntu1, 1.47.0-1ubuntu1), liblzma-dev:amd64 (5.4.1-0.0, 5.4.1-0.2), gir1.2-ibus-1.0:amd64 (1.5.28-1, 1.5.28-2), ibus-data:amd64 (1.5.28-1, 1.5.28-2), yaru-theme-sound:amd64 (22.10.3-1, 23.04.1-0ubuntu1), yaru-theme-gtk:amd64 (22.10.3-1, 23.04.1-0ubuntu1), dotnet-templates-6.0:amd64 (6.0.114-0ubuntu1, 6.0.115-0ubuntu1), librest-1.0-0:amd64 (0.9.1-4, 0.9.1-5), python3-doc:amd64 (3.11.1-3, 3.11.2-1), dotnet-host:amd64 (6.0.114-0ubuntu1, 6.0.115-0ubuntu1), gnome-control-center-data:amd64 (1:44~rc-1ubuntu1, 1:44~rc-1ubuntu2), ibus-gtk:amd64 (1.5.28-1, 1.5.28-2), netstandard-targeting-pack-2.1:amd64 (6.0.114-0ubuntu1, 6.0.115-0ubuntu1), gnome-control-center:amd64 (1:44~rc-1ubuntu1, 1:44~rc-1ub...

Read more...

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

Sounds like bug 2012230 or bug 2015974...

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.

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.

summary: - gnome-shell crashes while interacting with firefox
+ gnome-shell crashes with SIGSEGV in
+ meta_wayland_compositor_get_context()
Changed in gnome-shell (Ubuntu):
status: New → Incomplete
milestone: ubuntu-23.04 → none
Revision history for this message
Bruce Elrick (virtuous-sloth) wrote :

This link is not from this instance of the problem but does appear to be from a previous similar occurance: https://errors.ubuntu.com/oops/02171978-cd8e-11ed-adb8-fa163e55efd0

Revision history for this message
Bruce Elrick (virtuous-sloth) wrote :

I guess I should also note explicitly that there was no /var/crash file for this problem.

Revision history for this message
Bruce Elrick (virtuous-sloth) wrote :

BTW, if there is a config change I can do that will help capture more information the next time this happens such that it will help diagnose this or bug #2012100 then I'd be happy to do so.

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

The link in comment #5 doesn't seem to lead to any known crash. So next time you experience a crash please follow comment #4 again.

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

This does look most likely to be bug 2012100 so it probably doesn't hurt if this one expires.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.]

Changed in gnome-shell (Ubuntu):
status: Incomplete → Expired
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.