Closed Bug 954566 Opened 11 years ago Closed 10 years ago

Facebook account disconnected when set to unavailable on Facebook.com

Categories

(Instantbird Graveyard :: Account manager, defect)

x86
Windows Vista
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: bugzilla, Unassigned)

Details

*** Original post on bio 1133 by Tomáš Komárek <tomaskom.cz AT seznam.cz> at 2011-11-01 22:49:00 UTC ***

When I am online on chat via Instantbord and on facebook web too and manually turn off chat there (not log out, just disabling chat), it also disconnects Instantbird. It may be bug on FB side, BUT Instantbird doesn't try to reconnect. 
When I open account manager, it says "Error: conflict of sources" (note that this is my translation, I use Czech version of Instantbird).

Also, because of missing icons in contacts window, which should show state of various accounts I have in Instantbird, I'm not notified about the fact that I'm not currently connected.
*** Original post on bio 1133 at 2011-11-01 23:03:29 UTC ***

Apparently Facebook doesn't let you set different resources to offline or available. I can confirm that unchecking "Available to chat" on the Facebook websites will cause Instantbird to disconnect with an "Error: Resource Conflict" error message.

If you press "Connect" in Instantbird to reconnect the account you will receive a message from chat.facebook.com:
> You are now Online to Chat. Please note that this also marks you as Online on
> facebook.com.

I'm not sure what the "proper" thing to do here is though. The related code is at [1] which doesn't try to reconnect for a "stream:error", I'm not sure if that's the proper thing to do or not. This sounds more like Facebook having a bad XMPP gateway. :(

[1] http://lxr.instantbird.org/instantbird/source/purple/libpurple/protocols/jabber/jabber.c#2767
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: Reconnection to Facebook after disconnection triggered on facebook's site → Facebook account disconnected when set to unavailable on Facebook.com
I don't see this anymore, I'm guessing this was a server side issue.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.