Application that crashed: kopete Version of the application: 0.80.2 KDE Version: 4.3.2 (KDE 4.3.2) "release 5" Qt Version: 4.5.2 Operating System: Linux 2.6.27.29-0.1-pae i686 Distribution: "openSUSE 11.1 (i586)" -- Backtrace: Application: Kopete (kopete), signal: Segmentation fault [KCrash Handler] #6 0x00000000 in ?? () #7 0xb7bfd5e0 in ~Account (this=0x8b2f658) at /usr/src/debug/kdenetwork-4.3.2/kopete/libkopete/kopeteaccount.cpp:123 #8 0xb7c4b435 in ~PasswordedAccount (this=0x8b2f658) at /usr/src/debug/kdenetwork-4.3.2/kopete/libkopete/kopetepasswordedaccount.cpp:42 #9 0xb18340fa in ~FacebookAccount (this=0x8b2f658) at /usr/src/debug/dmacvicar-kopete-facebook-ffc26f60c2d08260098eeb7bc22119a0dc35ccd3/facebookaccount.cpp:55 #10 0xb6c053ef in QObjectPrivate::deleteChildren (this=0x8a4c458) at kernel/qobject.cpp:1847 #11 0xb6c0cd33 in ~QObject (this=0x8b596b0) at kernel/qobject.cpp:836 #12 0xb7c4d570 in ~Plugin (this=0x8b596b0) at /usr/src/debug/kdenetwork-4.3.2/kopete/libkopete/kopeteplugin.cpp:44 #13 0xb7c585e8 in ~Protocol (this=0x8b596b0) at /usr/src/debug/kdenetwork-4.3.2/kopete/libkopete/kopeteprotocol.cpp:77 #14 0xb182f068 in ~FacebookProtocol (this=0x8b596b0) at /usr/src/debug/dmacvicar-kopete-facebook-ffc26f60c2d08260098eeb7bc22119a0dc35ccd3/facebookprotocol.cpp:48 #15 0xb7c5431a in ~PluginManagerPrivate (this=0x80afd00) at /usr/src/debug/kdenetwork-4.3.2/kopete/libkopete/kopetepluginmanager.cpp:76 #16 0xb7c4d9aa in destroy () at /usr/src/debug/kdenetwork-4.3.2/kopete/libkopete/kopetepluginmanager.cpp:102 #17 0xb7bc7d8b in ~KCleanUpGlobalStatic (this=0xb7caee40) at /usr/include/kglobal.h:62 #18 0xb5e5c9b1 in exit () from /lib/libc.so.6 #19 0xb5e4570d in __libc_start_main () from /lib/libc.so.6 #20 0x08057001 in _start () at ../sysdeps/i386/elf/start.S:119 This bug may be a duplicate of or related to bug 207933 Reported using DrKonqi
This looks like bug 207515. - How did you installed the facebook protocol plugin. Is it updated? Thanks
I use the openSUSE RPM from the KDE 4.3 reposetory. Version 0.1.3-2.2
*** This bug has been marked as a duplicate of bug 207515 ***