Hi, I got hit by the same problem. It seems that it was caused by a re-login while gpg-daemon is running. Here is what happens:
Upon the first login, the gpg-agent is stated by /etc/X11/Xsession.d/90gpg-agent with the correct XAUTHORITY env variable. Everything works fine. Upon the second login, the mentioned script detects that a gpg-agent is already running and just sources the socket information etc. from $GNUPGHOME/gpg-agent-info-$(hostname). The new XAUTHORITY file information is not considered. Then some program tries to use gpg-agent, which itself spawns pinentry with the old XAUTHORITY information. That fails and gpg-agent gives up. Possible solutions: 1. Upon re-login, kill the old gpg-agent and start a new one 2. Ignore the old and start a second new one 3. Somehow pass the new display information (XAUTHORITY, DISPLAY) to the running gpg-agent The latter is the cleanest, but requires the most work and has to be carefully thought over security wise. Maybe someone knows a better fix. Greetings, Joachim -- Joachim "nomeata" Breitner Debian Developer [EMAIL PROTECTED] | ICQ# 74513189 | GPG-Keyid: 4743206C JID: [EMAIL PROTECTED] | http://people.debian.org/~nomeata -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
