application crashed on its first use on a very fresh install of lucid - all updates were applied and os restarted, application was opened alongside the Ubuntu Software Center but never appeared. I was then informed that it crashed; gwibber crashed with RuntimeError in run_couchdb()

[brendan boehr]

Binary package hint: gwibber

Just installed Lucid for the first time on my Fujitsu Lifebook T2010 tablet. I installed all recommended updates, restarted, and opened Gwibber for the first time. While it was loading I decided to check out the Ubuntu Software Center. Gwibber never appeared and I only knew that it had crashed when the crash reporter told me so.

# lsb_release -rd:
Description: Ubuntu lucid (development branch)
Release: 10.04

# apt-cache policy gwibber:
gwibber:
  Installed: 2.29.95-0ubuntu2
  Candidate: 2.29.95-0ubuntu2
  Version table:
 *** 2.29.95-0ubuntu2 0
        500 http://ca.archive.ubuntu.com/ubuntu/ lucid/main Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: gwibber 2.29.95-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.32-20.29-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-20-generic i686
Architecture: i386
Date: Mon Apr 12 01:27:33 2010
ExecutablePath: /usr/bin/gwibber
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100406.1)
InterpreterPath: /usr/bin/python2.6
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/gwibber
ProcEnviron:
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
PythonArgs: ['/usr/bin/gwibber']
SourcePackage: gwibber
Title: gwibber crashed with RuntimeError in run_couchdb()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #551781, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.