Dear Maintainer,

Step to reproduce:
Gnome-shell: Alt-F2, type 'r' or open Firefox/Chrome browser and play
any video for example from youtube.

all gnome-shell extensions are disabled

From kernel log:
200~2023-08-28T17:46:20.921037+02:00 stacjonarka kernel: [ 3498.554467]
gnome-shell[24802]: segfault at 28 ip 00007fed6c6f5f14 sp
00007ffc869e41a0 error 4 in
libmutter-clutter-12.so.0.0.0[7fed6c689000+8d000] likely on CPU 2 (core
2, socket 0)

I found similar problem:

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

Dear Maintainer,


The same bug happens on my machine. I sent a bug report to the gnome-shell maintainers:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050502

Best regards, Markus

Dear Maintainer,

I found workaround, changing the refresh in nvidia-settings from 144Hz to 60Hz
solves the problem with libmutter segfault. Nvidia drivers: 535.104.05


Architecture: amd64 (x86_64)

Kernel: Linux 6.4.0-3-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=pl_PL.utf8, LC_CTYPE=pl_PL.utf8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libmutter-12-0 depends on:
ii  adwaita-icon-theme         43-1
ii  gsettings-desktop-schemas  44.0-2
ii  libatk1.0-0                2.49.90-5
ii  libc6                      2.37-7
ii  libcairo-gobject2          1.16.0-7
ii  libcairo2                  1.16.0-7
ii  libcanberra0               0.30-10
ii  libcolord2                 1.4.6-2.2
ii  libdrm2                    2.4.115-1
ii  libegl1                    1.6.0-1
ii  libfontconfig1             2.14.2-4
ii  libfribidi0                1.0.13-3
ii  libgbm1                    23.1.6-1
ii  libgdk-pixbuf-2.0-0        2.42.10+dfsg-1+b1
ii  libgl1                     1.6.0-1
ii  libglib2.0-0               2.77.2-1
ii  libgnome-desktop-4-2       44.0-2
ii  libgraphene-1.0-0          1.10.8-1
ii  libgudev-1.0-0             237-2
ii  libharfbuzz0b              8.0.1-1
ii  libice6                    2:1.0.10-1
ii  libinput10                 1.23.0-2
ii  libjson-glib-1.0-0         1.6.6-1
ii  liblcms2-2                 2.14-2
ii  libpango-1.0-0             1.51.0+ds-2
ii  libpangocairo-1.0-0        1.51.0+ds-2
ii  libpangoft2-1.0-0          1.51.0+ds-2
ii  libpipewire-0.3-0          0.3.78-1
ii  libsm6                     2:1.2.3-1
ii  libstartup-notification0   0.12-6+b1
ii  libsystemd0                254.1-2
ii  libudev1                   254.1-2
ii  libwacom9                  2.7.0-1
ii  libwayland-server0         1.22.0-2
ii  libx11-6                   2:1.8.6-1
ii  libx11-xcb1                2:1.8.6-1
ii  libxau6                    1:1.0.9-1
ii  libxcb-randr0              1.15-1
ii  libxcb-res0                1.15-1
ii  libxcb1                    1.15-1
ii  libxcomposite1             1:0.4.5-1
ii  libxcursor1                1:1.2.1-1
ii  libxdamage1                1:1.1.6-1
ii  libxext6                   2:1.3.4-1+b1
ii  libxfixes3                 1:6.0.0-2
ii  libxi6                     2:1.8-1+b1
ii  libxinerama1               2:1.1.4-3
ii  libxkbcommon-x11-0         1.5.0-1
ii  libxkbcommon0              1.5.0-1
ii  libxkbfile1                1:1.1.0-1
ii  libxrandr2                 2:1.5.2-2+b1
ii  libxtst6                   2:1.2.3-1.1
ii  mutter-common              44.3-7
ii  mutter-common-bin          44.3-7

libmutter-12-0 recommends no packages.

libmutter-12-0 suggests no packages.

Versions of packages libmutter-12-0 is related to:
ii  libegl-mesa0 [libegl-vendor]  23.1.6-1
ii  libgl1-mesa-dri               23.1.6-1
ii  libglx-mesa0 [libglx-vendor]  23.1.6-1

Control: retitle -1 gnome-shell segfault in libmutter-clutter-12.so with nvidia-graphics-drivers set to 144Hz refresh
Control: severity -1 important
Control: tags -1 + moreinfo
Control: affects -1 + src:gnome-shell src:nvidia-graphics-drivers

A workaround exists, so this doesn't make GNOME Shell completely unusable;
downgrading the bug severity to important.

Those two might actually be two separate root causes, or they might be
two different ways to trigger the same root cause; it's not yet clear from
the information available.

Alt+F2, 'r' sometimes triggers bugs in shutdown/cleanup code paths
that would normally only result in the Shell crashing when it is already
trying to exit (which is a bug, but relatively harmless). This seems likely
to be the same thing as #1050502, which was also reported by a user of the
Nvidia proprietary graphics driver.

Playing videos in a web browser probably means there is a crash involving
hardware video acceleration (VA-API or VDPAU). This could be the same thing
as #1050512, which was *also* reported by a user of the Nvidia proprietary
graphics driver.

That doesn't seem to be a valid issue URL, do you mean
<https://gitlab.gnome.org/GNOME/mutter/-/issues/2977> or something else?

https://gitlab.gnome.org/GNOME/mutter/-/issues/2977 seems similar to your
first reproducer involving Alt+F2, 'r'.
or find a solution. Please could you get a backtrace? Please see:
<https://wiki.debian.org/HowToGetABacktrace>.

For gnome-shell, usually the easiest way to get a backtrace is:

* Install the systemd-coredump package
* Reboot (I'm not sure whether this is strictly necessary but it can't hurt)
* Do whatever you need to do to trigger the crash
* In a shell: DEBUGINFOD_URLS="https://debuginfod.debian.net" coredumpctl gdb
* Enable automatic download of debug symbols if prompted
* At the (gdb) prompt: set pagination off
* Still at the (gdb) prompt: bt

In your case, you've reported two different ways to trigger this crash
(one with Alt+F2, 'r' similar to #1050502, and one with videos similar
to #1050512) so it would be useful if you could get a separate backtrace
for each one, and send them to the bug address indicating which is which.

Also, please look for any messages from gnome-shell in the system log
(systemd journal) at the time of the crash, by using the journalctl
tool or reading the file /var/log/syslog. For example you might see
something similar to this:

2023-09-10T16:09:04.136417+01:00 tautology gnome-shell[2831]: clutter_actor_contains: assertion 'CLUTTER_IS_ACTOR (self)' failed

or this:

May  7 18:02:51 darter gnome-shell[2213]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked.

Please copy anything from around the time of the crash.

Thanks,
    smcv