kgpg crashes when refreshing keys from the key server or retrieving keys

[Jeremy Wilkins]

Binary package hint: kdeutils

When I open kgpg and select a key using the right-click menu to refresh from the key server, it doesn't matter which key I try kgpg hangs for a couple seconds and crashes, however it appears the next time I open kgpg that the operation I was performing still happened. The same happens when I retrieve a missing key from the key servers. I am not sure if it a certain key server that is causing the trouble or kgpg itself. The problem is reproducible every time.

ProblemType: Crash
Architecture: amd64
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/kgpg
Package: kgpg 4:4.2.1-0ubuntu1
ProcCmdline: /usr/bin/kgpg
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=
Signal: 11
SourcePackage: kdeutils
Stacktrace: #0 0x000000000043b7f3 in _start ()
StacktraceTop: _start ()
Title: kgpg crashed with SIGSEGV in _start()
Uname: Linux 2.6.28-11-generic x86_64
UserGroups: adm admin audio backup bin cdrom dialout dip disk floppy fuse games haldaemon irc klog kmem kvm lp lpadmin mail netdev operator plugdev powerdev pulse pulse-access pulse-rt root sambashare sasl scanner ssh ssl-cert staff sudo sys syslog tape tty uml-net video voice www-data

[Apport retracing service (apport)]

StacktraceTop:KGpgRefNode::keyUpdated (this=0x1c59d40,
KGpgRefNode::qt_metacall (this=0x1c59d40,
QMetaObject::activate ()
KGpgRootNode::newKeyNode (this=0x1c59d40,
KGpgRootNode::addKeys (this=0x17b36e0,

[Jonathan Thomas (echidnaman)]

Is this still an issue for you in Kubuntu 9.04 final?
If so, I can forward this report on to the KDE developers for you.

[Jonathan Thomas (echidnaman)]

Nevermind, I found a corresponding upstream report. I just didn't look hard enough the first time. ;-)

[Jeremy Wilkins (wjeremy)]

Most definitely it is not fixed yet. Now it crashes after the second refresh however and the first one works.

[Michael Evans (mjevans1983)]

The upstream bug is unconfirmed, while I can confirm that it does affect me as well. Unfortunately it looks, from a glance, that upstream needs a debug symbols version of kgpg run to collect additional information, but ubuntu provides only stripped binaries.

Are there packages containing split debug symbols that could be installed to help track this down?

[Jeremy Wilkins (wjeremy)]

I'm not sure if this bug remains in a fully updated Jaunty install anymore, but it no longer seems to exist in Karmic. I have not been able to crash kgpg for some time now. MichaelEvans, ave you tried updating to kde 4.2.2 or newer to see if the problem persists?

[Jeremy Wilkins (wjeremy)]

If the problem is fixed with the latest updates, this bug can be closed as fixed I think.

[Michael Evans (mjevans1983)]

-Fully- updated xubuntu jaunty (9.04) install (amd64, 2gb ram, Turion64 (AMD dual core)).

KGpg
Version 2.1.0
Using KDE 4.2.2 (KDE 4.2.2)

gpg (GnuPG) 1.4.9

While refreshing a selection of keys from the keyserver (after it updates the keyring successfully)

Application: KGpg (kgpg), signal SIGSEGV
0x00007f7fee940d21 in nanosleep () from /lib/libc.so.6
[Current thread is 0 (LWP 19133)]

Thread 2 (Thread 0x7f7fe5ad9950 (LWP 19134)):
#0 0x00007f7fee977742 in select () from /lib/libc.so.6
#1 0x00007f7fef4e8f06 in ?? () from /usr/lib/libQtCore.so.4
#2 0x00007f7fef421952 in ?? () from /usr/lib/libQtCore.so.4
#3 0x00007f7fec0de3ba in start_thread () from /lib/libpthread.so.0
#4 0x00007f7fee97efcd in clone () from /lib/libc.so.6
#5 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f7ff288c750 (LWP 19133)):
[KCrash Handler]
#5 0x0000000000436a17 in _start ()

[Jonathan Thomas (echidnaman)]

Can anybody still receiving this bug provide the info requested in comment 8 of http://bugs.kde.org/show_bug.cgi?id=180775 ?

[Jonathan Thomas (echidnaman)]

We are closing this bug report because it lacks the information we need to investigate the problem, as requested in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the "Status" column, and change the status back to "New". Thanks again!

[Jeremy Wilkins (wjeremy)]

This bug has been fixed in latest version. I no longer receive crashes. You can close.

[Jeremy Wilkins (wjeremy)]

Michael: The current version is 2.2.1... Try that version.