Re: pinentry-gtk2 doesn't react to keyboard input

surprised to see I have two processes.

$ ps axjf | grep gpg
    1 3980 3980 3980 ?           -1 Ss    1000   0:00 /usr/bin/gpg-agent --sh --daemon --write-env-file /home/lina/.cache/gpg-agent-info
    1 6109 6109 6109 ?           -1 Ss    1000   0:00 /usr/bin/gpg-agent --sh --daemon --write-env-file /home/lina/.cache/gpg-agent-info
6223 6739 6738 6223 pts/0     6738 S+    1000   0:00      \_ grep --color=auto gpg

:/tmp$ ls gpg*
gpg-RI3XNy:
S.gpg-agent

gpg-UGEUjm:
S.gpg-agent

$ more /home/lina/.cache/gpg-agent-info
GPG_AGENT_INFO=/tmp/gpg-UGEUjm/S.gpg-agent:6109:1

Well, it doesn't work for me. The pinentry window is dead, kinda of, won't be able to react my keyboard input, except the cancel/Okay button, might be some bug.

BTW,

SIGHUP This signal flushes all cached passphrases and if the program
              has been started with a configuration file, the configuration
              file is read again. Only certain options are honored: quiet,
              verbose, debug, debug-all, debug-level, no-grab, pinentry-pro‐
              gram, default-cache-ttl, max-cache-ttl, ignore-cache-for-sign‐
              ing, allow-mark-trusted, disable-scdaemon, and disable-check-
              own-socket. scdaemon-program is also supported but due to the
              current implementation, which calls the scdaemon only once, it
              is not of much use unless you manually kill the scdaemon.

I don't understand your point of .xsession-error here. Thanks,

On Tue, Jun 3, 2014 at 9:13 PM, Ralph Katz <ralph.katz@rcn.com> wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 06/02/2014 11:07 PM, lina wrote:
> Hi,
>
> I use icedove + enigmail for encryption with the pinentry-gtk2 as
> gpg-agent in the past.
>
> It worked well until yesterday I added a new email account with new gpg
> key for it.
>
> When the pop-up asked for passphrase, I just can't input anything inside.
>
> Later I tried the pinentry-qt4 and pinentry-curses, there is even no
> popup except telling me bad passphrases.
>
> Thanks ahead for any suggestions?
>
> Best regards, lina

Hi, I had a similar issue with icedove + enigmail with 'Error - bad
passphrase' and 'You are using gpg-agent for passphrase handling.
Clearing the passphrase is therefore not possible from within Enigmail.'

I had logged in on a 2nd virtual terminal which somehow killed the
gpg-agent. Check your .xsession-errors; I found this:
running 'pkill -INT ^gpg-agent$;

Check if gpg-agent is running:
~$ ps aux |grep gpg
ralph 3593 0.0 0.0 19352 680 ? Ss May24 0:15
gpg-agent --daemon --write-env-file /home/ralph/.cache/gpg-agent-info

This is up-to-date stable; uses pinentry-gtk2.

I rebooted to resolve the issue, but I think only gpg-agent needed to be
restarted.

Hope this may help you troubleshoot your issue.

Good luck!
Ralph

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Icedove - http://www.enigmail.net/

iQEcBAEBAgAGBQJTjcn5AAoJECe2FpioHXO6+R0H/RXx6GVBNuK7TtVQcT53/BSW
B5RCVSGwvb1i9ML44Jm3PaBhWk0CPbAyBEE4w1ic0iGihLevURLcgQdTPAzImzWC
zUXJY2bzY47JNHwiSXQ8wjp56AvD4twhy+4/pHUfjSltvbJ67iQs1T+k42ZVzzrL
DS1NnSwqEg9e+7O2vmA0Pbvb7aO6LkHE9Pp3xieCz59sKwYkfdECjyomij2q+2BZ
IJkOdYzmLTNgWkCJ5cOfVQyn9j1T/2bqJxPdjuJJ2vc7X3dNYHOdiJcLYPscFWGO
Qamr0f9P1HIb/GcUzgvtpl6xIS0c+lcI+tpvmqYLxWW6rTaFiD0nWkws1UxR2Es=
=I4R0
-----END PGP SIGNATURE-----

--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: [🔎] 538DCA06.2080407@rcn.com" target="_blank">https://lists.debian.org/[🔎] 538DCA06.2080407@rcn.com