← Back to team overview

desktop-packages team mailing list archive

[Bug 868522] Re: gwibber-accounts crashed with IOError in put_in_keyring()

 

*** This bug is a duplicate of bug 811465 ***
    https://bugs.launchpad.net/bugs/811465

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

** Changed in: gwibber (Ubuntu)
       Status: New => Confirmed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gwibber in Ubuntu.
https://bugs.launchpad.net/bugs/868522

Title:
  gwibber-accounts crashed with IOError in put_in_keyring()

Status in “gwibber” package in Ubuntu:
  Confirmed

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gwibber/+bug/868522/+subscriptions