| Summary: | kde-misc/basket-1.81 - GPGME: Bad passphrase | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Jason Oliveira <jason.oliveira> |
| Component: | [OLD] KDE | Assignee: | Gentoo KDE team <kde> |
| Status: | RESOLVED NEEDINFO | ||
| Severity: | major | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Jason Oliveira
2013-08-08 21:27:17 UTC
Upon further investigation (running the app via konsole/yakuake), it appears that the GPGME dialog is appearing in the terminal:
┌─────────────────────────────────────────────────────┐
│ Enter passphrase │
│ │
│ │
│ Passphrase ***************************************_ │
│ │
│ <OK> <Cancel> │
└─────────────────────────────────────────────────────┘
but fills with characters, and then makes the terminal unusable. This makes basket freeze, but does not bring up the "GPGME: Bad passphrase" before freezing.
According to htop, my CPU spikes when this happens, and the culprit is pinentry --display :0 'USE="qt4" emerge app-crypt/pinentry' was attempted, but pinentry seems to still be using the ncurses interface. Kleopatra is exhibiting an inability to create GPG keys, so this seems to be basket exhibiting symptoms of a larger issue. Okay, I think I have resolved the issue on my computer. changed the /usr/bin/pinentry symbolic link to point to pinentry-qt4 rather than pinentry-ncurses. basket and kleopatra are now confirmed working. I don't think there's a way for us to control the pinentry client, so maybe we could add a message to the ebuild advising that pinentry-qt4 is required to be active? (In reply to Jason Oliveira from comment #3) > Okay, I think I have resolved the issue on my computer. changed the > /usr/bin/pinentry symbolic link to point to pinentry-qt4 rather than > pinentry-ncurses. basket and kleopatra are now confirmed working. We have an eselect module to assist you with this, for example: eselect pinentry set pinentry-curses Could you confirm whether the pinentry-ncurses dialog issue only happens for basket? I've had problems with pinentry-ncurses in the past myself, so this may be a bug there rather than with basket. (In reply to Chris Reffett from comment #5) > Could you confirm whether the pinentry-ncurses dialog issue only happens for > basket? I've had problems with pinentry-ncurses in the past myself, so this > may be a bug there rather than with basket. |
