Bug 201646 - Kopete random crash. It happens since i'm using jabber protocol
Summary: Kopete random crash. It happens since i'm using jabber protocol
Status: RESOLVED NOT A BUG
Alias: None
Product: kopete
Classification: Unmaintained
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-07-27 12:07 UTC by Antonio
Modified: 2009-08-01 19:04 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Antonio 2009-07-27 12:07:08 UTC
Application that crashed: kopete
Version of the application: 0.70.90
KDE Version: 4.2.98 (KDE 4.2.98 (KDE 4.3 RC3))
Qt Version: 4.5.0
Operating System: Linux 2.6.29-02062903-generic i686
Distribution: Ubuntu 9.04

What I was doing when the application crashed:
(sorry, my english is really poor) I've been having problems with Kopete since i started to use it to connect to a jabber server. It doesn't matters if i connect through ssl or not (it connects both ways), Kopete crashes about 2 or 3 times in an hour. I can't define the steps to reproduce the crash because it happens even when i'm out and i leave the computer on. When i return i see the bug reporting tool open. Another problem i've been suffering is that Kopete disconnects from the jabber server around 7 or 8 times / hour. I'm using a jabber server at work and it  means i'm offline 90% of time, because when Kopete disconnects from jabber, it doesn't tries to reconnect.

 -- Backtrace:
Application: Kopete (kopete), signal: Segmentation fault
[Current thread is 0 (LWP 4355)]

