seahorse-agent stops responding when started with gpg-agent
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
seahorse-plugins |
Invalid
|
High
|
|||
seahorse-plugins (Ubuntu) |
Fix Released
|
High
|
Unassigned |
Bug Description
Binary package hint: seahorse
I used to have seahorse prompting for the SSH passphrase. For instance I typed "ssh myserver", and a dialog appeared automatically.
Now that I switched to Hardy, I have to type "ssh-add" at the start of my session, like I was doing a year ago.
But the seahorse agent seems to be properly running:
herve 6400 0.0 0.3 22296 6872 ? Ss 09:33 0:00 /usr/bin/
herve 10198 0.0 0.3 45496 7676 ? Ss 12:22 0:00 seahorse-agent
And in the seahorse application, my SSH key is listed.
From bug #217270:
When I access the seahorse program preferences, in the tab "PGP Passphrases", I get the message "A supported PGP passphrase caching agent is not running".
On the console where I launched seahorse, I see:
** Message: init gpgme version 1.1.5
** (seahorse:7462): WARNING **: Invalid or no GPG agent is running. Disabling cache preferences.
I'm pretty sure the agents are running, as show with a "ps auwx|grep agent":
foo 864 ? Ss 15:46 0:00 /usr/bin/gpg-agent --daemon --sh --write-
foo 756 ? Ss 15:46 0:00 /usr/bin/
Workaroung from comment 5:
I fixed my problem by looking at the default setup of another system and noting that it did not have:
/etc/
I renamed that file, restarted X, and all is well. Seahorse is running by itself rather than under gpg-agent:
/usr/
Related branches
Changed in seahorse: | |
assignee: | andreas-moog → nobody |
summary: |
- [hardy] seahorse agent no longer asks for the passphrase + seahorse-agent stops responding when started after gpg-agent |
summary: |
- seahorse-agent stops responding when started after gpg-agent + seahorse-agent stops responding when started with gpg-agent |
description: | updated |
description: | updated |
Changed in seahorse-plugins (Ubuntu): | |
status: | Confirmed → Triaged |
Changed in seahorse-plugins: | |
status: | Unknown → New |
Changed in seahorse-plugins: | |
importance: | Unknown → High |
status: | New → Invalid |
I can confirm this bug in Seahorse 2.22.0-0ubuntu2.
Ubuntu Hardy/AMD64.
The seahorse-agent is running but it only picks up the id_rsa key (and not id_rsa.1 etc), however other keys are configured and present in the keyring.