Didn't really seem relevant to the problem at hand, but I did read through it...

On 1/22/2017 09:09, Wade Smart wrote:
Tracy, have you read this:

https://github.com/dequis/purple-facebook/wiki
--
Registered Linux User: #480675
Registered Linux Machine: #408606
Linux since June 2005


On Sat, Jan 21, 2017 at 10:03 PM, Tracy <pid...@arisiasoft.com> wrote:
Following up on this. Turns out I fixed it, although I'm not *exactly* sure
what the fix was.

I was reading some old posts on the net about this kind of problem with past
versions of the Facebook plugin, and one of them mentioned that deleting the
Facebook account in Pidgin and recreating it would sometimes fix the
problem.

This led me to look at the accounts.xml in the Pidgin data directory, and I
found some "settings" information in there that looked a bit odd. So, on the
theory that deleting and recreating the account would replace that section
(along with the rest, obviously, but the rest looked OK to me), I deleted
the Settings section, saved the accounts.xml file with those changes, and
started Pidgin. Going in and enabling the Facebook account caused it to
start right up.

So, the problem has to be something in the Settings section. Now that I have
it running again, I'll have to compare those two Settings blocks.

My current "theory" is that the session token that was stored in the
settings block somehow became invalid, but the plugin either wasn't able to,
or wasn't designed to, update that - so it was trying to continue to use the
invalidated token for the session. But again, that's just a theory, and may
not be borne out by additional research.

If anyone is interested in following up on this and wants to look at the
stuff I pulled out of Settings in hopes of figuring out what went wrong,
feel free to reply to this thread (or contact me off-list, if that's more
convenient).

Thanks

Tracy


On 1/21/2017 20:32, Tracy wrote:
Greetings.

I have been running Pidgin 2.11.0 under Windows 10 Home (64-bit) (version
10.0.14393) for a while now. However, starting yesterday, I am having
trouble connecting to Facebook. I receive the error "Invalid HTTP response
code 401".

Nothing has changed about my setup, nor has my Facebook password changed.
I am still able to log in to Facebook directly (and I can log into Facebook
Messenger on my mobile devices) using the same user account and password as
I have set up in Pidgin.

I did a search of the bug list, and turned up a couple of closed bugs from
2014 about this problem, but it appeared to be a plugin problem (To the best
of my knowledge, I am not using any external plugins - just the ones that
come with Pidgin).

My configuration for Facebook is:

Login Options:
Protocol: Facebook
Username: <redacted>
Password: <redacted>
Remember Password (checked)

User Options:
Local Alias: Tracy

Proxy
Proxy Type: Use Global Proxy Settings

This had been working correctly up until yesterday.

I have tried basic things like closing and reopening Pidgin, and
restarting the computer. Are there other specific things I should try, or is
this something that has changed with the Facebook protocol (hence
necessitating a change to the program)?  If necessary or desirable, I can
produce a debug log - but for obvious reasons I wouldn't want to post that
here...

I would appreciate any suggestions you may offer (well, except ditching
Facebook O:-) )

Tracy

_______________________________________________
Support@pidgin.im mailing list
Want to unsubscribe?  Use this link:
https://pidgin.im/cgi-bin/mailman/listinfo/support
_______________________________________________
Support@pidgin.im mailing list
Want to unsubscribe?  Use this link:
https://pidgin.im/cgi-bin/mailman/listinfo/support


_______________________________________________
Support@pidgin.im mailing list
Want to unsubscribe?  Use this link:
https://pidgin.im/cgi-bin/mailman/listinfo/support

Reply via email to