Bug 754395

Yeah, same in F-17. Pidgin works with Office Communicator (over TLS). Empathy does not (it says it cannot retrieve account data from the server), although the same parameters are specified in the account as in Pidgin.

This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

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 prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 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 to click on 
"Clone This Bug" and open it against that version of Fedora.

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.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

still a problem in f18! pidgin works fine, empathy does not!

I have had the same problem with Empathy.  None of the updates have fixed it either.  My credentials are correct - and it works with Pidgin - but when OCS tries to connect it just displays the error:
"Failed to retrieve your personal information from the server."

I am running Fedora 17 x86_64.

[root@fedora log]# rpm -qa | grep -E "empathy|telepath|sipe"
telepathy-filesystem-0.0.2-3.fc17.noarch
purple-sipe-1.14.1-1.fc17.x86_64
empathy-3.4.2.3-1.fc17.x86_64
telepathy-gabble-0.16.5-1.fc17.x86_64
python-telepathy-0.15.19-4.fc17.noarch
telepathy-idle-0.1.12-1.fc17.x86_64
telepathy-salut-0.8.0-1.fc17.x86_64
remmina-plugins-telepathy-1.0.0-4.fc17.x86_64
telepathy-mission-control-5.12.3-1.fc17.x86_64
telepathy-logger-0.4.0-2.fc17.x86_64
telepathy-haze-0.6.0-1.fc17.x86_64
telepathy-farstream-0.4.0-2.fc17.x86_64
telepathy-glib-0.18.2-1.fc17.x86_64

I can reproduce this problem on F18. I have a fresh GNOME F18 x86_64 install running in a VM, updated to the latest packages:

empathy-3.6.4-2.fc18.x86_64
telepathy-haze-0.6.0-2.fc18.x86_64
libpurple-2.10.7-2.fc18.x86_64
purple-sipe-1.15.1-1.fc18.x86_64


The issue is related to the password handling:

 - haze no longer seems to store the "Password" advanced setting in the generated accounts.xml. Therefore SIPE doesn't see a password on the account and initiates a UI action for it

 - haze doesn't seem to intercept the password dialog and forward it to telepathy

-> so connection setup is stuck


To verify this I tried the following: at work I can use Kerberos. So I ran "kinit", set authentication to "krb5" and selected "SSO"

-> account goes online without problems.


A possible work-around might be to manually add the password for the sipe account to the GNOME password manager (seahorse & friends). Then my guess is that telepathy-haze will find the password for the account and add it to the generated accounts.xml.


This clearly needs to be fixed upstream in telepathy-haze. I would suggest to file a bug for it.

I've created an upstream bug with an implementation proposal. With the supplied patch, I was able to login by providing the password in the account settings or by filling in the password request generated by Empathy.

I generated a scratch build for F18 with the patch I proposed to upstream:

   http://koji.fedoraproject.org/koji/taskinfo?taskID=5239135

It would be nice if you could try it out.

I've got a family emergency and probably won't get a chance to look at this till next week. I'll keep an eye on the upstream bug for them to review you're patch.

I've updated the upstream patch after some review comments. Here is the scratch build for F18:

   http://koji.fedoraproject.org/koji/taskinfo?taskID=5242004

telepathy-haze-0.7.0-3.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/telepathy-haze-0.7.0-3.fc19

telepathy-haze-0.6.0-3.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/telepathy-haze-0.6.0-3.fc18

Package telepathy-haze-0.6.0-3.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing telepathy-haze-0.6.0-3.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-5557/telepathy-haze-0.6.0-3.fc18
then log in and leave karma (feedback).

Yes!!  I have tested it on my F18 Virtual Machine and it works 100%.

May I ask, will there be a F17 release?  I have not yet converted my office notebook to F18.

Once again, many thanks for your efforts.

(In reply to comment #13)
> May I ask, will there be a F17 release?

No, F17 is only getting security updates.

Better, for sure, but not quite there - at least not for me. It gets stuck in "Connecting..." and never completes. No idea why...

(In reply to comment #15)
> Better, for sure, but not quite there - at least not for me. It gets stuck
> in "Connecting..." and never completes. No idea why...

That is a variation of bug #579116.

Brian: Will added some tests for the new purple_account_request_password() and found one error in the new code. Please consider cherry-picking 4541819cc4133d1dfe6d3766c6cf8f0204a4c65f for the Fedora package.

@Bojan:  Something that was added to the original purple-sip latest update was that if SSO (single sign on) was checked, then your login credentials would be ignored.  As a first step I would make sure that in the options you have unchecked SSO.

Hope that helps you.

(In reply to comment #18)
> @Bojan:  Something that was added to the original purple-sip latest update
> was that if SSO (single sign on) was checked, then your login credentials
> would be ignored.  As a first step I would make sure that in the options you
> have unchecked SSO.
> 
> Hope that helps you.

It is not that. I ran empathy debugger and the problem is that empathy doesn't like certs signed by private authorities (e.g. company). So, one has to install such root ca by hand to make things work (and it does work then). Surely, users should be prompted to accept/decline such roots. Especially given the fact that this is office communicator - many companies will have their own cert authorities.

In other words, see comment #16.

telepathy-haze-0.7.0-3.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.

telepathy-haze-0.6.0-3.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.

(In reply to comment #19)
> It is not that. I ran empathy debugger and the problem is that empathy
> doesn't like certs signed by private authorities (e.g. company). So, one has
> to install such root ca by hand to make things work (and it does work then).
> Surely, users should be prompted to accept/decline such roots. Especially
> given the fact that this is office communicator - many companies will have
> their own cert authorities.
> 
> In other words, see comment #16.

Ah, yes, I *DO* agree.

I have just installed a fresh Fedora 18 on my laptop - thinking that I could now use Empathy again.  My Office Communicator also just stays in "connecting" state and tells me nothing more.  

I agree that the certificate thing *needs* to be more seamless like it is in Pidgin.

I will CC myself to bug #579116 also.

This bug affects me too. Happens just as described, keeps trying to connect and doesn't accept my company password. Pidgin works fine. telepathy-haze-0.6.0-3.fc18 does not fix this at all.