kopete frequent crashing

ArchNGEL · 03-31-2007, 01:53 PM

Hi there,

My kopete 0.12.4 picked up the habit of crashing rather frequently ever since I upgraded to FC6 from FC5, and thus to KDE 3.5.6 (Or does it have something to do with switching to Enlightenment 17 concurrently?)

Starting kopete from command line, the following output was produced:

Code:

Very strange! got a DCOPReplyFailed opcode, but we were not waiting for a reply!
QApplication::postEvent: Unexpected null receiver
QApplication::postEvent: Unexpected null receiver
QApplication::postEvent: Unexpected null receiver
QApplication::postEvent: Unexpected null receiver
QApplication::postEvent: Unexpected null receiver
CLIENT: Task: Task::done()
CLIENT: Task: emitting finished
QApplication::postEvent: Unexpected null receiver
QApplication::postEvent: Unexpected null receiver
QApplication::postEvent: Unexpected null receiver
QApplication::postEvent: Unexpected null receiver
CLIENT: Task: Task::done()
CLIENT: Task: emitting finished
terminate called after throwing an instance of 'std::bad_alloc'
  what():  St9bad_alloc
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = kopete path = <unknown> pid = 9092

So tons of the unexpected null receiver and a lot of times that: "Very strange! got a DCOPReplyFailed opcode, but we were not waiting for a reply!".

I don't know what searches I should make to find a relevant post about the problem. I found a recent bug report on zilla, where someone mentioned memory shortage. I have 2 GBs of memory, I don't think that would be the problem, however that bad_alloc does in fact sound like a mamory problem, doesn't it?

ArchNGEL · 04-01-2007, 06:56 AM

To tell you the full story the problem started with frequent freeezing of Kopete. Then I reinstalled the kdenetwork package, which resulted in the aforementioned crashes. Yesterday I compiled the source in a hope that it would solve the problems. As a matter of fact it has just brought back the good ol' freezing problem.

Sometimes it's enough if I choose "Kill" from the Enlightenment menu, and start a new instance. Other times I have to run "dcopserver_shutdown" and the start a new kopete. Sometimes this DCOP doesn't work well for me. I tried to start dcopserver everytime I log in my window manager, but it caused only more problems (something about being unable to launch klauncher).

Now that is far too complex for me to google after. What could be the problem?

DragonM15 · 05-13-2007, 10:24 PM

Please send me a PM if you figure out what the problem is. I am having the same problem, however with Slackware 11.0 I find it wierd that if I start KDE, log out of KDE and start a different window manager everything works find. But if I start in another window manager like xfce nothing kde-related works. I tried completely reinstalling kde-3.5.4 and that didnt fix the problem either. Please let me know if you find anything. I will do the same.

Thanks,
DragonM15