Gwibber stops updating
Bug #576764 reported by
Daniel de Souza Ramos
This bug report is a duplicate of:
Bug #530195: gwibber tries to call has_key on list---doesn't update streams.
Edit
Remove
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gwibber (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: gwibber
Frequently, with no aparent reason, Gwibber stops updating Twitter timeline. And it doesn't solve closing the application and openning it again. I don't know if it's only with Twitter, because it's the only account I use on Gwibber.
To post a comment you must log in.
Gwibber not updating timeline
I was previously using Gwibber released with Lucid. It was working at first but after a reboot, it doesn't update the timeline anymore. I removed version 2.30.01 and installed the one from the PPA. It worked. It updates the timeline and all others. After a reboot, again, it suddenly went back to its old self of not updating the timeline. I am able to send tweets and see my own tweets, but not the tweets from others.
Here's what I get from running gwibber-service:
$ gwibber-service -o -d python2. 6/dist- packages/ gwibber/ microblog/ network. py", line 32, in __init__ curl.perform( ) /twitter. com/statuses/ home_timeline. json?count= 200&since_ id=13605537625 python2. 6/dist- packages/ gwibber/ microblog/ dispatcher. py", line 81, in perform_operation account[ "protocol" ]].Client( account) (opname, **args) python2. 6/dist- packages/ gwibber/ microblog/ twitter. py", line 146, in __call__ python2. 6/dist- packages/ gwibber/ microblog/ twitter. py", line 149, in receive "statuses/ home_timeline. json", count=count, since_id=since) python2. 6/dist- packages/ gwibber/ microblog/ twitter. py", line 136, in _get key("error" ):
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 - Sun May 9 16:29:03 2010 **
Gwibber Dispatcher: DEBUG <twitter:receive> Performing operation
Gwibber Dispatcher: DEBUG <twitter:responses> Performing operation
Gwibber Dispatcher: DEBUG <twitter:responses> Finished operation
Gwibber Dispatcher: DEBUG <twitter:private> Performing operation
Gwibber Dispatcher: DEBUG <twitter:private> Finished operation
Traceback (most recent call last):
File "/usr/lib/
self.
error: (28, 'Operation timed out after 15000 milliseconds with 168000 out of 274756 bytes received')
Gwibber Dispatcher: ERROR Failed to communicate with https:/
Gwibber Dispatcher: ERROR Failed to parse the response, error was: Expecting object: line 1 column 168000 (char 168000)
Gwibber Dispatcher: ERROR <twitter:receive> Operation failed
Gwibber Dispatcher: DEBUG Traceback:
Traceback (most recent call last):
File "/usr/lib/
message_data = PROTOCOLS[
File "/usr/lib/
return getattr(self, opname)(**args)
File "/usr/lib/
return self._get(
File "/usr/lib/
if data.has_
AttributeError: 'str' object has no attribute 'has_key'
Gwibber Dispatcher: INFO Loading complete: 1 - ['Failure', 'Success', 'Success']
After restarting gwibber-service, it finally updated my timeline. So as a workaround, I would suggest unchecking the "Start service at login" option in the Options tab of Gwibber's Preferences. Reboot (or Log out and back in again) and see if it works for you.
I have rebooted once already and it seems to be working for now. HTH.