Bug 2419962

Summary: [abrt] gnome-shell: meta_logical_monitor_get_layout(): gnome-shell killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Nicky Gerritsen <redhat>
Component: gnome-shellAssignee: GNOME SIG Unassigned <gnome-sig>
Status: NEW --- QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 43CC: adscvr, development.group, fmuellner, gnome-sig, jadahl, otaylor, redhat
Target Milestone: ---Keywords: AutomationTriaged
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/f9826ee776f3fccaa34667764eb436c428f9a52
Whiteboard: abrt_hash:302bdcaf53a63a7fc15615cf11ca36b03cc7c719;VARIANT_ID=workstation;
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: proc_pid_status
none
File: maps
none
File: limits
none
File: environ
none
File: open_fds
none
File: mountinfo
none
File: os_info
none
File: cpuinfo
none
File: core_backtrace
none
File: exploitable
none
File: dso_list
none
File: var_log_messages
none
File: backtrace none

Description Nicky Gerritsen 2025-12-08 07:57:08 UTC
Description of problem:
My hardware:
* Framework laptop 13 (AMD Ryzen AI 9 HX 370)
* A Dell WD19TB Thunderbolt Dock
* An LG UltraFine 5K monitor connected to that dock

I have set the following display configuration:
* When not docked, 200% scaling on my internal display
* When docked, my internal display is disabled and the LG UltraFine is set to a 4K resolution with 200% scaling

As soon as I plug in the WD19TB dock, my gnome-shell crashes. Plugging out de dock doesn't have this effect.

Version-Release number of selected component:
gnome-shell-49.2-2.fc43

Additional info:
reporter:       libreport-2.17.15
type:           CCpp
reason:         gnome-shell killed by SIGSEGV
journald_cursor: s=8175191a0bec4c9b8adab3e8b4668f3e;i=7e368;b=a9a3549c108f4ca68a8c210afb68e42f;m=5f10746c;t=6456bd61bac62;x=1f011c5783a54000
executable:     /usr/bin/gnome-shell
cmdline:        /usr/bin/gnome-shell
cgroup:         0::/user.slice/user-1000.slice/user/session.slice/org.gnome.Shell
rootdir:        /
uid:            1000
kernel:         6.17.9-300.fc43.x86_64
package:        gnome-shell-49.2-2.fc43
runlevel:       /bin/sh: line 1: runlevel: command not found
backtrace_rating: 4
crash_function: meta_logical_monitor_get_layout

Truncated backtrace:
Thread no. 0 (49 frames)
 #0 meta_logical_monitor_get_layout at ../src/backends/meta-logical-monitor.c:242
 #1 send_output_events at ../src/wayland/meta-wayland-outputs.c:231
 #2 wayland_output_update_for_output at ../src/wayland/meta-wayland-outputs.c:433
 #3 meta_wayland_compositor_update_outputs at ../src/wayland/meta-wayland-outputs.c:564
 #4 _g_closure_invoke_va at ../gobject/gclosure.c:980
 #5 signal_emit_valist_unlocked at ../gobject/gsignal.c:3439
 #8 meta_monitor_manager_notify_monitors_changed at ../src/backends/meta-monitor-manager.c:1479
 #9 meta_monitor_manager_rebuild at ../src/backends/meta-monitor-manager.c:4322
 #10 meta_monitor_manager_native_apply_monitors_config at ../src/backends/native/meta-monitor-manager-native.c:304
 #11 meta_monitor_manager_apply_monitors_config at ../src/backends/meta-monitor-manager.c:726
 #12 meta_monitor_manager_ensure_configured at ../src/backends/meta-monitor-manager.c:887
 #13 handle_hotplug_event at ../src/backends/native/meta-monitor-manager-native.c:339
 #14 on_kms_resources_changed at ../src/backends/native/meta-monitor-manager-native.c:375
 #17 signal_emit_valist_unlocked at ../gobject/gsignal.c:3535
 #20 on_udev_hotplug at ../src/backends/native/meta-kms.c:323
 #21 g_cclosure_marshal_VOID__OBJECTv at ../gobject/gmarshal.c:1910
 #22 _g_closure_invoke_va at ../gobject/gclosure.c:980
 #23 signal_emit_valist_unlocked at ../gobject/gsignal.c:3439
 #26 on_drm_uevent at ../src/backends/meta-udev.c:357
 #27 on_uevent at ../src/backends/meta-udev.c:382
 #28 ffi_call_unix64 at ../src/x86/unix64.S:104
 #29 ffi_call_int at ../src/x86/ffi64.c:676
 #30 ffi_call at ../src/x86/ffi64.c:713
 #31 g_cclosure_marshal_generic at ../gobject/gclosure.c:1624
 #34 signal_emit_valist_unlocked at ../gobject/gsignal.c:3535
 #37 monitor_event at ../gudev/gudevclient.c:90
 #39 g_main_context_dispatch_unlocked at ../glib/gmain.c:4425
 #40 g_main_context_iterate_unlocked at ../glib/gmain.c:4490
 #42 meta_context_run_main_loop at ../src/core/meta-context.c:576
 #43 ffi_call_unix64 at ../src/x86/unix64.S:104
 #44 ffi_call_int at ../src/x86/ffi64.c:676
 #45 ffi_call at ../src/x86/ffi64.c:713
 #46 Gjs::Function::invoke at ../gi/function.cpp:1031
 #47 Gjs::Function::call at ../gi/function.cpp:1207
 #48 CallJSNative at /usr/src/debug/mozjs140-140.2.0-1.fc43.x86_64/js/src/vm/Interpreter.cpp:494
 #49 js::InternalCallOrConstruct at /usr/src/debug/mozjs140-140.2.0-1.fc43.x86_64/js/src/vm/Interpreter.cpp:576
 #50 InternalCall at /usr/src/debug/mozjs140-140.2.0-1.fc43.x86_64/js/src/vm/Interpreter.cpp:657
 #51 js::CallFromStack at /usr/src/debug/mozjs140-140.2.0-1.fc43.x86_64/js/src/vm/Interpreter.cpp:662
 #52 js::Interpret at /usr/src/debug/mozjs140-140.2.0-1.fc43.x86_64/js/src/vm/Interpreter.cpp:3286
 #53 MaybeEnterInterpreterTrampoline at /usr/src/debug/mozjs140-140.2.0-1.fc43.x86_64/js/src/vm/Interpreter.cpp:395
 #54 js::RunScript at /usr/src/debug/mozjs140-140.2.0-1.fc43.x86_64/js/src/vm/Interpreter.cpp:464
 #55 js::InternalCallOrConstruct at /usr/src/debug/mozjs140-140.2.0-1.fc43.x86_64/js/src/vm/Interpreter.cpp:622
 #56 InternalCall at /usr/src/debug/mozjs140-140.2.0-1.fc43.x86_64/js/src/vm/Interpreter.cpp:657
 #57 js::Call at /usr/src/debug/mozjs140-140.2.0-1.fc43.x86_64/js/src/vm/Interpreter.cpp:689
 #58 JS::Call at /usr/src/debug/mozjs140-140.2.0-1.fc43.x86_64/js/src/vm/CallAndConstruct.cpp:119
 #60 GjsContextPrivate::run_main_loop_hook at ../gjs/context.cpp:1463
 #61 GjsContextPrivate::eval_module at ../gjs/context.cpp:1616
 #62 gjs_context_eval_module at ../gjs/context.cpp:1355
 #63 gjs_context_eval_module_file at ../gjs/context.cpp:1702

