Version: 0.60.1 (using KDE 4.1.1) OS: FreeBSD Installed from: FreeBSD Ports Installed a fresh KDE 4.1.1 on FreeBSD 7.1-PRE and am having issues with MSN, gTalk and Yahoo. Yahoo displays errors on startup, but MSN and gTalk silently fail. Starting them from the console shows the following: Yahoo: Error Message 17. Remote host closed connection gTalk: kopete(26202)/kopete (jabber) JabberResourcePool::lockToResource: Locking "rhavenn@gmail.com" to "Kopete" kopete(26202)/kopete (jabber) JabberResourcePool::removeLock: Removing resource lock for "rhavenn@gmail.com" kopete(26202)/kopete (jabber) JabberResourcePool::removeLock: No locks found. kopete(26202)/kopete (jabber) JabberConnector::JabberConnector: New Jabber connector. kopete(26202)/kopete (jabber) JabberByteStream::JabberByteStream: Instantiating new Jabber byte stream. kopete(26202)/kopete (jabber) JabberConnector::setOptSSL: Setting SSL to true kopete(26202)/kopete (jabber) JabberConnector::setOptHostPort: Manually specifying host "talk.google.com" and port 5223 kopete(26202)/kopete (jabber) JabberByteStream::close: Closing stream. kopete(26202)/kopete (jabber) JabberConnector::connectToServer: Initiating connection to "gmail.com" kopete(26202)/kopete (jabber) JabberByteStream::connect: Connecting to "talk.google.com" , service "5223" kopete(26202)/kopete (jabber) JabberConnector::slotConnected: We are connected. QIODevice::write: ReadOnly device kopete(26202)/kopete (jabber) JabberByteStream::slotError: Socket error ' "remote host closed connection" ' - Code : 17 QObject: Do not delete object, 'unnamed', during its event handler! kopete(26202)/kopete (jabber) JabberByteStream::slotConnectionClosed: Socket has been closed. kopete(26202)/kopete (jabber) JabberByteStream::close: Closing stream. kopete(26202)/kopete (jabber) JabberByteStream::close: Closing stream. kopete(26202)/kopete (jabber - raw protocol) JabberAccount::slotClientDebugMessage: "Disconnected, freeing up file transfer port..." kopete(26202)/kopete (jabber) JabberAccount::slotCSDisconnected: Disconnected from Jabber server. kopete(26202)/kopete (jabber) JabberResourcePool::clear: Clearing the resource pool. kopete(26202)/kopete (jabber) JabberResourcePool::slotResourceDestroyed: Resource has been destroyed, collecting the pieces. kopete(26202)/kopete (jabber) JabberBaseContact::reevaluateStatus: Determining new status for "rhavenn@gmail.com" kopete(26202)/kopete (jabber) JabberResourcePool::bestJabberResource: Determining best resource for "rhavenn@gmail.com" kopete(26202)/kopete (jabber) JabberResourcePool::lockedJabberResource: No lock available for "rhavenn@gmail.com" kopete(26202)/kopete (jabber) JabberBaseContact::reevaluateStatus: New status for "rhavenn@gmail.com" is "Offline" For MSN: kopete(27869)/kopete (msn) MSNAccount::setOnlineStatus: "Online" kopete(27869)/kopete (msn - raw protocol) MSNSocket::slotReadyWrite: Sending command: "VER 0 MSNP11 MSNP10 CVR0" QIODevice::write: ReadOnly device kopete(27869)/kopete (msn) MSNSocket::slotSocketError: Error: 17 ( "remote host closed connection" ) QObject: Do not delete object, 'unnamed', during its event handler! kopete(27869)/kopete (msn) MSNSocket::slotSocketClosed: Socket closed. kopete(27869)/kopete (msn) MSNAccount::slotNotifySocketClosed: kopete(27869)/libkopete Kopete::Account::disconnected: 99 kopete(27869)/kopete (msn) MSNNotifySocket::~MSNNotifySocket: I believe I saw some info that Yahoo was fixed in SVN, but I couldn't find anything regarding the other 2. qca-ossl is installed from ports via the KDE build dependencies.
I'm trying to use Kopete 0.60.3 on PC-BSD 7 aka FreeBSD 7.1-PRERELEASE and I get the same error (and always have on KDE4). The error when trying to connect is: kopete(57073)/kopete (msn) MSNAccount::setOnlineStatus: "Online" kopete(57073) KopeteWindow::slotIdentityStatusIconChanged: QVariant(, ) kopete(57073)/kopete (msn - raw protocol) MSNSocket::slotReadyWrite: Sending command: "VER 0 MSNP11 MSNP10 CVR0" QIODevice::write: ReadOnly device kopete(57073)/kopete (msn) MSNSocket::slotSocketError: Error: 17 ( "remote host closed connection" ) QObject: Do not delete object, 'unnamed', during its event handler! kopete(57073)/kopete (msn) MSNSocket::slotSocketClosed: Socket closed. kopete(57073)/kopete (msn) MSNAccount::slotNotifySocketClosed: kopete(57073) KopeteWindow::slotIdentityStatusIconChanged: QVariant(, ) kopete(57073)/libkopete Kopete::Account::disconnected: 99 kopete(57073)/kopete (msn) MSNNotifySocket::~MSNNotifySocket: kopete(57073)/libkopete Kopete::FileEngine::FileEngine: "kopete-account-icon:JabberProtocol:atrox%40jabber.ee" kopete(57073)/libkopete Kopete::FileEngine::open: "kopete-account-icon:JabberProtocol:atrox%40jabber.ee"OpenMode( "ReadOnly" ) kopete(57073)/libkopete Kopete::FileEngine::close: kopete(57073)/libkopete Kopete::FileEngine::open: return: true kopete(57073)/libkopete Kopete::FileEngine::FileEngine: "kopete-account-icon:JabberProtocol:atrox%40jabber.ee" kopete(57073)/libkopete Kopete::FileEngine::~FileEngine: "kopete-account-icon:JabberProtocol:atrox%40jabber.ee" kopete(57073)/libkopete Kopete::FileEngine::close: kopete(57073)/libkopete Kopete::FileEngine::~FileEngine: "kopete-account-icon:JabberProtocol:atrox%40jabber.ee"
We've completely replaced the current MSN implementation with a new MSN implementation. If you continue to experience this bug after testing the new implementation (which can be gotten from our subversion repository or with the KDE 4.2 Beta 1 release), PLEASE, open a new bug rather than reopening this bug. Thank you for your time and efforting in helping us find and fix problems in Kopete.
Same error here, kde-base/kopete 4.1.96 gentoo, ~x86, kde-testing overlay. wlm and jabber can login, but yahoo can't,get error : Error Message 17. Remote host closed connection
Comment #2 states the code for MSN has changed and advices retesting. What about other affected protocols. I am unable to connect to Yahoo. I can connect successfully on my home network, but consistently get "Error Message 17. Remote host closed connection" using my company's network. This may suggest DNS is part of the problem. I found this bug: https://qa.mandriva.com/show_bug.cgi?id=45932 However, adding an entry for scs.msg.yahoo.com in /etc/hosts (with nsswitch.conf set to use files first) did not help. Perhaps Yahoo sends further hostnames to the client, provoking addition hostname lookups. If that were the case, then an entry for scs.msg.yahoo.com would only fix initial connection, but not 2nd stage communication. However I don't (yet) know how the Yahoo protocol operates, so that could be far from reality. I can try capturing packets and debugging the client/server communication. Can someone point me to some Yahoo IM protocol documentation to aid debugging? btw, using Kopete from KDE 4.2 on Kubuntu 8.10. Thanks.