Application that crashed: kopete Version of the application: 0.70.90 KDE Version: 4.2.95 (KDE 4.2.95 (KDE 4.3 RC1)) "release 1" Qt Version: 4.6.0 Operating System: Linux 2.6.30-10-default x86_64 Distribution: "openSUSE 11.2 Milestone 3 (x86_64)" What I was doing when the application crashed: Crashes every time I try to start it. when started from Konsole: kopete Calling appendChild() on a null node does nothing. Calling appendChild() on a null node does nothing. Calling appendChild() on a null node does nothing. Calling appendChild() on a null node does nothing. Calling appendChild() on a null node does nothing. Calling appendChild() on a null node does nothing. Calling appendChild() on a null node does nothing. KCrash: Application 'kopete' crashing... Added plugins for Kopete: Facebook and Skype. No other programs are interfering with Kopete, since the same crash occurs when loaded in an e17 environment. -- Backtrace: Application: Kopete (kopete), signal: Segmentation fault [KCrash Handler] #5 0x00007fdcf9bd2905 in FacebookProtocol::deserializeContact(Kopete::MetaContact*, QMap<QString, QString> const&, QMap<QString, QString> const&) () from /usr/lib64/kde4/kopete_facebook.so #6 0x00007fdd0e19ea45 in Kopete::MetaContact::slotProtocolLoaded(Kopete::Protocol*) () from /usr/lib64/libkopete.so.4 #7 0x00007fdd0e1a29d9 in Kopete::MetaContact::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libkopete.so.4 #8 0x00007fdd0c3bb692 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQtCore.so.4 #9 0x00007fdd0e1b3852 in Kopete::PluginManager::protocolLoaded(Kopete::Protocol*) () from /usr/lib64/libkopete.so.4 #10 0x00007fdd0e1b5396 in Kopete::PluginManager::loadPluginInternal(QString const&) () from /usr/lib64/libkopete.so.4 #11 0x00007fdd0e1b619c in Kopete::PluginManager::slotLoadNextPlugin() () from /usr/lib64/libkopete.so.4 #12 0x00007fdd0e1b8848 in Kopete::PluginManager::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libkopete.so.4 #13 0x00007fdd0c3bb692 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQtCore.so.4 #14 0x00007fdd0c3c069f in QSingleShotTimer::timerEvent(QTimerEvent*) () from /usr/lib64/libQtCore.so.4 #15 0x00007fdd0c3b5693 in QObject::event(QEvent*) () from /usr/lib64/libQtCore.so.4 #16 0x00007fdd0b84db0c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4 #17 0x00007fdd0b854dbe in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4 #18 0x00007fdd0cf8b516 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5 #19 0x00007fdd0c3a635c in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQtCore.so.4 #20 0x00007fdd0c3d266d in QTimerInfoList::activateTimers() () from /usr/lib64/libQtCore.so.4 #21 0x00007fdd0c3cf44d in timerSourceDispatch(_GSource*, int (*)(void*), void*) () from /usr/lib64/libQtCore.so.4 #22 0x00007fdd06989bce in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #23 0x00007fdd0698d2a8 in ?? () from /usr/lib64/libglib-2.0.so.0 #24 0x00007fdd0698d3d0 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #25 0x00007fdd0c3cf396 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #26 0x00007fdd0b8e1c6e in QGuiEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtGui.so.4 #27 0x00007fdd0c3a4c02 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #28 0x00007fdd0c3a4fdc in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #29 0x00007fdd0c3a7209 in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4 #30 0x00000000004155d6 in _start () Reported using DrKonqi
Facebook plugin is a bit unstable, but this is the first report it get some information about the facebook function involved in the backtrace. Thanks
Did you build the facebook protocol yourself from git or are you using packages?
*** This bug has been marked as a duplicate of bug 198675 ***