On 03/12/2014 00:40, Rolf Leggewie wrote: > On 03.12.2014 00:25, Rolf Leggewie wrote: >> "export GTK_IM_MODULE="";echo GETPIN | pinentry-curses" FAILS >> suggesting there is something essentially wrong with pinentry as well > > I got confused about what Ximin had written about pinentry-curses since > later on he mentioned only pinentry-gtk2, but here is the update on > pinentry-curses. > > export GTK_IM_MODULE=scim mytty=$(tty); echo GETPIN | pinentry-curses > --ttyname="$mytty" > WORKS, but at least here doesn't invoke scim and thus no CJKV or other > input. Only simple entry of ASCII and similar character is possible. > Contrary to my statement above, pinentry-curses seems to be generally > working as expected. >
Hi guys, Happy 2015. I have been following this thread and also done some homework. 1] I have tested on a clean workstation, with sid. The pinentry-gtk2, Enigmail and gpg-agent works perfect. And for forementioned package, the version in sid is the same as jessie. 2] I have only pinentry-gtk2 installed. $ dpkg --get-selections | grep pinentry pinentry-gtk2 install 3] The syslog indicates scim-bridge: Failed to allocate the current display scim-bridge: Failed to allocate the agent. Exitting... I wonder how deep the scim-bridge is related to it. is it possible due to my display setting reason? Thanks, lina -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
