Kopete connection keeps getting closed talking to MSN official client

Bug #53336 reported by Matt
4
Affects Status Importance Assigned to Milestone
Kopete
Fix Released
Medium
kdenetwork (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

In Kopete version 3.5.2-0ubuntu6, if I try and talk to any of my contacts over MSN who are using the official Microsoft client on WIndows, I keep getting a message of the form;

<Username> has left the chat (connection closed).

appear in the conversation window (where <username> is the contact name). This happens when I try and talk to any of my contacts who are using the Microsoft client.

My work colleagues are also seeing this problem on their installations of Kubuntu.

Revision history for this message
Matt (matt-madskills) wrote :

This problem is also seen if the other contact is using Trillian on Windows.

Revision history for this message
Matt (matt-madskills) wrote :

I have reported this upstream in the KDE bug tracker as bug ID 132002

Revision history for this message
Sarah Kowalik (hobbsee-deactivatedaccount) wrote :

There used to be a bug about this - it's upstream, and it dealt with the way msn handles connections, if i recall correctly. I might try to find that later, and see what the solution was.

I dont seem to see this in kopete 0.12 versions....did it go away, or have I learned to ignore it?

Revision history for this message
Matt (matt-madskills) wrote :

I re-compiled v0.12 from source and was still getting this problem. I think it is an interaction between our company firewall and Kopete. The firewall doesn't seem to affect any other clients, like Gaim, Trillian or Microsoft's client though.

Changed in kopete:
status: Unknown → Unconfirmed
Revision history for this message
Sarah Kowalik (hobbsee-deactivatedaccount) wrote :

please file this bug upstream, with kopete, help, file bug. Assuming it's not your firewall to blame.

Revision history for this message
Sarah Kowalik (hobbsee-deactivatedaccount) wrote :

er, sorry. i should learn to read.

Revision history for this message
Jérôme Guelfucci (jerome-guelfucci-deactivatedaccount) wrote :

Do you still have this issue with the latest release of Ubuntu ?

Changed in kdenetwork:
importance: Undecided → Medium
status: Unconfirmed → Needs Info
Revision history for this message
Reinier Boon (rtboon) wrote :

Yes, the bug is still present in Kopete on ubuntu...

Changed in kdenetwork:
status: Incomplete → Triaged
Revision history for this message
Daniel T Chen (crimsun) wrote :

Is this symptom still reproducible in 8.10 alpha?

Changed in kdenetwork:
status: Triaged → Incomplete
Revision history for this message
Matt (matt-madskills) wrote :

Unfortunately I no longer work at the same company, so am unable to reproduce this bug any more as I don't have access to the network with the troublesome firewall.

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

According to comments in the upstream support this is still an issue.

Changed in kdenetwork:
importance: Medium → Low
status: Incomplete → Triaged
Changed in kopete:
status: New → Fix Released
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Fix committed for KDE 4.2.

Changed in kdenetwork:
milestone: none → ubuntu-9.04
status: Triaged → Fix Committed
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Fix released to Jaunty. (As well as Intrepid via the kubuntu-experimental ppa packages)

Changed in kdenetwork:
milestone: ubuntu-9.04 → jaunty-alpha-4
status: Fix Committed → Fix Released
Changed in kopete:
importance: Unknown → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.