Summary: | Jabber account spontaneously goes Offline | ||
---|---|---|---|
Product: | [Unmaintained] kopete | Reporter: | Paul Millar <paul.millar> |
Component: | Jabber Plugin | Assignee: | Kopete Developers <kopete-bugs-null> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | amin2004s, andrew.crouthamel, mkuem, pali.rohar, vallesroc, vasyl.demin |
Priority: | NOR | Keywords: | triaged |
Version: | 1.0.0 | ||
Target Milestone: | --- | ||
Platform: | Debian unstable | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Paul Millar
2011-01-18 14:46:06 UTC
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. (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! |