Version: 1.0.0 (using KDE 4.4.5) OS: Linux I have an account with jabber.org that I use with Kopete. What I do and see (both in Kopete and tcpdump): 1) right-click on my jabber.org account and choose "Online" status 2) there's an initial flurry of messages (traffic observed in tcpdump, messagtes observed in XML Console) 3) the status of the Jabber.org account becomes "Online"; 4) kopete updates its internal state and shows various accounts (those accessible via Jabber.org) as being on-line; 5) there's a pause for a few seconds (10s--30s); 6) everyone (accessible via jabber.org account) "disappears" from kopete 7) the Jabber.org account status changes to "Offline" The accounts "disappear" because I have Kopete configured so offline accounts are not shown; if I change Kopete configuration so it also shows offline accounts then I see still these accounts. Sometimes going-Online-then-Offline process loops: after the Jabber.org account spontaneously switches to Offline, kopete spontaneously switches back to online again. The "Online" is, again, short-lived and flips back of "Offline" after a few seconds. This looping behaviour is rare, I have only observed it once. The XML Console shows many messages from jabber.org. The last one before the status becomes Offline is: <presence from="paul@jabber.org/Kopete-work" type="unavailable" to="paul@jabber.org/Kopete-work"/> Note that this "<presence/>" message is coming *from* jabber.org server. It seems that this message is received by kopete and kopete updates its status to match by switching offline. Some further information: the TCP connection is not broken: neither end sends a FIN or RST packet. jabber.org continue to send messages to kopete after kopete has marked the account as offline. These messages appear in the XML Console. It could be that the jabber.org server is in error in sending the message: <presence from="paul@jabber.org/Kopete-work" type="unavailable" to="paul@jabber.org/Kopete-work"/> I don't know XMPP well enough to say; however, even if it is, IMHO kopete should be robust against this kind of bug. Reproducible: Always Steps to Reproduce: Right-click on the Jabber.org account; select "Online" status; wait. Actual Results: Observe kopete updating its knowledge of whether people are currently online (people appear in kopete's main window) After a few (10--30) seconds, these people disappear and the Jabber.org account shows offline. Expected Results: Jabber.org account stays online. OS: Linux (i686) release 2.6.35.2 Compiler: cc
Same problem, Arch Linux x86_64, KDE 4.6.1, kopete 1.0.80
My problem is with jabber.org, I haven't tried connect to other servers.
I have exactly the same behaviour since about a week. The message, which makes my account go offline is the following: <presence from="myid@jabber.org/Kopete" type="unavailable" to="myid@jabber.org/Kopete"/> Very interesting: Kopete shows my account as offline, nevertheless I got messages from other people via jabber. Only I myself could not send messages. Sometimes after half an hour the connection gets stable.
Same here, with equivalent xml as comment 3.
(In reply to comment #4) > Same here, with equivalent xml as comment 3. ... with 4.8.2.
same problem with Kopete on Ubuntu 12.04! Jabber account goes offline after some 10 min of running fine!
In KDE 4.11 Kopete has new version of libiris xmpp library. Please check if this problem still exists.
I'm using Debian sid, which currently has KDE v4.10.5: paul@zitpcx6184:~$ dpkg-query -W *kopete* kopete 4:4.10.5-3 libkopete4 4:4.10.5-3 However, as v4.11 is pushed into sid, I should be able to provide some feedback. However, there's a couple of problems: a) the problem was sporadic, and could go many months before reoccuring. b) the problem appears to be triggered by the jabber server (in my case, jabber.org) sending a (seemingly incorrect) presence XML statement, as mentioned above. This could be a bug in their software, which may now be fixed. So, even once 4.11 is in sid and I'm using it without experiencing any problems, I'm not convinced that the problem could be confirmed as fixed. One way to really test if the problem is fixed would be to run a test jabber server that has been modified so it sends the problematic <presence /> statement and see if the jabber client goes offline -- either a real server or to simulate this via some kind of unit test. HTH, Pau.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
I currently have kopete v4.14 installed: paul@celebrimbor:~$ dpkg-query -W *kopete* kopete 4:4.14.1-2 libkopete4 4:4.14.1-2 paul@celebrimbor:~$ The problem appears to have gone away. However, I cannot say whether this is because the new software version or because the jabber.org server has changed its behaviour.
Great, thanks for the update!