Version: 0.12 (using KDE KDE 3.5.1) Installed from: Compiled From Sources OS: Linux Hi, i tried to make a call to a gtalk user (myself on another box, behind the same NAT (if it is important :)) but at the second i chose accept in gtalk, kopete crashed, i will add the debug output to this bug. i couldnt see the backtrace i dont know why, normally drkonqi would run.
Created attachment 14584 [details] debug output
Relevant-looking message: kopete: Fatal IO error: client killed You get no drkonqi because libICE exited the process: ICE default IO error handler doing an exit(), pid = 18696, errno = 9
Created attachment 14630 [details] Debug output of diverse situation (from gtalk, to gtalk, in the same NAT, not in the same NAT ...) I made some tests and put all the logs and backtraces in this file :) note : backtrace is not the same if i am in the same NAT than the gtalk or not, but psi crashes too when i am in the same NAT .. . . (didnt test from out with psi))
and a note about the backtraces : the backtrace when i get a call from gtalk to kopete from out of the NAT is the same as the one i get from psi when i get a call from gtalk to kopete from INSIDE the NAT :/
*** Bug 121730 has been marked as a duplicate of this bug. ***
Reassigning.
This bug is not talking about the error ICE reported in the bug 121730 but about a problem with libjingle: the bug 121730 appeared in mine, but is not the subject of this bug report. Could you please reverse che changes you made ? or should i reopen a bug for the libjingle one ?
Reverting to Kopete.
These problems should be fixes with the patches I have provided at bug report #126862
Can you still reproduce this bug with recent KDE version ?
Closing, if you can reproduce this bug with recent Kopete version please reopen.