gwibber-accounts crashed with IOError in put_in_keyring()

Bug #868522 reported by Dražen Matešić
This bug report is a duplicate of:  Edit Remove
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gwibber (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Tried creating a new account..after twitter successfully authorized access gwibber crashed.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gwibber 3.2.0.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 1.23-0ubuntu2
Architecture: amd64
Date: Wed Oct 5 18:36:12 2011
ExecutablePath: /usr/bin/gwibber-accounts
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110920.5)
InterpreterPath: /usr/bin/python2.7
ProcCmdline: python /usr/bin/gwibber-accounts
PythonArgs: ['/usr/bin/gwibber-accounts']
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

Revision history for this message
Dražen Matešić (crazylemon) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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 #811465, 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.

tags: removed: need-duplicate-check
visibility: private → public
visibility: private → public
Revision history for this message
Dražen Matešić (crazylemon) wrote :

FYI - I couldn't reproduce this bug

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gwibber (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
  • Duplicate of a private bug Remove

Other bug subscribers

Remote bug watches

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