Red Hat Bugzilla – Bug 804626
cannot set server name when setting up a Sametime account through Empathy
Last modified: 2015-02-18 08:42:33 EST
Description of problem:
When trying to set up an account through Empathy of type Sametime, there is not mechanism for setting the server to connect to.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Launch Empathy and go to Edit -> Accounts and try to add a Sametime account.
2.The only information it asks for is 'Account:'. Put anything in the account field.
3.Log in to create the account entry, it will obviously fail. Now view the "connection parameters".
Under the Advanced section you will only see fields for Passowrd, Force Login and Fake Client Id. There is nowhere to set the server name to connect to.
The ability to set the server name.
Bug already reported upstream. Reassigning to correct component.
any news on this? I have the same problem, running Fedora 18 here.
Same problem on Fedora 19, updated bug.
Some "little" progress has been made towards this, referencing FreeDesktop bug.
If there's anything you want me to try out, let me know. I'm one of those lucky few people who can test against a real Sametime server :)
This patch  allows me to have the "server" field back in the "Edit connection settings" dialog. I can now enter account and server separately and login back again.
I've also prepared an f19 x86_64 rpm binary  with the patch applied for those willing to test it.
So everything is working properly except the fact that the "new account" dialog is missing the server field. According to the freedesktop bug that is a new feature in Empathy.
Hello, any news?
This message is a notice that Fedora 19 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 19. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 19 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.