Problem with gpg-agent and seahorse

Bug #149359 reported by Reiner Jung
4
Affects Status Importance Assigned to Milestone
enigmail (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

I get the following result when decrypting a message:

gpg command line and output:
/usr/bin/gpg --charset utf8 --batch --no-tty --status-fd 2 --keyserver-options auto-key-retrieve --keyserver random.sks.keyserver.penguin.de -d --use-agent
can't connect to `/tmp/seahorse-4VRcyo/S.gpg-agent': No such file or directory
gpg: can't connect to `/tmp/seahorse-4VRcyo/S.gpg-agent': connect failed
gpg: can't query passphrase in batch mode
gpg: Invalid passphrase; please try again ...
gpg: can't query passphrase in batch mode
gpg: Invalid passphrase; please try again ...
gpg: can't query passphrase in batch mode
gpg: encrypted with 2048-bit ELG-E key, ID ADDABA22, created 2004-07-29
      "xxxxxxx xxxxx <email address hidden>"
gpg: public key decryption failed: bad passphrase
gpg: encrypted with 4096-bit ELG-E key, ID EDAFBD4C, created 2007-07-10
      "vvvvvvvvv vvvvvvvvvv <email address hidden>"
gpg: decryption failed: secret key not available

The problem seams to be the missing /tmp/seahorse-4VRcyo/S.gpg-agent
but a file named /tmp/seahorse-z2o2Db/S.gpg-agent exists. So why does enigmail tries toget the wrong file path?

I also tried to close and reopen thunderbird. But that has no effect.

Revision history for this message
Reiner Jung (prefec2) wrote :

A the used packages are:
enigmail 2:0.95.0-0
thunderbird 2.0.0.6-0ubuntu
gnupg 1.4.6-2ubuntu

Distribution is: ubuntu 7.10 (gutsy gibbon)

Revision history for this message
Scott Kitterman (kitterman) wrote :

If you restart the computer and try again, does that help?

Revision history for this message
Reiner Jung (prefec2) wrote :

that didn't work. But I found an entry in .gnupg/gpg.conf where the file path for the agent was explicitly set to /tmp/seahorse-4VRcyo/S.gpg-agent

This is strange, because I didn't configured that. Or at least I don't know when and how I made that change.

Deleting the line with

gpg-agent-info=/tmp/seahorse-4VRcyo/S.gpg-agent:12345:1

fixed the problem.

Revision history for this message
Scott Kitterman (kitterman) wrote :

Odd. I'm marking this invalid then as I don't think that can happen automatically.

Changed in enigmail:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.