Bug 386506

Summary: Can't get a Key
Product: [Applications] kleopatra Reporter: marcin.darecki
Component: generalAssignee: Andre Heinecke <aheinecke>
Status: RESOLVED FIXED    
Severity: normal CC: alejandro.espinoza, kdepim-bugs, mutz
Priority: NOR    
Version: 3.0.0   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed In:
Attachments: The error that I see

Description marcin.darecki 2017-11-03 20:11:38 UTC
Created attachment 108698 [details]
The error that I see

C:\Program Files\GnuPG\bin\gpgsm.exe to: gpgsm: key '' not found: Niepoprawny identyfikator uľytkownika (Incorrect User ID)
Comment 1 marcin.darecki 2017-11-03 20:13:15 UTC
Could someone help with that?
Comment 2 Andre Heinecke 2017-11-13 07:24:02 UTC
From the error it appears that GPGSM can't handle the UserID you are trying to specify or it might be an error with Kleopatra <> GPGSM Communication where the encoding might be mixed up.

Can you please try a simpler UserID (The fields you are specifying with Name Organisation etc.) And post here a copy of the "Review Certificate Parameters" page?

Thanks
Comment 3 Andre Heinecke 2017-11-15 06:59:19 UTC
I'll look into it later. This was reported by another user too. From your screenshot it also looks like it was a PGP key and still the error says GPGSM so something is definitely fishy.
Comment 4 Andre Heinecke 2017-11-15 06:59:30 UTC
*** Bug 386908 has been marked as a duplicate of this bug. ***
Comment 5 Andre Heinecke 2017-11-15 08:35:38 UTC
Git commit 705548a4de5c7bd9c4e26e2881ee892798253767 by Andre Heinecke.
Committed on 15/11/2017 at 08:30.
Pushed by aheinecke into branch 'Applications/17.12'.

Lookup and insert newly generated keys in cache

If the key is not in the keycache or keycache update takes
a while we might not find the key in the ::key() method. This
leads to bugs.

M  +9    -0    src/newcertificatewizard/newcertificatewizard.cpp

https://commits.kde.org/kleopatra/705548a4de5c7bd9c4e26e2881ee892798253767
Comment 6 Andre Heinecke 2017-11-15 08:36:58 UTC
I could reproduce it. The internal keycache was not always updated correctly and the internal reference to the newly created key did not exist.

Will be fixed in the next Gpg4win release (3.0.1) that should be available soon.