[meta] cannot add facebook account, facebook does not update and more

I think bug #595265 covers some of these problems, but not all.

I am having this problem. I cannot connect to Facebook. This is a MASSIVE problem, since Gwibber is included by default in 10.04. Please, someone, get to work on this. I would myself but I don't possess the skills.

Me too, same problem on 3 Pcs with fresh install Lucid, backports and proposed repositories added. note that twitter, identi.ca and status.net work fine.

 While trying to authorize in Facebook Gwibber says that there's a mistake in Gwibber and connection fails.

if it come as default apps...some1 really need to fix it fast.
go ubuntu!
(p/s: using my gwibber for twitter only, surf facebook like usual)

I am having this same problem with a fresh Lucid install. However i had Karmic loaded on one installation which i upgraded to Lucid and i don't have problems with facebook there.

Somehow i think that the 'Importance' of the issue needs to be elevated.

setting back to triage. it seems it was mistakenly marked fixed.

I'm getting the "An error occurred with Gwibber. Please try again later" error.

This run for me, try it.

'Not sure if I had the same problem, but try to open this page: http://www.facebook.com/username , go back to gwibber and use your username instead of your email when you login to your account. After that the Add button appeared for me.'

I just tried this and it also worked for my facebook account. ... quite strange

with this tip, work for me too :)

I had the same issue with Gwibber not authorizing Facebook. I kept getting the FB sign in box, so quit trying to use it for a while. I tried again a few days ago and suddenly was able to log into FB. But after only one post and quitting Gwibber, I can't get it to open at all. I removed, reinstalled, re-started, got nothing.

Gwibber just made me a liar, and started like it had never been comatose. plplplplplthhhhhbt. False alarm. Sorry.

I tried the proposed solution in comment #9 and it doesn't work for me. I get the same authentication failure error.

I also tried #9, but no luck. The add button does not appear.

The same problem with Empathy 2.30.2. =/

I've the same problem on Marverick Bêta Release

When trying to save the facebook account after a successful registration, the click on "Save" give this :
Saving...
Couldn't find field: username

And the facebook account is not added.
I use it on Mandriva Linux 2010.1.

Guys, i'm having the same problem. But i Solved it. I deleted in Facebook the application 'Gwibber'. Then I tried to add my Facebook account to Gwibber and the 'Add' button appears! Cheers.

This was fixed for me in the latest update.
--
Greg Bair
<email address hidden>

Same here, or at least worked in a fresh & updated 10.04 netbook install.

Same problem here. Tried repeatedly to add Facebook account but failed because there was no "Add" button after completing authorisation. (Didn't realise there was supposed to be one until I read this!). Facebook accepted Gwibber as an authorised application, so no problem that side. Was finally successful after using Facebook username to authorise rather than my sign in email address. Thanks Marcos (post #9)

In Maverick beta none of proposed workarounds is working.

gwibber-2.31.92 -

Saving...
Couldn't find field: username

only on facebook. none of the suggestions helped ( not deleting from facebook and not using the username).
twitter - buzz - flicker - all works.

correction - buzz and flicker added seccessfully, but showing empty.

log for buzz shows:
{"error":{"errors":[{"domain":"global","reason":"invalid","message":"User must have authorized this application to have the following scope in order to make this call: [https://www.googleapis.com/auth/buzz.readonly] Also , make sure your application is using the Buzz specific OAuth authorization URL.","locationType":"header","location":"Authorization"}],"code":401,"message":"User must have authorized this application to have the following scope in order to make this call: [https://www.googleapis.com/auth/buzz.readonly] Also , make sure your application is using the Buzz specific OAuth authorization URL."}}

checking buzz - deleted gwibber - and readded it and it appears in the allowed apps.

after latest maverick beta updates, I was finally able to add a facebook account. I propose to mark this as "fix released".

I don't think the bug should be closed because it is still present in Lucid!

The solution for me on Lucid (Ubuntu 10.04.1) with Empathy 2.30.2 was to folow Dr. Kenobi's comment #19!

So:
 * go to facebook -> account -> privacy settings -> applications and websites settings -> "Remove unwanted or spammy applications" -> remove Gwibber
 * launch gwibber, manage accounts, add facebook, enter your login (email address works here)/password to authorize Gwibber as if it was the first time
 * the "Add" button does *not* appear yet
 * close the Gwibber's account window, open it again and redo the facebook connexion process
 * the "Add" button appears and it works finally well

Does anyone else have success with this?

So:
 * go to facebook -> account -> privacy settings -> applications and websites settings -> "Remove unwanted or spammy applications" -> remove Gwibber
 * launch gwibber, manage accounts, add facebook, enter your login (email address works here)/password to authorize Gwibber as if it was the first time
 * the "Add" button does *not* appear yet
 * close the Gwibber's account window, open it again and redo the facebook connexion process
 * the "Add" button appears and it works finally well

Yes this finally worked for me in Ubuntu 10.10

yes worked for me too

On Fri, Sep 17, 2010 at 12:57 PM, 0N3_xyz <email address hidden> wrote:

> So:
> * go to facebook -> account -> privacy settings -> applications and
> websites settings -> "Remove unwanted or spammy applications" -> remove
> Gwibber
> * launch gwibber, manage accounts, add facebook, enter your login (email
> address works here)/password to authorize Gwibber as if it was the first
> time
> * the "Add" button does *not* appear yet
> * close the Gwibber's account window, open it again and redo the facebook
> connexion process
> * the "Add" button appears and it works finally well
>
> Yes this finally worked for me in Ubuntu 10.10
>
> --
> [meta] cannot add facebook account, facebook does not update and more
> https://bugs.launchpad.net/bugs/614742
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Gwibber: New
> Status in “gwibber” package in Ubuntu: Triaged
>
> Bug description:
> Binary package hint: gwibber
>
> This is a bug that covers many facebook related problems in gwibber. when a
> user add a facebook account after authorization gwibber dont show any add
> button so the account cannot be added. some people succeed in adding the
> account but then facebook does not update and gwibber-service logs show
> something like 'applicaton limit reached'. the logs seem to suggest that the
> problem is from the facebook side.. this bug is for tracking purpose so we
> have a single bug report as the root cause is the same.
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/gwibber/+bug/614742/+subscribe
>

Thank you so much. i appreciat your responce. i shall try this as soon as i
reach my home.

Regards
S. Asad Ali Zaidi

Electronics Engineer

.Net Specialist

MCSE

www.asadali.tk

www.freeonlinebooks.tk

+92-345-5164698

On 17/09/2010, Maxim Doucet <email address hidden> wrote:
>
> I don't think the bug should be closed because it is still present in
> Lucid!
>
> The solution for me on Lucid (Ubuntu 10.04.1) with Empathy 2.30.2 was to
> folow Dr. Kenobi's comment #19!
>
> So:
> * go to facebook -> account -> privacy settings -> applications and
> websites settings -> "Remove unwanted or spammy applications" -> remove
> Gwibber
> * launch gwibber, manage accounts, add facebook, enter your login (email
> address works here)/password to authorize Gwibber as if it was the first
> time
> * the "Add" button does *not* appear yet
> * close the Gwibber's account window, open it again and redo the facebook
> connexion process
> * the "Add" button appears and it works finally well
>
> Does anyone else have success with this?
>
> --
> [meta] cannot add facebook account, facebook does not update and more
> https://bugs.launchpad.net/bugs/614742
> You received this bug notification because you are a direct subscriber
> of a duplicate bug (638794).
>

--

No such luck for me using that process. I'll try a few other things, but there is some server problems here. If you hit authorize twice (when the add button /should/ appear, but doesn't) it pops up with a new frame with "Success" printed in it.

