Arch Linux

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#47427 - [telepathy-gabble] Jabber does not work with Cisco Unified Presence

Attached to Project: Arch Linux
Opened by Ulf Winkelvos (uwinkelvos) - Thursday, 17 December 2015, 21:09 GMT
Last edited by Doug Newgard (Scimmia) - Saturday, 19 December 2015, 17:15 GMT
Task Type Bug Report
Category Packages: Extra
Status Assigned
Assigned To Felix Yan (felixonmars)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No


Could never successfully get Empathy to connect to our Cisco Unified Presence Server at work. This is only an issue when linked against openssl, when I build with gnutls which is the default everything works fine. Apparently the switch to use openssl in the arch package was enabled because of some bug in gnutls 4 Years ago and then it has never been switch back. [1] Is there any good reason to stick with openssl here?

Additional info:
* extra/telepathy-gabble 0.18.3-1 (telepathy)
* (i can provide debug logs if necessary)

Steps to reproduce:
This task depends upon

Comment by Samantha McVey (samcv) - Saturday, 11 June 2016, 03:31 GMT
Did this ever get resolved in a more recent version of telepathy or is this still an issue? Thanks in advance for your response.
Comment by Ulf Winkelvos (uwinkelvos) - Monday, 13 June 2016, 19:57 GMT
I've been using pidgin for a while, but I will test this in the next days.
Comment by Samantha McVey (samcv) - Monday, 08 August 2016, 13:46 GMT
Haven't heard back from you. Any possibility you can test this? Thanks.
Comment by Ulf Winkelvos (uwinkelvos) - Tuesday, 09 August 2016, 22:59 GMT
Hey, I am sorry! I tested it back in June and wanted to dig into the issue further as with 0.18.3 it does not work at all with the server. Regardless of wich TLS backend is used. Then i forgot to report back and retested it today with the same result. I'll probably have to take this issue upstream.