Version-Release number of selected component: control-center-3.17.2-2.fc23 Additional info: reporter: libreport-2.6.0 backtrace_rating: 4 cmdline: gnome-control-center --overview crash_function: cc_panel_size_allocate executable: /usr/bin/gnome-control-center global_pid: 2879 kernel: 4.1.0-1.fc23.x86_64 runlevel: N 5 type: CCpp uid: 1001 Truncated backtrace: Thread no. 1 (10 frames) #4 cc_panel_size_allocate at cc-panel.c:202 #5 g_cclosure_marshal_VOID__BOXEDv at gmarshal.c:1950 #6 _g_closure_invoke_va at gclosure.c:864 #9 gtk_widget_size_allocate_with_baseline at gtkwidget.c:6119 #10 gtk_box_size_allocate_no_center at gtkbox.c:801 #11 g_cclosure_marshal_VOID__BOXEDv at gmarshal.c:1950 #12 _g_closure_invoke_va at gclosure.c:864 #15 gtk_widget_size_allocate_with_baseline at gtkwidget.c:6119 #16 gtk_widget_size_allocate at gtkwidget.c:6188 #17 gtk_stack_size_allocate at gtkstack.c:2128
Created attachment 1043884 [details] File: backtrace
Created attachment 1043885 [details] File: cgroup
Created attachment 1043886 [details] File: core_backtrace
Created attachment 1043887 [details] File: dso_list
Created attachment 1043888 [details] File: environ
Created attachment 1043889 [details] File: limits
Created attachment 1043890 [details] File: maps
Created attachment 1043891 [details] File: mountinfo
Created attachment 1043892 [details] File: namespaces
Created attachment 1043893 [details] File: open_fds
Created attachment 1043894 [details] File: proc_pid_status
Another user experienced a similar problem: - start the settings app - select the Date & Time option - Settings crashes reporter: libreport-2.6.1 backtrace_rating: 4 cmdline: gnome-control-center --overview crash_function: cc_panel_size_allocate executable: /usr/bin/gnome-control-center global_pid: 2682 kernel: 4.2.0-0.rc1.git3.1.fc23.x86_64 package: control-center-3.17.2-2.fc23 reason: gnome-control-center killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
This bug appears to have been reported against 'rawhide' during the Fedora 23 development cycle. Changing version to '23'. (As we did not run this process for some time, it could affect also pre-Fedora 23 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 23 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora23
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. 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 Fedora 'version' of '23'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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 please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.