Created attachment 437299 [details]
patched pinentry launcher
Description of problem:
When using gpg in a terminal, it detects that $DISPLAY is set and passes it along to pinentry. The wrapper script then errors out about no GUI pinentry existing when pinentry-ncurses would work fine. This patch should work, but since I also don't have any GUI applications that use GPG, I cannot really fully test it. Testing it without applying and installing it involves:
1. Comment out the check for $PINENTRY_BINARY and the corresponding 'fi'
2. Get an encrypted file (gpg --encrypt $file > $file.gpg)
3. Decrypt with:
PINENTRY_BINARY=/path/to/patched/pinentry gpg --decrypy $file.gpg > /dev/null
4. pinentry-ncurses should pop up.
Another thing that needs to be tested is:
where gui-app requires a pinentry dialog for some action. Doing this from the command line should *not* result in pinentry-ncurses popping up in the terminal and should instead fail if there are no GUI pinentry dialogs installed. This can be simulated by commenting out the relevant if branches.
Version-Release number of selected component (if applicable):
pinentry-0.8.1-4.fc14 has been submitted as an update for Fedora 14.
pinentry-0.8.1-4.fc15 has been submitted as an update for Fedora 15.
Sorry it took so long. This is indeed a nice fallback mechanism that should have been there in the beginning. I applied this to all current Fedoras (F14+). If you feel like it, you can test the update for F14/15.
* should fix your issue,
* was pushed to the Fedora 15 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing pinentry-0.8.1-4.fc15'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
pinentry-0.8.1-4.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.
pinentry-0.8.1-4.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.