Version-Release number of selected component: libreport-gtk-2.1.12-1.fc21 Additional info: reporter: libreport-2.1.12 backtrace_rating: 4 cmdline: report-gtk -- /var/tmp/abrt/ccpp-2014-02-03-01:21:46-869 crash_function: gtk_widget_show_all executable: /usr/bin/report-gtk kernel: 3.14.0-0.rc0.git15.2.fc21.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 gtk_widget_show_all at gtkwidget.c:4553 #1 prompt_timeout_cb at secrets.c:559 #7 secrets_prompt at secrets.c:653 #8 secrets_service_create_collection at secrets.c:924 #9 get_default_collection at secrets.c:1229 #10 save_event_config at secrets.c:1477 #11 libreport_save_event_config_data_to_user_storage at secrets.c:1593 #12 libreport_show_event_config_dialog at event_config_dialog.c:383 #13 on_configure_event_cb at wizard.c:285 #14 _g_closure_invoke_va at gclosure.c:840
Created attachment 859400 [details] File: backtrace
Created attachment 859401 [details] File: cgroup
Created attachment 859402 [details] File: core_backtrace
Created attachment 859403 [details] File: dso_list
Created attachment 859404 [details] File: environ
Created attachment 859405 [details] File: limits
Created attachment 859406 [details] File: maps
Created attachment 859407 [details] File: open_fds
Created attachment 859408 [details] File: proc_pid_status
Created attachment 859409 [details] File: var_log_messages
Created attachment 859410 [details] File: exploitable
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.