Version: 0.70.2 (using KDE 4.2.2) OS: Linux Installed from: Unspecified Linux Turning on kopete from console, logs: kopete(5137): Communication problem with "kopete" , it probably crashed. Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." " About contact already exists kopete(3988)/libkopete Kopete::Account::registerContact: Contact already exists!!! accountId: GaduAccount(0xd0c5600) contactId: "0" some others logs: kopete(3988): Attempt to use QAction "show_participants_widget" with KXMLGUIFactory! Calling appendChild() on a null node does nothing. kopete(3988): No language dictionaries for the language : "pl" Best regards, I have hope You'll repair this :)
The console output doesn't give us a lot of information :( If you can reproduce the crash at will, may you read http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_with_GDB to try to get a "backtrace" ? Thanks :)
Created attachment 32644 [details] First logs
Created attachment 32645 [details] Second
The backtrace in the kopete_2.kcrash file looks related to bug 174513 or bug 186121 The backtrace in the kopete_1.kcrash file looks unique. : Thread 1 (Thread 0xb5aab700 (LWP 28798)): #0 0xb7d43a1d in Kopete::Plugin::pluginId () from /usr/lib/libkopete.so.4 #1 0xb7d329d9 in Kopete::MetaContact::metaContactId () from /usr/lib/libkopete.so.4 #2 0x0809bf75 in _start () However it is still not really complete. If you are still experiencing this, can you install the debug symbol packages for kdenetwork/kopete ? Thanks
Sory but I stop using kopete, becouse I don't wanna twist my time to waiting 15min to start kopete... (I have 2.1GHz C2D, and 3Gb ram). In attechmed filles I upload from gdb logs, I have hope it will be helpfull, if not, Im sory. Best regards, kde rox ;)
*** This bug has been marked as a duplicate of bug 186852 ***