| Summary: | Kopete crashes when closing (Jabber plugin) | ||
|---|---|---|---|
| Product: | [Unmaintained] kopete | Reporter: | Jonathan Verner <jonathan.verner> |
| Component: | Jabber Plugin | Assignee: | Kopete Developers <kopete-bugs-null> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | crash | CC: | Regnaron |
| Priority: | NOR | ||
| Version: | 0.12.7 | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
If necessary I can post my configuration file... I can reprodce this crash with a current KDE4 SVN build.
Steps to reproduce:
1) Create two Jabber accounts A1 and A2
2) Log into accounts
3) Start a chat
4) Close kopete without closing the chat window
5) See kopete crash with the following backtrace:
Application: Kopete (kopete), signal SIGSEGV
Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xb5cd86d0 (LWP 29753)]
[KCrash handler]
#6 0xb6160630 in __dynamic_cast ()
from /usr/lib/gcc/i686-pc-linux-gnu/4.1.2/libstdc++.so.6
#7 0xb45723b2 in ~JabberChatSession (this=0x838d8e0)
at /var/tmp/portage/kde-base/kdenetwork-9999.4/work/kdenetwork-9999.4/kopete/protocols/jabber/jabberchatsession.cpp:102
#8 0xb7e47dee in QObjectPrivate::deleteChildren (this=0x82e4c50)
at kernel/qobject.cpp:1925
#9 0xb7e4ac58 in ~QObject (this=0x833c528) at kernel/qobject.cpp:823
#10 0xb6bc5042 in ~Account (this=0x833c528)
at /var/tmp/portage/kde-base/kdenetwork-9999.4/work/kdenetwork-9999.4/kopete/libkopete/kopeteaccount.cpp:127
#11 0xb6c01427 in ~PasswordedAccount (this=0x833c528)
at /var/tmp/portage/kde-base/kdenetwork-9999.4/work/kdenetwork-9999.4/kopete/libkopete/kopetepasswordedaccount.cpp:42
#12 0xb454d975 in ~JabberAccount (this=0x833c528)
at /var/tmp/portage/kde-base/kdenetwork-9999.4/work/kdenetwork-9999.4/kopete/protocols/jabber/jabberaccount.cpp:135
#13 0xb7e47fd7 in QObject::event (this=0x833c528, e=0x0)
at kernel/qobject.cpp:1105
#14 0xb6dade8a in QApplicationPrivate::notify_helper (this=0x80bd208,
receiver=0x833c528, e=0x845b348) at kernel/qapplication.cpp:3556
#15 0xb6daf77a in QApplication::notify (this=0xbf844e28, receiver=0x833c528,
e=0x845b348) at kernel/qapplication.cpp:3115
#16 0xb78dfc03 in KApplication::notify (this=0xbf844e28, receiver=0x833c528,
event=0x845b348)
at /var/tmp/portage/kde-base/kdelibs-9999.4/work/kdelibs-9999.4/kdeui/kernel/kapplication.cpp:311
#17 0xb7e36d7b in QCoreApplication::notifyInternal (this=0xbf844e28,
receiver=0x833c528, event=0x845b348) at kernel/qcoreapplication.cpp:530
#18 0xb7e3821a in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0,
event_type=0, data=0x80a7f50) at kernel/qcoreapplication.h:200
#19 0xb7e60905 in QEventDispatcherUNIX::processEvents (this=0x80c4e38,
flags=@0xbf844d28) at kernel/qeventdispatcher_unix.cpp:858
#20 0xb6e37cce in QEventDispatcherX11::processEvents (this=0x80c4e38,
flags=@0xbf844d54) at kernel/qeventdispatcher_x11.cpp:145
#21 0xb7e36191 in QEventLoop::processEvents (this=0xbf844dc0,
flags=@0xbf844d88) at kernel/qeventloop.cpp:140
#22 0xb7e3629a in QEventLoop::exec (this=0xbf844dc0, flags=@0xbf844dc8)
at kernel/qeventloop.cpp:186
#23 0xb7e38626 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:759
#24 0xb6dad487 in QApplication::exec () at kernel/qapplication.cpp:3053
#25 0x080891ec in main (argc=)
at /var/tmp/portage/kde-base/kdenetwork-9999.4/work/kdenetwork-9999.4/kopete/kopete/main.cpp:102
#26 0xb5f5cfdc in __libc_start_main (main=0x8087250 <main>, argc=1,
ubp_av=0xbf845214, init=0x80986f0 <__libc_csu_init>,
fini=0x80986e0 <__libc_csu_fini>, rtld_fini=0xb7efa100 <_dl_fini>,
stack_end=0xbf84520c) at libc-start.c:229
#27 0x08064411 in _start ()
#0 0xffffe410 in __kernel_vsyscall ()
|
Version: 0.12.7 (using KDE 3.5.8) Installed from: Ubuntu Packages Compiler: gcc version 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2) OS: Linux Kopete crashes when exiting. It seems to be connected to the Jabber plugin (I've specifically tested with a new user where I only added my Jabber account). Also the crash seems to happen in the JabberAccount destructor. The bug was (I think) present even in 3.5.7 and is present in kopete from KDE4 (although there I can't get a useable backtrace since my packages are compiled without debugging information) Here is the backtrace: (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1241085456 (LWP 19382)] [KCrash handler] #6 0x00000000 in ?? () #7 0xb57f70e5 in JabberAccount::~JabberAccount () from /usr/lib/kde3/kopete_jabber.so #8 0xb6907f5c in QObject::event (this=0x856ca40, e=0x84dcf78) at kernel/qobject.cpp:750 #9 0xb689faf0 in QApplication::internalNotify (this=0xbfff3384, receiver=0x856ca40, e=0x84dcf78) at kernel/qapplication.cpp:2635 #10 0xb68a191f in QApplication::notify (this=0xbfff3384, receiver=0x856ca40, e=0x84dcf78) at kernel/qapplication.cpp:2358 #11 0xb7065ca2 in KApplication::notify (this=0xbfff3384, receiver=0x856ca40, event=0x84dcf78) at /build/buildd/kdelibs-3.5.8/./kdecore/kapplication.cpp:550 #12 0xb6832209 in QApplication::sendEvent (receiver=0x856ca40, event=0x84dcf78) at ../include/qapplication.h:520 #13 0xb68a0b28 in QApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qapplication.cpp:3299 #14 0xb68a0c30 in QApplication::sendPostedEvents () at kernel/qapplication.cpp:3210 #15 0xb6846215 in QEventLoop::processEvents (this=0x816fe30, flags=4) at kernel/qeventloop_x11.cpp:202 #16 0xb68ba1ce in QEventLoop::enterLoop (this=0x816fe30) at kernel/qeventloop.cpp:198 #17 0xb68b9fde in QEventLoop::exec (this=0x816fe30) at kernel/qeventloop.cpp:145 #18 0xb68a1699 in QApplication::exec (this=0xbfff3384) at kernel/qapplication.cpp:2758 #19 0x0807f95c in ?? () #20 0xbfff3384 in ?? () #21 0xbfff337c in ?? () #22 0xbfff3374 in ?? () #23 0x00000000 in ?? ()