Kopete crash on network down

[Federico]

Binary package hint: kopete

(kopete), SIGABRT
[Current thread is 0 (LWP 1090)]

Thread 2 (Thread 0xb055bb90 (LWP 28185)):
#0 0xb7f9b430 in __kernel_vsyscall ()
#1 0xb608fae7 in poll () from /lib/tls/i686/cmov/libc.so.6
#2 0xb5b3a74b in g_poll () from /usr/lib/libglib-2.0.so.0
#3 0xb5b2cf82 in ?? () from /usr/lib/libglib-2.0.so.0
#4 0xb5b2d268 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#5 0xb6df8457 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4
#6 0xb6dcb06a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#7 0xb6dcb4aa in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#8 0xb2881e59 in QCA::SyncThread::run () from /usr/lib/libqca.so.2
#9 0xb6cd896e in ?? () from /usr/lib/libQtCore.so.4
#10 0xb5ccf4ff in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#11 0xb609a49e in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 1 (Thread 0xb5632700 (LWP 1090)):
[KCrash Handler]
#6 0xb7f9b430 in __kernel_vsyscall ()
#7 0xb5fe16d0 in raise () from /lib/tls/i686/cmov/libc.so.6
#8 0xb5fe3098 in abort () from /lib/tls/i686/cmov/libc.so.6
#9 0xb6cd0595 in qt_message_output () from /usr/lib/libQtCore.so.4
#10 0xb6cd0681 in qFatal () from /usr/lib/libQtCore.so.4
#11 0xb7cdecd4 in Kopete::MessageHandlerFactory::Private::factories () from /usr/lib/libkopete.so.4
#12 0xb7cdeef2 in Kopete::MessageHandlerFactory::~MessageHandlerFactory () from /usr/lib/libkopete.so.4
#13 0xb2a5e467 in ?? () from /usr/lib/kde4/kopete_history.so
#14 0xb7d010f2 in ?? () from /usr/lib/libkopete.so.4
#15 0xb7cfa4aa in ?? () from /usr/lib/libkopete.so.4
#16 0xb7c7657b in ?? () from /usr/lib/libkopete.so.4
#17 0xb5fe4bb9 in exit () from /lib/tls/i686/cmov/libc.so.6
#18 0xb4f73165 in ?? () from /usr/lib/libgdk-x11-2.0.so.0
#19 0xb731c2fa in KApplication::xioErrhandler () from /usr/lib/libkdeui.so.5
#20 0xb731c336 in ?? () from /usr/lib/libkdeui.so.5
#21 0xb5e0bf22 in _XIOError () from /usr/lib/libX11.so.6
#22 0xb5e13743 in ?? () from /usr/lib/libX11.so.6
#23 0xb5e13ccd in _XReply () from /usr/lib/libX11.so.6
#24 0xb5d22506 in XScreenSaverQueryInfo () from /usr/lib/libXss.so.1
#25 0xb7c7bde4 in ?? () from /usr/lib/libkopete.so.4
#26 0xb7d18ecf in Kopete::IdleTimer::idleTime () from /usr/lib/libkopete.so.4
#27 0xb7d1903f in Kopete::IdleTimer::updateIdleTime () from /usr/lib/libkopete.so.4
#28 0xb7d1955b in Kopete::IdleTimer::qt_metacall () from /usr/lib/libkopete.so.4
#29 0xb6de2ca8 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#30 0xb6de3932 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#31 0xb6e1e717 in QTimer::timeout () from /usr/lib/libQtCore.so.4
#32 0xb6de86fe in QTimer::timerEvent () from /usr/lib/libQtCore.so.4
#33 0xb6ddd15f in QObject::event () from /usr/lib/libQtCore.so.4
#34 0xb637fe9c in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4
#35 0xb638819e in QApplication::notify () from /usr/lib/libQtGui.so.4
#36 0xb731c94d in KApplication::notify () from /usr/lib/libkdeui.so.5
#37 0xb6dcca3b in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4
#38 0xb6dfbd71 in ?? () from /usr/lib/libQtCore.so.4
#39 0xb6df84e0 in ?? () from /usr/lib/libQtCore.so.4
#40 0xb5b29b88 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#41 0xb5b2d0eb in ?? () from /usr/lib/libglib-2.0.so.0
#42 0xb5b2d268 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#43 0xb6df8438 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4
#44 0xb6421365 in ?? () from /usr/lib/libQtGui.so.4
#45 0xb6dcb06a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#46 0xb6dcb4aa in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#47 0xb6dcd959 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#48 0xb637fd17 in QApplication::exec () from /usr/lib/libQtGui.so.4
#49 0x0808c27f in _start ()

[Federico (makexy)]

kopete 4.2.2-0ubuntu2.1
ubuntu 9.04

[Jonathan Thomas (echidnaman)]

Is this still an issue with Kubuntu 9.10?

[Jonathan Thomas (echidnaman)]

We are closing this bug report because it lacks the information we need to investigate the problem, as requested in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the "Status" column, and change the status back to "New". Thanks again!