Original bug report: https://bugzilla.gnome.org/show_bug.cgi?id=632424 An user reported that it can't set its alias on jabber.apinc.org. I didn't see anything suspect in the log so that could be a gabble issue. See https://bugzilla.gnome.org/attachment.cgi?id=173079 for the logs. Server is often down so I haven't be able to test myself. Works fine with Pidgin according to reporter.
Same on my ploum.net account.
Created attachment 40704 [details] gabble change alias log In this log, I've tried to change my jid (ploum at ploum.net) to "bépobépo". (so it's easy to scan)
I believe that this issue was caused by a pair of bugs Jonny tracked down in March, one in Empathy and one in Gabble: • Gabble didn't flag the relevant field in ContactInfo as being overwritten by the Alias; • Empathy ignored that flag anyway, and even if it hadn't would both set Nickname and call SetContactInfo on the CM, despite only the nickname having changed; and it would call SetContactInfo with the old nickname. So this led to the following sequence: • Empathy sets Account.Nickname to "bépobépo"; • MC calls SetAliases({self_handle: "bépobépo"}) on Gabble (1); • Empathy calls SetContactInfo( [..., ("NICKNAME", [], ["ploum@ploum.net"], ...] ) on Gabble (2); • Gabble patches your vCard to change your NICKNAME to "bépobépo" in response to (1); • Gabble then replaces your entire vCard with your old vCard, as Empathy told it to in (2). The Gabble issue was fixed in 0.11.8; I don't remember which Empathy release fixed it, but it should be fixed in 3.0 at least. Soooo … I'm marking this as fixed. Please reopen if it's still an issue.
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.