Comment 9 for bug 1223436

(In reply to comment #1)
> The only thing that I could
> get to trigger was if I set the 'Resource' in advanced configuration to
> 'laptop'. If I removed 'Resource' or changed it to '/laptop', then it
> worked. [...] I can say that perhaps it would be reasonable
> for empathy/telepathy-gabble to prepend a '/' to the Resource if it isn't
> present."

XMPP resourceparts (names of resources - the "resource" parameter in Telepathy) are not normally meant to start with "/". If you can only connect with resource omitted or set to start with "/", then something is wrong. Have you tried setting it to a string not starting with "/" but not equal to "laptop"?

If you set the resourcepart to "laptop", your full JID would be something like "<email address hidden>/laptop" - the / delimiter is part of the syntax, not part of the resourcepart. Similarly, if you set the resource to "/laptop", you would end up with the unconventional full JID "<email address hidden>//laptop" (I think - the second / might get escaped somehow, I can't remember what the syntactic restrictions are).

Do you have other XMPP clients connected to the same account? Might one of them have its resourcepart set to "laptop" too?

If you're able to create and delete disposable accounts on a jabberd2 server, it might be interesting to see the uncensored SASL handshake for an account with a known username, password and resourcepart, to be able to verify that the handshake is done correctly according to RFC6120 and RFC2831.