Gwibber Daily times out on low bandwidth connections

Bug #524132 reported by Simon Ives on 2010-02-18
44
This bug affects 10 people
Affects Status Importance Assigned to Milestone
Gwibber
Undecided
Unassigned

Bug Description

I first reported this behaviour here -> https://bugs.launchpad.net/gwibber/+bug/521569 <- but under advice have relisted the bug.

On my shaped Internet connection at home (64k) Gwibber is unable to update feeds from any of the accounts I have created (Twitter, Identi.ca, Facebook, and Flickr). When using Gwibber at work (the same install on the same computer) (1200k) all features appear to work fine.

When running gwibber-service from the command line (so I could see what was going on) it appears that gwibber-service is timing out before all of the data for each connection can be received.

I've attached a file (gwibber-service.txt) of the command line messages from gwibber-service that hopefully explains things a little more properly.

Running Gwibber 2.29.1 Daily on Ubuntu 9.10

Simon Ives (simon-simonives) wrote :
pak33m (pak33m) wrote :

The same has been happening to me only with updates from identi.ca as that's all I have configured. Since installing gwibber both from the lucid repos and the daily builds I've never received any messages.

Just to see I did a ping to identi.ca, added 174.142.114.102 identi.ca to /etc/hosts, started gwibber-service in the command line, confirmed that gwibber-service was updating (and taking much longer this time instead of timing out), launched gwibber from the mail icon and I finally had my messages.

Sprinky (rkallos) wrote :

I had a similar timeout issue, but with my Twitter account. Adding the Twitter IP to /etc/hosts fixed the issue.

Jacob Henderson (lmeditato) wrote :

Yeah, I was wondering why I wasn't getting gnome notifications about my feeds while the main gwibber window is closed, it's because gwibber-service does this when updating....

Updating...
Traceback (most recent call last):
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/network.py", line 32, in __init__
    self.curl.perform()
error: (28, 'Operation timed out after 15000 milliseconds with 0 bytes received')

So yeah, gwibber-service doesn't work, but gwibber does. They're separate issues.

tags: added: gwibber-service
Jacob Henderson (lmeditato) wrote :
Download full text (3.9 KiB)

Here is my debug mode error code:

Updating...
Gwibber Dispatcher: DEBUG Setting up monitors
Gwibber Dispatcher: DEBUG Monitors are up
Gwibber Dispatcher: DEBUG Refresh interval is set to 5
Gwibber Dispatcher: DEBUG ** Starting Refresh - Thu Mar 25 16:28:41 2010 **
Gwibber Dispatcher: DEBUG <facebook:responses> Performing operation
Gwibber Dispatcher: DEBUG <facebook:receive> Performing operation
Gwibber Dispatcher: DEBUG <facebook:receive> Finished operation
Gwibber Dispatcher: DEBUG <facebook:images> Performing operation
Traceback (most recent call last):
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/network.py", line 32, in __init__
    self.curl.perform()
error: (28, 'connect() timed out!')
Gwibber Dispatcher: ERROR Failed to communicate with https://api.facebook.com/restserver.php?api_key=71b85c6d8cb5bbb9f1a3f8bbdcdd4b05&v=1.0&sig=a369b56053fbd73c0059499e481dd3e2&format=json&query=%0A++++++SELECT+owner%2C+object_id%2C+created%2C+src_small%2C+src_big%2C+link%2C+caption%0A++++++++FROM+photo+WHERE+aid+in%0A++++++++%28SELECT+aid+FROM+album+WHERE+owner+IN%0A++++++++%28SELECT+uid2+FROM+friend+WHERE+uid1%3D1164601033%29%29%0A++++++++ORDER+BY+created+DESC+LIMIT+1%2C100%0A++++++&session_key=32ba28e8d9c78b4780cf32dd-1164601033&method=facebook.fql.query&call_id=1269548927000
Gwibber Dispatcher: ERROR Failed to parse the response, error was: No JSON object could be decoded
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 64, 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 233, in images
    return [self._image(post, profiles) for post in data]
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/facebook.py", line 165, in _image
    user = profiles[data["owner"]]
TypeError: string indices must be integers, not str

Traceback (most recent call last):
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/network.py", line 32, in __init__
    self.curl.perform()
error: (28, 'Operation timed out after 15000 milliseconds with 0 bytes received')
Gwibber Dispatcher: ERROR Failed to communicate with https://api.facebook.com/restserver.php?api_key=71b85c6d8cb5bbb9f1a3f8bbdcdd4b05&v=1.0&sig=ec8145df4edecf2669d5561d925ea735&format=json&query=%0A++++++SELECT+id%2C+post_id%2C+time%2C+fromid%2C+text%2C+object_id+FROM+comment+WHERE+post_id+IN%0A++++++++%28SELECT+post_id+FROM+stream+WHERE+source_id+%3D+1164601033%29+AND%0A++++++++fromid+%3C%3E+1164601033+ORDER+BY+time+DESC+LIMIT+1%2C100%0A++++++&session_key=32ba28e8d9c78b4780cf32dd-1164601033&method=facebook.fql.query&call_id=1269548921000
Gwibber Dispatcher: ERROR Failed to parse the response, error was: No JSON object could be decoded
Gwibber Dispatcher: ERROR <facebook:responses> Operation failed
Gwibber Dispatcher: DEB...

Read more...

Omer Akram (om26er) wrote :

Simon can you please confirm if this is still an issue under gwibber 2,29.95 I think this was fixed

Changed in gwibber:
status: New → Incomplete

It is still on 2.30.0.1.

Mike O (mike-orbinpost) wrote :

I am failing to refresh either twitter or identica.

On 2.30.0.1, when I run gwibber-service from the command line I get this output:
Updating...
Traceback (most recent call last):
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/network.py", line 32, in __init__
Traceback (most recent call last):
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/network.py", line 32, in __init__
    self.curl.perform()
error: (6, 'name lookup timed out')
    self.curl.perform()
error: (6, 'name lookup timed out')
Traceback (most recent call last):
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/network.py", line 32, in __init__
    self.curl.perform()
error: (6, 'name lookup timed out')

Stuart Bishop (stub) on 2010-05-20
Changed in gwibber:
status: Incomplete → New
anthony llinares (dvi43) wrote :

sorry for my english I'm not specialist, I resolved this bug for the ISP Orange in france by changing the dns servers, it seems orange's dns blocking twitter via gwibber so try to change your dns it may work

Ryan Paul (segphault) on 2010-06-26
Changed in gwibber:
status: New → Fix Committed
Omer Akram (om26er) wrote :

this bug is fixed in gwibber 2.31.2 and gwibber 2.30.1

Changed in gwibber:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers