Application that crashed: kopete Version of the application: 0.70.90 KDE Version: 4.2.95 (KDE 4.2.95 (KDE 4.3 RC1)) Qt Version: 4.5.2 Operating System: Linux 2.6.31-2-generic i686 Distribution: Ubuntu karmic (development branch) What I was doing when the application crashed: Uninstalling the facebook plugin allows kopete to start. I tried purging kopete & reinstalling; but as long as the facebook plugin was also installed, kopete crashed exactly as shown. uninstalling the facebook plugin allowed kopete to start & operate without problems. -- Backtrace: Application: Kopete (kopete), signal: Segmentation fault [KCrash Handler] #6 0x01f5f7f8 in ?? () from /usr/lib/kde4/kopete_facebook.so #7 0x00519ad9 in Kopete::MetaContact::slotProtocolLoaded(Kopete::Protocol*) () from /usr/lib/libkopete.so.4 #8 0x0051e668 in Kopete::MetaContact::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libkopete.so.4 #9 0x03c25343 in QMetaObject::activate (sender=0x975e92c, from_signal_index=6, to_signal_index=6, argv=0xbfb81f28) at kernel/qobject.cpp:3113 #10 0x03c25fa2 in QMetaObject::activate (sender=0x975e92c, m=0x590260, local_signal_index=2, argv=0xbfb81f28) at kernel/qobject.cpp:3187 #11 0x005305d3 in Kopete::PluginManager::protocolLoaded(Kopete::Protocol*) () from /usr/lib/libkopete.so.4 #12 0x005323dc in Kopete::PluginManager::loadPluginInternal(QString const&) () from /usr/lib/libkopete.so.4 #13 0x00533281 in Kopete::PluginManager::slotLoadNextPlugin() () from /usr/lib/libkopete.so.4 #14 0x005359ab in Kopete::PluginManager::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libkopete.so.4 #15 0x03c25343 in QMetaObject::activate (sender=0x9ab57e0, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3113 #16 0x03c25fa2 in QMetaObject::activate (sender=0x9ab57e0, m=0x3cff908, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3187 #17 0x03c2a467 in QSingleShotTimer::timeout (this=0x9ab57e0) at .moc/release-shared/qtimer.moc:76 #18 0x03c2a57c in QSingleShotTimer::timerEvent (this=0x9ab57e0) at kernel/qtimer.cpp:298 #19 0x03c1f49f in QObject::event (this=0x9ab57e0, e=0xbfb82660) at kernel/qobject.cpp:1075 #20 0x08914c34 in QApplicationPrivate::notify_helper (this=0x9754340, receiver=0x9ab57e0, e=0xbfb82660) at kernel/qapplication.cpp:4056 #21 0x0891c35c in QApplication::notify (this=0xbfb829c4, receiver=0x9ab57e0, e=0xbfb82660) at kernel/qapplication.cpp:3603 #22 0x0116d9ea in KApplication::notify (this=0xbfb829c4, receiver=0x9ab57e0, event=0xbfb82660) at ../../kdeui/kernel/kapplication.cpp:302 #23 0x03c0f7ab in QCoreApplication::notifyInternal (this=0xbfb829c4, receiver=0x9ab57e0, event=0xbfb82660) at kernel/qcoreapplication.cpp:610 #24 0x03c3c8ce in QCoreApplication::sendEvent (this=0x9757134) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213 #25 QTimerInfoList::activateTimers (this=0x9757134) at kernel/qeventdispatcher_unix.cpp:572 #26 0x03c3a1c0 in timerSourceDispatch (source=0x9757100) at kernel/qeventdispatcher_glib.cpp:165 #27 0x00edabc8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #28 0x00ede470 in ?? () from /usr/lib/libglib-2.0.so.0 #29 0x00ede5a3 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #30 0x03c3a10c in QEventDispatcherGlib::processEvents (this=0x9753ea0, flags=...) at kernel/qeventdispatcher_glib.cpp:327 #31 0x089b57a5 in QGuiEventDispatcherGlib::processEvents (this=0x9753ea0, flags=...) at kernel/qguieventdispatcher_glib.cpp:202 #32 0x03c0dd59 in QEventLoop::processEvents (this=0xbfb82924, flags=) at kernel/qeventloop.cpp:149 #33 0x03c0e1aa in QEventLoop::exec (this=0xbfb82924, flags=...) at kernel/qeventloop.cpp:201 #34 0x03c1061f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888 #35 0x08914ab7 in QApplication::exec () at kernel/qapplication.cpp:3525 #36 0x080598bc in _start () This bug may be a duplicate of or related to bug 198675 Reported using DrKonqi
Indeed, this is the same as bug 198675. The cause of the crash is the facebook plugin which seems to be rather unstable. The workaround is uninstalling it. Thanks *** This bug has been marked as a duplicate of bug 198675 ***