two "can't connect" error dialogs when syncing to unresponsive key server
@danw
Submitted by Dan Winship Link to original bug (#552664)
Description
+++ This bug was initially created as a clone of Bug #533473 +++
Steps to reproduce:
- Open applications -> accessories -> passwords and encryption keys
- Select your primary key, right click on it and select Sync and Publish keys
- Click on the sync button and wait
- 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.
As discussed in 533473, the bug occurs when trying to sync to a server that isn't running, so you can reproduce it by trying to sync to "hkp://localhost:9999" (when there's nothing listening on port 9999).
The crash is libsoup's fault, and there's a patch in 533473 to fix it, but there's another bug, which is that seahorse actually pops up 2 "can't connect" dialogs. You can see this even without having the libsoup fix; both dialogs pop up, but seahorse crashes after you close the first one. So you should be able to find and fix the seahorse bug without needing a fixed libsoup.