Version: (using Devel) OS: Linux Installed from: Compiled sources i am using kde 4.2 beta5 kopete with wlm plugin. it can connect properly and show my contacts. but after a while ( 1 minute or so ) it just stops updating them. if i connect with amsn or another app to the same account, kopete just keeps me showing as online on kopete. also online contacts that go offline or offline contacts that go online arent shown.
Created attachment 29408 [details] as you can see , i have the msn account online in amsn, but kopete still shows as the same account online first i connected with kopete. the , after 1 minute or so , i connected with amsn. its been 5 minutes or so , and kopete still shows the account as online.
I have the same problem. When I login I can change my status but after some minutes (1 or two) the wlm account "freezes", the account goes offline but the status shown in kopete is the one before the freeze. I have instaled KDE 4.2 from openSUSE repos. I updated libmsn to 4.0 beta4 but bug is still there.
I have the same problem except that for me Kopete takes much more than a minute to behave like that, several hours actually. People, if you want the developers to take attention to this bug please vote for it on the top of this page.
By the way, I use KDE 4.2.0 with Gentoo (profile amd64/2008.0/desktop) on a AMD64 notebook.
Same problem here after a reconnect, Jabber goes offline and doesn't reconnect, ICQ reconnects with status online (even if it wasn't online before) and msn keeps online for kopete, but you can't send or receive messages.
I have replicated this bug using the msntest application that comes with libmsn-4.0-beta4. I performed the following: 1. Logged on and connected to MSN server. 2. Set status as available (status NLN). Status reported as changed. 3. Observed contact status updates for a couple of minutes. 4. Tried to set status to away (status AWY). It failed and reported no error. 5. Tried to set status to away again. This time it printed the error 'MSN: Error: Error on socket'. So I think its fairly safe to say this is a bug in libmsn and not kopete or the WLM plugin.
I've done a bit more digging and it appears that neither libmsn, nor the kopete wlm plugin, actually ensure that the wlm connection is maintained as open using the using keep alive or ping commands. A quick and dirty hack with the msntest application shows that by adding in the msn ping commands on a 110sec timer fixes this issue.
SVN commit 970799 by rjarosz: Add SocketTimoutWather to wlm and also implement error detection. We still need some ping packet to be sent otherwise the timeout will only be detected when user interacts with wlm. SVN commit 970816 by rjarosz: Send keep alive packet so we know when we aren't connected anymore. Dropped connection will be detected at most in 65 seconds (on Linux).
Well, it works, I mean, the patch makes Kopete reconnects when it thinks the connection is broken. But the reconnections are too often, once in less than 10 minutes, one of my contacts even complaint that I was reconnecting too often. Is that also happening with other people using this patch?
SVN commit 972308 by rjarosz: If we get socket error for not main connection just close that connection and not all connections. CCBUG: 180058 CCBUG: 178053 M +14 -6 wlmlibmsn.cpp M +6 -0 wlmsocket.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=972308
Hi all, commit 97230 seems to solve the reconnect-too-often problem. Thanks :-)
SVN commit 974235 by rjarosz: Backport commits 972308, 970816, 970799 without the SocketTimoutWather. This will keep wlm connection alive and will catch socket errors and automatically reconnect. CCBUG: 180058 CCBUG: 178053 M +25 -15 wlmaccount.cpp M +16 -9 wlmaccount.h M +21 -2 wlmlibmsn.cpp M +5 -0 wlmlibmsn.h M +14 -10 wlmserver.h M +66 -37 wlmsocket.cpp M +20 -11 wlmsocket.h WebSVN link: http://websvn.kde.org/?view=rev&revision=974235
*** Bug 188469 has been marked as a duplicate of this bug. ***
*** Bug 190828 has been marked as a duplicate of this bug. ***