Bug 285803

I have two WLM accounts and I have the same experience with one of them. It keeps "connecting" forever and if I quit Kopete or disconnect the WLM plugin, it then tells me that it cannot reach the WLM server.

With the other account it works normally. I don't know if it helps, but the account that doesn't connect is a passport account (not a hotmail.x or msn.x).

Pidgin, emesene, empathy are connecting normally with both accounts.

Mine is a Passport account too.

Kopete
Versión 1.1.2
KDE 4.7.2 (4.7.2)

Packet sniffing with wireshark reveals kopete to be using msnp15 which does not work.  Packet sniffing empathy which does work reveals it to be using msnp18

Both were tested on the same OpenSuse 11.4 stable platform. 

Kopete also does not work on Opensuse 12.1 rc 1 but empathy does 

All testing on the same IP network with the same public address

Are M$oft blocking clients using msnp15 ?? kopete worked until 2/11/2011 on both OpenSuse11.4 stable and O-S1 2.1 rc1

using KDE4.7 on all platforms they are all 64bit

Hello!

Linux version: Linux 2.6.32-34-generic #77-Ubuntu SMP Tue Sep 13 19:40:53 UTC 2011 i686 GNU/Linux (Kubuntu)

KDE 4.4.5, Kopete 1.0.0

Same Problem here, no connect to msn since 2.November 2011. Pidgin connects without any problems.

Guido

I have the same problem.

Opensuse 11.4, Kopete 1.1.3.

I using emesene temporarily

same behaviour here with kubuntu 11.10 64bit
KDE 4.7.2
kopete 1.1.2

*** This bug has been confirmed by popular vote. ***

Same thing with KDE 4.7.3 and Kopete 1.1.3.

It affects me too. 
KDE 4.7.3 on Kubuntu 11.10

I have the same problem with a Passport account.
KDE 4.7.2
Kopete 1.1.2

The WLM account stays "connecting" forever.

same problem . . . 
my account ceruleanbluefab@hotmail.com

KDE 4.7.2
Kopete 1.1.2

The WLM account stays "connecting" forever. 
 
If I quit kopete or disconnect the WLM plugin, it then tells me that it cannot
reach the WLM server

Reproducible: Always

Steps to Reproduce:
Log to your wlm account

Actual Results:  
Keeps being in "connecting" status

Expected Results:  
Should be in "connected" status

emesene too

not only kopete has this issue.  kmess(.org) had it also... (but they allready got it fixed)

This looks like a bug in libmsn, that it doesn't handle redirects. WLM changed
and now is redirecting some HTTP(s) requests.

Kmess guys have a patch here:
http://kmess.org/board/viewtopic.php?f=4&t=20549

Also in libmsn:
http://sourceforge.net/mailarchive/message.php?msg_id=28327555

Same here, kubuntu 11.10 and 
Qt: 4.7.4
KDE Development Platform: 4.7.3 (4.7.3)
Kopete: 1.1.3

I did not get emesene to connect either, but pidgin connected.

Using libmsn's msntest program I get status code 200 during login request, which means no redirection. Probably the redirection comes from a different request and that is a big problem because libmsn only supports redirection in login requests while kmess reports it in any request.

Hi,
Just committed a fix in libmsn svn. It works on my msn account.
Can anybody checkout [1], compile and give some feedback so then I can release a new version?

Thank you.

[1] - https://libmsn.svn.sourceforge.net/svnroot/libmsn/trunk

I have been having this problem myself and the latest commit you pointed to has fixed the problem for myself and at least one other friend with the same problem. I have also patched the Fedora packages of libmsn and submitted them there as testing updates so they can be tested by a wider audience.

I'm having the same problem on Debian testing, Kopete 1.0.80 (KDE 4.6.5), libmsn 4.1-3. I also noticed this a couple of days ago. My address is zaq@fuckhotmail.com. This also seems to affect other addresses I tried, one on yahoo.fr and one on hotmail.com.

The problem I noticed is that Kopete continually uses CPU (from 1 to 10%). Apparently CPU usage increases with time. I only noticed today that MSN was not connected, but trying to connect.

The patch works for me also and I have patched Mageia packages and will get the
fix into Mandriva too.

Thanks.

There is an update in testing for Fedora users: http://koji.fedoraproject.org/koji/buildinfo?buildID=273046

Hi all,

just released libmsn 4.2 with the proper fix. Can any package maintainer test it and give some feedback?

Thank you.

