KGpg (kgpg), signal: Segmentation fault

Bug #472530 reported by starslights
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
KDE Utilities
Invalid
High
kdeutils (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: kdeutils

Hello,

i run Kubuntu Karmic 9.10 x86 64 and since the final release, kgpg make some crash with a seg fault.

Application: KGpg (kgpg), signal: Segmentation fault
[KCrash Handler]
#5 0x000000000043c623 in _start ()

i have added dbg but it refuse to send the rapport it's own.

Ces informations de plantage ne sont pas suffisantes, voulez-vous essayer de les améliorer ? Vous devrez alors installer quelques paquetages de débogage.

I have added it but no diference

best regards

ProblemType: Bug
Architecture: amd64
Date: Tue Nov 3 12:20:18 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/kgpg
InstallationMedia: Kubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
NonfreeKernelModules: nvidia
Package: kgpg 4:4.3.2-0ubuntu1
ProcEnviron:
 LANG=fr_CH.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: kdeutils
Uname: Linux 2.6.31-14-generic x86_64

Revision history for this message
starslights (starslights) wrote :
Revision history for this message
Liz Kaye (wait4the1) wrote :

Hi,

I had kgpg end after a segmentation fault as well. It happened and then when I restarted the program, it said that gnupg was running an agent that was interfering with the function of kgpg. I edited the ~/.gnupg/gpg.conf file and commented out the line that said "use-agent" and then it worked better (and had less exits because of segmentation faults).

Because I was still having problems, and the bug report was said to not be useful, I downloaded valgrind and followed the how-to located here: https://wiki.kubuntu.org/Valgrind

I put the valgrind.log file in a .tar.gz archive as recommended in the article and I attached it to this post. I'm not knowledgeable enough to be able to judge for myself whether the log file will be useful or not but I hope that it is.

Revision history for this message
Liz Kaye (wait4the1) wrote :

Sorry, I forgot to mention... I am running Xubuntu Karmic Koala 9.10. Kernel 2.6.31-16-generic with an Intel(R) Core(TM)2 Duo CPU T8100 @ 2.10GHz. Unlike the previous user who had issues with a segmentation fault, mine was not on an x64 processor.

~Liz

Revision history for this message
LimCore (limcore) wrote :
Download full text (4.5 KiB)

Example of crash:

#5 0x00000000006e6ba0 in QListData::shared_null ()
#6 0x0000000000438048 in KGpgItemModel::delNode (this=0x18e0770, node=0x257ddd0) at ../../kgpg/model/kgpgitemmodel.cpp:221
#7 0x000000000045fe87 in KeysManager::slotDelKeyDone (this=0x1ac2be0, res=<value optimized out>) at ../../kgpg/keysmanager.cpp:2381
#8 0x0000000000477c7e in KeysManager::qt_metacall (this=0x1ac2be0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffd0b7e3a0) at ./keysmanager.moc:333
#9 0x00007fd372368ddc in QMetaObject::activate (sender=0x1e66940, from_signal_index=<value optimized out>, to_signal_index=<value optimized out>, argv=0x1) at kernel/qobject.cpp:3113
#10 0x000000000044341c in KGpgTransaction::done (this=0x257ddd0, _t1=0) at ./kgpgtransaction.moc:86
#11 0x00000000004443a5 in KGpgTransaction::qt_metacall (this=0x1e66940, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffd0b7e4e0) at ./kgpgtransaction.moc:74
#12 0x00007fd372368ddc in QMetaObject::activate (sender=0x25aa510, from_signal_index=<value optimized out>, to_signal_index=<value optimized out>, argv=0x1) at kernel/qobject.cpp:3113
#13 0x000000000048fba0 in GPGProc::processExited (this=0x257ddd0, _t1=0x25aa510) at ./gpgproc.moc:95
#14 0x000000000048fc9c in GPGProc::qt_metacall (this=0x25aa510, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffd0b7e620) at ./gpgproc.moc:75
#15 0x00007fd372368ddc in QMetaObject::activate (sender=0x25aa510, from_signal_index=<value optimized out>, to_signal_index=<value optimized out>, argv=0x1) at kernel/qobject.cpp:3113
#16 0x00007fd3722f563f in QProcess::finished (this=0x257ddd0, _t1=0, _t2=QProcess::NormalExit) at .moc/release-shared/moc_qprocess.cpp:136
#17 0x00007fd3722faba7 in QProcessPrivate::_q_processDied (this=0x259d2e0) at io/qprocess.cpp:718
#18 0x00007fd3722fac69 in QProcess::qt_metacall (this=0x25aa510, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffd0b7e830) at .moc/release-shared/moc_qprocess.cpp:109
#19 0x00007fd37299fc88 in KProcess::qt_metacall (this=0x257ddd0, _c=3501711696, _id=1919178208, _a=0x1) at ./kprocess.moc:63
#20 0x0000000000490938 in KLineBufferedProcess::qt_metacall (this=0x257ddd0, _c=3501711696, _id=1919178208, _a=0x1) at ./klinebufferedprocess.moc:68
#21 0x000000000048fc30 in GPGProc::qt_metacall (this=0x257ddd0, _c=3501711696, _id=1919178208, _a=0x1) at ./gpgproc.moc:68
#22 0x00007fd372368ddc in QMetaObject::activate (sender=0x1fc3f00, from_signal_index=<value optimized out>, to_signal_index=<value optimized out>, argv=0x1) at kernel/qobject.cpp:3113
#23 0x00007fd37239ee9e in QSocketNotifier::activated (this=0x257ddd0, _t1=26) at .moc/release-shared/moc_qsocketnotifier.cpp:83
#24 0x00007fd37236d773 in QSocketNotifier::event (this=0x1fc3f00, e=0x7fffd0b7ed70) at kernel/qsocketnotifier.cpp:316
#25 0x00007fd372ee4efc in QApplicationPrivate::notify_helper (this=0x18ea640, receiver=0x1fc3f00, e=0x7fffd0b7ed70) at kernel/qapplication.cpp:4056
#26 0x00007fd372eec1ce in QApplication::notify (this=0x18e0c90, receiver=0x1fc3f00, e=0x7fffd0b7ed70) at kernel/qapplication.cpp:4021
#27 0x00007fd373b1bab6 in KApplication::notify (this=0x18e0c90, receiver...

Read more...

Revision history for this message
LimCore (limcore) wrote :

Several people, also other bug reports (duplicates)

Changed in kdeutils (Ubuntu):
status: New → Confirmed
Revision history for this message
LimCore (limcore) wrote :

I trigerred the crashes mostly with:
Adding / deleting key with import-key (it was an RSA type key)
and/or refreshing the window

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Hi,

Thanks for reporting this bug! Your bug seems to be a problem with the KDE program itself, and not with our KDE packages. While we appreciate your issue, it would be better if it was tracked at https://bugs.kde.org, so that the KDE developers can deal with this speedily and have direct communication with you as the reporter for more effective debugging.

Thanks!

Changed in kdeutils (Ubuntu):
status: Confirmed → Invalid
Revision history for this message
starslights (starslights) wrote :

Hello Jonathan,

I have open a bug by KDE and post link here for others users who want add infos:

https://bugs.kde.org/show_bug.cgi?id=221666

Best Regrads

Revision history for this message
LimCore (limcore) wrote :
Download full text (6.2 KiB)

This happens all the time.

I don't see why we close bug here?

More info: it seems to crash on boxes that have several keys etc, not so much on clean installs that so far do not have opnepgp keys or just 1 or 2.

Another crash:
Application: KGpg (kgpg), signal: Segmentation fault
The current source language is "auto; currently c".
[Current thread is 1 (Thread 0x7f8befe57750 (LWP 28609))]

Thread 2 (Thread 0x7f8bd9f6e910 (LWP 28610)):
#0 0x00007f8becbac3c2 in select () from /lib/libc.so.6
#1 0x00007f8bed276f31 in QProcessManager::run (this=0x2377270) at io/qprocess_unix.cpp:296
#2 0x00007f8bed1b1445 in QThreadPrivate::start (arg=0x2377270) at thread/qthread_unix.cpp:188
#3 0x00007f8be9173a04 in start_thread (arg=<value optimized out>) at pthread_create.c:300
#4 0x00007f8becbb37bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#5 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f8befe57750 (LWP 28609)):
[KCrash Handler]
#5 0x00007f8bed29d49c in QMetaObject::indexOfSignal (this=0x6e6ba0, signal=0x4be8ca "newKeyNode(KGpgKeyNode *)") at kernel/qmetaobject.cpp:581
#6 0x00007f8bed2a8a5b in QObject::connect (sender=0x3026b80, signal=0x4be8c9 "2newKeyNode(KGpgKeyNode *)", receiver=0x30841e0, method=0x4be896 "1keyUpdated(KGpgKeyNode *)", type=Qt::AutoConnection)
    at kernel/qobject.cpp:2468
#7 0x000000000043c7c9 in KGpgRefNode::keyUpdated (this=0x30841e0, nkey=<value optimized out>) at ../../kgpg/model/kgpgitemnode.cpp:921
#8 0x0000000000423780 in KGpgRefNode::qt_metacall (this=0x30841e0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff9c9a5340) at moc_kgpgitemnode.cpp:229
#9 0x00007f8bed2acddc in QMetaObject::activate (sender=0x3029b80, from_signal_index=<value optimized out>, to_signal_index=<value optimized out>, argv=0x7f8bed32c4ff) at kernel/qobject.cpp:3113
#10 0x00000000004230ad in KGpgKeyNode::updated (this=0x6e6ba0, _t1=0x0) at moc_kgpgitemnode.cpp:121
#11 0x000000000043aa82 in ~KGpgKeyNode (this=0x6e6ba0, __in_chrg=<value optimized out>) at ../../kgpg/model/kgpgitemnode.cpp:399
#12 0x000000000043814e in KGpgItemModel::refreshKeyIds (this=0x251c350, ids=...) at ../../kgpg/model/kgpgitemmodel.cpp:360
#13 0x000000000045f560 in KeysManager::refreshkey (this=0x25b9b00) at ../../kgpg/keysmanager.cpp:2467
#14 0x000000000047785e in KeysManager::qt_metacall (this=0x25b9b00, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x7fff9c9a5570) at ./keysmanager.moc:239
#15 0x00007f8bed2acddc in QMetaObject::activate (sender=0x25f0b90, from_signal_index=<value optimized out>, to_signal_index=<value optimized out>, argv=0x7f8bed32c4ff) at kernel/qobject.cpp:3113
#16 0x00007f8bede230a7 in QAction::triggered (this=0x6e6ba0, _t1=false) at .moc/release-shared/moc_qaction.cpp:236
#17 0x00007f8bede244ef in QAction::activate (this=0x25f0b90, event=<value optimized out>) at kernel/qaction.cpp:1160
#18 0x00007f8bede26fa7 in QAction::event (this=0x6e6ba0, e=<value optimized out>) at kernel/qaction.cpp:1079
#19 0x00007f8bee98e17d in KAction::event (this=0x6e6ba0, event=0x7fff9c9a5a70) at ../../kdeui/actions/kaction.cpp:88
#20 0x00007f8bede28efc in QApplicationPrivate::notify_helper (this=0x...

Read more...

Changed in kdeutils (Ubuntu):
status: Invalid → Confirmed
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Current Kubuntu bug policy is to only track packaging bugs at Launchpad. Tracking a bug that's already being tracked at KDE is pretty much useless, as the fix will always be incorporated in the next release.

Changed in kdeutils (Ubuntu):
status: Confirmed → Invalid
Changed in kdeutils:
status: Unknown → New
Changed in kdeutils:
importance: Unknown → Medium
Changed in kdeutils:
importance: Medium → High
Changed in kdeutils:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.