Version-Release number of selected component: seahorse-3.10.2-1.fc20 Additional info: reporter: libreport-2.1.11 backtrace_rating: 4 cmdline: /usr/bin/seahorse --no-window crash_function: gcr_collection_contains executable: /usr/bin/seahorse kernel: 3.12.8-300.fc20.i686+PAE runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 gcr_collection_contains at gcr-collection.c:145 #1 handle_get_subsearch_result_set at seahorse-search-provider.c:171 #2 ffi_call_SYSV at ../src/x86/sysv.S:65 #3 ffi_call at ../src/x86/ffi.c:411 #4 g_cclosure_marshal_generic at gclosure.c:1454 #5 g_type_iface_meta_marshal at gclosure.c:1021 #8 g_signal_emitv at gsignal.c:3063 #9 _seahorse_shell_search_provider2_skeleton_handle_method_call at seahorse-shell-search-provider-generated.c:1661 #10 g_dbus_interface_method_dispatch_helper at gdbusinterfaceskeleton.c:609 #11 skeleton_intercept_handle_method_call at gdbusinterfaceskeleton.c:650
Created attachment 860900 [details] File: backtrace
Created attachment 860901 [details] File: cgroup
Created attachment 860902 [details] File: core_backtrace
Created attachment 860903 [details] File: dso_list
Created attachment 860904 [details] File: environ
Created attachment 860905 [details] File: exploitable
Created attachment 860906 [details] File: limits
Created attachment 860907 [details] File: maps
Created attachment 860908 [details] File: open_fds
Created attachment 860909 [details] File: proc_pid_status
Created attachment 860910 [details] File: var_log_messages
I think I saw the same crash on my system, I reporeted it upstream.
fixed upstream https://bugzilla.gnome.org/show_bug.cgi?id=733957#c7 in 'master' branch, not sure how safe or will it be backported to 3.10, but it is good that it is fixed in next release. Possible 'duplicates' (probably reporeted eariler, but for older releases of 'seahorse' https://bugzilla.redhat.com/show_bug.cgi?id=1004901 https://bugzilla.redhat.com/show_bug.cgi?id=1026439 maybe there is more ...
*** Bug 1004901 has been marked as a duplicate of this bug. ***
*** Bug 1026439 has been marked as a duplicate of this bug. ***
seahorse-3.10.2-2.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/seahorse-3.10.2-2.fc20
Created attachment 931731 [details] trace I was testing this package from comment #16 and seahorse search provider finds my key (only trusted gpg key in my keyring), but when I click on it (not sure what it should do) it segfaults, I'll attach gdb backtrace without symbols. Should I report this upstream on same bug report?
Package seahorse-3.10.2-2.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing seahorse-3.10.2-2.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-9859/seahorse-3.10.2-2.fc20 then log in and leave karma (feedback).
Same as bitlord in comment 17, I see a crash following the same steps. ABRT says it's bug 1043691.
bug #1043691 (@ comment #19 ) is not related to this, it existed even before these backports, I'm able to reproduce it in f20 (with all updates, without test package from comment #16), I was wrong about saying that it was related. (filed upstream bug, you can get a link on bug #1043691 )
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.