Bug 153111

Summary:	SIGSEGV11 signal when leaving Kopete
Product:	[Unmaintained] kopete	Reporter:	Gilles Fay <gilles.fay1>
Component:	ICQ and AIM Plugins	Assignee:	Kopete Developers <kopete-bugs-null>
Status:	RESOLVED UNMAINTAINED
Severity:	crash	CC:	andresbajotierra, jonathan.verner, mariusz.radon, Regnaron, tcech
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Gilles Fay 2007-11-29 10:24:36 UTC

Version:           0.12.5 (using KDE 3.5.8, Debian Package 4:3.5.8.dfsg.1-3 (lenny/sid))
Compiler:          Target: x86_64-linux-gnu
OS:                Linux (x86_64) release 2.6.22-2-amd64

When I leave Kopete running with the ICQ plugin, the progam "crashes", ie it produces a SIGSEGV11 window. Removing the ICQ account solves this issue. The Backtrace is the following:


(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x2ad582213eb0 (LWP 3415)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#5  0x00002ad583e23450 in JabberAccount::~JabberAccount ()
   from /usr/lib/kde3/kopete_jabber.so
#6  0x00002ad57e5d422b in QObject::event () from /usr/lib/libqt-mt.so.3
#7  0x00002ad57e56e3aa in QApplication::internalNotify ()
   from /usr/lib/libqt-mt.so.3
#8  0x00002ad57e570158 in QApplication::notify () from /usr/lib/libqt-mt.so.3
#9  0x00002ad57d30658d in KApplication::notify ()
   from /usr/lib/libkdecore.so.4
#10 0x00002ad57e4ffabe in QApplication::sendEvent ()
   from /usr/lib/libqt-mt.so.3
#11 0x00002ad57e56f3c1 in QApplication::sendPostedEvents ()
   from /usr/lib/libqt-mt.so.3
#12 0x00002ad57e56f4b9 in QApplication::sendPostedEvents ()
   from /usr/lib/libqt-mt.so.3
#13 0x00002ad57e5132d6 in QEventLoop::processEvents ()
   from /usr/lib/libqt-mt.so.3
#14 0x00002ad57e588673 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#15 0x00002ad57e58835f in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#16 0x00002ad57e56fe8c in QApplication::exec () from /usr/lib/libqt-mt.so.3
#17 0x0000000000440ec5 in ?? ()
#18 0x00002ad5819a6b44 in __libc_start_main () from /lib/libc.so.6
#19 0x0000000000431859 in ?? ()
#20 0x00007fff313c2058 in ?? ()
#21 0x0000000000000000 in ?? ()

Comment 1 Oliver Putz 2008-02-01 20:20:37 UTC

The description (except the loaded plugin) and the backtrace look a lot like bug #157086. Maybe dupes?

Comment 2 Matt Rogers 2008-02-07 06:04:05 UTC

*** Bug 157086 has been marked as a duplicate of this bug. ***

Comment 3 Jonathan Verner 2008-03-07 20:29:49 UTC

I am the reporter of Bug 158086 and I've more info:

I have an ICQ transport and a SMS transport for my jabber account. When I removed both of them, kopete stopped crashing for me (both the KDE4 and the KDE3 version). 

Could it be that the destructor (~JabberAccount) for the transports gets called after the destructor for the main jabber account and tries to reference the main JabberAccount object? Just an idea, I didn't really understand the code, nor did I have time to go into it deeper. 

I am willing to do more testing, if you tell me what could help you.

Jonathan Verner

Comment 4 Christophe Marin 2008-07-03 17:03:52 UTC

*** Bug 144197 has been marked as a duplicate of this bug. ***

Comment 5 Nicolas L. 2008-07-22 22:59:31 UTC

moving to ICQ as the bug report tell that this is when using ICQ Plugin

Comment 6 Dario Andres 2008-12-06 02:13:37 UTC

@ Nicolas:  Isn't the crash more related to jabber ? (JabberAccount::~JabberAccount). Maybe it's only related to the ICQ transport for jabber plugin.

Also, bug 167831 seems to be a duplicate of this, but in KDE4

Comment 7 Dario Andres 2009-01-18 00:23:25 UTC

*** Bug 171265 has been marked as a duplicate of this bug. ***

Comment 8 Roman Jarosz 2009-10-31 10:54:10 UTC

We don't have manpower to fix KDE 3 bugs so I'm closing this bug, if you see this crash in KDE 4 please fill new bug report.