My favorites | Sign in
Project Home Downloads Wiki Issues Source
READ-ONLY: This project has been archived. For more information see this post.
Search
for
  Advanced search   Search tips   Subscriptions
Issue 10: I'm staying online after quit my client
  Back to list
Status:  Invalid
Owner:  jadest...@gmail.com
Closed:  Jan 2008


 
Reported by jadest...@gmail.com, Dec 9, 2007
 Posted by Kepi at 2006-01-16 16:28:18

Sometimes I'm online after close my client. I have same report from one of my
users. I can't find conditions why this is happening... 

Posted by jadestorm at 2006-01-16 17:30:39

Hrm.  The only situation I can think of where that would happen regularly is if
you don't actually have the transport in your roster, in which case you never
send a "I'm going offline" message to the transport.  (So the
transport never knows you've left)  Can you verify that the transport is in
your
roster?

Posted by jadestorm at 2006-02-03 22:44:27

Are you using Pandion?  I keep seeing this happen with Pandion.

Posted by guest at 2006-02-21 15:07:49

I'm using gajim and I'm experiencing the same problem
(http://trac.gajim.org/ticket/1594). Will update to current svn this evening 
and test if the problem still exists. No idea if this is a client or a
transport-problem. But I think it's client-side, becaus it just happes if I'm
using gajim.

Posted by jadestorm at 2006-02-21 15:17:45

I think I may need to work on a way for PyICQ/PyAIM to "ping" the
client and make sure it's still there, and sever the connection if not.  I
think
that would help a lot of these issues.  Regardless, I'd like to be able to
see a
tcpdump communicate between the transport and the jabber server when this is
going on to see what's being passed, what might be being ignored, etc.

Posted by Z_God at 2006-11-01 13:38:48

This happened to me too I think. It might be possible that my client crashed
then.

I received the messages people sent me after I logged on similar as if I would
receive other messages sent to me when I'm offline on Jabber. (Seemed quite
neat
actually :)


Jan 19, 2008
Project Member #1 d...@jabber.fsinf.de
Seems to be a generic Jabber protocol problem that's partially addressed by c2s
heartbeat.
Status: Invalid

Powered by Google Project Hosting