gwibber-bugs team mailing list archive

[Eric B <eric.broszeit@xxxxxxxxx>]

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 try to add the account.

-- 
You received this bug notification because you are a member of Gwibber
Bug Heros, which is subscribed to Gwibber.
https://bugs.launchpad.net/bugs/614742

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

Status in Gwibber:
  Fix Released
Status in “gwibber” package in Ubuntu:
  Fix Released
Status in “gwibber” source package in Lucid:
  Fix Released
Status in “gwibber” source package in Maverick:
  Fix Released

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.