Public bug reported:

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

** Affects: gwibber (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: apport-bug i386 lucid

-- 
 Gwibber Stopped working with Twitter on separate machines
https://bugs.launchpad.net/bugs/623497
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to