Stuck connecting, invalid slot type
Status: Alpha
Brought to you by:
scymtym
Menu
▾
▴
#20 Stuck connecting, invalid slot type
Hi, with Rudel Bazaar commit 632 (2011-07-21) and GNU Emacs 24.3.1 from Debian
unstable, I try to connect to a local infinoted 0.5.5 daemon with
--security-policy=no-tls using the infinoted protocol and xmpp
backend to the valid localhost server and 6523 port (I checked it
works with Gobby 0.5). I get a / Connecting (negotiate-stream) message
(with the rotating bar) and it gets stuck in that point until I hit C-g.
The message buffer shows the following:
Loading /home/ivan/vc/bzr/rudel/rudel-loaddefs.el (source)...done
Discovering Sessions ... Initializing Zeroconf ... Discovering Sessions
... error in process filter: eieio-validate-slot-value: Invalid slot
type: rudel-assembling-transport-filter, buffer, list, "" error in process
filter: Invalid slot type: rudel-assembling-transport-filter, buffer,
list, "" Quit
When I dump traffic to port 6523 I get this:
(Rudel to infinoted) <?xml version="1.0" encoding="UTF-8"?> <stream:stream
xmlns:stream="http://etherx.jabber.org/streams" xmlns="jabber:client"
version="1.0" to="localhost" id="ivan@elvil.net">
(infinoted to Rudel) <stream:stream
xmlns:stream="http://etherx.jabber.org/streams" xmlns="jabber:client"
version="1.0" from="sax"><stream:features><mechanisms
xmlns="urn:ietf:params:xml:ns:xmpp-sasl"><mechanism>ANONYMOUS</mechanism></mechanisms></stream:features>
And nothing else happens. By sniffing the connection with the Gobby client,
the client should now send something like this:
<auth xmlns="urn:ietf:params:xml:ns:xmpp-sasl"
mechanism="ANONYMOUS"/><challenge
xmlns="urn:ietf:params:xml:ns:xmpp-sasl"/><response
xmlns="urn:ietf:params:xml:ns:xmpp-sasl">SXZhbg==</response><success
xmlns="urn:ietf:params:xml:ns:xmpp-sasl"/><stream:stream version="1.0"
xmlns="jabber:client" xmlns:stream="http://etherx.jabber.org/streams"
to="sax.local">
But I guess nothing gets sent by Rudel because of the error above. I guess it
isn't a problem in protocol implementation, but maybe just some later change
in EIEIO (I have version 1.4), but I have insufficient knowledge about Emacs
Lisp or EIEIO to debug myself.
Thanks for your work, having such a collaborative tool working with Emacs
would be a real boon! :)
