I can't send a PGP-signed e-mail

Bug #14814 reported by Ricardo Pérez López
8
Affects Status Importance Assigned to Milestone
evolution (Ubuntu)
Invalid
Medium
Sebastien Bacher

Bug Description

1. Open Evolution
2. Click on "New" button, for a new e-mail
3. "Compose a message" window appears
4. I select Security -> PGP Sign
5. I compose the message, and click on Send.
6. A dialog box appears asking me for the passphrase to unlock the key. I type it.
7. An error message appears:

------------
 No se pudo crear un mensaje.

 Debido a «gpg: can't connect to `/tmp//seahorse-b6NfP9/S.gpg-agent': No existe
el fichero o el directorio
  gpg: writing to `-'
  gpg: DSA signature from: "4DE85EF8 Ricardo Pérez <email address hidden>"
  », quizá necesite seleccionar diferentes opciones de correo.
------------

(In an English-Spanish mixin.)

Of course, I've configured the security settings (the PGP key ID) correctly
before composing the new e-mail.

Any ideas?

Ricardo.

Revision history for this message
Sebastien Bacher (seb128) wrote :

do you have seahorse installed ? does that happen without it ?

Revision history for this message
Ricardo Pérez López (ricardo) wrote :

(In reply to comment #1)
> do you have seahorse installed ? does that happen without it ?

No, I haven't seahorse installed. I tried installing it, but the problem remains.

Revision history for this message
Sebastien Bacher (seb128) wrote :

can you write to /tmp with your user ? could you get the english version of this
message ?

Revision history for this message
Ricardo Pérez López (ricardo) wrote :

(In reply to comment #3)
> can you write to /tmp with your user ?

Yes, perfectly.

> could you get the english version of this
> message ?

With LANG=en_US and LC_ALL=en_US, and doing the same seven steps as before, I
got an empty dialog box, with title "Evolution error", and containing only a red
traffic icon and an "ok" button. Pressing this "ok" button closes the dialog box.

Revision history for this message
Sebastien Bacher (seb128) wrote :

do you use gpg-agent ? can you try without it ?

Revision history for this message
Ricardo Pérez López (ricardo) wrote :

(In reply to comment #5)
> do you use gpg-agent ? can you try without it ?

Sorry, I don't know what gpg-agent is. Is it a package? I can't find it in the
repositories.

Revision history for this message
Sebastien Bacher (seb128) wrote :

that's a gnupg option. Do you have a file with this name (~/.gnupg) or a such
option for the gpg config ?

Revision history for this message
Ricardo Pérez López (ricardo) wrote :

(In reply to comment #7)
> that's a gnupg option. Do you have a file with this name (~/.gnupg) or a such
> option for the gpg config ?

Yes! In ~/.gnupg/gpg.conf, there's an uncomment line that shows:

   user-agent

and another that shows:

   gpg-agent-info /tmp//seahorse-b6NfP9/S.gpg-agent:2310:1

Maybe I must remove that two lines? Or to change with anothers?

I attach my gpg.conf.

Thanks!

Revision history for this message
Ricardo Pérez López (ricardo) wrote :

Created an attachment (id=1973)
My ~/.gnupg/gpg.conf file

Revision history for this message
Sebastien Bacher (seb128) wrote :

(In reply to comment #8)

> Yes! In ~/.gnupg/gpg.conf, there's an uncomment line that shows:
>
> user-agent
>
> and another that shows:
>
> gpg-agent-info /tmp//seahorse-b6NfP9/S.gpg-agent:2310:1

Right, can you comment these 2 lines and try again ?

Revision history for this message
Ricardo Pérez López (ricardo) wrote :

(In reply to comment #10)
> (In reply to comment #8)
>
> > Yes! In ~/.gnupg/gpg.conf, there's an uncomment line that shows:
> >
> > user-agent
> >
> > and another that shows:
> >
> > gpg-agent-info /tmp//seahorse-b6NfP9/S.gpg-agent:2310:1
>
> Right, can you comment these 2 lines and try again ?
>
>

Yes! And works perfectly!

I don't know why these two lines are here. But the problem is now fixed
commenting that lines.

Thank you very much.

Ricardo.

Revision history for this message
Sebastien Bacher (seb128) wrote :

is that ok to close the bug ?

Revision history for this message
Ricardo Pérez López (ricardo) wrote :

(In reply to comment #12)
> is that ok to close the bug ?

Yes for me. The problem is solved in my box.

Thanks again.

Revision history for this message
Sebastien Bacher (seb128) wrote :

user config issue, fixed, bug closed

Revision history for this message
Mario Vukelic (kreuzsakra) wrote :

I woud like to have the bug reopened, because I don't think it's a user config
problem, but rather a bug in seahorse (possibly only in an older version). I run
up-to-date Dapper, the machine was upgraded from Breezy, and before that from
Hoary, with all changes applied as per the release notes.

Before I installed Seahorse, gpg worked fine in Evolution. Then I installed
Seahorse, added seahorse-agent to the session, and gpg continued to work fine in
Evo, but with the seahorse agent.
At one point (during Breezy) I removed Seahorse (including session entry) for
some reason, and gpg stopped working in Evo, with the error message mentioned by
the original submitter. Since I didn't really care one way or the other, I
reinstalled seahorse, and then it worked again.

Now I again wanted to remove seahorse, same result. Investigation shows that:

* Indeed there are the entries "use-agent" and "gpg-agent-info
/home/mario/.gnome2/seahorse-kbMJf4/S.gpg-agent:8477:1" in gpg.conf.
But I didn't put them there for sure, and since the second one references
seahorse, this is the only application that reasonably can have put it there.

* I have a whole bunch of files named S.gpg-agent in directories that were named
like the one referenced in gpg.conf above, ~/.gnome2/seahorse-<random>.
When I try to rm the files I get the error, "cannot remove <file> no such file
or directory". The file command I used to check for the type of file says that
those are sockets.
There are ca. 40 of these directories, plus
A directory ~/.gconf/apps/seahorse with gconf stuff inside
A config file ~/.gnome2/accels/seahorse which is a "automated accelerator map
dump" for GtkAccelMap by seahorse
A .desktop file in ~/.local/share/applications/seahorse-usercustom.desktop

Removing the use-agent and gpg-agent-info lines from gpg.conf fixes the gpg
error in Evo, but I am sure seahorse messed it up.

Revision history for this message
Mario Vukelic (kreuzsakra) wrote :

Sorry, gotta correct myself. After all I can rm the sockets I mentioned. The
"cannot remove file" error was caused by a mistyped find command.
The point about seahorse stands though :)

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.