jkltechinc, Try uninstalling - reinstalling gwibber then do that process. Thats what i had to do and it is now working correctly for me.

The bug is still there:

The Save account button is not there after authorizing with facebook.
But if I try to change the color of the messages the button suddenly appears along with a cancel button, then:

Saving...
Couldn't find field: username

I hope this gets fixed before the Official Release.

I can confirm this too, however, for those who tried the comment #19 solution and it didn't worked (like me):
maybe i have a workaround...

close gwibber, delete the gwibber authorization from facebook, then, (if like me you have tried the previous steps before) you may have some gwibber-services still running: kill them (you can do this via system->administration->system monitor, processes tab, sort by name, and kill everything that starts with gwibber), open gwibber again, and now it MAY work

one last thing: i started to notice this problem, when i connected my facebook account with a gwibber on another ubuntu machine (lucid, while my main is a maverick)... can someone confirm that this may be (one of) the cause(s)?

unfortunately i'm unable to confirm my workaround on this second machine now, so i'm not certain that this always works

  On 09/24/2010 05:34 PM, Dario Bertini wrote:
> I can confirm this too, however, for those who tried the comment #19 solution and it didn't worked (like me):
> maybe i have a workaround...
>
> close gwibber, delete the gwibber authorization from facebook, then, (if
> like me you have tried the previous steps before) you may have some
> gwibber-services still running: kill them (you can do this via
> system->administration->system monitor, processes tab, sort by name, and
> kill everything that starts with gwibber), open gwibber again, and now
> it MAY work
>
>
> one last thing: i started to notice this problem, when i connected my facebook account with a gwibber on another ubuntu machine (lucid, while my main is a maverick)... can someone confirm that this may be (one of) the cause(s)?
>
> unfortunately i'm unable to confirm my workaround on this second machine
> now, so i'm not certain that this always works
>
after doing a system update this morning, Facebook now works on my
install of Gwibber for Ubuntu 10.10 Beta.....but it's slow on updating,
like hours slow.....

Workaround for bug (worked for me at least):
Open Gwibber.
Open Accounts.
Add Facebook account in Gwibber and authorize. It will say 'authorized', but give no add button.
Go into application settings in Facebook (in web browser); Find Gwibber, and click 'Edit Settings'.
Uncheck all settings for gwibber.
Close Gwibber account window.
Open Gwibber account window.
Add/Authorize Facebook account again, and this time there should be an 'add' button.

The related branch fixes the missing "Add" button - now the error message appears if login is unsuccessful.

I've prepared an experimental build at ppa:roignac/svn (https://launchpad.net/~roignac/+archive/svn) - please, test this and post here if this helps. Most likely, the error will be "Application request limit reached", so the only way to add Facebook account is just to wait and try again in several minutes.

