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-rc2-wl x86_64 Distribution: Ubuntu karmic (development branch) What I was doing when the application crashed: Kopete krashes immediately on startup, no matter what I do. Deleting the configuration does not help. -- Backtrace: Application: Kopete (kopete), signal: Segmentation fault [KCrash Handler] #5 0x00007f4fde1404fb in QString::length (this=0xfffffff0, other=...) at ../../include/QtCore/../../src/corelib/tools/qstring.h:683 #6 QString::operator< (this=0xfffffff0, other=...) at tools/qstring.cpp:1973 #7 0x00007f4fcedf888e in ?? () from /usr/lib/kde4/kopete_facebook.so #8 0x00007f4fe0022a35 in Kopete::MetaContact::slotProtocolLoaded (this=0x240f5a0, p=0x24561c0) at ../../../kopete/libkopete/kopetemetacontact.cpp:1061 #9 0x00007f4fe00269c9 in Kopete::MetaContact::qt_metacall (this=0x240f5a0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff13b6c250) at ./kopetemetacontact.moc:181 #10 0x00007f4fde1fbe1c in QMetaObject::activate (sender=0x21446a8, from_signal_index=<value optimized out>, to_signal_index=<value optimized out>, argv=0x2472bbc) at kernel/qobject.cpp:3113 #11 0x00007f4fe0037842 in Kopete::PluginManager::protocolLoaded (this=0xfffffff0, _t1=0x24561c0) at ./kopetepluginmanager.moc:140 #12 0x00007f4fe00393a6 in Kopete::PluginManager::loadPluginInternal (this=<value optimized out>, pluginId=<value optimized out>) at ../../../kopete/libkopete/kopetepluginmanager.cpp:394 #13 0x00007f4fe003a1ac in Kopete::PluginManager::slotLoadNextPlugin (this=0x21446a8) at ../../../kopete/libkopete/kopetepluginmanager.cpp:330 #14 0x00007f4fe003c878 in Kopete::PluginManager::qt_metacall (this=0x21446a8, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff13b6c750) at ./kopetepluginmanager.moc:114 #15 0x00007f4fde1fbe1c in QMetaObject::activate (sender=0x23b0400, from_signal_index=<value optimized out>, to_signal_index=<value optimized out>, argv=0x2472bbc) at kernel/qobject.cpp:3113 #16 0x00007f4fde200e5f in QSingleShotTimer::timerEvent (this=0x23b0400) at kernel/qtimer.cpp:298 #17 0x00007f4fde1f5dc3 in QObject::event (this=0x23b0400, e=0x7fff13b6c040) at kernel/qobject.cpp:1075 #18 0x00007f4fdd68f62c in QApplicationPrivate::notify_helper (this=0x2040cd0, receiver=0x23b0400, e=0x7fff13b6cd60) at kernel/qapplication.cpp:4056 #19 0x00007f4fdd6968fe in QApplication::notify (this=0x7fff13b6d0b0, receiver=0x23b0400, e=0x7fff13b6cd60) at kernel/qapplication.cpp:4021 #20 0x00007f4fdedf33a6 in KApplication::notify (this=0x7fff13b6d0b0, receiver=0x23b0400, event=0x7fff13b6cd60) at ../../kdeui/kernel/kapplication.cpp:302 #21 0x00007f4fde1e6c6c in QCoreApplication::notifyInternal (this=0x7fff13b6d0b0, receiver=0x23b0400, event=0x7fff13b6cd60) at kernel/qcoreapplication.cpp:610 #22 0x00007f4fde211912 in QCoreApplication::sendEvent (this=0x2044650) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213 #23 QTimerInfoList::activateTimers (this=0x2044650) at kernel/qeventdispatcher_unix.cpp:572 #24 0x00007f4fde20f2ad in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:165 #25 0x00007f4fd8bdd8fe in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #26 0x00007f4fd8be0fd8 in ?? () from /usr/lib/libglib-2.0.so.0 #27 0x00007f4fd8be1100 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #28 0x00007f4fde20f1f6 in QEventDispatcherGlib::processEvents (this=0x200e150, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:327 #29 0x00007f4fdd723ace in QGuiEventDispatcherGlib::processEvents (this=0xfffffff0, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202 #30 0x00007f4fde1e5572 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149 #31 0x00007f4fde1e5944 in QEventLoop::exec (this=0x7fff13b6d000, flags=) at kernel/qeventloop.cpp:201 #32 0x00007f4fde1e7af9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888 #33 0x00000000004155a6 in main (argc=<value optimized out>, argv=<value optimized out>) at ../../../kopete/kopete/main.cpp:104 This bug may be a duplicate of or related to bug 198675 Reported using DrKonqi
turn off the facebook plugin and see if that helps. kopete --disable facebook from the command line or the Run Command Interface should do the trick.
After recompiling the facebook plugin against the latest version of Kopete, the problem goes away. Kopete now works fine, except for crashing on exit, like this: Application: Kopete (kopete), signal: Segmentation fault [KCrash Handler] #5 0x0000000000000000 in ?? () #6 0x00007f7a1ef01924 in ~Account (this=0x1a85020, __in_chrg=<value optimized out>) at ../../../kopete/libkopete/kopeteaccount.cpp:123 #7 0x00007f7a0d8a9395 in ?? () from /usr/lib/kde4/kopete_facebook.so #8 0x00007f7a1d108e9c in QObjectPrivate::deleteChildren (this=0x1b1f320) at kernel/qobject.cpp:1847 #9 0x00007f7a1d111499 in ~QObject (this=<value optimized out>, __in_chrg=<value optimized out>) at kernel/qobject.cpp:836 #10 0x00007f7a1ef5658a in ~Protocol (this=0x1851d70, __in_chrg=<value optimized out>) at ../../../kopete/libkopete/kopeteprotocol.cpp:77 #11 0x00007f7a0d8a56d5 in ?? () from /usr/lib/kde4/kopete_facebook.so #12 0x00007f7a1ef5219b in ~PluginManagerPrivate (this=0x1863690, __in_chrg=<value optimized out>) at ../../../kopete/libkopete/kopetepluginmanager.cpp:76 #13 0x00007f7a1ef4b9c7 in destroy () at ../../../kopete/libkopete/kopetepluginmanager.cpp:102 #14 0x00007f7a1bdb975d in *__GI_exit (status=0) at exit.c:75 #15 0x00007f7a1bda15ed in __libc_start_main (main=0x412f60 <main>, argc=3, ubp_av=0x7fff5a396cb8, init=0x42d850 <__libc_csu_init>, fini=<value optimized out>, rtld_fini=<value optimized out>, stack_end=0x7fff5a396ca8) at libc-start.c:252 #16 0x0000000000412e99 in _start () at ../sysdeps/x86_64/elf/start.S:113
@Michael: for next reports, try to not mix different backtraces (or situations) in the same report, as it difficults a bit organizing the reports. Now, could you recompile the Facebook plugin with debug symbols to get a complete backtrace? Thanks
Please open a new bug for the facebook crash on exit.
*** Bug 199307 has been marked as a duplicate of this bug. ***
*** Bug 200324 has been marked as a duplicate of this bug. ***
*** Bug 200459 has been marked as a duplicate of this bug. ***
*** Bug 201025 has been marked as a duplicate of this bug. ***