This bug is on yesterdays git-master stage. I have as little as possble kde4 stuff installed, this is basically a gentoo-KF5 only install. Reproducible: Always Steps to Reproduce: 1. Create gpg key with password 2. Try to use it in kleopatra or via kmail 3. Create gpg key without password and try the same Actual Results: It should ask for a password to open the key, but it just does not. On the Kleopatra interface it simply does nothing, when used via kmail no prompt, but an immediate wrong password error appears. Expected Results: It should ask for the password to decrypt. It works currently only for non encrypted keys
This sounds a bit like a problem in your setup or pinentry. This behavior would occur if pinentry can't be launched from the environment kleopatra runs in. In the same environment where you run Kleopatra (e.g. same LD_LIBARARY_PATH, same PATH variables) can you run: echo foo | gpg -s And are asked for your passphrase? Second question: Which pinentry are you using? Did you cahange pinentry in your gpg-agent.conf (using pinentry-program option) What does: pinentry --version output?
Pinentry --version on konsole prompt: pinentry-curses (pinentry) 0.9.5 Copyright (C) 2015 g10 Code GmbH License GPLv2+: GNU GPL version 2 or later <http://gnu.org/licenses/> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. echo foo | gpg -s: gpg: enabled debug flags: memstat Sie benötigen eine Passphrase, um den geheimen Schlüssel zu entsperren. Benutzer: "xxxxx" 2048-Bit DSA Schlüssel, ID xxxx gpg-agent[575]: enabled debug flags: assuan gpg: Problem mit dem Agenten: Unpassender IOCTL (I/O-Control) für das Gerät gpg: no default secret key: Verarbeitung wurde abgebrochen gpg: signing failed: Verarbeitung wurde abgebrochen random usage: poolsize=600 mixed=0 polls=0/0 added=0/0 outmix=0 getlvl1=0/0 getlvl2=0/0 secmem usage: 0/65536 bytes in 0 blocks If I repeat it without a password set on the key, then it does not give an error but gibberish appears in the screen echo foo | gpg -s gpg: enabled debug flags: memstat ������!ȸ5�k��ӗ����▒�T�����suır0��2�D▒�8`��;▒� eix pinentry: I] app-crypt/pinentry Available versions: 0.9.0 ~0.9.0-r3 0.9.5 ~0.9.6-r4 ~0.9.6-r5 **9999[1] {caps clipboard emacs gnome-keyring gtk ncurses qt4 qt5 static} Installed versions: 0.9.5(02:02:18 16.10.2015)(gtk ncurses -caps -clipboard -emacs -gnome-keyring -qt4 -static) Homepage: http://gnupg.org/aegypten2/index.html Description: Collection of simple PIN or passphrase entry dialogs which utilize the Assuan protocol ---- I see that 0.9.5 stable does not support qt5 use flag - could that be the problem? I will increase it to testing or git-master and retry.
Bumped to testing, same bug: gpg: Problem mit dem Agenten: Unpassender IOCTL (I/O-Control) für das Gerät app-crypt/pinentry Available versions: 0.9.0 (~)0.9.0-r3 0.9.5 (~)0.9.6-r4 (~)0.9.6-r5 **9999[1] {caps clipboard emacs gnome-keyring gtk ncurses qt4 qt5 static} Installed versions: 0.9.6-r5(19:47:06 19.10.2015)(gtk ncurses qt5 -caps -emacs -gnome-keyring -qt4 -static)
Also here, after retrying after 8 months the bug seems to be gone now. Must have been fixed together with other general bugfixes.