Bug is still there. On the add account page there are two Add buttons. The Add... seems not to do anything. The other Add, under the drop down, does start the Facebook login process. However, after getting back an Authorized message and closing the dialog, it appears it did not work. And, When I go back to add an account, Facebook is not listed.

I am using Meerkat 64 Desktop latest as of now (Sep 28, 4:00 PM EST)

In response to coment #9 of Marcos Lans, using my username on the login dialog worked fine for me.

Still have the problem with latest Gwibber updates from 10.10 RC and even if I use my user name instead of the email address. Tried all workarounds, none did work.

That workaround https://bugs.launchpad.net/gwibber/+bug/614742/comments/37 #37 worked for me

Upgraded to latest Maverick, even rebooted, but can't add Facebook account.

I choose to add a Facebook account, press add, press Authorize, proceed to enter my login info, press Aanmelden (sign in, it automatically switches to Dutch). It shows "Facebook authorized", but there is no save button. Opening up the Advanced settings, opening the Message Color dialog, closing that (does not matter if I change the color), results in the Cancel and Save buttons being shown but the Save button does nothing. The cancel button however goes back to asking what kind of account I want to add.

Hope there will be a fix for this soon, I would but I do not possess the abilities to create such a fix. Just doing my part in reporting the bug :)

Confirm that workaround https://bugs.launchpad.net/ubuntu/+source/gwibber/+bug/614742/comments/37 worked for me while all of other workarounds didn't work. Thanks Ben.

Today was an update (gwibber 2.32.0.1-0ubuntu1) that fixed the problem for me.

Updated to gwibber 2.32.0.1-0ubuntu1, and I confirm that that fixed the problem here as well.

The workaround does not work for me (updated 10.04 system). Will this bug be solved?

I managed to add facebook to gwibber at first. However it was updating very slowly for me. Like #36 said, it took several hours to update. I decided to try to remove facebook and then add it back. However there's no add button now and workarounds don't work.
I have the latest version (2.32.0.1-0ubuntu1)

version 2.33.0~bzr883-0ubuntu1~daily1~lucid
still no add button. Tried everything, comment 9, 44, update forced update reboots etc. No add button!

The same for me, but with the official version, 2.32.0.1, not the one from the PPA. Facebook authorized, no add button.

I made it work with this:

-edit /etc/hosts
-Make sure all the entries for the loopback are 127.0.0.1 One of my entries was 127.0.1.0 (notice the 1)

I had 127.0.1.1 in one line what is my pc, i edited to 127.0.0.1, and it worked like a charm.. strange.

same troubles with the last 10.10 release. found the 127.0.1.1 in my /etc/hosts, remove it and now, it works fine :-)

the loopback workaround does not work for the 2.30.2-0ubuntu3 package in the 10.04 release.

Loopback workaround didn't work for me either on 10.10.

because thats not a workaround. the *only* workaround is to delete gwibber from facebook's trusted applications and then re-authorize gwibber.

I have deleted gwibber from facebook's trusted apps and then reauthorized, and the Add account button still does not appear after reauthorization.

Either disabling the privacy settings of gwibber or completely removing it from facebook authorized applications does not work either (again, using 10.10 release and 2.30.2-0ubuntu3 package).

sorry, that was 10.04 release in #57

Solucionated.

In this page I get the solution.

http://www.ubuntu-es.org/node/135482

Thanks to all.

https://bugs.launchpad.net/gwibber/+bug/614742/comments/59

This worked for me, thank you! The only solution that worked for me.

I just did a clean install of ubuntu 10.10 and here's how I got Gwibber working.

Go to System: Administration: System Monitor. Kill everything with Gwibber in the name. Wait for the gwibber-service zombies to die out. (5ish seconds)

Run: sudo add-apt-repository ppa:gwibber-daily/ppa; sudo apt-get update; sudo apt-get upgrade

The above will update to the newest gwibber client, which is much newer then Ubuntu ships.

Run: sudo gedit /etc/hosts

Find the entry showing 127.0.1.1 and change to 127.0.0.1

Save your file.

in command line (very important) run gwibber. It'll throw a few messages but ignore them. The gwibber screen to add an account will come up. Add the facebook account. You will now hav0.1.1 and change to 27.0.0.1e your save button after the account was authorised. Save the account. Now the gwibber main screen will show up, and you should see your facebook entries.

I got the account added using the info above, but I still wasn't pulling down facebook data. I found a guy on the facebook group for gwibber who said to use your username, and not your email address, when signing into facebook. This worked perfectly and the application is running smooth. If you don't have a username setup with facebook it can be done in preferences.

The only way I could resolve the issue was by creating a new user
account in ubuntu, after I did that the new user account could add fb,
so I use it and deleted the old user account.

#61 worked for me.
thanks!

the work-around in comment 59 seems to work:
https://bugs.launchpad.net/ubuntu/+source/gwibber/+bug/614742/comments/59

It basically says delete these directories:
~/.cache/desktop-couch
~/.config/desktop-couch
~/.local/share/desktop-couch

Then try again.

N.B: You may have to delete the gwibber directory as well (~/.config/gwibber) I deleted it before the others so, I don't know if it had any effect.

