With the latest version of libpurple (2.10.1) a change was made to the Sametime protocol:
+ Sametime:
- Separate "username" and "server" when adding new Sametime
accounts
Although at first this seems harmless and only affecting the pidgin client, it seems that telepathy-haze can not handle this separation. When a new account is created for Sametime, the server details are no longer displayed. Also an old account (that has all the details already) no longer works due to the same issue. Adding the missing parameter to the accounts.cfg file (mission-control) causes that this parameter is ignored and removed.
Returning to libpurple 2.10.0 resolves the issue and the server can be identified again when the account is created.
With the latest version of libpurple (2.10.1) a change was made to the Sametime protocol:
+ Sametime:
- Separate "username" and "server" when adding new Sametime
accounts
Although at first this seems harmless and only affecting the pidgin client, it seems that telepathy-haze can not handle this separation. When a new account is created for Sametime, the server details are no longer displayed. Also an old account (that has all the details already) no longer works due to the same issue. Adding the missing parameter to the accounts.cfg file (mission-control) causes that this parameter is ignored and removed.
Returning to libpurple 2.10.0 resolves the issue and the server can be identified again when the account is created.