On 9/4/18 6:10 PM, Daniel Kahn Gillmor wrote: > or do you mean something else?
without DISPLAY env var, qt version automatically falls back to curses variant despite the argument kristianf@ares ~ $ unset DISPLAY kristianf@ares ~ $ /usr/bin/pinentry-qt4 --display :0 (pinentry-qt4:6370): Gtk-WARNING **: 09:31:41.576: cannot open display: kristianf@ares ~ $ export DISPLAY=:0 kristianf@ares ~ $ /usr/bin/pinentry-qt4 --display :0 OK Pleased to meet you throwing in a simple wrapper around pinentry, #!/bin/bash env > /tmp/pinentry-log.txt echo "$@" >> /tmp/pinentry-log.txt exec /usr/bin/pinentry-qt "$@" and diffing the log between keep-display, shows that the difference is +DISPLAY=:0 btw, you say started, but this should also be updated when issuing UPDATESTARTUPTTY shouldn't it? In any case, it solved the issue for the user and I replicated it also on pinentry 1.1.0 on gnupg 2.2.10 -- ---------------------------- Kristian Fiskerstrand Blog: https://blog.sumptuouscapital.com Twitter: @krifisk ---------------------------- Public OpenPGP keyblock at hkp://pool.sks-keyservers.net fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3 ---------------------------- Credo quia absurdum I believe it because it is absurd
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
