Bug 46034 - Unable to connect to corporate jabber server
Summary: Unable to connect to corporate jabber server
Status: RESOLVED MOVED
Alias: None
Product: Telepathy
Classification: Unclassified
Component: gabble (show other bugs)
Version: 0.13
Hardware: All All
: medium normal
Assignee: Telepathy bugs list
QA Contact: Telepathy bugs list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-02-14 05:18 UTC by Robert Munteanu
Modified: 2019-12-03 19:55 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
Contents of the debug window when trying to connect (10.30 KB, text/plain)
2012-02-15 23:52 UTC, Robert Munteanu
Details
Another try at attaching the gabble debug log (21.27 KB, text/plain)
2012-02-16 13:09 UTC, Robert Munteanu
Details

Description Robert Munteanu 2012-02-14 05:18:39 UTC
Empathy version 3.2.1.1, Telepathy-Gabble  version 0.13.7 .

Telepathy-Gabble does not connect to my corporate server . From the debug log I've narrowed this down to

connector_error_disconnect (connection.c:1699): connection failed: WOCKY_AUTH_ERROR_NOT_SUPPORTED (#1): Server doesn't have any sasl mechanisms

However, I can connect just fine with other clients, like Pidgin, and my other colleagues connect using a variety of clients ( iChat for instance ).

I am willing to help troubleshoot this issue, but I'm not sure where to start from.
Comment 1 Jonny Lamb 2012-02-15 14:45:34 UTC
Thanks for your bug report. We'll need more information to debug the problem though. Could you attach the complete debug log please? If you think it has personal information in it (it shouldn't), feel free to email it to me personally.
Comment 2 Robert Munteanu 2012-02-15 23:52:35 UTC
Created attachment 57130 [details]
Contents of the debug window when trying to connect

I've attached the debug log for the 'gabble' category when trying to connect. Let me know if you need something else.
Comment 3 Jonny Lamb 2012-02-16 12:34:10 UTC
(In reply to comment #2)
> I've attached the debug log for the 'gabble' category when trying to connect. Let me know if you need something else.

Can you please change the log to "gabble" and post that log, instead of the "mission-control" log you posted? Thanks!
Comment 4 Robert Munteanu 2012-02-16 13:09:38 UTC
Created attachment 57176 [details]
Another try at attaching the gabble debug log
Comment 5 Robert Munteanu 2012-02-28 03:59:32 UTC
Is there any other info that I can provide?
Comment 6 Robert Munteanu 2012-11-27 14:47:45 UTC
Now running telepathy-gabble 0.16.4 and it still does not work. However, I've found that there was a similar issue opened for Adium

http://trac.adium.im/ticket/16081

which contains lots of debug information and also a fix for libpurple. 

I've removed the needinfo status since this should be enough information to determine the root cause. Please let me know if you need anything else.
Comment 7 GitLab Migration User 2019-12-03 19:55:43 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/telepathy/telepathy-gabble/issues/210.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.