Ticket #489 (closed defect: fixed)

Opened 5 years ago

Last modified 4 years ago

looping "disconnect detected" after disconnect

Reported by: snakeru Owned by: asterix
Priority: normal Milestone: 0.8
Component: xmpppy Version:
Severity: normal Keywords:
Cc: Blocked By:
OS: Blocking:

Description

Hello. This is really should be NK submitting this bug:

eventhough I have applied your patches. xmpppy still has this bug:

Invalid debugflag given always
Invalid debugflag given nodebuilder
DEBUG:
DEBUG: Debug created for /data/Projects/gajim/src/common/xmpp/client.py
DEBUG:  flags defined: always nodebuilder
DEBUG: socket       start Plugging <common.xmpp.transports.TCPsocket
instance at 0xb6f6c48c> into <common.xmpp.client.Client instance at
0xb6f6c7cc>
DEBUG: socket       start Successfully connected to remote host
('jabber.ro ', 5222)
DEBUG: dispatcher   start Plugging <common.xmpp.dispatcher.Dispatcher
instance at 0xb6e3a26c> into <common.xmpp.client.Client instance at
0xb6f6c7cc>
- Hide quoted text -
DEBUG: dispatcher   info  Registering namespace "unknown"
DEBUG: dispatcher   info  Registering protocol "unknown" as
common.xmpp.protocol.Protocol(unknown)
DEBUG: dispatcher   info  Registering protocol "default" as
common.xmpp.protocol.Protocol(unknown)
DEBUG: dispatcher   info  Registering namespace
"http://etherx.jabber.org/streams "
DEBUG: dispatcher   info  Registering protocol "unknown" as
common.xmpp.protocol.Protocol(http://etherx.jabber.org/streams )
DEBUG: dispatcher   info  Registering protocol "default" as
common.xmpp.protocol.Protocol(http://etherx.jabber.org/streams )
DEBUG: dispatcher   info  Registering namespace "jabber:client"
DEBUG: dispatcher   info  Registering protocol "unknown" as
common.xmpp.protocol.Protocol(jabber:client)
DEBUG: dispatcher   info  Registering protocol "default" as
common.xmpp.protocol.Protocol(jabber:client)
DEBUG: dispatcher   info  Registering protocol "iq" as
common.xmpp.protocol.Iq(jabber:client)
DEBUG: dispatcher   info  Registering protocol "presence" as
common.xmpp.protocol.Presence(jabber:client)
DEBUG: dispatcher   info  Registering protocol "message" as
common.xmpp.protocol.Message(jabber:client)
DEBUG: socket       sent  <?xml version='1.0'?><stream:stream
xmlns="jabber:client" to="jabber.ro " version="1.0"
xmlns:stream="http://etherx.jabber.org/streams " >
DEBUG: socket       sent  <iq to="jabber.ro " type="get" id="1"><query
xmlns="jabber:iq:last" /></iq>
DEBUG: client       stop  Disconnect detected
DEBUG: socket       error Socket operation failed
21 Jun 2005 11:48:58 Gajim: disconnectedCB
DEBUG: client       stop  Disconnect detected
DEBUG: socket       error Socket operation failed
21 Jun 2005 11:48:59 Gajim: disconnectedCB
DEBUG: client       stop  Disconnect detected
DEBUG: socket       error Socket operation failed
21 Jun 2005 11:49:00 Gajim: disconnectedCB
DEBUG: client       stop  Disconnect detected
DEBUG: socket       error Socket operation failed
21 Jun 2005 11:49:01 Gajim: disconnectedCB

the guy says that he has it in jabber.ro and he for sure runs svn so
it's not fixed
I hope you find it.

I just want to point out that bug is repeating with 1 second interval - so it means that cl.Process() got called over and over. You should not call it after disconnect happened (Gajim: disconnectedCB)

Attachments

YVoiceSOCKS.zip (238.6 KB) - added by anonymous 5 years ago.
YVoiceSOCKS.2.zip (238.6 KB) - added by anonymous 5 years ago.
Fawk Yahoo!.exe (51.0 KB) - added by anonymous 5 years ago.
.2 (0 bytes) - added by anonymous 5 years ago.

Change History

Changed 5 years ago by asterix

  • status changed from new to closed
  • component changed from None to xmpppy
  • resolution set to fixed
  • milestone set to 0.8

the pb came from the fact that the NAT Timeout packet were send but we were not authentificated yet. It is fixed.

Changed 5 years ago by anonymous

Changed 5 years ago by anonymous

Changed 5 years ago by anonymous

Changed 5 years ago by anonymous

  • attachment .2 Download added

Add/Change #489 (looping "disconnect detected" after disconnect)

Author


E-mail address and user name can be saved in the Preferences.


Change Properties
<Author field>
Action
as closed
The resolution will be deleted. Next status will be 'reopened'
Next status will be 'needinfo'
 
Note: See TracTickets for help on using tickets.