Ingredient Key Editor "Close" button doesn't work

Confirming the issue

The console log is interesting, something is crashing which may or may not have a relation to this problem. The crash occurs when opening the ingredient editor, nothing new is added to the console when trying and closing the ingredient editor window.

Thomas, can you please comment if this bug should be fixed in 0.14.5?

This seems to be working fine in 0.14.5-2ubuntu2.

no, in fact, it's not. Reopening.

Rolf, can you details steps to reproduce the problem? I cannot reproduce here. Ie, going to Tools/Ingredient Key Editor and clicking 'Close' works fine.

I should mention I am using 0.14.5-2ubuntu2 in Karmic.

This bug was fixed in the package gourmet - 0.15.2-0ubuntu1

---------------
gourmet (0.15.2-0ubuntu1) lucid; urgency=low

  * New upstream release (LP: #431806, Closes: #530841). Also fixes the
    following bugs:
    - LP: #315836
    - LP: #295982
    - LP: #316445 (the GUI has been changed so this no longer applies)
  * Drop forcing of python2.5
  * debian/control: Recommends python-gnome2-extras for printing
  * drop debian/patches/05-add_manpage.patch, which is now included upstream
  * Fix some lintian warnings:
    - add debian/README.source
    - debian/control: bump Standards-Version to 3.8.3
    - debian/compat: bump to 5
  * debian/control: Depends on python-poppler (needed for printing)
  * debian/patches/01_fix_raise_str.patch: don't raise str exception
    in src/lib/plugin_gui.py
  * debian/patches/02_fix_nutrition_index_out_of_range.patch: don't
    add entries beyond the width of the field in databaseGrabber.py
  * debian/patches/03_dont_remove_nonexistent_plugin.patch: don't
    remove an inactive plugin in plugin_loader.py and don't deactivate
    a plugin from a non-existent database
 -- Jamie Strandboge <email address hidden> Tue, 29 Dec 2009 09:12:49 -0600

Note: the 02_fix_nutrition_index_out_of_range.patch is almost certainly an incorrect solution to the updating of the USDA nutrient database.

I believe I fixed this the proper way (remapping all the nutrient fields in line with the updated DB) in 0.15.3 which was released almost immediately on the heals of 0.15.2 to address this and other bugs.

Well, 02_fix_nutrition_index_out_of_range.patch wasn't meant to be a fix for the nutrition database so much as simply preventing the index out of range error. There seemed to be other things wrong with the nutrition database at the time, so I just added a little defensive programming until a fixed gourmet was out. I didn't notice 0.15.3 until today, so I can get that into Ubuntu and drop this patch.

Jamie,

No problem.

Feel free to keep in close email or chat contact as you run into bugs packaging up a release -- it's a small project (pretty much just me) so it's often easy for me to address things like this quickly on the upstream side of things -- and thanks for picking up the work on the packaging end!