Comment 1 Nicky Gerritsen 2025-12-08 07:57:11 UTC
Created attachment 2117914 [details]
File: proc_pid_status

Comment 2 Nicky Gerritsen 2025-12-08 07:57:13 UTC
Created attachment 2117915 [details]
File: maps

Comment 3 Nicky Gerritsen 2025-12-08 07:57:14 UTC
Created attachment 2117916 [details]
File: limits

Comment 4 Nicky Gerritsen 2025-12-08 07:57:16 UTC
Created attachment 2117917 [details]
File: environ

Comment 5 Fedora Admin user for bugzilla script actions 2025-12-08 07:57:17 UTC
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!

Comment 6 Nicky Gerritsen 2025-12-08 07:57:17 UTC
Created attachment 2117918 [details]
File: open_fds

Comment 7 Nicky Gerritsen 2025-12-08 07:57:20 UTC
Created attachment 2117919 [details]
File: mountinfo

Comment 8 Nicky Gerritsen 2025-12-08 07:57:21 UTC
Created attachment 2117920 [details]
File: os_info

Comment 9 Nicky Gerritsen 2025-12-08 07:57:22 UTC
Created attachment 2117921 [details]
File: cpuinfo

Comment 10 Nicky Gerritsen 2025-12-08 07:57:24 UTC
Created attachment 2117922 [details]
File: core_backtrace

Comment 11 Nicky Gerritsen 2025-12-08 07:57:25 UTC
Created attachment 2117923 [details]
File: exploitable

Comment 12 Nicky Gerritsen 2025-12-08 07:57:26 UTC
Created attachment 2117924 [details]
File: dso_list

Comment 13 Nicky Gerritsen 2025-12-08 07:57:28 UTC
Created attachment 2117925 [details]
File: var_log_messages

Comment 14 Nicky Gerritsen 2025-12-08 07:57:29 UTC
Created attachment 2117926 [details]
File: backtrace

Comment 15 redhat 2026-01-20 08:27:07 UTC
I'm running Fedora 43 on a Thinkpad T14s connected via USB-C/Thunderbolt to an Apple Studio Display. From time to time, the Gnome-shell just dies out of nowhere, I have to login again, but like half the programs continue running in the background (but another session). I literally just use the computer and suddenly, the bug appears. It could also be connected with some energy saving stuff? IIRC the most of the time happens after I leave the computer for some time so that the screensaver kicks in? I don't know.


