Re: pinentry-{qt,gtk2,gnome3} stopped working pinentry-fltk works, why?

[Gregor Zattler <telegraph@gmx.net>]

Hi didier, debian users,
* didier gaumet <didier.gaumet@gmail.com> [21. Dez. 2020]:
> Le lundi 21 décembre 2020 à 00:30:05 UTC+1, Gregor Zattler a écrit :
>> Dear fellow debian users, since yesterday pinentry-{qt,gtk2,gnome3}
>> stopped working. When I want to decrypt some .gpg file, no dialog
>> appears and gpg-agent times out. Luckily pinentry-curses and
>> pinentry-fltk still do work.
>>
>> This is on a buster system with gpg* packages from backports,
>> pinentry* packages from buster (since there are no backports).

> It is not clear to me if pinentry-{qt,gtk2,gnome3} stopped working or if it is not called anymore as it was previously.
> As a first step, I would  check what are the values of pinentry and pinentry-x11 alternatives keys (you may use upate-alternatives in a terminal or {g,k}alternatives as a GUI tool).

thanks.  The alternatives mechanism was OK all the time, atm it is:
$ update-alternatives --display pinentry
pinentry - auto mode
link best version is /usr/bin/pinentry-fltk
link currently points to /usr/bin/pinentry-fltk
link pinentry is /usr/bin/pinentry
slave pinentry.1.gz is /usr/share/man/man1/pinentry.1.gz
/usr/bin/pinentry-curses - priority 50
slave pinentry.1.gz: /usr/share/man/man1/pinentry-curses.1.gz
/usr/bin/pinentry-fltk - priority 70
slave pinentry.1.gz: /usr/share/man/man1/pinentry-fltk.gz

Since I use etckeeper, I also know that there are no mofifications
under /etc in the time frame in question.

I now found a way to get more debug info from gpg-agent
and will check this.

Ciao, Gregor
--
 -... --- .-. . -.. ..--.. ...-.-