(In reply to comment #22)
> Hi all,
> 
> just released libmsn 4.2 with the proper fix. Can any package maintainer test
> it and give some feedback?

Rebuilt with the new upstream release (we already carried all the commits up to the new release so no real changes) and everything is still working as expected. Modified Fedora updates based on the new release are in progress.

Ok too for Mageia packages, a patched version of 4.1 update for mga1 is already on QA testing and cauldron (development version) has been updated to 4.2. Mandriva packages are being updated too.

A friend confirmed he was also experiencing the problem using his account on videotron.ca, using Debian stable's Kopete.

I reported the problem against Debian's libmsn in #648134.

Patch works just fine in OpenSuse11.4 stable thanks guys ,built from source no rpm to try yet.

I'm working on the Debian packages already

Applying the updated soap.h and soap.cpp and recompiling the ubuntu libmsn 4.1 in kubuntu 11.10 solves the problem for me.

However, the one who reported the ubuntu bug at launchpad says that this does not help.

https://bugs.launchpad.net/ubuntu/+source/libmsn/+bug/887104

*** Bug 286265 has been marked as a duplicate of this bug. ***

Closing this bug as upstream since the problem is in libmsn, not Kopete.

libmsn's developers already released a fix, so upgrade it to libmsn 4.2 and everything should work.

To the packagers subscribed to this report (and Tiago, of course ;) -- libmsn 4.2 seems to be broken in the sense that soap.h includes xmlParser.h which is not installed. This effectively breaks the kdenetwork build.

I've worked around the problem by simply adding xmlParser.h to msn_HEADERS in msn/CMakeLists.txt, but I'm not sure if Tiago intended xmlParser.h to be installed by libmsn, as it is third-party code.

*** Bug 286530 has been marked as a duplicate of this bug. ***

(In reply to comment #31)
> To the packagers subscribed to this report (and Tiago, of course ;) -- libmsn
> 4.2 seems to be broken in the sense that soap.h includes xmlParser.h which is
> not installed. This effectively breaks the kdenetwork build.
> 

True, this is the error message:

In file included from /usr/include/msn/notificationserver.h:36:0,                                                                                    
                 from /usr/include/msn/msn.h:33,
                 from /home/juancho/kde/kdenetwork/kopete/protocols/wlm/wlmsocket.h:22,
                 from /home/juancho/kde/kdenetwork/kopete/protocols/wlm/wlmlibmsn.h:21,
                 from /home/juancho/kde/kdenetwork/kopete/protocols/wlm/wlmserver.h:20,
                 from /home/juancho/kde/kdenetwork/kopete/protocols/wlm/wlmaccount.h:24,
                 from /home/juancho/kde/kdenetwork/kopete/protocols/wlm/ui/wlmeditaccountwidget.cpp:33:
/usr/include/msn/soap.h:38:23: fatal error: xmlParser.h: No such file or directory

(In reply to comment #31)
> To the packagers subscribed to this report (and Tiago, of course ;) -- libmsn
> 4.2 seems to be broken in the sense that soap.h includes xmlParser.h which is
> not installed. This effectively breaks the kdenetwork build.
> 
> I've worked around the problem by simply adding xmlParser.h to msn_HEADERS in
> msn/CMakeLists.txt, but I'm not sure if Tiago intended xmlParser.h to be
> installed by libmsn, as it is third-party code.

The Debian package is patched to install xmlParser.h

Because the fix to avoid installing it requires an API change that is ABI-incompatible and there has been no answr from Tiago.

(In reply to comment #34)
> The Debian package is patched to install xmlParser.h
> 

Do you refer to the workaround posted in comment #31 ? I ask so I can fix Mageia/Mandriva packages too.

(In reply to comment #35)
> (In reply to comment #34)
> > The Debian package is patched to install xmlParser.h
> 
> Do you refer to the workaround posted in comment #31 ? I ask so I can fix
> Mageia/Mandriva packages too.

Yes, that's what I'm doing. You can see the patch here:

http://patch-tracker.debian.org/package/libmsn/4.2-1

The other alternative is explained here:

http://thread.gmane.org/gmane.network.instant-messaging.libmsn.general/114/focus=115

(In reply to comment #5)
> Hello!
> 
> Linux version: Linux 2.6.32-34-generic #77-Ubuntu SMP Tue Sep 13 19:40:53 UTC
> 2011 i686 GNU/Linux (Kubuntu)
> 
> KDE 4.4.5, Kopete 1.0.0

Got a new msnlib via KPackageKit and it works. Thank you.

Hi,

I have released libmsn 4.2.1.
Can anybody test to make sure it fixes the missing header?

Thanks.

(In reply to comment #38)

> I have released libmsn 4.2.1.
> Can anybody test to make sure it fixes the missing header?

Why are you installing the header? Wouldn't be easier just forward declaring XMLNode, as I said in the libmsn mailing list?

http://article.gmane.org/gmane.network.instant-messaging.libmsn.general/115

Hi,

your idea is good, but IMO it is better to include the header and avoid similar problems in the future. I see no problem installing the header though.