Bug #6394

Seahorse launched from the gpgApplet cannot search for public keys

Added by sajolida 2013-10-31 11:05:06 . Updated 2015-03-23 02:02:44 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Target version:
Tails_1.3.1
Start date:
2013-10-31
Due date:
% Done:

100%

Feature Branch:
bugfix/6394-start-seahorse-using-torsocks
Type of work:
Code
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

Doing click on the gpgApplet → Manage Keys → Remote → Find Remote Keys → Search for “tails-bugs”, fails with an error message “Cannot connect to destination”.

The same operation is successful when starting Seahorse from the main menu System → Preferences → Passwords and Encryption Keys.

Is there a proxy misconfiguration when starting Seahorse from gpgApplet?

Subtasks

Related issues

Related to Tails - Bug #7051: Seahorse does have a configured default keyserver but it's not selected by default Confirmed 2014-04-09
Blocks Tails - Feature #8955: Write tests for syncing keys with Seahorse Resolved 2015-02-25

History

#1 Updated by intrigeri 2013-10-31 11:39:58

It would be awesome to track down which version of Tails introduced
this regression, assuming that’s one.

#2 Updated by sajolida 2013-11-02 07:52:29

I made it work with Tails 0.18 but no more with Tails 0.19.

#3 Updated by intrigeri 2014-05-29 07:59:25

  • related to Bug #7051: Seahorse does have a configured default keyserver but it's not selected by default added

#4 Updated by kytv 2015-02-25 10:42:45

  • Category set to Tor configuration
  • Status changed from Confirmed to In Progress
  • Assignee set to kytv
  • Target version set to Tails_1.3.2
  • % Done changed from 0 to 20

#5 Updated by kytv 2015-02-25 10:45:33

  • blocks Feature #8955: Write tests for syncing keys with Seahorse added

#6 Updated by intrigeri 2015-02-25 11:21:21

  • Category deleted (Tor configuration)

(“Tor Configuration” category is for little-t-tor config, e.g. torrc, Tor Launcher, this kind of stuff. So it doesn’t apply here I think.)

#7 Updated by kytv 2015-02-25 12:56:01

intrigeri wrote:
> (“Tor Configuration” category is for little-t-tor config, e.g. torrc, Tor Launcher, this kind of stuff. So it doesn’t apply here I think.)

(Makes sense.)

#8 Updated by kytv 2015-02-25 18:46:07

  • Assignee deleted (kytv)
  • QA Check set to Ready for QA
  • Feature Branch set to kytv:bugfix/6394-start-seahorse-using-torsocks
  • Starter deleted (No)

#9 Updated by intrigeri 2015-03-14 09:42:50

  • Assignee set to alant

#10 Updated by alant 2015-03-22 16:50:43

  • Assignee changed from alant to intrigeri
  • % Done changed from 20 to 80
  • QA Check changed from Ready for QA to Pass
  • Feature Branch changed from kytv:bugfix/6394-start-seahorse-using-torsocks to bugfix/6394-start-seahorse-using-torsocks

I tested and reviewed bugfix/6394-start-seahorse-using-torsocks as of commit:bfedc56d2b017c822d0a3063165666ec44221ea7. Everything is fine so the branch can be merged in stable. I let the RM of 1.3.1 decide when it’s appropriate.

#11 Updated by intrigeri 2015-03-22 16:59:33

  • Target version changed from Tails_1.3.2 to Tails_1.3.1

#12 Updated by intrigeri 2015-03-22 16:59:46

  • Status changed from In Progress to Fix committed
  • % Done changed from 80 to 100

Applied in changeset commit:177f7ffa686d827af422ceca12de9a02f1edf025.

#13 Updated by intrigeri 2015-03-22 18:26:56

  • Assignee deleted (intrigeri)

#14 Updated by BitingBird 2015-03-23 02:02:44

  • Status changed from Fix committed to Resolved