Bug 134558

Summary:	WARNING: void MSNSocket slotSocketError
Product:	[Unmaintained] kopete	Reporter:	TheLinuxFr <thelinux>
Component:	general	Assignee:	Kopete Developers <kopete-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	crash
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description TheLinuxFr 2006-09-23 20:15:04 UTC

Version:           0.12.2 (using KDE KDE 3.5.4)
Installed from:    Ubuntu Packages
OS:                Linux

kopete (msn): WARNING: [void MSNSocket::slotSocketError(int)] Error: 17 (connexion fermée par la machine distante)

Kopete 0.12.2

Comment 1 Philip Rodrigues 2006-09-23 23:25:28 UTC

Please explain what happened and give the steps required to reproduce the problem.

Comment 2 Julien Hillairet 2006-10-03 20:46:55 UTC

I have the same bug (today!). This bug happen each times I try to connect to MSN. Additionnally, I have the error message (in french) :

"Erreur MSN non gérée, code d'erreur 403.
Veuillez remplir un rapport de bogue avec une description détaillée et si possible la dernière sortie de débogage de la console."

Comment 3 Jeremy Bowers 2006-10-03 21:48:07 UTC

I am also seeing this, starting yesterday evening. I'm doing anything other than trying to connect with a previously-working account and no software changes on 0.11.3. I am in the Michigan area, if the server I am connecting to matters.

Gaim is also not working for me anymore, so I'm thinking it might be a protocol change.

For both gaim and kopete, when I connect with a Windows machine and try to connect in Linux, it connects enough to kick me off my Windows account, so it's not completely broken, just enough to not work.

I'm getting the same error messages, albeit in English.

I can provide a tcpdump of my session if needed.

Comment 4 Philip Rodrigues 2006-10-15 00:07:16 UTC

Is this still happening for anyone? There were problems with the MSN server around about 2006-10-03, which may have been the cause, but they're fixed now

Comment 5 Julien Hillairet 2006-10-15 10:15:21 UTC

For me, it is ok now. It may have been this MSN server problem.

Comment 6 Philip Rodrigues 2006-10-16 23:56:52 UTC

OK, sounds like that's all it was, but please do reopen if you can still reproduce the problem