gajim trace back when trying to contact ejabberd with a wrong configuration
At work, the firewall do not let me do jabber directly, so i use a ssh tunnel to the server, and use localhost to connect, like this :
ssh -L 5222:localhost:5222 jabber.example.org
So, in gajim config, i have a account with custom_host set to localhost, and this is working fine.
After reboot of my computer, gajim was no longer working for this account. The icon was spinning, trying to connect without succeeding.
After some search, I found the root of the problem, some test ejabberd was running on my workstation, set to use a different domain ( like localhost ), so gajim was connected to the wrong server and was using wrong credential for the jid part.
Ejabberd closed the connection, but it seems that gajim didn't see it.
In the console, i have seen this backtrace :
Traceback (most recent call last):
File "/home/misc/checkout/svn/gajim/src/common/xmpp/idlequeue.py", line 133, in process_events
obj.pollin()
File "/home/misc/checkout/svn/gajim/src/common/xmpp/transports_nb.py", line 144, in pollin
self._do_receive()
File "/home/misc/checkout/svn/gajim/src/common/xmpp/transports_nb.py", line 242, in _do_receive
self.on_receive(received)
File "/home/misc/checkout/svn/gajim/src/common/xmpp/client_nb.py", line 143, in _on_receive_document_attrs
self.onreceive(None)
AttributeError: NonBlockingClient instance has no attribute 'onreceive'