GNOME Shell 50.1 crashes in meta_window_x11_update_shape_region() after closing PPSSPP (XWayland / AMD / Fedora 44)

Desktop
,
1

GNOME Shell crashes on Fedora 44 during normal desktop use on a Wayland session with XWayland active.

The crash happened shortly after closing PPSSPP.

Crash

Process gnome-shell crashed in meta_window_x11_update_shape_region()
SIGSEGV in libmutter-18.so.0

Stack trace includes:

meta_window_x11_update_shape_region()
meta_wayland_transaction_commit
wl_surface_commit

Some logs before crash:

XWayland reset:

Connection to xwayland lostUsing public X11 display :0

GPU issues:

Failed to open gpu '/dev/dri/card1': EBUSYFailed to setup: No GPUs found

Then GPU reappears:

Added device '/dev/dri/card1' (amdgpu)Created gbm renderer for '/dev/dri/card1'
  • Fedora 44
  • GNOME Shell 50.1
  • Mutter 50.1
  • Kernel 7.0.10-201.fc44.x86_64
  • AMD GPU

is this a known issue?

2

mine randomly crashed when i try to open nautilus and showed gdm. happens like one in a million time even without extensions.

"Aug 09 17:30:01 HP-250-G9-Notebook-PC gnome-shell[7189]: Connection to xwayland lost
Aug 09 17:30:01 HP-250-G9-Notebook-PC gnome-shell[7189]: Using public X11 display :0, (using unix:/tmp/.X11-unix/X1 for managed services)
Aug 09 17:30:02 HP-250-G9-Notebook-PC kernel: gnome-shell[7189]: segfault at 5b8 ip 00007a2cd133e007 sp 00007ffead0e32a0 error 4 in libmutter-18.so.0.0.0[13e007,7a2cd1264000+18e000] likely on CPU 7 (core 11, socket 0)
Aug 09 17:30:02 HP-250-G9-Notebook-PC systemd-coredump[19673]: Process 7189 (gnome-shell) of user 1000 terminated abnormally with signal 11/SEGV, processing...
Aug 09 17:30:03 HP-250-G9-Notebook-PC systemd-coredump[19677]: Process 7189 (gnome-shell) of user 1000 dumped core.
Module /usr/bin/gnome-shell from deb gnome-shell-50.1-0ubuntu1.2.amd64
Module libmutter-18.so.0 from deb mutter-50.1-0ubuntu2.2.amd64
#0 0x00007a2cd133e007 n/a (libmutter-18.so.0 + 0x13e007)
#1 0x00007a2cd139b418 n/a (libmutter-18.so.0 + 0x19b418)
#2 0x00007a2cd137a52a n/a (libmutter-18.so.0 + 0x17a52a)
Aug 09 17:30:06 HP-250-G9-Notebook-PC gnome-shell[20284]: Running GNOME Shell (using mutter 50.1) as a Wayland display server
Aug 09 17:30:06 HP-250-G9-Notebook-PC systemd[20008]: Started org.gnome.Shell@gdm.service - GNOME Shell.
Aug 09 17:30:06 HP-250-G9-Notebook-PC gnome-shell[20284]: Using public X11 display :1024, (using unix:/tmp/.X11-unix/X1025 for managed services)
Aug 09 17:30:06 HP-250-G9-Notebook-PC gnome-shell[20284]: Using Wayland display name 'wayland-0'
Aug 09 17:30:11 HP-250-G9-Notebook-PC gnome-shell[22273]: Running GNOME Shell (using mutter 50.1) as a Wayland display server
Aug 09 17:30:11 HP-250-G9-Notebook-PC gnome-shell[22273]: Added device '/dev/dri/card1' (i915) using atomic mode setting.
Aug 09 17:30:12 HP-250-G9-Notebook-PC gnome-shell[22273]: Using public X11 display :0, (using unix:/tmp/.X11-unix/X1 for managed services)
Aug 09 17:30:12 HP-250-G9-Notebook-PC gnome-shell[22273]: Using Wayland display name 'wayland-0'"

3

Hello and welcome to the forum.

Can you report the issue on the issue tracker? GNOME / gnome-shell · GitLab . This is support forum first and foremost, GitLab is the proper place for reporting bugs/crashes.

4

I suggest using niri with Fedora if u get more crashes like this check out https://danklinux.com/ similar to gnome

5

I would recommend to actually report the crashes first. You can’t expect them to be fixed if you won’t even report them.