Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 1058021

Summary: [backport] Can't connect to Facebook chat
Product: [Fedora] Fedora Reporter: Martin <mholec>
Component: gajimAssignee: Michal Schmidt <mschmidt>
Status: CLOSED UPSTREAM QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 20CC: lemenkov, mschmidt, tpelka
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-01-27 14:01:50 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Martin 2014-01-26 13:44:16 UTC
Filled upstream:

Description of problem:
Gajim can't connect to Facebook XMPP server. Gajim is unable to receive Facebook roster and stays in "connecting" state forever. Gajim can receive messages and respond to them, but can't open new conversation. Also in "connecting" state user can't be sure if he can receive messages and Facebook doesn't support receiving offline messages via XMPP. This makes Facebook in Gajim practically useless and prone to losing messages.

This is caused by RFC violation in Facebook server implementation. But, there is an easy workaround in Telepathy and Pidgin also works for me.

Please consider adding same workaround into Gajim. It can be documented for now and removed when Facebook fixes their server.


Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
Run Gajim
Add Facebook account and connect to i

Comment 1 Michal Schmidt 2014-01-27 14:01:50 UTC
Thank you for filing this with upstream.

I do not value tracking this BZ in both bugtrackers, so I'm going to close this one. Feel free to ping me when upstream has a fix. Then we can consider a backport or a rebase.