GNOME Bugzilla – Bug 533473
seahorse crashed with SIGSEGV in g_value_peek_pointer()
Last modified: 2008-10-22 17:18:12 UTC
Steps to reproduce: 1. Open applications -> accessories -> passwords and encryption keys 2. Select your primary key, right click on it and select Sync and Publish keys 3. Click on the sync button and wait 4. If it cannot get a response from the keyserver you get an error dialog box. This is very hard to close. I then got the sigsegv. https://bugs.edge.launchpad.net/ubuntu/+source/seahorse/+bug/198562 is the Ubuntu bug, with 5 duplicates. The stacktrace is from 2.21.92, I have confirmed with 2.22.1. Stack trace: Thread stack trace: .
+ Trace 197912
Thread 1 (process 9940)
Other information: https://bugs.edge.launchpad.net/ubuntu/+source/seahorse/+bug/198562 is the Ubuntu bug, with 5 duplicates. The stacktrace is from 2.21.92, I have confirmed with 2.22.1.
I cannot duplicate this problem, but this looks like a libsoup bug that seahorse is aggravating.
(In reply to comment #1) > I cannot duplicate this problem It happens when you try to sync to a keyserver that isn't responding. (eg, adding hkp://localhost:9999/ as a keyserver and trying to sync to it will trigger the bug). Ubuntu adds keyserver.ubuntu.com into the seahorse defaults, and apparently that server must go down a lot, cause people to trip over this bug. > but this looks like a libsoup bug that seahorse is aggravating. Yup. (Caused by unreffing the session from the queue_message callback, which is *supposed* to work, but apparently doesn't in this particular case.)
Created attachment 118879 [details] [review] patch to fix session refcounting This should fix the bug. We're in hard code freeze now, but this will be committed post-freeze for GNOME 2.24.1.
Fixed on trunk (differently from the earlier patch) and will eventually make it into libsoup 2.24.1.
Has this gone in for 2.24.1?
*** Bug 557408 has been marked as a duplicate of this bug. ***
*** Bug 551003 has been marked as a duplicate of this bug. ***
yes, it's in 2.24.1