Thread 4 (Thread 0xb2871b90 (LWP 4401)):
#0  0xb7f91430 in __kernel_vsyscall ()
#1  0xb5c460e5 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/tls/i686/cmov/libpthread.so.0
#2  0xb60272ed in pthread_cond_wait () from /lib/tls/i686/cmov/libc.so.6
#3  0xb6c579b2 in QWaitCondition::wait (this=0x96343b0, mutex=0x96343ac, time=4294967295) at thread/qwaitcondition_unix.cpp:87
#4  0xb752b152 in QHostInfoAgent::run (this=0x96343a0) at kernel/qhostinfo.cpp:260
#5  0xb6c5696e in QThreadPrivate::start (arg=0x96343a0) at thread/qthread_unix.cpp:189
#6  0xb5c424ff in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#7  0xb601849e in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 3 (Thread 0xb2013b90 (LWP 4415)):
#0  0xb5b1a0ac in clock_gettime () from /lib/tls/i686/cmov/librt.so.1
#1  0xb6d7806b in QTimerInfoList::getTime (this=0x96c3834, t=@0x96c3858) at kernel/qeventdispatcher_unix.cpp:339
#2  0xb6d78241 in QTimerInfoList::updateCurrentTime (this=0x96c3834) at kernel/qeventdispatcher_unix.cpp:297
#3  0xb6d79e2c in QTimerInfoList::timerWait (this=0x96c3834, tm=@0xb2013124) at kernel/qeventdispatcher_unix.cpp:420
#4  0xb6d7661a in timerSourcePrepare (source=0xb5b1dff4, timeout=0xb2013178) at kernel/qeventdispatcher_glib.cpp:140
#5  0xb5a9a9c0 in g_main_context_prepare () from /usr/lib/libglib-2.0.so.0
#6  0xb5a9adda in ?? () from /usr/lib/libglib-2.0.so.0
#7  0xb5a9b268 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#8  0xb6d76457 in QEventDispatcherGlib::processEvents (this=0x9646730, flags={i = -1308544408}) at kernel/qeventdispatcher_glib.cpp:325
#9  0xb6d4906a in QEventLoop::processEvents (this=0x95ce370, flags={i = -1308544344}) at kernel/qeventloop.cpp:149
#10 0xb6d494aa in QEventLoop::exec (this=0x95ce370, flags={i = -1308544200}) at kernel/qeventloop.cpp:200
#11 0xb2c39e59 in QCA::SyncThread::run () from /usr/lib/libqca.so.2
#12 0xb6c5696e in QThreadPrivate::start (arg=0x9605788) at thread/qthread_unix.cpp:189
#13 0xb5c424ff in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#14 0xb601849e in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 2 (Thread 0xb1812b90 (LWP 4423)):
#0  0xb5a9af7c in ?? () from /usr/lib/libglib-2.0.so.0
#1  0xb5a9b268 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#2  0xb6d76457 in QEventDispatcherGlib::processEvents (this=0x99de5a0, flags={i = -1316937016}) at kernel/qeventdispatcher_glib.cpp:325
#3  0xb6d4906a in QEventLoop::processEvents (this=0x99e00d8, flags={i = -1316936952}) at kernel/qeventloop.cpp:149
#4  0xb6d494aa in QEventLoop::exec (this=0x99e00d8, flags={i = -1316936904}) at kernel/qeventloop.cpp:200
#5  0xb2e9f6e2 in ?? () from /usr/lib/kde4/kopete_jabber.so
#6  0xb6c5696e in QThreadPrivate::start (arg=0x977b840) at thread/qthread_unix.cpp:189
#7  0xb5c424ff in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#8  0xb601849e in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 1 (Thread 0xb55a5700 (LWP 4355)):
[KCrash Handler]
#6  0xb2df1f41 in ?? () from /usr/lib/kde4/kopete_jabber.so
#7  0xb2dda3ee in ?? () from /usr/lib/kde4/kopete_jabber.so
#8  0xb6d60ca8 in QMetaObject::activate (sender=0x9d1e2e0, from_signal_index=6, to_signal_index=6, argv=0x0) at kernel/qobject.cpp:3069
#9  0xb6d61932 in QMetaObject::activate (sender=0x9d1e2e0, m=0xb2f132e4, local_signal_index=2, argv=0x0) at kernel/qobject.cpp:3143
#10 0xb2dd2047 in ?? () from /usr/lib/kde4/kopete_jabber.so
#11 0xb2e5e36d in ?? () from /usr/lib/kde4/kopete_jabber.so
#12 0xb2dd99b6 in ?? () from /usr/lib/kde4/kopete_jabber.so
#13 0xb6d60ca8 in QMetaObject::activate (sender=0x9ee59a0, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3069
#14 0xb6d61932 in QMetaObject::activate (sender=0x9ee59a0, m=0xb6e3c908, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3143
#15 0xb6d660a7 in QSingleShotTimer::timeout (this=0x9ee59a0) at .moc/release-shared/qtimer.moc:76
#16 0xb6d661cc in QSingleShotTimer::timerEvent (this=0x9ee59a0) at kernel/qtimer.cpp:298
#17 0xb6d5b15f in QObject::event (this=0x9ee59a0, e=0xbffae9dc) at kernel/qobject.cpp:1082
#18 0xb62fde9c in QApplicationPrivate::notify_helper (this=0x9265c98, receiver=0x9ee59a0, e=0xbffae9dc) at kernel/qapplication.cpp:4084
#19 0xb630619e in QApplication::notify (this=0xbffaec6c, receiver=0x9ee59a0, e=0xbffae9dc) at kernel/qapplication.cpp:3631
#20 0xb72ad5cd in KApplication::notify (this=0xbffaec6c, receiver=0x9ee59a0, event=0xbffae9dc) at /build/buildd/kde4libs-4.2.98a/kdeui/kernel/kapplication.cpp:302
#21 0xb6d4aa3b in QCoreApplication::notifyInternal (this=0xbffaec6c, receiver=0x9ee59a0, event=0xbffae9dc) at kernel/qcoreapplication.cpp:602
#22 0xb6d79d71 in QTimerInfoList::activateTimers (this=0x9276c34) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#23 0xb6d764e0 in timerSourceDispatch (source=0x9276c00) at kernel/qeventdispatcher_glib.cpp:164
#24 0xb5a97b88 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#25 0xb5a9b0eb in ?? () from /usr/lib/libglib-2.0.so.0
#26 0xb5a9b268 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#27 0xb6d76438 in QEventDispatcherGlib::processEvents (this=0x9235fc8, flags={i = -1074074792}) at kernel/qeventdispatcher_glib.cpp:323
#28 0xb639f365 in QGuiEventDispatcherGlib::processEvents (this=0x9235fc8, flags={i = -1074074744}) at kernel/qguieventdispatcher_glib.cpp:202
#29 0xb6d4906a in QEventLoop::processEvents (this=0xbffaec00, flags={i = -1074074680}) at kernel/qeventloop.cpp:149
#30 0xb6d494aa in QEventLoop::exec (this=0xbffaec00, flags={i = -1074074616}) at kernel/qeventloop.cpp:200
#31 0xb6d4b959 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:880
#32 0xb62fdd17 in QApplication::exec () at kernel/qapplication.cpp:3553
#33 0x08059773 in _start ()

Reported using DrKonqi
Comment 1 Dario Andres 2009-07-28 13:57:18 UTC
Please install the "kdenetwork-dbg" package and then paste here a new backtrace (which hopefully will be complete). Thanks!
Comment 2 Antonio 2009-07-31 10:18:19 UTC
Hello Dario Andrés,

    thanks for the quick response. I've changed the wire that connects my computer to the office network and it seems to have solved the problem. No crashes and no disconnections since i did it, so it was my fault, nor kopete's. Happy ending at last :-D, sorry for wasting your time and thank you very much for your attention.
Comment 3 Dario Andres 2009-08-01 19:04:16 UTC
I'm glad you could solve the issue. Do not apologize :)
Regards