Description of problem: Closed Gigolo after it had failed to access a machine using SSH. The problem occurs frequently but not always. Version-Release number of selected component: gigolo-0.4.1-11.fc20 Additional info: reporter: libreport-2.2.1 backtrace_rating: 4 cmdline: gigolo crash_function: magazine_cache_push_magazine executable: /usr/bin/gigolo kernel: 3.13.9-200.fc20.i686 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 magazine_cache_push_magazine at gslice.c:706 #1 thread_memory_magazine2_unload at gslice.c:815 #2 g_slice_free1 at gslice.c:1106 #3 g_type_free_instance at gtype.c:1938 #6 gtk_object_destroy at gtkobject.c:406 #7 gtk_notebook_forall at gtknotebook.c:4305 #8 gtk_container_foreach at gtkcontainer.c:1534 #9 gtk_container_destroy at gtkcontainer.c:1073 #10 gtk_notebook_destroy at gtknotebook.c:1534 #17 gtk_object_dispose at gtkobject.c:421
Created attachment 884758 [details] File: backtrace
Created attachment 884759 [details] File: cgroup
Created attachment 884760 [details] File: core_backtrace
Created attachment 884761 [details] File: dso_list
Created attachment 884762 [details] File: environ
Created attachment 884763 [details] File: exploitable
Created attachment 884764 [details] File: limits
Created attachment 884765 [details] File: maps
Created attachment 884766 [details] File: open_fds
Created attachment 884767 [details] File: proc_pid_status
Created attachment 884768 [details] File: var_log_messages
Is it always on close? Or any other patterns you can see?
So far, when it has crashed the crash has always been on close.
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.