Sometimes gwibber doesn't send updates to FB

[Juan Simón]

Sometimes gwibber doesn't send updates to FB, neither it shows error!
Ever this application will do well, at least, the basic: send/receive updates?
---
Architecture: i386
DistroRelease: Ubuntu 10.04
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
NonfreeKernelModules: nvidia
Package: gwibber 2.31.2~bzr750-0ubuntu1~daily1 [modified: usr/share/gwibber/ui/gwibber-accounts-dialog.ui]
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, user)
 LANG=es_ES.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-23.37-generic-pae 2.6.32.15+drm33.5
Tags: lucid
Uname: Linux 2.6.32-23-generic-pae i686
UnreportableReason: This is not a genuine Ubuntu package
UserGroups: adm admin cdrom dialout dip fax floppy fuse lpadmin nopasswdlogin plugdev sambashare tape users vboxusers video winbindd_priv

[Juan Simón (simonbcn)]

apport information

[Juan Simón (simonbcn)]

Testing with Gwibber 2.30.0.1 and same problem.
Gwibber now doesn't send NEVER my messages to facebook!

[Omer Akram (om26er)]

maybe gwibber-service -do will show something. please attach those logs

[Juan Simón (simonbcn)]

$ gwibber-service -do
Updating...
Gwibber Dispatcher: DEBUG Setting up monitors
Gwibber Dispatcher: DEBUG Monitors are up
Gwibber Dispatcher: INFO Gwibber Service is reloading account credentials
Gwibber Dispatcher: DEBUG Refresh interval is set to 7
Gwibber Dispatcher: DEBUG ** Starting Refresh - Thu Jul 8 20:31:36 2010 **
Gwibber Dispatcher: DEBUG <facebook:receive> Performing operation
Gwibber Dispatcher: DEBUG <facebook:images> Performing operation
Gwibber Dispatcher: DEBUG <facebook:responses> Performing operation
Gwibber Dispatcher: DEBUG <identica:receive> Performing operation
Gwibber Dispatcher: ERROR <facebook:receive> Operation failed
Gwibber Dispatcher: DEBUG Traceback:
Traceback (most recent call last):
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/dispatcher.py", line 75, in perform_operation
    message_data = PROTOCOLS[account["protocol"]].Client(account)(opname, **args)
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/facebook.py", line 198, in __call__
    return getattr(self, opname)(**args)
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/facebook.py", line 210, in receive
    profiles = dict((p["id"], p) for p in data["profiles"])
KeyError: 'profiles'

Gwibber Dispatcher: DEBUG <identica:responses> Performing operation
Gwibber Dispatcher: DEBUG <identica:receive> Finished operation
Gwibber Dispatcher: DEBUG <identica:private> Performing operation
Gwibber Dispatcher: ERROR <facebook:responses> Operation failed
Gwibber Dispatcher: DEBUG Traceback:
Traceback (most recent call last):
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/dispatcher.py", line 75, in perform_operation
    message_data = PROTOCOLS[account["protocol"]].Client(account)(opname, **args)
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/facebook.py", line 198, in __call__
    return getattr(self, opname)(**args)
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/facebook.py", line 220, in responses
    profiles = self._friends()
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/facebook.py", line 195, in _friends
    return dict((p["uid"], p) for p in friends)
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/facebook.py", line 195, in <genexpr>
    return dict((p["uid"], p) for p in friends)
TypeError: string indices must be integers

Gwibber Dispatcher: DEBUG <twitter:receive> Performing operation
Gwibber Dispatcher: DEBUG <identica:private> Finished operation
Gwibber Dispatcher: DEBUG <twitter:responses> Performing operation
Gwibber Dispatcher: DEBUG <twitter:responses> Finished operation
Gwibber Dispatcher: DEBUG <twitter:private> Performing operation
Gwibber Dispatcher: ERROR <facebook:images> Operation failed
Gwibber Dispatcher: DEBUG Traceback:
Traceback (most recent call last):
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/dispatcher.py", line 75, in perform_operation
    message_data = PROTOCOLS[account["protocol"]].Client(account)(opname, **args)
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/facebook.py", line 198, in __call__
    return getattr(self, opname)(**args)
  File "...

[Omer Akram (om26er)]

thanks for the bug report. can you please try the latest build of gwibber from the gwibber ppa. it resolves many facebook related problems and should solve the one you are facing too

[Juan Simón (simonbcn)]

I have read your changelog of last version, especially this part:
"All of these fixes are related to reducing the number of calls we make to facebook and reducing the size of the result. Facebook throttles application wide, not per-user based on usage. This throttling is the root cause for (LP: #552227) and (LP: #595265) and probably many other bug reports where facebook rejects gwibber."

This is the most absurd decision of Facebook developers. There are multiple Facebook clients who are suffering the same problem.
By other side, FB doesn't distinguish between client versions, so even if you shall have you changed the number of calls to the FB API in last gwibber version, while all of us not to use this last version we will continue to be affected by this problem.
This change should be in all versions, including the stable, so that the solution actually works. Don't you think?

[Omer Akram (om26er)]

the change has been proposed for the stable version too but it will take a
bit of time to get into the stable version

On Fri, Jul 9, 2010 at 5:57 PM, Simon <email address hidden> wrote:

> I have read your changelog of last version, especially this part:
> "All of these fixes are related to reducing the number of calls we make to
> facebook and reducing the size of the result. Facebook throttles
> application wide, not per-user based on usage. This throttling is the root
> cause for (LP: #552227) and (LP: #595265) and probably many other bug
> reports where facebook rejects gwibber."
>
> This is the most absurd decision of Facebook developers. There are multiple
> Facebook clients who are suffering the same problem.
> By other side, FB doesn't distinguish between client versions, so even if
> you shall have you changed the number of calls to the FB API in last gwibber
> version, while all of us not to use this last version we will continue to be
> affected by this problem.
> This change should be in all versions, including the stable, so that the
> solution actually works. Don't you think?
>
> --
> Sometimes gwibber doesn't send updates to FB
> https://bugs.launchpad.net/bugs/603146
> You received this bug notification because you are subscribed to
> Gwibber.
>
> Status in Gwibber: Incomplete
>
> Bug description:
> Sometimes gwibber doesn't send updates to FB, neither it shows error!
> Ever this application will do well, at least, the basic: send/receive
> updates?
> ---
> Architecture: i386
> DistroRelease: Ubuntu 10.04
> InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
> NonfreeKernelModules: nvidia
> Package: gwibber 2.31.2~bzr750-0ubuntu1~daily1 [modified:
> usr/share/gwibber/ui/gwibber-accounts-dialog.ui]
> PackageArchitecture: all
> ProcEnviron:
> PATH=(custom, user)
> LANG=es_ES.utf8
> SHELL=/bin/bash
> ProcVersionSignature: Ubuntu 2.6.32-23.37-generic-pae 2.6.32.15+drm33.5
> Tags: lucid
> Uname: Linux 2.6.32-23-generic-pae i686
> UnreportableReason: This is not a genuine Ubuntu package
> UserGroups: adm admin cdrom dialout dip fax floppy fuse lpadmin
> nopasswdlogin plugdev sambashare tape users vboxusers video winbindd_priv
>
>
>
>

[Juan Simón (simonbcn)]

It still fails.
I guess it will be solved when most gwibber users adopt the last version.

[Juan Simón (simonbcn)]

Sorry for this little Off-toppic, but it's only one question: Is it true that this limitation API calls was not warned by FB to the developers? And that it is not even documented?