Bug 2008472

Summary: Switching from single display to join display causes gnome control center to crash
Product: [Fedora] Fedora Reporter: grumpey0
Component: gnome-control-centerAssignee: GNOME SIG Unassigned <gnome-sig>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 35CC: gnome-sig, walter.pete
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-12-13 15:36:38 UTC Type: Bug
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
coredumpctl debug
none
coredumpctl debub, issue repeated.
none
my system info
none
gdb gnome-control-center running displays none

Description grumpey0 2021-09-28 10:50:38 UTC
Created attachment 1826926 [details]
coredumpctl debug

Description of problem:
Switching from single display to join display causes gnome-control-center to crash.  
Core was generated by `gnome-control-center display'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  cc_display_mode_get_preferred_scale (self=0x0) at ../panels/display/cc-display-config.c:106
106	cc_display_mode_get_preferred_scale (CcDisplayMode *self)
[Current thread is 1 (Thread 0x7f458c887200 (LWP 12947))]
[?2004h(gdb) bt
[?2004l
#0  cc_display_mode_get_preferred_scale (self=0x0) at ../panels/display/cc-display-config.c:106
#1  config_ensure_of_type.part.0.lto_priv.0 (panel=0x55f872102240, type=<optimized out>) at ../panels/display/cc-display-panel.c:241
#2  0x00007f458de83c2f in g_closure_invoke (closure=0x55f872114cb0, return_value=0x0, n_param_values=1, param_values=0x7ffc90ddfd30, invocation_hint=0x7ffc90ddfcb0) at ../gobject/gclosure.c:830
#3  0x00007f458dea0056 in signal_emit_unlocked_R (node=node@entry=0x55f871fdd510, detail=detail@entry=0, instance=instance@entry=0x55f8719d7290, emission_return=emission_return@entry=0x0, 
    instance_and_params=instance_and_params@entry=0x7ffc90ddfd30) at ../gobject/gsignal.c:3742
#4  0x00007f458dea191a in g_signal_emit_valist (instance=<optimized out>, signal_id=<optimized out>, detail=<optimized out>, var_args=var_args@entry=0x7ffc90ddfee0) at ../gobject/gsignal.c:3497
#5  0x00007f458dea1b33 in g_signal_emit (instance=<optimized out>, signal_id=<optimized out>, detail=<optimized out>) at ../gobject/gsignal.c:3553
#6  0x00007f458d6ff5eb in gtk_radio_button_clicked (button=0x55f8719d7290) at /usr/src/debug/gtk3-3.24.30-3.fc35.x86_64/gtk/gtkradiobutton.c:789
#7  0x00007f458dea19ea in _g_closure_invoke_va (param_types=0x0, n_params=<optimized out>, args=0x7ffc90de0180, instance=0x55f8719d7290, return_value=0x0, closure=0x55f871f53450) at ../gobject/gclosure.c:893
#8  g_signal_emit_valist (instance=0x55f8719d7290, signal_id=<optimized out>, detail=0, var_args=var_args@entry=0x7ffc90de0180) at ../gobject/gsignal.c:3406
#9  0x00007f458dea1b33 in g_signal_emit (instance=instance@entry=0x55f8719d7290, signal_id=<optimized out>, detail=detail@entry=0) at ../gobject/gsignal.c:3553
#10 0x00007f458d58d102 in gtk_button_clicked (button=button@entry=0x55f8719d7290) at /usr/src/debug/gtk3-3.24.30-3.fc35.x86_64/gtk/gtkbutton.c:1541


Version-Release number of selected component (if applicable):
gnome-control-center-41.0-1.fc35

How reproducible:


Steps to Reproduce:
1.Set Gnome Control Center, Displays to single display, Apply and Keep Settings
2.Set Gnome Control Center, Displays to join display, Apply 


Actual results:
Gnome Control Center crashes.

Expected results:
Switches to join displays with both displays available.

Additional info:
Switching to mirror displays and then join display works correctly.

Comment 1 grumpey0 2021-09-28 10:53:08 UTC
Created attachment 1826928 [details]
coredumpctl debub, issue repeated.

Comment 2 grumpey0 2021-09-28 10:53:38 UTC
Created attachment 1826929 [details]
my system info

Comment 3 grumpey0 2021-09-29 15:22:54 UTC
Created attachment 1827392 [details]
gdb gnome-control-center running displays

Comment 4 grumpey0 2021-09-29 15:34:16 UTC
Additional testing today. 
Monitor 1 is an LG electronics TV
Monitor 2 is an Samsung Monitor and is normally my primary display. 


If when going to a single display Monitor 1 is selected there is no crash.
It only crashes when Monitor 2 is the single display/primary display.

Comment 5 grumpey0 2021-09-29 15:58:41 UTC
Upstream bug report: https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1477

Comment 6 Ben Cotton 2022-11-29 17:05:41 UTC
This message is a reminder that Fedora Linux 35 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13.
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 '35'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 35 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 7 Ben Cotton 2022-12-13 15:36:38 UTC
Fedora Linux 35 entered end-of-life (EOL) status on 2022-12-13.

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