Description of problem: Connecting dual monitor created this issue Version-Release number of selected component: gnome-shell-45.0-1.fc39 Additional info: reporter: libreport-2.17.11 type: CCpp reason: gnome-shell killed by SIGSEGV journald_cursor: s=e8173ca5b1b242d2a59f9a2407b65317;i=931d;b=3da746bfa1d648808f502a41a5a43571;m=1a7ef9595;t=6090c15e99b18;x=a95aa46768f8b69e 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.5.2-301.fc39.x86_64 package: gnome-shell-45.0-1.fc39 runlevel: N 5 dso_list: /usr/bin/gnome-shell gnome-shell-45.0-1.fc39.x86_64 (Fedora Project) 1698785255 backtrace_rating: 4 crash_function: meta_monitor_get_outputs comment: Connecting dual monitor created this issue Truncated backtrace: Thread no. 1 (29 frames) #0 meta_monitor_get_outputs at ../src/backends/meta-monitor.c:318 #1 meta_monitor_config_manager_assign at ../src/backends/meta-monitor-config-manager.c:411 #2 meta_monitor_manager_native_apply_monitors_config at ../src/backends/native/meta-monitor-manager-native.c:303 #3 meta_monitor_manager_apply_monitors_config at ../src/backends/meta-monitor-manager.c:740 #4 restore_previous_config at ../src/backends/meta-monitor-manager.c:1958 #5 save_config_timeout at ../src/backends/meta-monitor-manager.c:1989 #8 g_main_context_dispatch_unlocked at ../glib/gmain.c:4284 #9 g_main_context_iterate_unlocked.isra.0 at ../glib/gmain.c:4349 #11 meta_context_run_main_loop at ../src/core/meta-context.c:514 #12 ffi_call_unix64 at ../src/x86/unix64.S:104 #13 ffi_call_int at ../src/x86/ffi64.c:673 #14 ffi_call at ../src/x86/ffi64.c:710 #15 Gjs::Function::invoke at ../gi/function.cpp:1058 #16 Gjs::Function::call at ../gi/function.cpp:1236 #17 CallJSNative at /usr/src/debug/mozjs115-115.3.1-1.fc39.x86_64/vm/Interpreter.cpp:486 #18 js::InternalCallOrConstruct at /usr/src/debug/mozjs115-115.3.1-1.fc39.x86_64/vm/Interpreter.cpp:566 #19 InternalCall at /usr/src/debug/mozjs115-115.3.1-1.fc39.x86_64/vm/Interpreter.cpp:647 #20 js::CallFromStack at /usr/src/debug/mozjs115-115.3.1-1.fc39.x86_64/vm/Interpreter.cpp:652 #21 js::Interpret at /usr/src/debug/mozjs115-115.3.1-1.fc39.x86_64/vm/Interpreter.cpp:3395 #22 MaybeEnterInterpreterTrampoline at /usr/src/debug/mozjs115-115.3.1-1.fc39.x86_64/vm/Interpreter.cpp:400 #23 js::RunScript at /usr/src/debug/mozjs115-115.3.1-1.fc39.x86_64/vm/Interpreter.cpp:458 #24 js::InternalCallOrConstruct at /usr/src/debug/mozjs115-115.3.1-1.fc39.x86_64/vm/Interpreter.cpp:612 #25 InternalCall at /usr/src/debug/mozjs115-115.3.1-1.fc39.x86_64/vm/Interpreter.cpp:647 #26 js::Call at /usr/src/debug/mozjs115-115.3.1-1.fc39.x86_64/vm/Interpreter.cpp:679 #27 JS::Call at /usr/src/debug/mozjs115-115.3.1-1.fc39.x86_64/vm/CallAndConstruct.cpp:117 #29 GjsContextPrivate::run_main_loop_hook at ../gjs/context.cpp:1428 #30 GjsContextPrivate::eval_module at ../gjs/context.cpp:1545 #31 gjs_context_eval_module at ../gjs/context.cpp:1324 #32 gjs_context_eval_module_file at ../gjs/context.cpp:1629 Potential duplicate: bug 2082991
Created attachment 1996483 [details] File: proc_pid_status
Created attachment 1996484 [details] File: maps
Created attachment 1996485 [details] File: limits
Created attachment 1996486 [details] File: environ
Created attachment 1996487 [details] File: open_fds
Created attachment 1996488 [details] File: mountinfo
Created attachment 1996489 [details] File: os_info
Created attachment 1996490 [details] File: cpuinfo
Created attachment 1996491 [details] File: core_backtrace
Created attachment 1996492 [details] File: exploitable
Created attachment 1996493 [details] File: var_log_messages
Created attachment 1996494 [details] File: backtrace
Seems to be some constraints happening, perhaps memory: > Oct 31 17:06:39 framework gnome-shell[42666]: Failed to create offscreen effect framebuffer: Failed to create texture 2d due to size/format constraints but ideally it should be handled more gracefully. The crash seems to imply that a previous mode is to be applied, but one monitor was disconnected in the mean time.
This component is maintained by the GNOME project. Issues with it should be reported directly to GNOME at https://gitlab.gnome.org/GNOME/. 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!
Some breadcrumbs upstream point me to https://gitlab.gnome.org/GNOME/mutter/-/issues/1820 , which does look at superficially similar...
This message is a reminder that Fedora Linux 39 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 39 on 2024-11-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '39'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 39 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 39 entered end-of-life (EOL) status on 2024-11-26. Fedora Linux 39 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.