Summary: | Kgpg crashing on getting properties of empty (NULL) keys | ||
---|---|---|---|
Product: | [Applications] kgpg | Reporter: | RJVB <rjvbertin> |
Component: | general | Assignee: | Rolf Eike Beer <kde> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | rjvbertin |
Priority: | NOR | Keywords: | drkonqi |
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | macOS | ||
Latest Commit: | https://commits.kde.org/kgpg/432f03e8f3eae5d7d0e3c70c5324006a2f2a381a | Version Fixed In: | 17.12.3 |
Attachments: |
after requesting the key properties of the selected item
New crash information added by DrKonqi |
Description
RJVB
2017-11-28 15:54:51 UTC
Created attachment 109097 [details]
after requesting the key properties of the selected item
Can you share the key? If you don't want to put it somewhere in public you can send it encrypted to me. I would if I knew what key this was. When I open the group edit dialog window the "keys in the group" list contains a large number which looks like it could well be my entire key collection (my own and imported keys). I tried moving out a single key from one of those weird groups, and that emptied the entire "keys in the group" list. After that the bogus entry was gone from the group representation in the manager window too. Belay that: the bogus entry was gone but comes back as soon as I restart kgpg. I don't see the groups in other gnupg utilities, are they a kgpg feature? Where are their definitions stored? They are stored in the GnuPG configuration file. Indeed, somehow I missed that. So it looks like these bogus entries happen for me in all empty groups. I can recreate the issue as follows: - in kgpg, create a group (foo1) from one or more keys - quit kgpg, open gpg.conf in a text editor, create a new group by copying the line with the new group and changing the groupname to foo2 - (launch kgpg to verify foo2 exists with the expected content) - in the text editor, remove all keys from foo2 leaving a line with just "foo2 =" - launch kgpg; I now see a bogus entry in foo2 Created attachment 109179 [details]
New crash information added by DrKonqi
kgpg (17.08.3) using Qt 5.8.0
The issue can be reproduced on Linux following the instructions provided in my previous comments.
Note that this will also happen with groups that are emptied via the key manager. They will appear empty immediately after doing that, but will contain the bogus key after restarting the application.
-- Backtrace (Reduced):
#6 0x00000000004eaaec in KGpgChangeKey::KGpgChangeKey (this=0x2bd4880, node=0x0, widget=0x2bd98d0) at /opt/local/var/lnxports/build/_opt_local_site-ports_kf5_kf5-kgpg/kf5-kgpg/work/kgpg-17.08.3/kgpgchangekey.cpp:25
#7 0x00000000004da428 in KgpgKeyInfo::KgpgKeyInfo (this=0x2bd98d0, node=0x0, model=0x26614e0, parent=<optimized out>) at /opt/local/var/lnxports/build/_opt_local_site-ports_kf5_kf5-kgpg/kf5-kgpg/work/kgpg-17.08.3/keyinfodialog.cpp:101
#8 0x00000000004972ff in KeysManager::keyproperties (this=0x2635a00) at /opt/local/var/lnxports/build/_opt_local_site-ports_kf5_kf5-kgpg/kf5-kgpg/work/kgpg-17.08.3/keysmanager.cpp:1683
#9 0x00007f791936332e in call (a=0x7ffcff2739e0, r=0x2635a00, this=<optimized out>) at /opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.8.0/qtbase/include/QtCore/../../src/corelib/kernel/qobject_impl.h:101
[...]
#12 0x00007f791a59d902 in QAction::triggered (this=this@entry=0x28d0020, _t1=<optimized out>) at .moc/moc_qaction.cpp:371
Git commit 432f03e8f3eae5d7d0e3c70c5324006a2f2a381a by Rolf Eike Beer. Committed on 09/02/2018 at 18:01. Pushed by dakon into branch 'Applications/17.12'. ignore empty entries in key groups FIXED-IN:17.12.3 M +1 -1 core/KGpgRootNode.cpp https://commits.kde.org/kgpg/432f03e8f3eae5d7d0e3c70c5324006a2f2a381a |