Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: Moving the window from one monitor to another while maximised, crashes the GNOME desktop and returns to the login screen. Version-Release number of selected component (if applicable): # System Details Report --- ## Report details - **Date generated:** 2025-09-22 07:26:22 ## Hardware Information: - **Hardware Model:** Micro-Star International Co., Ltd. MS-7B47 - **Memory:** 32.0 GiB - **Processor:** Intel® Core™ i7-8700K × 12 - **Graphics:** Intel® UHD Graphics 630 - **Graphics 1:** NVIDIA GeForce GTX 1050 - **Disk Capacity:** 26.5 TB ## Software Information: - **Firmware Version:** 1.B0 - **OS Name:** Fedora Linux 43 (Workstation Edition Prerelease) - **OS Build:** (null) - **OS Type:** 64-bit - **GNOME Version:** 49 - **Windowing System:** Wayland - **Kernel Version:** Linux 6.17.0-0.rc6.49.fc43.x86_64 How reproducible: Happened 100% of the time. Steps to Reproduce: 1. Open say Chrome and drag a tab to another monitor maximised. Actual results: Crashed the desktop and returned to the login screen Expected results: Just move the window to another monitor. Additional info: System fully up-to-date All extensions are disabled Fresh login, no other apps open Dmesg: (the core changes on each crash) [64217.922998] gnome-shell[239246]: segfault at 18 ip 00007fd410ec6114 sp 00007ffd29683d38 error 4 in libmutter-17.so.0.0.0[c6114,7fd410e00000+19d000] likely on CPU 4 (core 4, socket 0) [64217.923009] Code: 00 c0 e8 07 0f b6 c0 c3 0f 1f 00 66 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 0f b6 87 54 02 00 00 83 e0 01 c3 90 f3 0f 1e fa <48> 8b 47 18 c3 0f 1f 80 00 00 00 00 f3 0f 1e fa 8b 47 60 c3 0f 1f Sep 22 06:36:10 xxx kernel: gnome-shell[251725]: segfault at 18 ip 00007fe7710c6114 sp 00007ffe825602d8 error 4 in libmutter-17.so.0.0.0[c6114,7fe771000000+19d000] likely on CPU 2 (core 2, socket 0) Module libmutter-cogl-17.so.0 from rpm mutter-49.0-1.fc43.x86_64 Module libmutter-mtk-17.so.0 from rpm mutter-49.0-1.fc43.x86_64 Module libmutter-17.so.0 from rpm mutter-49.0-1.fc43.x86_64 Module libmutter-clutter-17.so.0 from rpm mutter-49.0-1.fc43.x86_64 #0 0x00007fe7710c6114 meta_window_get_display (libmutter-17.so.0 + 0xc6114) #1 0x00007fe771091618 meta_window_drag_end (libmutter-17.so.0 + 0x91618) #2 0x00007fe77113db3b meta_wayland_toplevel_drag_end (libmutter-17.so.0 + 0x13db3b) #3 0x00007fe77111fce3 drag_grab_release (libmutter-17.so.0 + 0x11fce3) #4 0x00007fe771129428 meta_wayland_input_handle_event (libmutter-17.so.0 + 0x129428) #5 0x00007fe77142ede8 emit_event (libmutter-clutter-17.so.0 + 0x71de8) #6 0x00007fe7714316de clutter_sprite_propagate_event (libmutter-clutter-17.so.0 + 0x746de) #7 0x00007fe77141d519 clutter_stage_process_event (libmutter-clutter-17.so.0 + 0x60519) #8 0x00007fe7714321c4 _clutter_stage_process_queued_events (libmutter-clutter-17.so.0 + 0x751c4) #9 0x00007fe77140bbfb clutter_frame_clock_dispatch (libmutter-clutter-17.so.0 + 0x4ebfb) #10 0x00007fe77140c1c1 frame_clock_source_dispatch (libmutter-clutter-17.so.0 + 0x4f1c1) #14 0x00007fe7710a911a meta_context_run_main_loop (libmutter-17.so.0 + 0xa911a) #6 0x00007fe771194d80 thread_impl_func (libmutter-17.so.0 + 0x194d80) #6 0x00007fe77118db49 input_thread (libmutter-17.so.0 + 0x18db49) Sep 22 06:36:13 xxx gnome-shell[274604]: Running GNOME Shell (using mutter 49.0) as a Wayland display server Sep 22 06:36:21 xxx gnome-shell[275539]: Running GNOME Shell (using mutter 49.0) as a Wayland display server Sep 22 06:36:27 xxx mutter-x11-frames[276600]: Unknown key gtk-modules in /home/xxx/.config/gtk-4.0/settings.ini
Bug reports for this component on Red Hat Bugzilla are not actively monitored. Please consider reporting your issue directly to GNOME at https://gitlab.gnome.org/GNOME/ to improve the chances that your issue will be resolved. This issue should only be kept open if it: 1. Relates to Fedora packaging or integration with other Fedora components 2. Is required for Fedora release processes, such as blocker bugs and freeze exceptions If this issue isn't needed for either of these two reasons, please: * create an issue with GNOME * add a link to the GNOME issue here * close this issue as CLOSED/UPSTREAM Thank you!
*** This bug has been marked as a duplicate of bug 2399795 ***