This bug still exists. Tried solutions in comments 65 and 29. Still does not work. Did a complete removal of gwibber and gwibber-service from synaptic then did a find . -name *gwibber* and deleted everything on the machine with gwibber in the name, re-installed gwibber from the software center, removed application authorization for gwibber from within facebook, added facebook account, it asked for authorization, it authorized and no add button. Closed and retried 10+ times.

Gwibber is an embarrassment to Ubuntu at this point broken by default in at least the last two versions of Ubuntu.

Ken, could you please review the attached branch and, possibly, release a version of Gwibber with this fix? I don't mean to push on you, but this will allow us to see what kind of errors will people get during authorization.
If the issue is caused by application rate limiting on Facebook side (which is most likely), all workarounds will be useless. Otherwise, the error message will give us more information.

Upgraded to the daily ppa as mentioned in comment 61, and it seems to work fine now. I'm at 2.33.0~bzr886-0ubuntu1~daily1

great. It's work fine now.
thanks!

Gwibber never worked properly in Lucid, right up to the release of 10.10. Now we have put out another OS and marketed it also as "social from the start," and Gwibber has failed us again. I'm confused as to why this was never given more priority when it's marketed as one of Ubuntu's main features that set it apart from other OS's? I love Ubuntu, and I'm grateful for all the professionals who take pride in their work. However, it seems we have really dropped the ball on this one. I notice the bug report still has no one assigned to fix it, and in my view this should have been fixed immediately. I hope we don't have to wait for 11.04 to be social from the start. With respect, Les.

Finally I've got my facebook account added to gwibber, by deleting the desktop-couch directories from ~/.cache, ~/.config, and ~/.local/share. as seen in comment #65.

After trying lots of combinations, I have to say the workaround #37 worked for me. Thanks guys!

I have tried #37 and #65 in combination, and reinstall. Nothing seams to work. I have looked forward to a new working gwibber in 10.10.

Please priorities this.

The solution described by #61 worked for me :)

+1 for #67: please push the branch to ease error reporting

#28 on Lucid works for me. Thanks!

I've managed to get my Facebook account installed through a combination of workarounds on 32 bit Maverick. :
Exiting Gwibber
Removing the gwibber and gwibber-service packages
Manually deleting the gwibber directories in ~/.cache and ~/.config
Removing the desktop-couch directories as described in #65
Removing Gwibber from the Facebook applications list (on the FB website)
Add the Gwibber daily build PPA
Reinstall
Logout, login
Reauthorize the FB account (using either email or username)
The "Add" button then appears

Now the issue is that FB status doesn't continue to update continuously. I've attached a portion of the log to show what I mean:

2010-10-13 12:47:47,057 - Gwibber Dispatcher - INFO - Loading complete: 1 - []
2010-10-13 12:48:19,955 - Gwibber Preferences - INFO - Running from the system path
2010-10-13 12:48:20,679 - Gwibber Dispatcher - INFO - Loading complete: 2 - []
2010-10-13 12:48:31,909 - Gwibber Dispatcher - INFO - Loading complete: 3 - []
2010-10-13 12:53:23,038 - Gwibber Dispatcher - INFO - Loading complete: 4 - []
2010-10-13 12:58:23,121 - Gwibber Dispatcher - INFO - Loading complete: 5 - []
2010-10-13 13:00:18,782 - Gwibber Dispatcher - INFO - Loading complete: 6 - []
2010-10-13 13:05:21,125 - Gwibber Dispatcher - INFO - Loading complete: 7 - []
2010-10-13 13:10:18,089 - Gwibber Dispatcher - INFO - Loading complete: 8 - []
2010-10-13 13:15:20,223 - Gwibber Dispatcher - INFO - Loading complete: 9 - []
2010-10-13 13:20:09,386 - Gwibber Dispatcher - INFO - Facebook error 4 - Application request limit reached
2010-10-13 13:20:09,395 - Gwibber Dispatcher - INFO - Facebook error 4 - Application request limit reached
2010-10-13 13:20:10,257 - Gwibber Dispatcher - INFO - Facebook error 4 - Application request limit reached
2010-10-13 13:20:12,161 - Gwibber Dispatcher - INFO - Loading complete: 10 - []
2010-10-13 13:25:09,418 - Gwibber Dispatcher - INFO - Facebook error 4 - Application request limit reached

Occasionally (every hour or so), Facebook will update, but then it hits those "Facebook error 4 - Application request limit reached" errors. I have Gwibber set to refresh every 5 minutes.

@Ian, thanks for the log - it shows, that Gwibber can't be fixed to register on Facebook immediately - as it is Facebook, which is limiting requests from one application.

A call to others - please, stop posting "That didn't work for me" and "Workaround #x worked for me" comments without the log attached - use "This bug affects me" feature. If your log contains some Facebook error (except "4 - Application request limit reached") - attach the log or, possibly, steps to reproduce, this will be really helpful for the developers.

Also, if somebody knows the way to loosen the limit, please, specify it - as for now these is no way to avoid these errors in Gwibber

after doing what #77 seggest i now cannot start gwibber.
gwibber accounts throws this:
gwibber-accounts -d -o

** (gwibber-accounts:3738): WARNING **: Trying to register gtype 'WnckWindowState' as enum when in fact it is of type 'GFlags'

