Version info: KGpg Version 2.18.0 Using KDE Development Platform 4.14.24 Reproducible: Always Steps to Reproduce: 1. create a group in the gpg.conf with an identifier that is different from the kgpg default (i.e. use a 0x in front of the fingerprint) 2. check that the group is working in gpg (gnupg supports lots of different formats for groups) 3. open kgpg/refresh the keylist 4. look for the group you created and if it is there try to edit it with kgpg Actual Results: If the group was at one point in the past usable by kgpg (for instance because it was initially created by kgpg) and later edited outside of kgpg, then reloading the list will make the group unusable but it will still be visible. If kgpg was launched after the group started using non-standard ids it will not even be visible in the key list. Expected Results: Groups should be visible and editable irregardless of the used id format. GnuPG support lots of ID formats in group definitions i.e.: the email address in UID, full fingerprint of key, long id, short id, long id with leading 0x, short id with leading 0x, … It seems that currently kgpg can only handle the full fingerprint without leading 0x in group definitions. It should support all ID formats in groups that GnuPG supports, for viewing and editing. I use groups extensively for mailing lists and company internal communication. I guess these functions are not used a lot by most users. My workaround for groups is to use a text editor on the gpg.conf and copy paste everything around from gpg in konsole.
Git commit f33f8c759a13da6ab663bd9fd1baef17a238836d by Rolf Eike Beer. Committed on 19/10/2016 at 17:37. Pushed by dakon into branch 'master'. tolerate group member ids to begin with 0x M +5 -2 core/KGpgGroupNode.cpp http://commits.kde.org/kgpg/f33f8c759a13da6ab663bd9fd1baef17a238836d
Thank you for reporting this bug in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!