gwibber crashed with RuntimeError in run_couchdb()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gwibber (Ubuntu) |
In Progress
|
High
|
Chad Miller |
Bug Description
Binary package hint: gwibber
Migrated to Lucid, first time I open gwibber... did it from command line, just to check.
It seems it tried to access my keyring, so I put my password, and gwibber crashed.
Then, I tried once more, and it worked ok... maybe the time elapsed when I was inserting the password made the difference?
Anyway, extra points if you fix this raise:
File "/usr/lib/
raise RuntimeError(
it should be:
raise RuntimeError(
ProblemType: Crash
Architecture: i386
Date: Wed Mar 10 09:28:11 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/gwibber
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
InterpreterPath: /usr/bin/python2.6
NonfreeKernelMo
Package: gwibber 2.29.91-0ubuntu1
PackageArchitec
ProcCmdline: /usr/bin/python /usr/bin/gwibber
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, user)
LANG=es_AR.UTF-8
ProcVersionSign
PythonArgs: ['/usr/
SourcePackage: gwibber
Title: gwibber crashed with RuntimeError in run_couchdb()
Uname: Linux 2.6.32-
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
Ah, of the format, this goes to show why logging. Level(" format string", arguments...) is evil. You can't trivially change the call to be a new Exception to be raised.