[Bug 44631] haze cannot deal with some of the latest changes that came with libpurple 2.10.1

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=44631

--- Comment #7 from Simon McVittie <simon.mcvittie at collabora.co.uk> ---
(In reply to comment #6)
> 1- When creating the account the only field is "account", no "server" field.
> 2- I edit the "connection settings" and fill in the fields.
> 3- It asks me for the password, and when filling it in it keeps on asking.
> 4- If I edit the account settings to re-check, all the settings have
> vanished; only the account is there and the rest is blank.

That sounds like several bugs. What telepathy-mission-control version is this?
Did you log out and back in (or reboot) between installing the patched Haze and
trying to use it?

Since there are no Telepathy contributors with access to a Sametime server (as
far as I know), if you want this fixed, I'm afraid you'll need to do some
debugging. Sources of information that could be useful include:

* Empathy's Debug window (empathy-debugger)
* <https://live.gnome.org/Empathy/Debugging>
* <http://telepathy.freedesktop.org/wiki/Debugging/>
* dbus-monitor

The debug logs for both Haze and Mission Control are probably relevant.

(In reply to comment #6)
> maybe a faster / dirtier
> fix would be to add a text at the account creation screen (screenshot 1)
> with instructions to use <account>:<server> as the account name.

That'd be an Empathy feature request: Telepathy doesn't have much control over
its account creation UI. If you're giving Empathy a protocol-specific UI for
sametime anyway, you could use logic like:

* have text-entry boxes for both account and server
* if the connection manager claims to support the server parameter, send them
as account and server
* if the connection manager does not claim to support the server parameter,
send ${account}:${server} as the value of the 'account' parameter"

and it'd work whether Haze splits them or not.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.