Bug 2082991

Summary: [abrt] gnome-shell: meta_monitor_get_outputs(): gnome-shell killed by SIGSEGV
Product: [Fedora] Fedora Reporter: misterlindon <misterlindon>
Component: gnome-shellAssignee: Florian Müllner <fmuellner>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 36CC: adscvr, fmuellner, gnome-sig, jadahl, otaylor, philip.wyett, shichen
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/aaa94ae8d569fbecadf799494d5d3939ad81c522
Whiteboard: abrt_hash:b42271df61b6fb015097832b88e74534909dc2b8;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-05-25 16:20:37 UTC 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: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: cpuinfo
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: mountinfo
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description misterlindon@gmail.com 2022-05-09 01:39:36 UTC 
Description of problem:
I changed the framerate/resolution combo to 4K 144 on my Framework laptop (paired with an LG 27GN850) and my system crashed. I tried doing it again and the same thing happened.

Version-Release number of selected component:
gnome-shell-42.0-3.fc36

Additional info:
reporter:       libreport-2.17.1
backtrace_rating: 4
cmdline:        /usr/bin/gnome-shell
crash_function: meta_monitor_get_outputs
dso_list:       /usr/bin/gnome-shell gnome-shell-42.0-3.fc36.x86_64 (Fedora Project) 1651787406
executable:     /usr/bin/gnome-shell
journald_cursor: s=2d3b1af47e0644a29d785f480b34558e;i=b36;b=b8e71f102b7a41e5bca2b528bafeaf67;m=a35a7fd;t=5de894b1bd806;x=c76937b9f66569cf
kernel:         5.17.5-300.fc36.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 meta_monitor_get_outputs at ../src/backends/meta-monitor.c:315
 #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:325
 #3 meta_monitor_manager_apply_monitors_config at ../src/backends/meta-monitor-manager.c:635
 #4 restore_previous_config at ../src/backends/meta-monitor-manager.c:1790
 #5 ffi_call_unix64 at ../src/x86/unix64.S:105
 #6 ffi_call_int at ../src/x86/ffi64.c:672
 #7 Gjs::Function::invoke(JSContext*, JS::CallArgs const&, JS::Handle<JSObject*>, _GIArgument*) at ../gi/function.cpp:968
 #8 Gjs::Function::call(JSContext*, unsigned int, JS::Value*) at ../gi/function.cpp:1148
 #9 CallJSNative(JSContext*, bool (*)(JSContext*, unsigned int, JS::Value*), js::CallReason, JS::CallArgs const&) at /usr/src/debug/mozjs91-91.8.0-1.fc36.x86_64/vm/Interpreter.cpp:426
Comment 1 misterlindon@gmail.com 2022-05-09 01:39:38 UTC 
Created attachment 1877957 [details]
File: backtrace
Comment 2 misterlindon@gmail.com 2022-05-09 01:39:39 UTC 
Created attachment 1877958 [details]
File: cgroup
Comment 3 misterlindon@gmail.com 2022-05-09 01:39:40 UTC 
Created attachment 1877959 [details]
File: core_backtrace
Comment 4 misterlindon@gmail.com 2022-05-09 01:39:41 UTC 
Created attachment 1877960 [details]
File: cpuinfo
Comment 5 misterlindon@gmail.com 2022-05-09 01:39:42 UTC 
Created attachment 1877961 [details]
File: environ
Comment 6 misterlindon@gmail.com 2022-05-09 01:39:43 UTC 
Created attachment 1877962 [details]
File: exploitable
Comment 7 misterlindon@gmail.com 2022-05-09 01:39:45 UTC 
Created attachment 1877963 [details]
File: limits
Comment 8 misterlindon@gmail.com 2022-05-09 01:39:46 UTC 
Created attachment 1877964 [details]
File: maps
Comment 9 misterlindon@gmail.com 2022-05-09 01:39:47 UTC 
Created attachment 1877965 [details]
File: mountinfo
Comment 10 misterlindon@gmail.com 2022-05-09 01:39:48 UTC 
Created attachment 1877966 [details]
File: open_fds
Comment 11 misterlindon@gmail.com 2022-05-09 01:39:49 UTC 
Created attachment 1877967 [details]
File: proc_pid_status
Comment 12 misterlindon@gmail.com 2022-05-09 01:39:50 UTC 
Created attachment 1877968 [details]
File: var_log_messages
Comment 13 Dmitry 2022-11-07 18:04:31 UTC 
Similar problem has been detected:

I disabled one monitor in the settings and while timer for "keep changes" pop up kept ticking I unplugged the other monitor and plugged it back

reporter:       libreport-2.17.4
backtrace_rating: 4
cgroup:         0::/user.slice/user-1000.slice/user/session.slice/org.gnome.Shell
cmdline:        /usr/bin/gnome-shell
crash_function: meta_monitor_get_outputs
dso_list:       /usr/bin/gnome-shell gnome-shell-42.5-1.fc36.x86_64 (Fedora Project) 1663576684
executable:     /usr/bin/gnome-shell
journald_cursor: s=613380e1231c418593fd608feca73e19;i=32f814;b=f9b15972c4cd42ab88fe77683c4fe704;m=5badb5afd;t=5ece44b76a1e0;x=af189b37efbd7d
kernel:         6.0.5-200.fc36.x86_64
package:        gnome-shell-42.5-1.fc36
reason:         gnome-shell killed by SIGSEGV
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 14 Ben Cotton 2023-04-25 17:07:16 UTC 
This message is a reminder that Fedora Linux 36 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16.
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 '36'.

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 36 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.
Comment 15 Ludek Smid 2023-05-25 16:20:37 UTC 
Fedora Linux 36 entered end-of-life (EOL) status on 2023-05-16.

Fedora Linux 36 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.