gwibber-accounts crashed with IOError in put_in_keyring()
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| gwibber (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
This happened after authorizing a new Twitter account for Gwibber (after the “Redirecting back to the application” message). The new account wasn’t added to Gwibber.
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gwibber 3.1.4-0ubuntu2
ProcVersionSign
Uname: Linux 3.0.0-7-generic i686
NonfreeKernelMo
Architecture: i386
Date: Tue Jul 26 20:49:49 2011
ExecutablePath: /usr/bin/
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110723)
InterpreterPath: /usr/bin/python2.7
ProcCmdline: python /usr/bin/
ProcEnviron:
LANGUAGE=es_MX:es
LANG=es_MX.UTF-8
SHELL=/bin/bash
PythonArgs: ['/usr/
SourcePackage: gwibber
Title: gwibber-accounts crashed with IOError in put_in_keyring()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
| Adolfo Jayme Barrientos (fitojb) wrote | #1 |
| visibility: | private → public |
| Victor Vargas (kamus) wrote | #2 |
Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 813755, so it 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.