Description of problem: It happended during a screen resolution modification Version-Release number of selected component: gnome-control-center-43.2-1.fc37 Additional info: reporter: libreport-2.17.4 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-gnome-org.gnome.Settings-50371.scope cmdline: gnome-control-center crash_function: cc_display_config_dbus_generate_cloning_modes executable: /usr/bin/gnome-control-center journald_cursor: s=4d355c2323f04b45bbcd164f57dfd065;i=1fabbd;b=ab23db4f74354a5bb174700af21db718;m=4ecaa6d22;t=5f5d6d5a74e77;x=5147220833cd9d44 kernel: 6.1.13-200.fc37.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (9 frames) #0 cc_display_config_dbus_generate_cloning_modes at ../panels/display/cc-display-config-dbus.c:1437 #1 config_ensure_of_type at ../panels/display/cc-display-panel.c:262 #2 g_signal_group__target_weak_notify at ../gobject/gsignalgroup.c:163 #3 g_closure_new_simple at ../gobject/gclosure.c:226 #4 gtk_at_context_update at ../gtk/gtkatcontext.c:697 #6 gtk_accessible_update_state at ../gtk/gtkaccessible.c:179 #7 gtk_toggle_button_set_active at ../gtk/gtktogglebutton.c:429 #8 g_signal_group__target_weak_notify at ../gobject/gsignalgroup.c:163 #9 g_object_new_with_custom_constructor at ../gobject/gobject.c:2195
Created attachment 1947224 [details] File: backtrace
Created attachment 1947225 [details] File: core_backtrace
Created attachment 1947226 [details] File: cpuinfo
Created attachment 1947227 [details] File: dso_list
Created attachment 1947228 [details] File: environ
Created attachment 1947229 [details] File: exploitable
Created attachment 1947230 [details] File: limits
Created attachment 1947231 [details] File: maps
Created attachment 1947232 [details] File: mountinfo
Created attachment 1947233 [details] File: open_fds
Created attachment 1947234 [details] File: proc_pid_status
Similar problem has been detected: on Screen section of gnome-control-center, just change "multiple display" from "linked" to "cloned" reporter: libreport-2.17.4 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/app.slice/dbus-:1.2-org.gnome.Settings.SearchProvider cmdline: gnome-control-center -s zoom crash_function: cc_display_config_dbus_generate_cloning_modes executable: /usr/bin/gnome-control-center journald_cursor: s=b97bf0924ae0418eb9a6576b6e716b7d;i=28de24;b=4451c3d703e5449da56ab98b873817e1;m=e976eb0d6;t=5f6880a7f10b2;x=2897b616bebd2218 kernel: 6.1.14-200.fc37.x86_64 package: gnome-control-center-43.2-1.fc37 reason: gnome-control-center killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
I have a similar stack trace ending with 'cc_display_config_dbus_generate_cloning_modes' and gnome-control-center-44.3-1.fc38.x86_64, while trying to configure mirror mode with a newly plugged-in HDMI overhead system. The default is split (side-by-side),and I'd like the external HDMI system to mirror my LCD display instead.
This message is a reminder that Fedora Linux 37 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 37 on 2023-12-05. 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 '37'. 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 37 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 37 entered end-of-life (EOL) status on 2023-12-05. Fedora Linux 37 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.