| Summary: | telepathy-gabble 0.18 does not work with jabberd2 | ||
|---|---|---|---|
| Product: | Telepathy | Reporter: | Sebastien Bacher <seb128> |
| Component: | gabble | Assignee: | Telepathy bugs list <telepathy-bugs> |
| Status: | RESOLVED MOVED | QA Contact: | Telepathy bugs list <telepathy-bugs> |
| Severity: | normal | ||
| Priority: | medium | ||
| Version: | unspecified | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
|
Description
Sebastien Bacher
2013-11-05 19:42:39 UTC
I commented in the Ubuntu bug: "I had troubles connecting again. I ended up upgrading to 0.18.1-1ubuntu2, deleting the offending account and recreating it. I was then able to connect. I then tried to reproduce the error. 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't recall if I had the '/' before or not.... At this point, I'm probably not going to be able to reproduce the bug since I'm not sure what my previous configuration was. I can say that perhaps it would be reasonable for empathy/telepathy-gabble to prepend a '/' to the Resource if it isn't present." (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 "jamie@example.com/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 "jamie@example.com//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. -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/telepathy/telepathy-gabble/issues/267. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.