Version-Release number of selected component: control-center-3.10.0-1.fc20 Additional info: reporter: libreport-2.1.7 backtrace_rating: 4 cmdline: gnome-control-center --overview crash_function: remote_call_complete executable: /usr/bin/gnome-control-center kernel: 3.11.2-301.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (5 frames) #0 remote_call_complete at /lib64/libnm-glib.so.4 #1 result_cb at /lib64/libnm-glib.so.4 #2 complete_pending_call_and_unlock at dbus-connection.c:2314 #8 g_main_context_iteration at gmain.c:3773 #9 g_application_run at gapplication.c:1635
Created attachment 807334 [details] File: backtrace
Created attachment 807335 [details] File: cgroup
Created attachment 807336 [details] File: core_backtrace
Created attachment 807337 [details] File: dso_list
Created attachment 807338 [details] File: environ
Created attachment 807339 [details] File: exploitable
Created attachment 807340 [details] File: limits
Created attachment 807341 [details] File: maps
Created attachment 807342 [details] File: open_fds
Created attachment 807343 [details] File: proc_pid_status
Please provide reproduction information. Why is the bug marked as private?
Client crashes are not typically regarded as security flaws if the only issue is a crash. Removing the security bits.
(In reply to Adam Williamson from comment #11) > Why is the bug marked as private? ABRT marked it as private. See: Bug 1025935 - Cannot Uncheck box "Private Group..." even though I am the Reporter Don't know STR.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 '20'. 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 20 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 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.