Version: 0.12.3 (using KDE KDE 3.5.5) Installed from: SuSE RPMs OS: Linux About 2 or 3 weeks ago i started having problems with sending messages over msn. Half of the sent messages didnt make their destinations. I have WinXP dualboot with that computer, and there is no problems with Live Messanger. Today I tried again over some period of time and now Kopete changes status also to offline...all the time. Only loaded plugin im usin is MSN plugin. Console shows following output: QGArray::at: Absolute index -5 out of range QGArray::at: Absolute index -4 out of range QGArray::at: Absolute index -3 out of range QGArray::at: Absolute index -2 out of range QGArray::at: Absolute index -1 out of range kopete (msn): WARNING: [void MSNSocket::slotSocketError(int)] Error: 17 (server sulges ühenduse) kopete (msn): WARNING: [void MSNSocket::slotSocketError(int)] Error: 17 (server sulges ühenduse) kopete (msn): WARNING: [void MSNSocket::slotSocketError(int)] Error: 17 (server sulges ühenduse) kopete (msn): WARNING: [void MSNSocket::slotSocketError(int)] Error: 17 (server sulges ühenduse) kopete (msn): WARNING: [void MSNSocket::slotSocketError(int)] Error: 17 (server sulges ühenduse) kopete (msn): WARNING: [void MSNSocket::slotSocketError(int)] Error: 17 (server sulges ühenduse) kopete (msn): WARNING: [void MSNSocket::slotSocketError(int)] Error: 17 (server sulges ühenduse) kopete (msn): WARNING: [void MSNSocket::slotSocketError(int)] Error: 17 (server sulges ühenduse) kopete (msn): WARNING: [void MSNSocket::slotSocketError(int)] Error: 17 (server sulges ühenduse) Very strange! got a DCOPReply opcode, but we were not waiting for a reply! QFont::setPointSize: Point size <= 0 (-1) QFont::setPointSize: Point size <= 0 (-1) kopete (msn): WARNING: [void MSNSocket::slotSocketError(int)] Error: 17 (server sulges ühenduse) kopete (msn): WARNING: [void MSNSocket::slotSocketError(int)] Error: 17 (server sulges ühenduse) kopete (msn): WARNING: [void MSNSocket::slotSocketError(int)] Error: 17 (server sulges ühenduse) "server sulges ühenduse" = server closed the connection
Are you behind a firewall? And do you think that bug 137443 or bug 132002 are the same issue?
If you count NAT as firewall then yes...behind at least 2 levels of NAT(some ports are forwarded, though), but i dont think its network issue, because I have no problems with another computer in the same network with the same distribution and have problems sending messages to all clients(live messanger, gaim). It may be the bug 137443...but im not sure and I cant think no way of testing it.
*** This bug has been marked as a duplicate of 137443 ***