Version: 0.60.81 (using 4.1.85 (KDE 4.1.85 (KDE 4.2 Beta2)), Kubuntu packages) Compiler: cc OS: Linux (i686) release 2.6.27-9-generic sometimes I want to send a msg to a contact, but it won't send. it will just timeout after long minutes saying the contact could not be reach. then my other co-working is asking me: "aren't you not online?" kopete looks online, my contact list is all online looking. but people see my as offline and I can't send messages. I need to disconnect and reconnect.
(In reply to comment #0) > Version: 0.60.81 (using 4.1.85 (KDE 4.1.85 (KDE 4.2 Beta2)), Kubuntu > packages) > Compiler: cc > OS: Linux (i686) release 2.6.27-9-generic > > sometimes I want to send a msg to a contact, but it won't send. > it will just timeout after long minutes saying the contact could not be reach. > > then my other co-working is asking me: "aren't you not online?" > > kopete looks online, my contact list is all online looking. but people see my > as offline and I can't send messages. > > I need to disconnect and reconnect. > I can confirm, same behaviour as the one described. I'm using kubuntu kde 4.2 rc1, kopete 0.60.82, Linux 2.6.27-11-generic. Kopete goes offline often while still appearing online. Sometimes, instead, while you are still online and chatting to someone, you appear offline to other users.
I can confirm this also. Using kopete 0.70.0 with libmsn 4.0-beta4 under FreeBSD
I can confirm this, using ubuntu/kubuntu 8.10 with all updates from backports and proposed, using Kopete Version 0.70.0 with KDE 4.2.00 (KDE 4.2.0).
*** This bug has been confirmed by popular vote. ***
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. CCBUG: 180058 M +17 -1 libkopete/kopetesockettimeoutwatcher.cpp M +7 -1 libkopete/kopetesockettimeoutwatcher.h M +7 -2 protocols/oscar/oscaraccount.cpp M +25 -15 protocols/wlm/wlmaccount.cpp M +16 -9 protocols/wlm/wlmaccount.h M +13 -2 protocols/wlm/wlmlibmsn.cpp M +5 -0 protocols/wlm/wlmlibmsn.h M +14 -10 protocols/wlm/wlmserver.h M +2 -1 protocols/wlm/wlmsocket.h WebSVN link: http://websvn.kde.org/?view=rev&revision=970799
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). BUG: 180058 M +66 -37 wlmsocket.cpp M +19 -11 wlmsocket.h WebSVN link: http://websvn.kde.org/?view=rev&revision=970816
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
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 170849 has been marked as a duplicate of this bug. ***