Gnome 48 crashing after maximizing an app on second display

Desktop
,
1

Hey, I just updated to GNOME 48 and unfortunately it keeps crashing for me.
I tried disabling all the extensions and that’s not it.
My specs:

# System Details Report
---

## Report details
- **Date generated:**                              2025-03-24 18:34:44

## Hardware Information:
- **Hardware Model:**                              Lenovo Legion 5 Pro 16ARH7H
- **Memory:**                                      32.0 GiB
- **Processor:**                                   AMD Ryzen™ 7 6800H with Radeon™ Graphics × 16
- **Graphics:**                                    AMD Radeon™ 680M
- **Graphics 1:**                                  NVIDIA GeForce RTX™ 3070 Ti Laptop GPU
- **Disk Capacity:**                               2.0 TB

## Software Information:
- **Firmware Version:**                            JUCN65WW
- **OS Name:**                                     Arch Linux
- **OS Build:**                                    rolling
- **OS Type:**                                     64-bit
- **GNOME Version:**                               48
- **Windowing System:**                            Wayland
- **Kernel Version:**                              Linux 6.13.8-arch1-1
- Resolution: 2560x1600 2560x1440
Laptop screen (1600p) running 150% fractional scaling; monitor screen running 100%.

Steps to replicate the problem:

  1. Launch firefox.
  2. Move it to laptop screen.
  3. Maximize it.
  4. The system freezes for a second and then crashes to GDM login screen and displays the volume bar in the bottom.
    Results of journalctl:
    journalctl --user -e -n 1000 > file.txt:
    Mar 24 18:29:54 arch-legion gsd-keyboard[39180]: Cannot open display:Mar 24 18 - Pastebin.com
    I’ll gladly accept any help I can get.

EDIT:
Crashing seems to got less… consitent after changing the scaling from 150% → 100% and back to 150% - so even though nothing theoretically changed - it doesn’t crash every time now - altough I had some unexpected crashes now. I will be observing the issue.

2

Do you have the MUTTER_DEBUG_KMS_THREAD_TYPE environment variable set?

3

I’ve downgraded to GNOME 47, but:
echo $MUTTER_DEBUG_KMS_THREAD_TYPE
user
If that’s not something… Gnome version based - then I guess the answer is yes.

4

It is a bug that happens when using a current git snapshot of mutter while having MUTTER_DEBUG_KMS_THREAD_TYPE set to user. If you no longer set that environment variable this should no longer crash.

2 Likes
5

Thank you very much! The solution works.
For other users with the problem - you most probably have the line to set the env added somewhere, as it was a way of solving another issue.
One place you could have added the line is ~/.config/environment.d/99-mutter-no-rt.conf, another place is /etc/environment. Just delete the line that looks like:
MUTTER_DEBUG_KMS_THREAD_TYPE = user

1 Like