Adding facebook account makes gwibber crash

[Ernst]

Binary package hint: gwibber

I just wanted to start using gwibber - I don't have any earlier experiences. As I only have a Facebook account, I cannot test if this problem exist with other providers.

If I start gwibber, I'm getting a dialog if I want to add an account. I click 'Facebook' and add. On the next sreen, I click 'Authorize' and after that I enter my credentials. My picture from Facebook is shown in the examples and I'm asked if I want to allow gwibber to post messages. I click deny and at that moment, I get a popup saying "Facebook authorization failed. Please try again." Clicking the 'ok' button doesn't work, and the only way to exit gwibber is 'sudo pkill gwibber'.

I did 'rm -rf ~/.cache/desktop-couch ~/.config/desktop-couch ~/.local/share/desktop-couch/' (as suggested in other gwibber bug reports), but that didn't solve this problem.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: gwibber 2.30.0.1-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-21.31-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic x86_64
Architecture: amd64
Date: Fri Apr 16 15:46:47 2010
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100122)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=
 PATH=(custom, user)
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: gwibber

[malev (marcosvanetta)]

Hi there!
Thanks for report this bug and help with a better Ubuntu.
However, I tried to reproduce your bug, but, I have no luck.
I'm using gwibber 2.30.0.1
As I can see, your bug was reported when you were using alpha 1. Could you upgrade gwibber and check if the bug persist?
regards

[Ernst (ernst-blaauw)]

I have a fully upgraded Lucid, and the date listed above only shows the
initial installation date. It also lists gwibber's version, which is the
same as yours.
However, I tried to reproduce the bug and I now clicked 'allow' everywhere.
That succeeded. Afterwards, I removed the account and re-added it, but I did
not had to re-allow gwibber to facebook. So, I could not get to the state
where I clicked 'deny', making gwibber crash.
I will mark this bug invalid, as I cannot reproduce it. However, it is
possible it can be reproduced by dening gwibber the access to facebook
during authorization - but I cannot check that anymore as my account is
already authorized.

On Sun, Apr 18, 2010 at 21:56, malev <email address hidden> wrote:

> Hi there!
> Thanks for report this bug and help with a better Ubuntu.
> However, I tried to reproduce your bug, but, I have no luck.
> I'm using gwibber 2.30.0.1
> As I can see, your bug was reported when you were using alpha 1. Could you
> upgrade gwibber and check if the bug persist?
> regards
>
> ** Changed in: gwibber (Ubuntu)
> Status: New => Incomplete
>
> --
> Adding facebook account makes gwibber crash
> https://bugs.launchpad.net/bugs/564707
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[gowthamn (narisipalli)]

Version: Gwibber 2.30.0.1
Adding accounts with flickr, twitter works fine but facebook extension seems to be giving a lot of trouble to many. This error still exists.
Here is the error description:

An error occurred with Gwibber. Please try again later. There is an Okay button and upon clicking the Okay button a popup comes up with "Facebook authorization failed. Please try again". This is the end of the application and is hung at this point. I click OK to close the popup and it doesn't close. I have to forcefully quit everytime and it relaunches the application.

[Jake Guthmiller (jguthmiller)]

I just did a fresh install of lucid and updated to 2.30.0.1, and I'm having the same issue as well. I can connect to twitter just fine, but Gwibber locks up the same way that gowthamn descibes when I try to add facebook.

[Thiago Atanes (thiago-atanes)]

I'm having this exact same issue. Gwibber locks up when I try to authorize it with my facebook account. Working OK with Twitter though.

[Pepe Lebuntu (majagray75)]

Same problem. Twitter is fine, but no FB. I've tried using both my email address and my FB username as the login, and neither makes any difference.