Version-Release number of selected component: control-center-3.11.3-1.fc21 Additional info: reporter: libreport-2.1.11 backtrace_rating: 4 cmdline: gnome-control-center --overview crash_function: g_permission_release_finish executable: /usr/bin/gnome-control-center kernel: 3.14.0-0.rc0.git3.1.fc21.x86_64 runlevel: 3 5 type: CCpp uid: 1001 Truncated backtrace: Thread no. 1 (10 frames) #0 g_permission_release_finish at gpermission.c:245 #1 release_cb at gtklockbutton.c:431 #2 g_simple_async_result_complete at gsimpleasyncresult.c:770 #3 release_check_cb at polkitpermission.c:717 #4 g_simple_async_result_complete at gsimpleasyncresult.c:770 #5 check_authorization_cb at polkitauthority.c:836 #6 g_simple_async_result_complete at gsimpleasyncresult.c:770 #7 reply_cb at gdbusproxy.c:2631 #8 g_simple_async_result_complete at gsimpleasyncresult.c:770 #9 g_dbus_connection_call_done at gdbusconnection.c:5486
Created attachment 855187 [details] File: backtrace
Created attachment 855188 [details] File: cgroup
Created attachment 855189 [details] File: core_backtrace
Created attachment 855190 [details] File: dso_list
Created attachment 855191 [details] File: environ
Created attachment 855192 [details] File: exploitable
Created attachment 855193 [details] File: limits
Created attachment 855194 [details] File: maps
Created attachment 855195 [details] File: open_fds
Created attachment 855196 [details] File: proc_pid_status
Created attachment 855197 [details] File: var_log_messages
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle. Changing version to '22'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.