** (gwibber-accounts:3738): WARNING **: Trying to register gtype 'WnckWindowActions' as enum when in fact it is of type 'GFlags'

** (gwibber-accounts:3738): WARNING **: Trying to register gtype 'WnckWindowMoveResizeMask' as enum when in fact it is of type 'GFlags'
Traceback (most recent call last):
  File "/usr/bin/gwibber-accounts", line 66, in <module>
    from gwibber import accounts
  File "/usr/lib/python2.6/dist-packages/gwibber/accounts.py", line 37, in <module>
    from gwibber.lib.gtk import *
  File "/usr/lib/python2.6/dist-packages/gwibber/lib/gtk/facebook.py", line 29, in <module>
    from gwibber.microblog.util import facelib
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/util/facelib.py", line 64, in <module>
    from util.const import proxy_factory
ImportError: No module named util.const
Exception AttributeError: "'NoneType' object has no attribute 'px_proxy_factory_free'" in <bound method ProxyFactory.__del__ of <libproxy.ProxyFactory object at 0x949f2ec>> ignored

Vadim,

According to this thread and others: http://forum.developers.facebook.net/viewtopic.php?pid=41338

The problem appears not to be that we need to loosen Facebook's limits. It's that Gwibber makes too many API calls too quickly. Each user application pair only gets a few calls per minute. There is some advice in the thread about how to work around limited API calls that may or may not be helpful for Gwibber.

Yes, this is the problem. We've known that and reduced our API calls as much as we can. The hard part of the problem is the allocation, apparently, is per application, not per user/application. So it is throttling based on all gwibber users, not just throttling the calls for the individual users that are exceeding the limits. The latest version in lucid-updates and in maverick all should be well under our allocation, but according to the statistics on facebook our API calls haven't gone down.

So either users aren't updating or there are other problems with the way facebook calculates the API calls. The facebook documentation is rather vague on how the allocation works, and how it handles mobile/desktop applications vs. web applications. I have been trying to get in touch with anyone from facebook that can help shed light on how it works and have been ignored. If anyone knows anyone at facebook, PLEASE try to get us in contact.

Solution #28 by Maxime Doucet worked for me:
 * go to facebook -> account -> privacy settings -> applications and websites settings -> "Remove unwanted or spammy applications" -> remove Gwibber

 I also tried removing .config/gwibber directory from my home, with no luck.

