| Summary: | Crash when setting default key after generating new key [KGpgItemModel::setDefaultKey] | ||
|---|---|---|---|
| Product: | [Applications] kgpg | Reporter: | Kevin Clevenger <kevin.clevenger> |
| Component: | general | Assignee: | Rolf Eike Beer <kde> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | dante9281, darth.surtur, kevin.clevenger, stabbmesiter, tmoschou |
| Priority: | NOR | ||
| Version: | 2.7.2 | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | http://commits.kde.org/kgpg/2d252cf08c51866a6acebe705db11b29941691bf | Version Fixed In: | 4.8.5 |
| Sentry Crash Report: | |||
| Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi New crash information added by DrKonqi |
||
|
Description
Kevin Clevenger
2012-04-20 04:22:19 UTC
*** Bug 299634 has been marked as a duplicate of this bug. *** It seems that after the crash, I can no longer open up Kgpg. I am not sure if it is related or not. That could be related to bug 298773. You could look if there is a "default-key" line in ~/.gnupg/gpg.conf and if commenting out that line makes things better. That line is already commented out. When run from a terminal, I get $ kgpg QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. $ It seems to be related to 298773. When I run kgpg, the process is running, but I get nothing to show up, and it sits there sleeping. Those lines are totally unrelated (and from all that I know harmless). Are you sure KGpg isn't just hiding in the systray? I can kill kgpg and then run it again, and I still get those same messages each time, and then the process just sleeps. I never get anything to show up after that crash. Okay I feel dumb now. kgpg -k opened up the key management window I wanted to get to. However, it still won't open from the application launcher. At least I can get back to it now. Actually, it seems that it did create the RSA 4096/4096 key I asked for, but it also made an RSA 4096/1024 key. I don't recall trying to make that key. Created attachment 70970 [details]
New crash information added by DrKonqi
kgpg (2.7.2) on KDE Platform 4.8.3 (4.8.3) using Qt 4.8.1
- What I was doing when the application crashed:
Generated an RSA/RSA 4096 key on a Fedora 16 desktop (original was F17)
-- Backtrace (Reduced):
#6 KGpgItemModel::setDefaultKey (this=0x180ace0, def=0x0) at /usr/src/debug/kgpg-4.8.2/model/kgpgitemmodel.cpp:346
#7 0x0000000000469fcf in KeysManager::slotGenerateKeyDone (this=0x180a290, job=<optimized out>) at /usr/src/debug/kgpg-4.8.2/keysmanager.cpp:611
#8 0x00000000004722b6 in qt_static_metacall (_a=<optimized out>, _id=<optimized out>, _o=0x180a290, _c=<optimized out>) at /usr/src/debug/kgpg-4.8.2/x86_64-redhat-linux-gnu/keysmanager.moc:232
#9 KeysManager::qt_static_metacall (_o=0x180a290, _c=<optimized out>, _id=<optimized out>, _a=<optimized out>) at /usr/src/debug/kgpg-4.8.2/x86_64-redhat-linux-gnu/keysmanager.moc:199
[...]
#11 0x00000035e21424a2 in KJob::result(KJob*) () from /usr/lib64/libkdecore.so.5
Created attachment 71390 [details]
New crash information added by DrKonqi
kgpg (2.7.2) on KDE Platform 4.8.3 (4.8.3) using Qt 4.8.1
- What I was doing when the application crashed:
I was generating new key (first one). Tried to save it in my documents directory, for future revoking etc. then when i tried to save, first he said that cannot open file with the given name, after that i have made file with a name, actually text file, then i had it chosen and gave SAVE. Then the app crashed.
Notice. All above i made as root user from root account.
- Custom settings of the application:
Custom directory for saving the key, custom file and file name.
-- Backtrace (Reduced):
#7 KGpgItemModel::setDefaultKey (this=0x85f1988, def=0x0) at /usr/src/debug/kgpg-4.8.3/model/kgpgitemmodel.cpp:346
#8 0x080b120f in KeysManager::slotGenerateKeyDone (this=0x85caa88, job=0x8e707b8) at /usr/src/debug/kgpg-4.8.3/keysmanager.cpp:610
#9 0x080ba0a3 in qt_static_metacall (_a=0xbfb3bd58, _id=24, _o=0x85caa88, _c=<optimized out>) at /usr/src/debug/kgpg-4.8.3/i686-redhat-linux-gnu/keysmanager.moc:231
#10 KeysManager::qt_static_metacall (_o=0x85caa88, _c=QMetaObject::InvokeMetaMethod, _id=24, _a=0xbfb3bd58) at /usr/src/debug/kgpg-4.8.3/i686-redhat-linux-gnu/keysmanager.moc:198
[...]
#12 0x436ca4c6 in KJob::result (this=0x8e707b8, _t1=0x8e707b8) at /usr/src/debug/kdelibs-4.8.3/i686-redhat-linux-gnu/kdecore/kjob.moc:207
Created attachment 71528 [details]
New crash information added by DrKonqi
kgpg (2.7.2) on KDE Platform 4.8.3 (4.8.3) using Qt 4.8.1
- What I was doing when the application crashed:
Created new key pair.
Confirmation dialogue appeared.
"You have successfully created the following key: ..."
Set as Default Key
Selected OK/Finish, then KGpg crashed
-- Backtrace (Reduced):
#6 KGpgItemModel::setDefaultKey (this=0x2755860, def=0x0) at /usr/src/debug/kgpg-4.8.3/model/kgpgitemmodel.cpp:346
#7 0x0000000000469f0f in KeysManager::slotGenerateKeyDone (this=0x2753630, job=<optimized out>) at /usr/src/debug/kgpg-4.8.3/keysmanager.cpp:610
#8 0x0000000000472576 in qt_static_metacall (_a=<optimized out>, _id=<optimized out>, _o=0x2753630, _c=<optimized out>) at /usr/src/debug/kgpg-4.8.3/x86_64-redhat-linux-gnu/keysmanager.moc:231
#9 KeysManager::qt_static_metacall (_o=0x2753630, _c=<optimized out>, _id=<optimized out>, _a=<optimized out>) at /usr/src/debug/kgpg-4.8.3/x86_64-redhat-linux-gnu/keysmanager.moc:198
[...]
#11 0x00000033c6b424a2 in KJob::result (this=<optimized out>, _t1=0x28c03a0) at /usr/src/debug/kdelibs-4.8.3/x86_64-redhat-linux-gnu/kdecore/kjob.moc:207
Seems to hit more people, so I take this as confirmed. Although I still can't see what's going wrong there. Git commit a3b0cb755ff08721a3b9e2c25d4aaf655fb40804 by Rolf Eike Beer. Committed on 06/06/2012 at 17:40. Pushed by dakon into branch 'KDE/4.8'. fix NULL-deref when new setting default key Thanks to John Tapsell for spotting the line I have been looking at for weeks without seeing the bug. CCMAIL:johnflux@gmail.com M +6 -2 model/kgpgitemmodel.cpp http://commits.kde.org/kgpg/a3b0cb755ff08721a3b9e2c25d4aaf655fb40804 Git commit 2d252cf08c51866a6acebe705db11b29941691bf by Rolf Eike Beer. Committed on 11/06/2012 at 19:29. Pushed by dakon into branch 'KDE/4.8'. fix key comparison returning wrong values This fixes a regression introduced in 4.8.2 with commit 2a100ae8d203107d17e438f67f65d26a4949cccc when trying to fix bug 292405. Related: bug 301618, bug 292405 M +7 -5 core/KGpgKeyNode.cpp http://commits.kde.org/kgpg/2d252cf08c51866a6acebe705db11b29941691bf *** Bug 303077 has been marked as a duplicate of this bug. *** |