GNOME Bugzilla – Bug 481139
Generic "telepathy" jabber resource name causing clashes.
Last modified: 2009-10-29 16:22:05 UTC
on two computers, if you login using the same account with empathy, one will disconnect the other. Other clients can handle simultaneous connections fine (gajim/pidgin/gmail/whatever). Basically: gajim + gajim = ok gajim + empathy = ok empathy + empathy = collision
oh, forgot to mention that this is a feature of the jabber protocol. I doubt that MSN and others support that.
I suppose that's because both accounts use the same ressource and/or priority.
Yes, you have to change your recource. We should change default resource to hostname to minimize collisions and, in my opinion, gabble should add a randomized suffix to the resource in case of conflict.
is it even possible to have two computers you own with the same hostname ?_?
I don't think randomising the resource is Gabble's business. Empathy can do that itself at any rate.
I agree, Gabble should just set the ressource we ask it to set. I think the easiest solution is to set a random string as default ressource instead of a hardcoded one. So Empathy won't have to deal to change it at each connection and people who want to use a specific ressource can still do.
*** Bug 546202 has been marked as a duplicate of this bug. ***
Gabble 0.7.28 uses a random resource if you don't explicitly set one. Maybe Empathy should use a function of the hostname as the resource nonetheless? I note that lots of people use "ubuntu" as their hostname, so that alone is unlikely to disambiguate two concurrent connections. So, Empathy would have to add random misc to the resource, and then it might as well just delegate to Gabble.
I remember I fixed this problem in Gossip by handling disconnect with reason NAME_IN_USE by happending a random number to the resource. So it will first try to connect with "telepathy" then if it does not work, it tries "telepathy.YGLDFDGR" If gabble sets a random resource, I think it's fine for empathy to let resource empty since that's considered an "advanced" setting anyway in the UI. So if the user don't know what it is, a random is fine. If the user knows what it is, a name-in-use error message is fine. AFAIK Empathy sets no value to resource atm, right? I think we can close this bug now that gabble have a fix.
Jean-François Fortin Tam, Murray: can you reproduce this? I suspect improvements in gabble have fixed it.
Yes, Gabble has used a random resource as the default for a while now. It will soon instead default to a resource derived from a unique ID for your machine, so you'll always have the same unique resource when connecting from a given machine.