Description of problem: Gnome Control Center crashes after opening Display tab while booted with nomodeset. Version-Release number of selected component: gnome-control-center-3.32.1-1.fc30 Additional info: reporter: libreport-2.10.0 backtrace_rating: 4 cmdline: gnome-control-center crash_function: cc_display_mode_get_freq_f executable: /usr/bin/gnome-control-center journald_cursor: s=cb5d21a9c68942819c5b3f27536c3d13;i=4746;b=99fb64d1b500463da805eade22e99500;m=31431460;t=58691587060ff;x=f812f34d382b9563 kernel: 5.0.7-300.fc30.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 cc_display_mode_get_freq_f at ../panels/display/cc-display-config.h:73 #1 cc_display_settings_rebuild_ui at ../panels/display/cc-display-settings.c:311 #2 cc_display_settings_set_selected_output at ../panels/display/cc-display-settings.c:809 #3 set_current_output at ../panels/display/cc-display-panel.c:705 #4 rebuild_ui at ../panels/display/cc-display-panel.c:774 #5 on_screen_changed at ../panels/display/cc-display-panel.c:885 #10 _cc_display_config_manager_emit_changed at ../panels/display/cc-display-config-manager.c:54 #11 got_current_state at ../panels/display/cc-display-config-manager.h:29 #12 g_task_return_now at ../gio/gtask.c:1209 #13 g_task_return at ../gio/gtask.c:1278
Created attachment 1555246 [details] File: backtrace
Created attachment 1555247 [details] File: cgroup
Created attachment 1555248 [details] File: core_backtrace
Created attachment 1555249 [details] File: cpuinfo
Created attachment 1555250 [details] File: dso_list
Created attachment 1555251 [details] File: environ
Created attachment 1555252 [details] File: exploitable
Created attachment 1555253 [details] File: limits
Created attachment 1555254 [details] File: maps
Created attachment 1555255 [details] File: mountinfo
Created attachment 1555256 [details] File: open_fds
Created attachment 1555257 [details] File: proc_pid_status
Note: This is happening in BIOS mode (I've tested it on bare metal), behavior in UEFI might be different but that's not possible to test right now because of: https://bugzilla.redhat.com/show_bug.cgi?id=1693409
Proposed as a Freeze Exception for 30-final by Fedora user frantisekz using the blocker tracking app because: As per https://fedoraproject.org/wiki/Fedora_30_Final_Release_Criteria#.27Basic_graphics_mode.27_boot_mode_behavior this probably is not a blocker, but we should at least consider FE/CB.
I believe the patch in https://gitlab.gnome.org/GNOME/gnome-control-center/merge_requests/466 will fix this. Basically we are trying to display the settings for am monitor that does not have any mode currently (possibly disabled). We try to select the preferred mode then, but failing that we would run into the crash. The patch adds a fallback to simply select the first available mode.
I have submitted a scratch build: https://koji.fedoraproject.org/koji/taskinfo?taskID=34477580 Would be great if you can give it a try.
(In reply to Benjamin Berg from comment #16) > I have submitted a scratch build: > https://koji.fedoraproject.org/koji/taskinfo?taskID=34477580 > > Would be great if you can give it a try. Hmm, it seems I am no longer able to reproduce this issue (F30 RC1.2) even without this scratch build. Anyway, installing it at least does not regress anything.
You might be able to reproduce it if you log out, delete ~/.config/monitors.xml and then log back in again.
(In reply to Benjamin Berg from comment #18) > You might be able to reproduce it if you log out, delete > ~/.config/monitors.xml and then log back in again. I see no such file on my testing desktop but it's there on my work laptop (which is a UEFI installation and this bug was happening only on BIOS systems, so I can't test it on it).
In the event we cut the release without there being an occasion to vote on this, so dropping the FE nomination.
The upstream fix has been merged into g-c-c and will be included in the 3.32.2 release of g-c-c.
Similar problem has been detected: simply tried to load gnome display settings reporter: libreport-2.10.0 backtrace_rating: 4 cmdline: gnome-control-center display crash_function: cc_display_mode_get_freq_f executable: /usr/bin/gnome-control-center journald_cursor: s=e4730f1a5aa148a599b37c54a9e7cd95;i=1c8e;b=3f31c84e75294ed9908a7dd6e7b2415e;m=c5c0e37e;t=590fea6974bc0;x=dc3e1959c25338d8 kernel: 5.0.9-301.fc30.x86_64 package: gnome-control-center-3.32.1-2.fc30 reason: gnome-control-center killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Sorry for delay, it's working in F31, closing.
Similar problem has been detected: Not sure wiki doo pee pee reporter: libreport-2.10.0 backtrace_rating: 4 cmdline: gnome-control-center crash_function: cc_display_mode_get_freq_f executable: /usr/bin/gnome-control-center journald_cursor: s=75f53acb128847fc94e1fcadd918aa79;i=6a6;b=548506910f334946adbdc64efe2e983b;m=5c7cc15c;t=592284d8d5f2c;x=ee0da0a66e375cb7 kernel: 5.0.9-301.fc30.x86_64 package: gnome-control-center-3.32.1-2.fc30 reason: gnome-control-center killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000