When I'm doing: $ gpg --decrypt somekey.gpg it returns (sorry that some parts are in german, if you need it in english please tell me how to switch the lang): gpg: 3DES verschlüsselte Daten can't connect to `/root/.gnupg/S.gpg-agent': Datei oder Verzeichnis nicht gefunden pinentry: cannot connect to X server gpg-agent[5178]: can't connect server: ec=4.16383 gpg-agent[5178]: can't connect to the PIN entry module: Dateiende gpg-agent[5178]: command get_passphrase failed: Kein Pinentry gpg: Problem mit dem Agenten: Kein Pinentry gpg: Verschlüsselt mit einer Passphrase gpg: Entschlüsselung fehlgeschlagen: Kein geheimer Schlüssel pinentry is with USE-Flags ncurses and qt4 for the console, an entry in gpg-agent.conf like "pinentry-program /usr/bin/pinentry-curses" helps, but it doesn't help if gnupg is called while booting (for cryptsetup in my case). if you need more info (like emerge --info), let me know. Reproducible: Always
The fallback curses only works when $DISPLAY is not set.
Yeah, but with -0.7.5 it works too, if $DISPLAY is set -> regression (esp. because crypted volumes don't work with cryptsetup anymore)
it's easy to fix for gtk, but it's qt itself that forcibly terminates pinentry when it can't access the x server. i suspect it's a qt3 vs qt4 thing.
i just tried out the app-crypt/pinentry-0.8.0 and it works fine for the fallback! So this bug might be closed if you make sure that stabilazation skips the -0.7.6 version.
(In reply to comment #4) > i just tried out the app-crypt/pinentry-0.8.0 and it works fine for the > fallback! > > So this bug might be closed if you make sure that stabilazation skips the > -0.7.6 version. > I've adjusted the stable bug to 0.8.0... and closing.
