Bug 221666 - KGpg (kgpg), signal: Segmentation fault [KGpgItemModel::delNode]
Summary: KGpg (kgpg), signal: Segmentation fault [KGpgItemModel::delNode]
Status: RESOLVED WORKSFORME
Alias: None
Product: kgpg
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Rolf Eike Beer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-07 15:41 UTC by stars
Modified: 2011-10-06 22:08 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments
Dependencies.txt (6.26 KB, text/plain)
2010-01-07 15:44 UTC, stars
Details
ProcMaps.txt (50.68 KB, text/plain)
2010-01-07 15:45 UTC, stars
Details
ProcStatus.txt (769 bytes, text/plain)
2010-01-07 15:46 UTC, stars
Details
XsessionErrors.txt (2.48 KB, text/plain)
2010-01-07 15:47 UTC, stars
Details

Note You need to log in before you can comment on or make changes to this bug.
Description stars 2010-01-07 15:41:53 UTC
Version:            (using KDE 4.3.2)
Compiler:          gcc-4.4-base 4.4.1-4ubuntu8 
OS:                Linux
Installed from:    Ubuntu Packages

Hello,

This bug was originally send to launchpad and redirected here because it seem a KDE bug in the program.

I copy the different answers: 
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

Liz Kaye  wrote on 2009-12-08:  	  #2

    * KGpg 2.2.1 - valgrind.log file in a .tar.gz archive (786.2 KiB, application/x-tar)

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.
Liz Kaye wrote on 2009-12-08: 	#3

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

LimCore  wrote 43 minutes ago:  	  #4

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=0x1fc3f00, event=0x7fffd0b7ed70) at ../../kdeui/kernel/kapplication.cpp:302
#28 0x00007fd372353c2c in QCoreApplication::notifyInternal (this=0x18e0c90, receiver=0x1fc3f00, event=0x7fffd0b7ed70) at kernel/qcoreapplication.cpp:610
#29 0x00007fd37237c42a in QCoreApplication::sendEvent (source=0x18f00d0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#30 socketNotifierSourceDispatch (source=0x18f00d0) at kernel/qeventdispatcher_glib.cpp:110
#31 0x00007fd36e480bce in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#32 0x00007fd36e484598 in ?? () from /lib/libglib-2.0.so.0
#33 0x00007fd36e4846c0 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#34 0x00007fd37237c1a6 in QEventDispatcherGlib::processEvents (this=0x18becb0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:327
#35 0x00007fd372f794be in QGuiEventDispatcherGlib::processEvents (this=0x257ddd0, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#36 0x00007fd372352532 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#37 0x00007fd372352904 in QEventLoop::exec (this=0x7fffd0b7efd0, flags=) at kernel/qeventloop.cpp:201
#38 0x00007fd372354ab9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#39 0x000000000047aa84 in main (argc=<value optimized out>, argv=<value optimized out>) at ../../kgpg/main.cpp:57

LimCore  wrote 21 minutes ago:  	  #6

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


Jonathan Thomas  wrote 17 minutes ago:  	  #7

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!


ubuntu bug n°: https://bugs.launchpad.net/ubuntu/+source/kdeutils/+bug/472530
Comment 1 stars 2010-01-07 15:44:07 UTC
Created attachment 39650 [details]
Dependencies.txt
Comment 2 stars 2010-01-07 15:45:31 UTC
Created attachment 39651 [details]
ProcMaps.txt
Comment 3 stars 2010-01-07 15:46:32 UTC
Created attachment 39652 [details]
ProcStatus.txt
Comment 4 stars 2010-01-07 15:47:16 UTC
Created attachment 39654 [details]
XsessionErrors.txt
Comment 5 Rolf Eike Beer 2010-01-07 19:01:05 UTC
I suspect this is a duplicate of #208659 even if the backtrace looks different. Could you please make sure that the sources for this package are at least svn r1049727 and recheck?
Comment 6 stars 2010-01-07 19:09:06 UTC
well actually it's the kubuntu karmic 9.10 default kgpg ( 4:4.3.40ubuntu1~karmic1)

I haven't the svn. You suggest to uninstall the official and take the svn ?

Will i lost all my actually config ? 

I will try on  a VM
Comment 7 Rolf Eike Beer 2010-01-07 20:24:30 UTC
Your configuration will not be touched by package upgrade. That package name suggests it's rather recent, if it identifies itself as KDE 4.3.4 all patches from 4.3 branch are already included and I need to search another bug :/
Comment 8 Rolf Eike Beer 2011-02-22 15:37:20 UTC
Does this still happen with a more recent version?
Comment 9 Rolf Eike Beer 2011-10-06 22:08:47 UTC
No response for more than a year, closing.