Unfortunately (depending on the point of view....) I'm not the sysadmin of the SameTime servers and I'm not able to ask creation of accounts for these purposes. I would be very glad to give accounts to developers but I can not :(
(In reply to comment #7)
> What telepathy-mission-control version is this?
telepathy-mission-control-5.14.1-2.fc19.x86_64
> Did you log out and back in (or reboot) between installing the patched
> Haze and trying to use it?
No, I simply quit empathy. Could not quit while I was at the office. Actually logging off and logging in back again solved the issue; sorry for the noise.
I can now log in after editing the account by splitting the account and server options.
Thanks for the patch. Can you push it to telepathy-haze?
> (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.
Unfortunately (depending on the point of view....) I'm not the sysadmin of the SameTime servers and I'm not able to ask creation of accounts for these purposes. I would be very glad to give accounts to developers but I can not :(
(In reply to comment #7) mission- control version is this?
> What telepathy-
telepathy- mission- control- 5.14.1- 2.fc19. x86_64
> Did you log out and back in (or reboot) between installing the patched
> Haze and trying to use it?
No, I simply quit empathy. Could not quit while I was at the office. Actually logging off and logging in back again solved the issue; sorry for the noise.
I can now log in after editing the account by splitting the account and server options.
Thanks for the patch. Can you push it to telepathy-haze?
> (In reply to comment #6) :${server} as the value of the 'account' parameter"
> > 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}
>
> and it'd work whether Haze splits them or not.
Thanks, should I file a bug on Empathy for this?