Summary: | Crash when setting jabber status to offline | ||
---|---|---|---|
Product: | [Unmaintained] kopete | Reporter: | Balázs Béla <balazsbela> |
Component: | Jabber Plugin | Assignee: | Kopete Developers <kopete-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | aleixpol, andresbajotierra, jedi.kenjiro, kachristmas, kde-bugs, mail, nevion, skunk, sven.burmeister, tobias.doerffel |
Priority: | NOR | ||
Version: | 0.60.81 | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | Patch for fixing the crash on Jabber-logout |
Description
Balázs Béla
2008-12-03 21:19:13 UTC
Forgot to mention that the same thing happens if I install the qca-tls package from apt (I'm using Debian) and copy the plugin manually to qt-copy directory. I can confirm that with kopete from today's trunk. When I set my gtalk account to offline, it crashes with the backtrace below. That doesn't happen with my jabber.org account, which doesn't use tls. Εφαρμογή: Kopete (kopete), σήμα SIGSEGV 0x00007f8189257ff1 in nanosleep () from /lib/libc.so.6 [Current thread is 0 (LWP 894)] Thread 3 (Thread 0x42fcd950 (LWP 1220)): #0 0x00007f8189280b66 in poll () from /lib/libc.so.6 #1 0x00007f81871dbdf8 in g_main_context_iterate (context=0x1010c60, block=1, dispatch=1, self=<value optimized out>) at /build/buildd/glib2.0-2.16.6/glib/gmain.c:2954 #2 0x00007f81871dc11b in IA__g_main_context_iteration (context=0x1010c60, may_block=1) at /build/buildd/glib2.0-2.16.6/glib/gmain.c:2708 #3 0x00007f818999572e in QEventDispatcherGlib::processEvents (this=0xcc44c0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:321 #4 0x00007f818996bca2 in QEventLoop::processEvents (this=<value optimized out>, flags={i = 1123864416}) at kernel/qeventloop.cpp:143 #5 0x00007f818996be2d in QEventLoop::exec (this=0xc6d400, flags={i = 1123864816}) at kernel/qeventloop.cpp:194 #6 0x00007f8176b94f9b in QCA::SyncThread::run () from /usr/lib/libqca.so.2 #7 0x00007f8189885162 in QThreadPrivate::start (arg=0xfff300) at thread/qthread_unix.cpp:185 #8 0x00007f8186f89fc7 in start_thread () from /lib/libpthread.so.0 #9 0x00007f81892895ad in clone () from /lib/libc.so.6 #10 0x0000000000000000 in ?? () Thread 2 (Thread 0x427cc950 (LWP 1224)): #0 0x00007f8186f8dd29 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 #1 0x00007f8189886159 in QWaitCondition::wait (this=0x10fecf0, mutex=0x10fece8, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:82 #2 0x00007f8185764f4c in QHostInfoAgent::run (this=0x10fecd0) at kernel/qhostinfo.cpp:241 #3 0x00007f8189885162 in QThreadPrivate::start (arg=0x10fecd0) at thread/qthread_unix.cpp:185 #4 0x00007f8186f89fc7 in start_thread () from /lib/libpthread.so.0 #5 0x00007f81892895ad in clone () from /lib/libc.so.6 #6 0x0000000000000000 in ?? () Thread 1 (Thread 0x7f818d5696f0 (LWP 894)): [KCrash Handler] #5 0x0000000000000170 in ?? () #6 0x00007f8189975895 in QMetaObject::invokeMethod (obj=0x12d7dd0, member=<value optimized out>, type=Qt::DirectConnection, ret={<QGenericArgument> = {_data = 0x0, _name = 0x0}, <No data fields>}, val0={_data = 0x0, _name = 0x0}, val1={_data = 0x0, _name = 0x0}, val2={_data = 0x0, _name = 0x0}, val3={_data = 0x0, _name = 0x0}, val4={_data = 0x0, _name = 0x0}, val5= {_data = 0x0, _name = 0x0}, val6={_data = 0x0, _name = 0x0}, val7={_data = 0x0, _name = 0x0}, val8={_data = 0x0, _name = 0x0}, val9={_data = 0x0, _name = 0x0}) at kernel/qmetaobject.cpp:945 #7 0x00007f818577a004 in QAbstractSocket::disconnectFromHost (this=0x12d7dd0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs.h:365 #8 0x00007f818577d678 in QAbstractSocketPrivate::canReadNotification (this=0x12d8220) at socket/qabstractsocket.cpp:547 #9 0x00007f818576e5e1 in QReadNotifier::event (this=<value optimized out>, e=0x23) at socket/qnativesocketengine.cpp:968 #10 0x00007f818bea2a5d in QApplicationPrivate::notify_helper (this=0x6b0ff0, receiver=0x11209f0, e=0x7fff956aef10) at kernel/qapplication.cpp:3803 #11 0x00007f818beaa7da in QApplication::notify (this=0x7fff956af200, receiver=0x11209f0, e=0x7fff956aef10) at kernel/qapplication.cpp:3768 #12 0x00007f818a56768b in ?? () from /usr/lib/libkdeui.so.5 #13 0x0000000000000003 in ?? () #14 0x00007f818987ce04 in QInternal::activateCallbacks (cb=19758544, parameters=0x23) at global/qglobal.cpp:2726 #15 0x00007f818996d381 in QCoreApplication::notifyInternal (this=0x7fff956af200, receiver=0x67a770, event=0x7fff956af200) at kernel/qcoreapplication.cpp:587 #16 0x00007f8189995989 in socketNotifierSourceDispatch (source=0x6c3d80) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:209 #17 0x00007f81871d878b in IA__g_main_context_dispatch (context=0x6b3220) at /build/buildd/glib2.0-2.16.6/glib/gmain.c:2012 #18 0x00007f81871dbf5d in g_main_context_iterate (context=0x6b3220, block=1, dispatch=1, self=<value optimized out>) at /build/buildd/glib2.0-2.16.6/glib/gmain.c:2645 #19 0x00007f81871dc11b in IA__g_main_context_iteration (context=0x6b3220, may_block=1) at /build/buildd/glib2.0-2.16.6/glib/gmain.c:2708 #20 0x00007f818999570f in QEventDispatcherGlib::processEvents (this=0x6afb30, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:319 #21 0x00007f818bf3444f in QGuiEventDispatcherGlib::processEvents (this=0x12d7dd0, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:198 #22 0x00007f818996bca2 in QEventLoop::processEvents (this=<value optimized out>, flags={i = -1788153552}) at kernel/qeventloop.cpp:143 #23 0x00007f818996be2d in QEventLoop::exec (this=0x7fff956af170, flags={i = -1788153472}) at kernel/qeventloop.cpp:194 #24 0x00007f818996e2dd in QCoreApplication::exec () at kernel/qcoreapplication.cpp:845 #25 0x000000000044a03c in main (argc=3, argv=0x7fff956affb8) at ../../../kopete/kopete/main.cpp:102 Same problem here *** Bug 175890 has been marked as a duplicate of this bug. *** *** Bug 178048 has been marked as a duplicate of this bug. *** Still happening - using kde unstable from opensuse (4.2 b2?) *** Bug 178486 has been marked as a duplicate of this bug. *** Look at bug 178486 for a proposed patch to fix this crash. (thanks to Tobias Doerffel) Created attachment 29560 [details]
Patch for fixing the crash on Jabber-logout
As already mentioned by Darío, here's a little patch that I made and that fixes the crash for me.
SVN commit 900642 by gkiagia: Do not crash on logout. Patch written by Tobias Doerffel. Thanks. BUG: 176821 M +1 -1 jabberbytestream.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=900642 *** Bug 179885 has been marked as a duplicate of this bug. *** *** Bug 180560 has been marked as a duplicate of this bug. *** |