Bug 672076 - [abrt] gourmet-0.15.6-4.fc14: reccard.py:2091:commit_iter:KeyError: 'ingkey'
Summary: [abrt] gourmet-0.15.6-4.fc14: reccard.py:2091:commit_iter:KeyError: 'ingkey'
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: gourmet
Version: 14
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jeff Raber
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:f11b7d9f
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-01-23 19:02 UTC by David
Modified: 2012-08-16 13:31 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-16 13:31:36 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (2.00 KB, text/plain)
2011-01-23 19:02 UTC, David
no flags Details

Description David 2011-01-23 19:02:38 UTC
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: /usr/bin/python /usr/bin/gourmet
component: gourmet
executable: /usr/bin/gourmet
kernel: 2.6.35.10-74.fc14.i686
package: gourmet-0.15.6-4.fc14
reason: reccard.py:2091:commit_iter:KeyError: 'ingkey'
release: Fedora release 14 (Laughlin)
time: 1295809193
uid: 500

How to reproduce
-----
1.Open recipe card
2.Edit recipe name
3.Save

Comment 1 David 2011-01-23 19:02:41 UTC
Created attachment 474851 [details]
File: backtrace

Comment 2 David 2011-02-12 12:56:45 UTC
Package: gourmet-0.15.6-4.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.Inport recipe
2.Mod recipe
3.Save (crash at save)

Comment 3 Jeff Raber 2011-02-12 16:15:45 UTC
I cannot reproduce this error.  The problem could be specific to your recipe database.  Please do the following test:

Backup your current recipe database (~/.gourmet/recipe.db)  
Delete your current recipe database (~/.gourmet/recipe.db)
Open Gourmet, a new recipe.db will be created.
Try to reproduce the crash.



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 4 Joseph O Morrow 2011-05-03 02:25:28 UTC
Package: gourmet-0.15.6-4.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.WHILE DOWNLOADING INTO GOURMET
2.
3.

Comment 5 Jeff Raber 2011-05-10 20:03:18 UTC
I would be interested to know if you can reproduce this crash with the latest
version of gourmet.  You can install the latest version by running running the
following in a root shell:  'yum --enablerepo=updates-testing update gourmet'

You can provide feedback about the latest version here:
https://admin.fedoraproject.org/updates/gourmet-0.15.9-1.fc14

Comment 6 Joseph O Morrow 2011-06-02 19:18:37 UTC
Package: gourmet-0.15.6-4.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.adding into the description field
2.
3.


Comment
-----
nothing to share with anyone

Comment 7 Jeff Raber 2011-06-03 02:38:36 UTC
gourmet-0.15.9-1.fc14 was just pushed to stable and should be available in the repos soon. 

I would like to know if you are able to reproduce this crash with that version.

Comment 8 Fedora End Of Life 2012-08-16 13:31:39 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. 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 '14' 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 14 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


Note You need to log in before you can comment on or make changes to this bug.