Gwibber Stopped working with Twitter on separate machines

Bug #623497 reported by Sam Williams
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gwibber (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: gwibber

Trying to attach this report to ticket #623490, but was unable to find the ticket once I generated the report.

In the last 24 hours I've started encountering Twitter errors with Gwibber on at least two separate machines. My last accepted tweet on one machine was about 24 hours ago, the other was within 12. In neither case can I received any updates. I've been looking for the troubleshooting guide for both Gwibber and couchdb and can't find them on the help site either.

Here is the last snippet from ~/.cache/gwibber/gwibber.log:-------------------------------------------
2010-08-24 11:47:29,152 - Gwibber Dispatcher - ERROR - Failed to parse the response, error was: No JSON object could be decoded
2010-08-24 11:47:36,468 - Gwibber Dispatcher - ERROR - <twitter:receive> Operation failed
2010-08-24 11:47:41,202 - Gwibber Dispatcher - ERROR - <twitter:responses> Operation failed
2010-08-24 11:47:45,306 - Gwibber Dispatcher - ERROR - <twitter:private> Operation failed
2010-08-24 11:47:48,833 - Gwibber Dispatcher - ERROR - <twitter:user_messages> Operation failed
2010-08-24 11:47:48,836 - Gwibber Dispatcher - INFO - Loading complete: 21 - ['Failure', 'Success', 'Success', 'Failure', 'Failure', 'Failure', 'Failure']
2010-08-24 11:50:44,068 - Gwibber Dispatcher - ERROR - <twitter:receive> Operation failed
2010-08-24 11:50:51,327 - Gwibber Dispatcher - INFO - Loading complete: 22 - ['Success', 'Success', 'Success', 'Failure', 'Success', 'Success', 'Success']
2010-08-24 11:53:31,306 - Gwibber Dispatcher - ERROR - Failed to parse the response, error was: No JSON object could be decoded
2010-08-24 11:53:46,174 - Gwibber Dispatcher - ERROR - <twitter:receive> Operation failed
2010-08-24 11:53:56,181 - Gwibber Dispatcher - INFO - Loading complete: 23 - ['Failure', 'Success', 'Success', 'Failure', 'Success', 'Success', 'Success']
2010-08-24 11:56:44,669 - Gwibber Dispatcher - ERROR - <twitter:receive> Operation failed
2010-08-24 11:56:56,738 - Gwibber Dispatcher - INFO - Loading complete: 24 - ['Success', 'Success', 'Success', 'Failure', 'Success', 'Success', 'Success']
2010-08-24 11:59:43,349 - Gwibber Dispatcher - ERROR - <twitter:receive> Operation failed
2010-08-24 11:59:54,522 - Gwibber Dispatcher - INFO - Loading complete: 25 - ['Success', 'Success', 'Success', 'Failure', 'Success', 'Success', 'Success']==============================================

I am running two fully updated 10.04.1 installations. The rest of my software looks as follows:
LSB Version: core-2.0-ia32:core-2.0-noarch:core-3.0-ia32:core-3.0-noarch:core-3.1-ia32:core-3.1-noarch:core-3.2-ia32:core-3.2-noarch:core-4.0-ia32:core-4.0-noarch
Distributor ID: Ubuntu
Description: Ubuntu 10.04.1 LTS

gwibber 2.30.1-0ubuntu1 Open source social networking client for GNOME

I was using the "compact" theme, but changing that didn't help at all.

I've tried everything to get this going again. I't would appear its something directly in gwibber . I wanted to explore this in depth, but for the life of me I can't find the troubleshooting guide any more.

Thanks for looking into this issue!

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: gwibber 2.30.1-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-22.36-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Tue Aug 24 12:16:09 2010
ExecutablePath: /usr/bin/gwibber
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
InterpreterPath: /usr/bin/python2.6
PackageArchitecture: all
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gwibber

Revision history for this message
Sam Williams (sam-williams) wrote :
Revision history for this message
Sam Williams (sam-williams) wrote :

Just found the debugging guide, please ignore that part of the comment above.

Revision history for this message
Sam Williams (sam-williams) wrote :

Decided there might have been a problem with my account. Recreated and fired up gwibber one more time. Here is the start of gwibber.log:

2010-08-24 12:38:39,188 - Gwibber GNOME Client - INFO - Running from the system path
2010-08-24 12:38:42,174 - Gwibber Service - INFO - Running from the system path
2010-08-24 12:38:44,577 - Gwibber Dispatcher - INFO - Gwibber Service is reloading account credentials
2010-08-24 12:39:00,086 - Gwibber Dispatcher - ERROR - <twitter:receive> Operation failed
2010-08-24 12:39:04,213 - Gwibber Dispatcher - ERROR - <twitter:responses> Operation failed
2010-08-24 12:39:08,096 - Gwibber Dispatcher - ERROR - <twitter:private> Operation failed
2010-08-24 12:39:11,224 - Gwibber Dispatcher - ERROR - <twitter:user_messages> Operation failed
2010-08-24 12:39:11,237 - Gwibber Dispatcher - INFO - Loading complete: 1 - ['Success', 'Success', 'Success', 'Failure', 'Failure', 'Failure', 'Failure']
2010-08-24 12:41:57,288 - Gwibber Dispatcher - ERROR - <twitter:receive> Operation failed
2010-08-24 12:41:59,801 - Gwibber Dispatcher - ERROR - <twitter:responses> Operation failed
2010-08-24 12:42:02,412 - Gwibber Dispatcher - ERROR - <twitter:private> Operation failed
2010-08-24 12:42:04,962 - Gwibber Dispatcher - ERROR - <twitter:user_messages> Operation failed
2010-08-24 12:42:04,963 - Gwibber Dispatcher - INFO - Loading complete: 2 - ['Success', 'Success', 'Success', 'Failure', 'Failure', 'Failure', 'Failure']
2010-08-24 12:44:55,270 - Gwibber Dispatcher - ERROR - <twitter:receive> Operation failed
2010-08-24 12:44:57,387 - Gwibber Dispatcher - ERROR - <twitter:responses> Operation failed
2010-08-24 12:45:01,617 - Gwibber Dispatcher - ERROR - <twitter:private> Operation failed
2010-08-24 12:45:04,126 - Gwibber Dispatcher - ERROR - <twitter:user_messages> Operation failed
2010-08-24 12:45:04,133 - Gwibber Dispatcher - INFO - Loading complete: 3 - ['Success', 'Success', 'Success', 'Failure', 'Failure', 'Failure'

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.