Bug 144197

Summary:	Crash on exit when using Gadu-gadu transport
Product:	[Unmaintained] kopete	Reporter:	Mariusz Radon <mariusz.radon>
Component:	Jabber Plugin	Assignee:	Kopete Developers <kopete-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	crash	CC:	mariusz.radon, martin.nowack
Priority:	NOR
Version:	0.12.3
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Mariusz Radon 2007-04-14 00:33:30 UTC

Version:           0.12.3 (using KDE 3.5.5 "release 45.2" , openSUSE 10.2)
Compiler:          Target: i586-suse-linux
OS:                Linux (i686) release 2.6.18.8-0.1-default

Kopete crashes (receive SIGSEGV signal) each time on exit; it does not matter if accounts are online or offline. 

On jabber server I have gadu-gadu transport service activated (this was previously done using another client, psi). This transport service has been recognized by kopete and is visible as a separate account. The crash seem to be related to the "transport account", because the whole problem disappears if only I remove this account from kopete (which probably means unregistering from gadu-gadu transport service).

Bugtrace below:
===============
(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)
[Thread debugging using libthread_db enabled]
[New Thread -1239636272 (LWP 10136)]
(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)
(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]
#9  0x0811ad8e in ?? ()
#10 0xb5a8ac55 in JabberAccount::~JabberAccount ()
   from /opt/kde3/lib/kde3/kopete_jabber.so
#11 0xb6f8cd98 in QObject::event () from /usr/lib/qt3/lib/libqt-mt.so.3
#12 0xb6f2e647 in QApplication::internalNotify ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#13 0xb6f2f4f9 in QApplication::notify () from /usr/lib/qt3/lib/libqt-mt.so.3
#14 0xb76171f2 in KApplication::notify () from /opt/kde3/lib/libkdecore.so.4
#15 0xb6f2fed0 in QApplication::sendPostedEvents ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#16 0xb6f30066 in QApplication::sendPostedEvents ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#17 0xb6edd4f2 in QEventLoop::processEvents ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#18 0xb6f450e0 in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3
#19 0xb6f44f76 in QEventLoop::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#20 0xb6f2e00f in QApplication::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#21 0x0807dfdb in QWidget::setUpdatesEnabled ()
#22 0xbfc7c09c in ?? ()
#23 0xbfc7c1d0 in ?? ()
#24 0xbfc7c1c8 in ?? ()
#25 0x00000000 in ?? ()

Comment 1 Tommi Tervo 2007-04-24 17:08:14 UTC

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

Comment 2 Martin 2007-04-24 18:20:15 UTC

confirmation from me - happens with kopete 0.12.4 (kde 3.5.6) too.

Comment 3 Bram Schoenmakers 2007-08-13 21:38:48 UTC

Please refer to http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports for a more detailed backtrace.

Comment 4 Ivo Emanuel Gonçalves 2007-08-30 13:45:15 UTC

I have the same problem.  Here's my backtrace:

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1241831024 (LWP 20344)]
[KCrash handler]
#6  0xb2d3c94f in ?? () from /usr/lib/libGL.so.1
#7  0x0811e768 in ?? ()
#8  0xb2d72660 in ?? () from /usr/lib/libGL.so.1
#9  0x0811e768 in ?? ()
#10 0xb2d3b1a6 in ?? () from /usr/lib/libGL.so.1
#11 0x0811e768 in ?? ()
#12 0x0811e768 in ?? ()
#13 0xb636fb2c in ?? () from /usr/lib/libX11.so.6
#14 0xb2ef90e8 in ?? ()
#15 0xb629aebd in XCloseDisplay () from /usr/lib/libX11.so.6
#16 0xb675eb74 in qt_cleanup () from /usr/lib/libqt-mt.so.3
#17 0xb67d9b76 in QApplication::~QApplication () from /usr/lib/libqt-mt.so.3
#18 0xb6f60529 in ~KApplication (this=0xbf9e5a04)
    at /build/buildd/kdelibs-3.5.6/./kdecore/kapplication.cpp:1652
#19 0xb6f606ff in ~KUniqueApplication (this=0xbf9e5a04)
    at /build/buildd/kdelibs-3.5.6/./kdecore/kuniqueapplication.cpp:351
#20 0x0807fef4 in ?? ()
#21 0xbf9e5a04 in ?? ()
#22 0xbf9e59fc in ?? ()
#23 0xbf9e59f4 in ?? ()
#24 0x00000000 in ?? ()

Also, I can report that this happened before managing a Jabber account.  And I'm using KDE 3.5.6, Ubuntu packages, Linux x86, GCC 4.

Comment 5 Will Stephenson 2007-11-14 16:00:05 UTC

No useful backtrace (#4 is something else)

Comment 6 Michał S. 2008-02-21 01:22:32 UTC

I confirm - the same for me (Kopete 0.12.7, KDE 3.5.7-3.5.9, openSuse 10.1). It happens with Jabber account with Gadu-Gadu transport. Crash happen every time on exit. My backtrace:
Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1239406288 (LWP 19077)]
[KCrash handler]
#6  0x0811ceee in ?? ()
#7  0xb582d7d2 in JabberAccount::~JabberAccount ()
   from /opt/kde3/lib/kde3/kopete_jabber.so
#8  0xb6fb57e8 in QObject::event () from /usr/lib/qt3/lib/libqt-mt.so.3
#9  0xb6f56897 in QApplication::internalNotify ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#10 0xb6f57661 in QApplication::notify () from /usr/lib/qt3/lib/libqt-mt.so.3
#11 0xb763c5c3 in KApplication::notify () from /opt/kde3/lib/libkdecore.so.4
#12 0xb6f58250 in QApplication::sendPostedEvents ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#13 0xb6f583e6 in QApplication::sendPostedEvents ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#14 0xb6f04e62 in QEventLoop::processEvents ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#15 0xb6f6d6b8 in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3
#16 0xb6f6d54e in QEventLoop::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#17 0xb6f5644f in QApplication::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#18 0x0807e03b in main ()

Comment 7 Christophe Marin 2008-07-03 17:03:48 UTC


*** This bug has been marked as a duplicate of 153111 ***