Bugzilla – Bug 147400
KGpg works incorrectly with non-latin charsets
Last modified: 2008-06-16 11:06:24 UTC
Greetings! Seems that KGpg is unable to handle unicode correctly. My desktop is localised for russian, and when I try to modify my PGP key with KGpg after I enter Visible Name and Comment in relevant fields in russian, KGpg shows them as question sighs (?????? ??????). Please observe the screenshots attached.
Created attachment 66093 [details] First tried to add UserID with KGpg Shot of KGpg after I tried to add yet another User ID to my exsisting key - quiestion signs seen instead of russian letters.
Created attachment 66094 [details] Next tried to add another UserID again with russian characters Here is KGpg's dialog for adding another User ID to the exsisting key - once again, trying to add another ID with non-latin symbols.
Created attachment 66095 [details] After second try Here how it looks after my second try
Created attachment 66097 [details] Procedure of adding UserID from console This is successfull attempt to add UserID with UTF-8 from console. This was called with Alt+Return keystroke (or 'Edit from console' right-click menu item) from within KGpg.
Created attachment 66098 [details] How UserID added from console looks like in KGpg And finally this is how successfully added UserID from console looks like in KGpg.
Created attachment 66099 [details] Wrong charset in message
Fixed in KDE SVN by rev. 547761, will put in autobuild on Monday
Probably no need to, it will appear in next SL version anyway
The problem still persists in openSUSE 10.2 with latest updates.
Created attachment 125584 [details] Kgpg and console keys editing Kgpg screenshot with "Edit key via konsole" konsole opened. 1 - wrong escape sequences instead of unicode symbols 2 - console key editing blocks Kgpg
Hmm, I believe I fixed it some time ago, don't know what happened that it appeared again... :(
new maintainer
Leaving SUSE - reassigning to Vladimir. I'm suspicious about gpg not using Unicode under some circumstances and confusing pinentry.
Eh pinentry - I meant Kgpg. As for now, it seems to me, this is related to bug #305752.
The bug is caused by wrong parsing of 'gpg --list-keys --with-colons' output (in kgpg). Closing with wontfix, because - already fixed in kgpg-4.x - it's a minor issue not affecting functionality - backporting the fix from KDE4 would not be trivial (because of major changes in underlying libraries)