Version: (using KDE 4.0.2) Installed from: Debian testing/unstable Packages Kopete crashed when I terminated it by selecting Quit in the systray context menu. It was not connected at that time since my network connection was down. I'm using Debian's kopete 4:4.0.2-1 on i386. Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0xb57e6ae0 (LWP 5216)] [KCrash handler] #6 0xb7f23424 in __kernel_vsyscall () #7 0xb6782f15 in raise () from /lib/i686/cmov/libc.so.6 #8 0xb6784891 in abort () from /lib/i686/cmov/libc.so.6 #9 0xb67c66c5 in free_check () from /lib/i686/cmov/libc.so.6 #10 0xb67c7325 in free () from /lib/i686/cmov/libc.so.6 #11 0xb695d081 in operator delete () from /usr/lib/libstdc++.so.6 #12 0xb3b2d902 in ~CoreProtocol (this=0x83b3130) at /tmp/buildd/kdenetwork-4.0.2/kopete/protocols/jabber/libiris/iris/xmpp-core/protocol.cpp:605 #13 0xb7e9fd3c in QObjectPrivate::deleteChildren (this=0x80bbe88) at kernel/qobject.cpp:1941 #14 0xb7ea464e in ~QObject (this=0xbfe413bc) at kernel/qobject.cpp:830 #15 0xb7e932df in ~QCoreApplication (this=0xbfe413bc) at kernel/qcoreapplication.cpp:485 #16 0xb704b5c1 in ~QApplication (this=0xbfe413bc) at kernel/qapplication.cpp:1002 #17 0xb79cde5a in ~KApplication (this=0xbfe413bc) at /build/buildd/kde4libs-4.0.2/kdeui/kernel/kapplication.cpp:914 #18 0xb79d5688 in ~KUniqueApplication (this=0xbfe413bc) at /build/buildd/kde4libs-4.0.2/kdeui/kernel/kuniqueapplication.cpp:328 #19 0x0808a2a6 in ~KopeteApplication (this=0xbfe413bc) at /tmp/buildd/kdenetwork-4.0.2/kopete/kopete/kopeteapplication.cpp:108 #20 0x08089734 in main (argc=3, argv=0xbfe417a4) at /tmp/buildd/kdenetwork-4.0.2/kopete/kopete/main.cpp:102 #21 0xb676e450 in __libc_start_main () from /lib/i686/cmov/libc.so.6 #22 0x08063051 in _start () #0 0xb7f23424 in __kernel_vsyscall ()
[OT] Congratulations! This is the bug number: 160000!!! But you have won nothing, I'm sorry :-( [OT]
What, no prize? What if I describe how to reproduce: 1. Disconnect from the network. 2. Launch Kopete with a Jabber account. 3. It will show an error dialog about network connection failure. 4. From the systray menu, set your status to "online". 5. Quickly bring up the tray menu and "Quit". Crashes every time.
I can confirm this crash with kdenetwork r790087. My (slightly more verbose) backtrace is: Application: Kopete (kopete), signal SIGABRT Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0xb5a0b6d0 (LWP 7286)] [KCrash handler] #6 0xffffe410 in __kernel_vsyscall () #7 0xb5e1c1f1 in *__GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #8 0xb5e1d9b8 in *__GI_abort () at abort.c:88 #9 0xb5e58b78 in malloc_printerr (action=2, str=0xb5f04ee4 "free(): invalid pointer", ptr=0x1c76) at malloc.c:5892 #10 0xb5e5a7e5 in *__GI___libc_free (mem=0x84a33a0) at malloc.c:3586 #11 0xb6009011 in operator delete () from /usr/lib/gcc/i686-pc-linux-gnu/4.1.2/libstdc++.so.6 #12 0xb412847b in ~CoreProtocol (this=0x84a33a0) at /var/tmp/portage/kde-base/kdenetwork-9999.4/work/kdenetwork-9999.4/kopete/protocols/jabber/libiris/iris/xmpp-core/protocol.cpp:605 #13 0xb7e856ee in QObjectPrivate::deleteChildren (this=0x80c3390) at kernel/qobject.cpp:1854 #14 0xb7e8dbe9 in ~QObject (this=0xbfcef368) at kernel/qobject.cpp:871 #15 0xb7e77747 in ~QCoreApplication (this=0xbfcef368) at kernel/qcoreapplication.cpp:515 #16 0xb6cd80e7 in ~QApplication (this=0xbfcef368) at kernel/qapplication.cpp:1038 #17 0xb78d2c9d in ~KApplication (this=0xbfcef368) at /var/tmp/portage/kde-base/kdelibs-9999.4/work/kdelibs-9999.4/kdeui/kernel/kapplication.cpp:913 #18 0xb78dac78 in ~KUniqueApplication (this=0xbfcef368) at /var/tmp/portage/kde-base/kdelibs-9999.4/work/kdelibs-9999.4/kdeui/kernel/kuniqueapplication.cpp:351 #19 0x0808adbe in ~KopeteApplication (this=0xbfcef368) at /var/tmp/portage/kde-base/kdenetwork-9999.4/work/kdenetwork-9999.4/kopete/kopete/kopeteapplication.cpp:108 #20 0x08089f96 in main (argc=) at /var/tmp/portage/kde-base/kdenetwork-9999.4/work/kdenetwork-9999.4/kopete/kopete/main.cpp:102 #21 0xb5e08fdc in __libc_start_main (main=0x8087ff0 <main>, argc=1, ubp_av=0xbfcef754, init=0x809d080 <__libc_csu_init>, fini=0x809d070 <__libc_csu_fini>, rtld_fini=0xb7f72100 <_dl_fini>, stack_end=0xbfcef74c) at libc-start.c:229 #22 0x08065101 in _start () #0 0xffffe410 in __kernel_vsyscall ()
Created attachment 24145 [details] Crash fix Could you try the patch?
I'm not able to try patches currently. But it should be easy to reproduce and verify.
SVN commit 792652 by rjarosz: Fix bug 160000: kopete segfault in Jabber protocol at exit It crashes because "CoreProtocol client;" and "CoreProtocol srv;" in ClientStream::Private are deleted twice. BUG: 156057 BUG: 160000 A 022_fix_crash.patch M +1 -1 iris/xmpp-core/xmlprotocol.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=792652
SVN commit 792654 by rjarosz: Backport fix for bug 160000: kopete segfault in Jabber protocol at exit It crashes because "CoreProtocol client;" and "CoreProtocol srv;" in ClientStream::Private are deleted twice. CCBUG: 156057 CCBUG: 160000 A 022_fix_crash.patch M +1 -1 iris/xmpp-core/xmlprotocol.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=792654