Description of problem: Closed gigolo with an automounted ssh share and it crashed. Version-Release number of selected component: gigolo-0.4.2-1.fc20 Additional info: reporter: libreport-2.1.11 backtrace_rating: 4 cmdline: gigolo crash_function: magazine_chain_pop_head executable: /usr/bin/gigolo kernel: 3.12.6-300.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 magazine_chain_pop_head at gslice.c:550 #1 magazine_chain_prepare_fields at gslice.c:624 #2 magazine_cache_push_magazine at gslice.c:697 #3 thread_memory_magazine2_unload at gslice.c:815 #4 g_slice_free1 at gslice.c:1106 #5 g_type_free_instance at gtype.c:1938 #6 gtk_menu_shell_forall at gtkmenushell.c:1113 #7 gtk_container_destroy at gtkcontainer.c:1073 #12 gtk_object_dispose at gtkobject.c:421 #14 gtk_menu_item_destroy at gtkmenuitem.c:545
Created attachment 850262 [details] File: backtrace
Created attachment 850263 [details] File: cgroup
Created attachment 850264 [details] File: core_backtrace
Created attachment 850265 [details] File: dso_list
Created attachment 850266 [details] File: exploitable
Created attachment 850267 [details] File: limits
Created attachment 850268 [details] File: maps
Created attachment 850269 [details] File: open_fds
Created attachment 850270 [details] File: proc_pid_status
Created attachment 850271 [details] File: var_log_messages
Can you get this to happen everytime? Or is it sporadic?
Just happened to me. I clicked the exit button on the toolbar and was greeted by the error a couple seconds later. It seems to happen sporadically for me.
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.