Created attachment 116815 [details] Screenshot SUMMARY Version 3.1.3 STEPS TO REPRODUCE 1. Open Application, go to "Notepad" -> "Recipients" 2. Click on "sign as" OBSERVED RESULT Selection list is empty, no keys appear EXPECTED RESULT Signing key should be in the list SOFTWARE/OS VERSIONS Linux/KDE Plasma: Opensuse Leap 15 KDE Plasma Version: 5.14.4 KDE Frameworks Version: 5.52.0 Qt Version: 5.11.2 ADDITIONAL INFORMATION I can select the key as the encryption key but not as the signing key
This should only happen if your key is disabled / exipred or revoked. Or if you do not have a suitable key: Do you have an ultimately trusted private OpenPGP key? If you select "My Certificates" in the keylist, what does it show? Can you please attach a screenshot of that if it shows your key? Thanks! Andre
Created attachment 116828 [details] Screenshot Sometimes it shows up in 'My certificates' and sometimes it shows up in 'Trusted certificates'. After a reboot I can't even use the key to encrypt the notepad anymore.
Created attachment 116829 [details] Second screenshot
There is indeed something very fishy going on here. From the first screenshot I would have said: Ok. You don't have the private key. Because the key is not bold and you are showing trusted certificates and not "my certificates" But the second screenshot in contrast shows the "Add email address", "Change passphrase" etc,.. options that are only available if Kleopatra detects that you have the private key. o.O I would not have thought that this is possible. Did you make the screenshots in two different runs of Kleopatra? For further analysis please show the command line output of: gpg --version gpg2 --version (I'm not sure if in OpenSUSE Leap GnuPG 2 is called gpg or gpg2, please use gpg2 in the following commands if gpg --version shows something like 1.4.x) gpg -K echo foo | gpg -sau "your email or keyid"
No the screenshots are from the same run. I. gpg version: 2.2.5 II. gpg -K: /home/rofl/.gnupg/pubring.kbx ----------------------------- sec rsa4096 2018-12-01 [SCA] [expires: 2019-03-11] E0EFCD620BE2D9E1246158309BDB38B5A80CF964 uid [ultimate] Matthieu Gras <grasm@student.ethz.ch> uid [ultimate] Matthieu Gras <matthieu.gras@aol.com> ssb rsa4096 2018-12-01 [E] [expires: 2020-12-02] III. echo foo | gpg -sau "grasm@student.ethz.ch": Opens window to enter passphrase, then outputs: -----BEGIN PGP MESSAGE----- owEBaAKX/ZANAwAIAZvbOLWoDPlkAcsKYgBcDnE8Zm9vCokCSgQAAQgANBYhBODv zWIL4tnhJGFYMJvbOLWoDPlkBQJcDnE8FhxncmFzbUBzdHVkZW50LmV0aHouY2gA CgkQm9s4tagM+WRfvw/+PGULrsi5K4TZTFlOVTdH9AwXPKwznonuaLMvbzrgDVV3 krWRnzjx0DlRxpNlMzYNm0EbjPWyZGefZlXzY/ClK+NWQ1+6UOUThs/ggjwRwSzf JeE/MqCwfqlNFnrLT3NC7n7VGvwKOD4lhs+6U0P/sFeTSE23/eOgt86QhwL4p2u5 3WWszLH/MHVg52PhUNLYS50HeqMITW2MUZdo7VG1NQ6yJ/iTk6VjbrK9za/Z/arJ 1hi2q87i7ID9tGsTo8wJMEhQM4q83Ned2thLUbGUu7atmbHPGwsGYOpHu1YB1qnJ wKEPsAWaDGGoiFhEqbFnM8pe5eL2q9hSPUEwXKO43vPX7GKqLyv+cjFejkPv7SYs 4N0u8ZVlpqiRbLgG82FUJzSOgUkZyYxF/bpUOL+gSoKPBGgq2mG9Vhc8MEgamURH 0HBQHE6XDPy8bljgpx/OI859aV8Zib9qnJvBaPtH2wU1jMVFzQiJ/AtA8FyFLcpK +DI+yFexJ0l4Goy/DsppGvxvuG45Qbh4ClBBlFIfbXHeU9y8mmlPuIlIE1DE+kXw uyKylaGDaTxtLQs75e5U2z1LUdIdB778LGjSJjXe6VRedJUR9GA9qKpdyTHImIp7 pZntW9wTfQa+fTB44XrtGmjlSKoOpDQdLdRWq9slb3Usw9tspEe84Z+jplIsdYY= =NzqR -----END PGP MESSAGE-----
I have exactly the same problem with the same installation on a different laptop and even with a clean user.
Honestly,.. I have absolutely no idea how this is possible or what the reason for this could be. :-/ There is nothing special with your key, maybe except for the "Authentication" capability on the primary key but that should be no issue. My next step here would be to try to reproduce your setup in a virtual machine. In the meantime you could install GPA which has a "clipboard" which is comparable to Kleopatra's. As a last question: If you generate a test key in Kleopatra with the defaults does it work then?
No even with the default settings I get the exact same behavior. The behavior also isn't really deterministic. If I do pkill kleopatra && kleopatra sometimes everything is fine, sometimes nothing works and sometimes only encryption or only signing work. The problem is that signing E-Mails in Kmail also doesn't work anymore. Thank you, maybe I'll have a look at the source code if it's not too convoluted.
Found the error: In libkleo in the file defaultkeyfilter.cpp at line 160 I get 'jump depends on uninitialized value' which is cause by the missing initialization of the field 'mIsDeVs'.
Just checked phabricator, the fix I was going to propose is already in upstream.
Awesome, thanks for looking into this ! So you have a version that contained my Friday bug (sorry for that) db3fd6ea8c6619da75b9903a90fffc0f9330cf12 But not my Monday fix 98cf4b67ac005832a0ada734ba805e10e51a0319 That is a weird version! Does SUSE Leap just use random git master snapshots? There was no tag or so in between. I've just checked (to be sure that the fix was properly included in the applications 18.12 branch). Anyway. Thanks for your efforts trying to help making Kleopatra better! (btw. other contributions are always welcome ;-) )
*eats his words* git tag --contains db3fd6ea8c6619da75b9903a90fffc0f9330cf12 v18.11.80 v18.11.90 git tag --contains 98cf4b67ac005832a0ada734ba805e10e51a0319 ^ none I think v18.11.90 might have been wrongly tagged. I'll check the dates.
*expletive* Totally my fault. I commited the fix to the Applications/18.12 branch but only pushed my master branch. So locally it showed to be in Applications/18.12 but not in the repo. I've fixed that now.
(In reply to Andre Heinecke from comment #11) > Awesome, thanks for looking into this ! > > So you have a version that contained my Friday bug (sorry for that) > db3fd6ea8c6619da75b9903a90fffc0f9330cf12 > > But not my Monday fix 98cf4b67ac005832a0ada734ba805e10e51a0319 > > That is a weird version! Does SUSE Leap just use random git master snapshots? > > There was no tag or so in between. I've just checked (to be sure that the > fix was properly included in the applications 18.12 branch). > > Anyway. Thanks for your efforts trying to help making Kleopatra better! > (btw. other contributions are always welcome ;-) ) Stock Leap uses the 5.12 LTS. I'm using the additional (semi-offical) KDE repo, I think my KDE applications are at version 18.11.90.
(In reply to Matthieu Gras from comment #14) > Stock Leap uses the 5.12 LTS. I'm using the additional (semi-offical) KDE > repo, I think my KDE applications are at version 18.11.90. We ensured that the final tarball of 18.12.0 won't contain this Bug. It was very close that this would have happened. That is your achievement, so you have saved a lot of users from this Bug. Again, thanks.