I don't know if Facebook's policies are the same as Twitter (see http://blog.nelhage.com/2010/09/dear-twitter/) but shouldn't there be a more permanent, flexible solution than more throttling? Is it possible to generate IDs per-user rather than for all Gwibber users? Apparently this is an inherent problem for OAuth desktop clients.

@Ken VanDine If you are right that this is caused by Facebook limiting requests by application instead of by user, wouldn't an app like Facebook for Blackberry have the same problem? I use this app, and it is reliable, giving me instant updates of any activity on my Facebook account. I don't have any stats on this, but I would imagine there must be many more Facebook requests coming from Blackberry & iPhone users than Gwibber users?

@Ken VanDine this is probably nothing you don't already know, but just in case it's useful, here is some contact info I found, with tips on best ways to get a response from Facebook:

http://www.contacthelp.com/directory/Internet/Web+Sites/Facebook?ListingID=324

Hope something there is helpful.

Closed-source, official applications may well get special treatment - just as they do for Twitter. That's why I posted the link.

They most likely do have negotiated deals to prevent the allocation problems. Regardless, I really want someone to be able to get official information on how the APIs count toward the allocation usage, our allocation should really be fine for our usage.

The API calls that are consistently way over our allocation is fql.query, which is an API that gives us the ability to query facebook with a similar syntax as SQL which helps narrow down the amount of data returned and also reduce the number of independent API calls. However, our fql queries have nested sub-queries, and I wonder if those count toward the allocation. Facebook's API docs suggest using fql.query or fql.multiquery whenever possible to reduce the data returned, so we should be doing the right thing there. For reference, our API calls for fql.query is consistently over 200% of our allocation with our number 2 API call always being around 1% of our allocation. In analyzing our requests, we make about 3 times as many fql.query calls as the other REST requests. So that percentage of allocation seems very skewed. I also wonder if there are bugs on facebook's side in calculating the allocation usage using the old REST API we are using. For Gwibber 3.0 I plan to move the facebook plugin to use their new graph API.

The worst thing about this bug is the nature of testing fixes, there is no way for me to try a fix and see what the results are. We have to push updates out to all of our users, and we have no way to ensure our users are upgrading gwibber. There is no way to tell which gwibber versions are out there and what versions are over-using the API. It is entirely possible that the previous fixes we have provided to Lucid users really are enough to fix the problem, but we just haven't had enough users upgrade gwibber to see the improvement.

We do know this problem started after the Lucid release, so most like the spike in Gwibber users cause by gwibber being included by default was the trigger. So clearly we need to get upgrades to all those users to see a difference, just no way of knowing how many upgraded. So trying new fixes is just stabbing in the dark. I haven't given up on chasing down someone from facebook to help explain it so we can ensure we are doing the right thing :)

@Ken VanDine Thanks for the great explanation. I don't understand half of the technical part of it, but I get the bottom line, and I appreciate all the work you and others are doing to get us up and running with Gwibber. Kudos!

I found that deleting the gwibber.sqlite as suggested somewhere didn't work for me. What did was removing :

.gconf/apps/gwibber/preferences/%gconf.xml

This was under the user profile. Soon as I did this it worked find and the size of the newly created xml file jumped up by 6 times the amount.

Paul.

Regarding testing: is it not possible to send the version number as part of some kind of client ID so you can see from your Facebook API account which versions are being used? And maybe test changes probabilistically - i.e. decide at runtime whether to use the old or new method. This would temporarily complicate the code of course, but once it's all understood the complexity can be removed again.

Unfortunately no, Facebook doesn't provide any way for us to track that kind of data.

#65 worked for me , thank you

This bug is also reported to FB's bug tracker at http://bugs.developers.facebook.net/show_bug.cgi?id=13040

#37 works for me... thanks ;)

In Ubuntu 10.04, I installed the ppa version of gwibber. I can confirm that now it works by deleting the files as explained in #65 and #89, including .config/gwibber/* and .gconf/apps/gwibber/*

I also have all loopbacks to 127.0.0.1, not sure if this is really needed. The procedure of first non-authorizing gwibber in facebook, deleting the files and then reauthorize gwibber as explained in #28 was then succesful.

Facebook is updating now and I can also send messages.

A continuation of the previous post #95. I am also using a username instead of email for authorizing facebook. I am also not sure of this is a need.

I add Facebook account to gwibber, but can't send messages. When I send message to facebook - nothing happened - message not added to facebook (((

I just updated from 10.04 to 10.10, and tried to add my Facebook account, but the "add" button didn't appear.
I simply changed my default browser to Firefox (it was Chromium) and tried again, wich worked!

Nevertheless, i cant send messages to facebook yet... :\

I was wrong. I can send messages to facebook, but with some delay (wierd network problems?). So, after changing my default browser to Firefox, add the account and changing the default browser to Chromium again, everything appears to work...

Bug 595265 seems to be a duplicate of this bug.

On Ubuntu 10.10, Gwibber 2.32.0.1, resolution in comment 36 did not work, but the resolution in #51 did. After the edit, Gwibber needs to be shut down and restarted.

For the benefit of the non-tech community who found this thread by searching and don't know how to edit the hosts file:

From the applications menu, choose the "Accessories" menu and then "terminal."
type:
     sudo gedit /etc/hosts
If prompted for your password, enter it
If you see:
    127.0.1.1 [Name of Your System]
Edit that number to read 127.0.0.1
Save and close the file
(Exit the terminal)
Shut down Gwibber and restart

Make it work by deleting the
~/.cache/desktop-couch
~/.config/desktop-couch
~/.local/share/desktop-couch

Then change the /etc/hosts

and login with me username and NOT the email

Thanks for all the suggestions

Posting to Facebook via MeMenu or Gwibber on Lucid solved!!! (via workaround)

Hello guys. I found a workaround for posting to Facebook via Gwibber in Lucid using a twitter account. I actually do not use twitter, so doing it like this does not bother me at all.

1. Create a twiiter account.

2. Add twitter account to Gwibber.

3. Go to: http://apps.facebook.com/twitter/ , link the two accounts and allow Twitter post to Facebook.

4. You are done! You can post using MeMenu to Facebook now.

Reading some of the posts here, I understood that it could be quite a long process to get Gwibber posting directly, so I thought a little bit, and came to my mind that surely Twitter itself has a way to post to Facebook. Google gave me the answer with its firt hit.

P.S.
Apparently there is an app that does not repost all the tweets. You will find it at: http://www.facebook.com/selectivetwitter
I have not tried this one, because for me it has not use. Does someone knows if it is working well or not??

I hope many people can enjoy this :-)

Solution promoted in #95 / #96 seemed to have worked for me.

To test 2.30.3 in Lucid and 2.32.2 in Maverick, restart gwibber-service and gwibber. You should notice "Facebook" doesn't have a "Replies" stream anymore.

As mentioned before, this fix won't be something that will just work, fixing the facebook allocation problem right away. We won't see the benefit from this fix until the update makes it to quite a few users. Based on the information facebook has provided, the API request we removed in this update was making 266 million database queries per day, so this fix should make a significant improvement.

Accepted gwibber into lucid-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

Accepted gwibber into maverick-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

I installed maverick-proposed version of gwibber and could add my facebook-account. Messages are shown and it seems to be working now.

Installed the update too. Does still not work. Deleted all config files before I tried the fix. I still cannot add my account. Is this really that hard?

Ok, works. I had to use the network-manager instead of indicator-network. With the last one, it doesn't run. Whatever...

for gwibber upstream its fix released since i have seen many people seeing positive results after the update. and as Ken said the problem will go away eventually.

gwibber 2.91.1 is in natty which includes the changes.

i have been using gwibber 2.32.1 and then later 2.32.2 but have not found any regression neither received any regression bug reports. on the other side facebook situation have improved alot so i am marking this as verification done.

I installed maverick-proposed version of gwibber, but it didn't work at the first time.
After removing : ~/.gconf/apps/gwibber/preferences/%gconf.xml I was able to add my facebook-account.

It seems to be working now.