reporter:       libreport-2.17.15
type:           CCpp
reason:         gnome-shell killed by SIGSEGV
journald_cursor: s=31568992684447a095d7f524f1082ace;i=2c2f7;b=b3f8a7f9c58a45358e9153fb6a2bb6b4;m=3e850c20;t=6476cde17b49f;x=be9c6ed038deb49f
executable:     /usr/bin/gnome-shell
cmdline:        /usr/bin/gnome-shell
cgroup:         0::/user.slice/user-1000.slice/user/session.slice/org.gnome.Shell
rootdir:        /
uid:            1000
kernel:         6.17.12-300.fc43.x86_64
package:        gnome-shell-49.2-2.fc43
runlevel:       /bin/sh: line 1: runlevel: command not found
backtrace_rating: 4
crash_function: meta_logical_monitor_get_layout
comment:        I'm running Fedora 43 on a Thinkpad T14s connected via USB-C/Thunderbolt to an Apple Studio Display. From time to time, the Gnome-shell just dies out of nowhere, I have to login again, but like half the programs continue running in the background (but another session). I literally just use the computer and suddenly, the bug appears. It could also be connected with some energy saving stuff? IIRC the most of the time happens after I leave the computer for some time so that the screensaver kicks in? I don't know.

Comment 16 m.saman 2026-02-06 16:04:58 UTC
When connecting an external monitor via Thunderbolt 3, GNOME Shell crashes.

External monitor:
Display 1
   I2C bus:  /dev/i2c-16
   DRM_connector:           card1-DP-4
   EDID synopsis:
      Mfg id:               GSM - Goldstar Company Ltd (LG)
      Model:                LG UltraFine 27MD5KA
      Product code:         23313  (0x5b11)
      Serial number:        901NTLE6W680
      Binary serial number: 234680 (0x000394b8)
      Manufacture year:     2019,  Week: 1
   VCP version:         Detection failed


Computer:
Vendor: LENOVO
Model: 21QJ0048CK
Version: ThinkPad T14 Gen 6


reporter:       libreport-2.17.15
type:           CCpp
reason:         gnome-shell killed by SIGSEGV
journald_cursor: s=63307c958eae4f66b5deb6d06c569e58;i=1e746a;b=eb9b80d9cc924934ad7786760fe070b5;m=8e59fe9c0;t=645fab2d9f507;x=31f5f4be121a7c42
executable:     /usr/bin/gnome-shell
cmdline:        /usr/bin/gnome-shell
cgroup:         0::/user.slice/user-1000.slice/user/session.slice/org.gnome.Shell
rootdir:        /
uid:            1000
kernel:         6.17.11-300.fc43.x86_64
package:        gnome-shell-49.2-2.fc43
runlevel:       /bin/sh: line 1: runlevel: command not found
backtrace_rating: 4
crash_function: meta_logical_monitor_get_layout

Comment 17 Nicolas Vaagen 2026-04-07 17:19:10 UTC
Gnome stopped responding to input and I switched to a tty. Gnome crashed.


reporter:       libreport-2.17.15
type:           CCpp
reason:         gnome-shell killed by SIGSEGV
journald_cursor: s=f0bf850b2df64dcd8b486f759ed3e9b0;i=274adbc;b=24efd84589cd4916add60ab03e5d4fe6;m=7b6ebd3;t=64ee1e3a51e6c;x=f6d2360acf2c34c5
executable:     /usr/bin/gnome-shell
cmdline:        /usr/bin/gnome-shell
cgroup:         0::/user.slice/user-1000.slice/user/session.slice/org.gnome.Shell
rootdir:        /
uid:            1000
kernel:         6.19.8-200.fc43.x86_64
package:        gnome-shell-49.5-1.fc43
runlevel:       /bin/sh: line 1: runlevel: command not found
backtrace_rating: 4
crash_function: meta_logical_monitor_get_layout
comment:        Gnome stopped responding to input and I switched to a tty. Gnome crashed.

Comment 18 laolux 2026-04-13 01:17:45 UTC
I unplugged my USB-C dock that has two monitors connected. One via DisplayPort, the other via HDMI.
This happens reliably. When I unplug my USB-C dock, then gnome crashes, my applications crash and I need to log in again.
Note: This did not happen a few month ago when I started using this laptop.


reporter:       libreport-2.17.15
type:           CCpp
reason:         gnome-shell killed by SIGSEGV
journald_cursor: s=9eeb36b5de6e44aca270e55f4c425425;i=266c00;b=8a0e05cec60d4816a91a0348f5cac561;m=c9cea41da;t=64eeed2a45c62;x=5fccd10be6ef7bb7
executable:     /usr/bin/gnome-shell
cmdline:        /usr/bin/gnome-shell
cgroup:         0::/user.slice/user-1000.slice/user/session.slice/org.gnome.Shell
rootdir:        /
uid:            1000
kernel:         6.19.10-200.fc43.x86_64
package:        gnome-shell-49.5-1.fc43
runlevel:       /bin/sh: line 1: runlevel: command not found
backtrace_rating: 4
crash_function: meta_logical_monitor_get_layout