Gwibber does not show any tweets, timelines are empty

[Jeroen Brandligt]

Binary package hint: gwibber

Gwibber does not show anything, completely emtpy. No errors or nothing. Just emptyness... Happened after some update or upgrade to 10.04
---
Architecture: i386
DistroRelease: Ubuntu 10.04
Package: gwibber 2.30.0.1-0ubuntu3
PackageArchitecture: all
ProcEnviron:
 LANG=nl_NL.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
Tags: lucid
Uname: Linux 2.6.32-22-generic i686
UserGroups: adm admin audio cdrom dialout dip fax fuse lpadmin netdev plugdev sambashare tape video www-data

[Dr. Kenobi (drkenobi)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem.

To be considered complete, a bug report should normally contain:

    * The version of Ubuntu you are running
    * The version of the package you are using (look at Synaptic Package Manager)
    * The actions taken to produce the problem
    * Whether or not it is possible for to reproduce the bug
    * The expected result of these actions
    * The actual result of these actions

Please add more information running this in a terminal: apport-collect 579603

Also run gwibber in a terminal and 'copy & paste' it.

This page could also be useful: https://help.ubuntu.com/community/ReportingBugs

It's also good to update to the latest Gwibber version. Activate the pre-release updates in 'System --> Administration --> Software Sources --> Updates --> Pre-release updates (lucid-proposed)". You could fix the problem in a few seconds. Maybe the bug is already fixed.

[Jeroen Brandligt (jbrandligt)]

Ok, here some additional information:

Ubuntu version: 10.04
Package version: 2.30.0.1-0ubuntu3 (from pre-released updates)
It occurs every time i start Gwibber, so I can't NOT reproduce the bug

Starting from terminal shows this:
** (gwibber:7252): WARNING **: Trying to register gtype 'WnckWindowState' as enum when in fact it is of type 'GFlags'

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

** (gwibber:7252): WARNING **: Trying to register gtype 'WnckWindowMoveResizeMask' as enum when in fact it is of type 'GFlags'
Updating...
Updating...

[Dr. Kenobi (drkenobi)]

Please add more information running this in a terminal: apport-collect 579603

[Jeroen Brandligt (jbrandligt)]

apport information

[Omer Akram (om26er)]

Please do the following in a terminal and attach the logs here.

$ sudo pkill gwibber
$ gwibber-service -d -o

[Jeroen Brandligt (jbrandligt)]

jeroen@jeroen-thuis:~$ sudo pkill gwibber
[sudo] password for jeroen:
jeroen@jeroen-thuis:~$ gwibber-service -d -o
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 5
Gwibber Dispatcher: DEBUG ** Starting Refresh - Mon May 17 13:42:21 2010 **
Gwibber Dispatcher: DEBUG <twitter:responses> Performing operation
Gwibber Dispatcher: DEBUG <twitter:receive> 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: (6, 'name lookup timed out')
Gwibber Dispatcher: ERROR Failed to communicate with https://twitter.com/statuses/mentions.json?count=200
Gwibber Dispatcher: ERROR Failed to parse the response, error was: No JSON object could be decoded
Gwibber Dispatcher: ERROR <twitter: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/twitter.py", line 146, in __call__
    return getattr(self, opname)(**args)
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/twitter.py", line 155, in responses
    return self._get("statuses/mentions.json", count=count, since_id=since)
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/twitter.py", line 136, in _get
    if data.has_key("error"):
AttributeError: 'str' object has no attribute 'has_key'

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')
Gwibber Dispatcher: ERROR Failed to communicate with https://twitter.com/statuses/home_timeline.json?count=200
Gwibber Dispatcher: ERROR Failed to parse the response, error was: No JSON object could be decoded
Gwibber Dispatcher: ERROR <twitter: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/twitter.py", line 146, in __call__
    return getattr(self, opname)(**args)
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/twitter.py", line 149, in receive
    return self._get("statuses/home_timeline.json", count=count, since_id=since)
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/twitter.py", line 136, in _get
    if data.has_key("error"):
AttributeError: 'str' object has no attribute 'has_key'

Gwibber Dispatcher: DEBUG <twitter:private> Performing operation
Traceback (most recent call last):
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/network.py", line 32, in __init__
   ...

[Omer Akram (om26er)]

thanks for the bug report this particular bug has already been reported but feel free to report any other bugs you may find. on the duplicate bug report there is a suggestion that using open dns solves the problem for a few people.