This bug was fixed in the package gwibber - 2.30.3-0ubuntu1

---------------
gwibber (2.30.3-0ubuntu1) lucid-proposed; urgency=low

  * New upstream release.
    - Drop the responses operation from facebook, it abuses the allocation
      facebook gives us based on the DB query count (LP: #614742)
    - Backport fix for getting facebook comments embedded in the message
      content, which makes the removed responses operation un-needed.
  * -debian/patches/lp_653225.patch upstreamed
  * -debian/patches/refresh_timer.patch upstreamed
 -- Ken VanDine <email address hidden> Wed, 10 Nov 2010 22:40:41 -0500

This bug was fixed in the package gwibber - 2.32.2-0ubuntu1

---------------
gwibber (2.32.2-0ubuntu1) maverick-proposed; urgency=low

  * Drop the responses operation from facebook, it abuses the
    allocation facebook gives us based on the DB query count (LP: #614742)
  * Fixed notifications for private messages (LP: #663377)

gwibber (2.32.1-0ubuntu1) maverick-proposed; urgency=low

  * New upstream release (LP: #673161)
    - Backported fix for clearing multi-column streams when activated by
      the messaging indicator (LP: #643487)
    - Save window size/position when it changes, so it doesn't get moved
      unexpectedly when activated by the messaging indicator
    - Fixed dupe notifications as well as displaying dupes in the stream
    - Shouldn't display reply icon for messages from you (LP: #661330)
    - Private messages shouldn't allow public replies (LP: #661358)
    - Private messages shouldn't allow retweets (LP: #661359)
 -- Ken VanDine <email address hidden> Wed, 10 Nov 2010 23:14:44 -0500

unfortunately, i cannot confirm that this fix works.

gwibber 2.32.2-0ubuntu2 -> cannot add facebook.

launching gwibber from shell, i see:
> Saving...
> Couldn't find field: username

what do i neet to do to create a logfile?

This is not fixed.

Just installed Ubuntu 10.10 yesterday, and there was no add button after authorization.

Updated Gwibber to 2.32.2, and it still does not work.

gwibber-service -d -o
Gwibber Dispatcher: DEBUG Setting up monitors
Gwibber Dispatcher: DEBUG Refresh interval is set to 15
Gwibber Dispatcher: DEBUG ** Starting Refresh - 2010-12-21 11:15:21.17 **
Gwibber Dispatcher: DEBUG <twitter:receive> Performing operation
Gwibber Dispatcher: DEBUG libproxy: getting proxies
Gwibber Dispatcher: DEBUG <twitter:responses> Performing operation
Gwibber Dispatcher: DEBUG libproxy: getting proxies
Gwibber Dispatcher: DEBUG <twitter:responses> Finished operation
Gwibber Dispatcher: DEBUG <twitter:private> Performing operation
Gwibber Dispatcher: DEBUG libproxy: getting proxies
Gwibber Dispatcher: DEBUG <twitter:receive> Adding record
Gwibber Dispatcher: DEBUG <twitter:receive> Adding record
Gwibber Dispatcher: DEBUG <twitter:receive> Finished operation
Gwibber Dispatcher: DEBUG <twitter:lists> Performing operation
Gwibber Dispatcher: DEBUG libproxy: getting proxies
Gwibber Dispatcher: DEBUG libproxy: getting proxies
Gwibber Dispatcher: DEBUG libproxy: getting proxies
Gwibber Dispatcher: DEBUG <twitter:private> Finished operation
Gwibber Dispatcher: DEBUG <buzz:receive> Performing operation
Gwibber Dispatcher: DEBUG libproxy: getting proxies
Gwibber Dispatcher: DEBUG <twitter:lists> Adding record
Gwibber Dispatcher: DEBUG <twitter:lists> Adding record
Gwibber Dispatcher: DEBUG <twitter:lists> Adding record
Gwibber Dispatcher: DEBUG <twitter:lists> Adding record
Gwibber Dispatcher: DEBUG <twitter:lists> Adding record
Gwibber Dispatcher: DEBUG <twitter:lists> Adding record
Gwibber Dispatcher: DEBUG <twitter:lists> Finished operation
Traceback (most recent call last):
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/network.py", line 53, in __init__
    self.curl.perform()
error: (56, 'GnuTLS recv error (-9): A TLS packet with unexpected length was received.')
Gwibber Dispatcher: ERROR Failed to communicate with https://www.googleapis.com/buzz/v1/activities/@me/@consumption?oauth_nonce=22574045&oauth_timestamp=1292948170&oauth_consumer_key=anonymous&oauth_signature_method=HMAC-SHA1&oauth_version=1.0&oauth_token=1%2FSP8cnI_8TqFb_4G23yszErqH6AEOjx2uhLkTchxLEik&oauth_signature=AICMJ8A1oYuC0SwmTbfHOKGzmFw%3D&alt=json
Gwibber Dispatcher: ERROR <buzz:receive> Operation failed
Gwibber Dispatcher: DEBUG Traceback:
Traceback (most recent call last):
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/dispatcher.py", line 79, in perform_operation
    message_data = PROTOCOLS[account["service"]].Client(account)(opname, **args)
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/buzz.py", line 117, in __call__
    return getattr(self, opname)(**args)
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/buzz.py", line 120, in receive
    return self._get("activities/@me/@consumption")
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/buzz.py", line 113, in _get
    if parse: return [getattr(self, "_%s" % parse)(m) for m in data["data"][collection]]
KeyError: 'data'

Gwibber Dispatcher: INFO Loading complete: 1 - []

This clearly shows how Buzz doesn't work, but I see nothing about Facebook when I ...

are you using gwibber 2.32.2?

... if not(since you just installed maverick) please update your gwibber first and then try to add the account.

Yes, I am running 2.32.2. I said so in post #118 after saying I just installed Maverick. Sorry about including my log in a septate post. I didn't find the debug switch until later.

The add button just never shows up.

Same here, Omer. Running Gwibber 2.32.2 and when I attempt to add a Facebook account, after authorizing, I still never get an "Add" button.

For me the issue resolved only when I bypassed my proxy and connected to the Internet directly. When the proxy is enabled, the 'Add' button never appears. When it's disabled, the 'Add' button appears as expected. This is not an issue when adding a Twitter account, so apparently the Facebook account code doesn't traverse the proxy as gracefully as the Twitter code.

I went on our guest wireless system that does not require a proxy, went to system>preferences>network proxy and turned off all proxy settings. There was still no add button.

Its kind of frustrating that Ubuntu is packaged with apps that don't work properly through proxies if at all. Empathy has a lot of issues as well.

I've successfully added a Facebook account, but, I've changed the Facebook password, then I've no received updates anymore.
I've deleted the Facebook account from Gwibber, and when I attempt to add it again, I can't see the Add button after Authorize it.

Plus:
If I don't delete Gwibber from my Facebook applications, I can't authorize it, and the Add button don't show.

Regards!

Using Gwibber 2.32.2

Using gwibber 3.0.0.1-0ubuntu3, I cannot add my Facebook account. After entering username and password, the embedded browser frame becomes white and the String "Success" appears, nothing else. No Add button, nothing.

I get the following output when launching gwibber via Terminal:
Loading plugin for twitter
Loading plugin for facebook
Loading plugin for identica
Traceback (most recent call last):
  File "/usr/share/gwibber/plugins/facebook/gtk/facebook/__init__.py", line 121, in on_facebook_auth_title_change
    data = json.loads(urllib.urlopen("https://graph.facebook.com/me?access_token=" + self.account["access_token"]).read())
  File "/usr/lib/python2.7/urllib.py", line 84, in urlopen
    return opener.open(url)
  File "/usr/lib/python2.7/urllib.py", line 205, in open
    return getattr(self, name)(url)
  File "/usr/lib/python2.7/urllib.py", line 435, in open_https
    h.endheaders(data)
  File "/usr/lib/python2.7/httplib.py", line 951, in endheaders
    self._send_output(message_body)
  File "/usr/lib/python2.7/httplib.py", line 811, in _send_output
    self.send(msg)
  File "/usr/lib/python2.7/httplib.py", line 773, in send
    self.connect()
  File "/usr/lib/python2.7/httplib.py", line 1158, in connect
    self.sock = ssl.wrap_socket(sock, self.key_file, self.cert_file)
  File "/usr/lib/python2.7/ssl.py", line 344, in wrap_socket
    ciphers=ciphers)
  File "/usr/lib/python2.7/ssl.py", line 121, in __init__
    self.do_handshake()
  File "/usr/lib/python2.7/ssl.py", line 283, in do_handshake
    self._sslobj.do_handshake()
IOError: [Errno socket error] [Errno 1] _ssl.c:499: error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol

dpkg -s gwibber returns:
Package: gwibber
Status: install ok installed
Priority: optional
Section: misc
Installed-Size: 1392
Maintainer: Ubuntu Developers <email address hidden>
Architecture: all
Version: 3.0.0.1-0ubuntu3
Depends: python-dbus, python-gtk2, python-gconf, python-egenix-mxdatetime, python-simplejson, python-webkit, librsvg2-2, librsvg2-common, python-imaging, python-xdg, python-mako, python-gtkspell, python-wnck, python-oauth, gwibber-service (= 3.0.0.1-0ubuntu3), python (>= 2.6), python-central (>= 0.6.11)
Suggests: gwibber-themes, gwibber-service-flickr, gwibber-service-digg, gwibber-service-buzz, gwibber-service-statusnet, gwibber-service-foursquare, gwibber-service-friendfeed, gwibber-service-pingfm, gwibber-service-qaiku
Conffiles:
 /etc/xdg/autostart/gwibber.desktop 6375e4874fa720f900c9407348998716
Description: Open source social networking client for GNOME
 Gwibber is a social networking client for GNOME. It supports Facebook,
 Twitter, Identi.ca, StatusNet, FriendFeed, Qaiku, Flickr, and Digg.
 .
 This package includes the Gwibber desktop client
Homepage: https://launchpad.net/gwibber
Python-Version: >=2.6

For me, it's happening on

Ubuntu 12.04
Gwibber 3.4.2

I have tried

Web browser --> Facebook --> Apps --> My Apps --> Remove Gwibber
Quit browser
Start Gwibber
Create Facebook account and authorise again, giving the same 'Success' message, but quitting Gwibber and restarting it shows only my (good) Twitter account.