Comment 42 for bug 530195

Revision history for this message
Aditya (adityapatadia) wrote : Re: Twitter doesn't work at all

I am getting following output in gwibber.log file

2010-05-01 00:21:49,925 - Gwibber Accounts - INFO - Running from the system path
2010-05-01 00:21:52,975 - Gwibber Service - INFO - Running from the system path
2010-05-01 00:21:54,265 - Gwibber Service - INFO - Running from the system path
2010-05-01 00:21:55,322 - Gwibber Dispatcher - INFO - Gwibber Service is reloading account credentials
2010-05-01 00:22:16,548 - Gwibber Dispatcher - INFO - Gwibber Service is reloading account credentials
2010-05-01 00:22:19,419 - Gwibber Dispatcher - ERROR - <twitter:responses> Operation failed
2010-05-01 00:22:24,658 - Gwibber GNOME Client - INFO - Running from the system path
2010-05-01 00:22:24,792 - Gwibber Dispatcher - ERROR - Failed to communicate with https://twitter.com/statuses/home_timeline.json?count=200
2010-05-01 00:22:24,793 - Gwibber Dispatcher - ERROR - Failed to parse the response, error was: No JSON object could be decoded
2010-05-01 00:22:24,793 - Gwibber Dispatcher - ERROR - <twitter:receive> Operation failed
2010-05-01 00:22:27,482 - Gwibber Dispatcher - ERROR - Failed to communicate with https://twitter.com/direct_messages.json?count=200
2010-05-01 00:22:27,482 - Gwibber Dispatcher - ERROR - Failed to parse the response, error was: No JSON object could be decoded
2010-05-01 00:22:27,483 - Gwibber Dispatcher - ERROR - <twitter:private> Operation failed
2010-05-01 00:22:27,483 - Gwibber Dispatcher - INFO - Loading complete: 1 - ['Failure', 'Failure', 'Failure']
2010-05-01 00:22:33,776 - Gwibber Dispatcher - ERROR - <twitter:responses> Operation failed
2010-05-01 00:22:34,043 - Gwibber Dispatcher - ERROR - <twitter:receive> Operation failed
2010-05-01 00:22:42,170 - Gwibber Dispatcher - INFO - Loading complete: 2 - ['Failure', 'Failure', 'Success']

Hope this will help...

I am also getting the output in terminal which is same as in comment #3