Bug 148124

Summary:	kopete doesn't connect to msn, not every time but frequently (I use kwallet)
Product:	[Unmaintained] kopete	Reporter:	Ugo Martiri <ugo.martiri>
Component:	MSN Plugin	Assignee:	Kopete Developers <kopete-bugs-null>
Status:	RESOLVED FIXED
Severity:	normal	CC:	casta
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Ugo Martiri 2007-07-23 01:41:26 UTC

Version:           0.12.4 (using KDE 3.5.6, Kubuntu (feisty) 4:3.5.6-0ubuntu14)
Compiler:          Target: i486-linux-gnu
OS:                Linux (i686) release 2.6.20-16-generic

kopete (msn): WARNING: [void MSNSocket::slotSocketError(int)] Error: 17 (connessione chiusa dall'host remoto)
kopete (msn): WARNING: [QString MSNNotifySocket::statusToString(const Kopete::OnlineStatus&) const] Unknown status 0!
kopete (msn): WARNING: [void MSNSocket::slotSocketError(int)] Error: 17 (connessione chiusa dall'host remoto)

Comment 1 Bram Schoenmakers 2007-08-11 19:16:59 UTC

What do those error messages mean? "Connection closed by remote host?"

Comment 2 Guillaume Castagnino 2007-08-16 10:14:26 UTC

I encounter the same problem from the network at work (not at home strangely)...

when I dump the network traffic I get a RST during the Shield.xml transfert :

1187250016.251719   10.33.1.69 -> 207.46.110.44 MSNMS GCF 5 Shields.xml
1187250016.251901 207.46.110.44 -> 10.33.1.69   TCP 1863 > 39742 [ACK] Seq=934 Ack=519 Win=8187 Len=0
1187250016.410532 207.46.110.44 -> 10.33.1.69   MSNMS GCF 5 Shields.xml 6769
1187250016.410575 207.46.110.44 -> 10.33.1.69   MSNMS <config>
1187250016.410588 207.46.110.44 -> 10.33.1.69   MSNMS   <shield>
1187250016.410595 207.46.110.44 -> 10.33.1.69   MSNMS     <cli maj="7" min="0" minbld="0" maxbld="9999" deny="" />
1187250016.410605 207.46.110.44 -> 10.33.1.69   MSNMS   </shield>
1187250016.410611 207.46.110.44 -> 10.33.1.69   MSNMS   <block>
1187250016.410625 207.46.110.44 -> 10.33.1.69   MSNMS     <hashes>
1187250016.410630 207.46.110.44 -> 10.33.1.69   MSNMS     </hashes>
1187250016.410637 207.46.110.44 -> 10.33.1.69   MSNMS     <regexp>
1187250016.410642 207.46.110.44 -> 10.33.1.69   MSNMS       <imtext value="XC5waWY=" />
1187250016.410650 207.46.110.44 -> 10.33.1.69   MSNMS       <imtext value="XC5zY3I=" />
1187250016.410654 207.46.110.44 -> 10.33.1.69   MSNMS       <imtext value="Z3JvdXBwaWN0dXJlXC5waHA=" />
1187250016.410658 207.46.110.44 -> 10.33.1.69   MSNMS       <imtext value="Z3JvdXBpY3R1cmVcLnBocA==" />
1187250016.410666 207.46.110.44 -> 10.33.1.69   MSNMS       <imtext value="Z2FsbGVyeVwucGhw" />
1187250016.410671 207.46.110.44 -> 10.33.1.69   MSNMS       <imtext value="c3RhZmZcLnBocA==" />
1187250016.410680 207.46.110.44 -> 10.33.1.69   MSNMS       <imtext value="cGljc1wucGhw" />
1187250016.410684 207.46.110.44 -> 10.33.1.69   MSNMS       <imtext value="bXNuXC5waHBcP2VtYWlsPQ==" />
1187250016.410692 207.46.110.44 -> 10.33.1.69   MSNMS       <imtext value="ZG93bmxvYWRcLnBocA==" />
1187250016.410708   10.33.1.69 -> 207.46.110.44 TCP 39742 > 1863 [ACK] Seq=519 Ack=1504 Win=8624 Len=0
1187250016.410716 207.46.110.44 -> 10.33.1.69   MSNMS       <imtext value="eG1hcy0yMDA2" />
1187250016.410721 207.46.110.44 -> 10.33.1.69   MSNMS       <imtext value="bWlyYWxhZm90by9mb3RvXC5leGU=" />
1187250016.410730 207.46.110.44 -> 10.33.1.69   MSNMS       <imtext value="cHJvZmlsZVwucGhwXD8=" />
1187250016.410741 207.46.110.44 -> 10.33.1.69   MSNMS       <imtext value="dHVmb3Rv" />
1187250016.410745 207.46.110.44 -> 10.33.1.69   MSNMS       <imtext value="dmVydGkyL2ZhbnRhc21hXC56aXA=" />
1187250016.410755 207.46.110.44 -> 10.33.1.69   MSNMS       <imtext value="YXJtYXpmaWxlc1wuc210cFwucnU=" />
1187250016.410760 207.46.110.44 -> 10.33.1.69   MSNMS       <imtext value="Y2huc3R1ZGlvXC5jb20vdXBsb2FkL2ltcGx1c2VcLmV4ZQ==" />
1187250016.410767 207.46.110.44 -> 10.33.1.69   MSNMS       <imtext value="dDM1XC5jb20=" />
1187250016.410772 207.46.110.44 -> 10.33.1.69   MSNMS       <imtext value="dmlvdGFnYWxsZXJ5XC5jb20=" />
1187250016.410779 207.46.110.44 -> 10.33.1.69   MSNMS       <imtext value="aW1hZ2UwMDFcLnBuZw==" />
1187250016.410784 207.46.110.44 -> 10.33.1.69   MSNMS       <imtext value="aW1hZ2UwMDJcLmdpZg==" />
1187250016.410795   10.33.1.69 -> 207.46.110.44 TCP 39742 > 1863 [ACK] Seq=519 Ack=2049 Win=8624 Len=0
1187250016.410798 207.46.110.44 -> 10.33.1.69   MSNMS       <imtext value="ZnVuYnVkZHlpY29uc1wuY29t" />
1187250016.410914 207.46.110.44 -> 10.33.1.69   MSNMS       <imtext value="d2VsbHdlbGxcLmJpeg==" />
1187250016.410924 207.46.110.44 -> 10.33.1.69   TCP 1863 > 39742 [FIN, ACK] Seq=2147 Ack=519 Win=8192 Len=0
1187250016.414331   10.33.1.69 -> 207.46.110.44 TCP 39742 > 1863 [FIN, ACK] Seq=519 Ack=2148 Win=8624 Len=0
1187250016.414485 207.46.110.44 -> 10.33.1.69   TCP 1863 > 39742 [ACK] Seq=2148 Ack=520 Win=8192 Len=0
1187250016.568540 207.46.110.44 -> 10.33.1.69   TCP 1863 > 39742 [RST, ACK] Seq=2148 Ack=520 Win=0 Len=0


I have not this problem of connexion resetting at home.
When I comment the Shield.xml request in kopete source code (in msnnotifysocket.cpp), all went OK : the connection works again (of course without transfert of Shield.xml).

When I dump network traffic of pidgin msn connection, I do not see any Shield.xml request. Is this really usefull to get this file ?

Regards,

Comment 3 Matt Rogers 2008-11-15 06:08:59 UTC

We've completely replaced the current MSN implementation with a new MSN implementation which  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.