Bug 683699

Summary: [abrt] gwibber-1:2.33.0-13.894bzr.fc15: accounts.py:131:put_in_keyring:IOError
Product: [Fedora] Fedora Reporter: Gerard Ryan <gerard>
Component: gwibberAssignee: Tom "spot" Callaway <tcallawa>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 15CC: tcallawa
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:62830374
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-06 20:07:16 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description Gerard Ryan 2011-03-10 04:08:07 UTC
abrt version: 1.1.17
architecture: x86_64
cmdline: /usr/bin/python /usr/bin/gwibber-accounts
component: gwibber
executable: /usr/bin/gwibber-accounts
kernel: 2.6.38-0.rc8.git0.1.fc15.x86_64
package: gwibber-1:2.33.0-13.894bzr.fc15
reason: accounts.py:131:put_in_keyring:IOError
release: Fedora release 15 (Lovelock)
time: 1299729898
uid: 500

backtrace
-----
accounts.py:131:put_in_keyring:IOError

Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/gwibber/accounts.py", line 202, in on_edit_account_save
    self.account["id"], config, self.account[config])
  File "/usr/lib/python2.7/site-packages/gwibber/accounts.py", line 131, in put_in_keyring
    {"id": str(id)}, str(value), True)
IOError

Local variables in innermost frame:
acctid: '9042f1ac4acb11e0ba3500219bd35457'
self: <gwibber.accounts.GwibberAccountManager object at 0x29f8950>
id: u'9042f1ac4acb11e0ba3500219bd35457/secret_token'
value: 'AyJVL13YNA4TIxD1d1vk9dLXI4hZ3JHUrhjK5Rbs6Rk'
name: u'secret_token'

How to reproduce
-----
1. Start Gwibber.
2. Try to add twitter accout, enter login credentials when prompted and click authorize.
3. It doesn't crash as such, but something must be happening, since abrt came up with this!

Comment 1 Gerard Ryan 2011-03-10 04:08:09 UTC
Created attachment 483351 [details]
File: backtrace

Comment 2 Fedora End Of Life 2012-08-06 20:07:16 UTC
This message is a notice that Fedora 15 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 15. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 15 reached end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 3 Fedora End Of Life 2012-08-06 20:07:16 UTC
This message is a notice that Fedora 15 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 15. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 15 reached end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping