Re: pinentry-gtk2 doesn't react to keyboard input
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 06/03/2014 10:17 AM, lina wrote:
>
> 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,
>
Hi lina, please don't top-post because it makes the thread hard to
follow. Also, please note debian list policy on html:
https://www.debian.org/MailingLists/#codeofconduct
" Never send your messages in HTML; use plain text instead."
My point on the .xsession-error was only that for me, it provided a key
clue. I'm certainly no expert, but your two gpg-agent processes seem
suspect. Why would there be two? Maybe kill the one that is not in
your .cache/gpg-agent-info and see if that helps. Otherwise, I have no
clue.
Good luck!
Ralph
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Icedove - http://www.enigmail.net/
iQEcBAEBAgAGBQJTjfBMAAoJECe2FpioHXO6GrEIAIlKkS+Bv+HzjrLchxLPo94d
e0j59u69h/MbKvKLGiZt14Eu3bcYdErZx5EnlTusWT/CO3tLLHP80WREDtR/JJRr
3uokoksjOQwOxwYSelO+Kedqc72DwRkuVqY8cOtiFNjPzQKW2ZKGjiJTmOHhiR0b
I83Olfc/86y7CMdipzGBjQyqWXqnMA4Hd12EfgASLJBGT7M3NXH8DqrMAaKRJvKD
2lvpR85z5Tu+VetqyWQL9gaanNDOX+uHacenBA4LFoykmGEdY+bi5G0keh4RJg+r
UJaBJPiano/u9OezXymL/QgTF7BMxfAqRf3atq0uApltOMckGkBuLZWiFgihcak=
=M0Aw
-----END PGP SIGNATURE-----
Reply to: