Hide Forgot
Description of problem: When I try to print a recipe from Gourmet, it will not print. Version-Release number of selected component (if applicable): gourmet-0.15.6-4.fc14.noarch How reproducible: Steps to Reproduce: 1. Select a recipe from existing recipes or enter a new one 2. attempt to print recipe Actual results: Nothing prints Expected results: Printer should print the recipe I tried to print Additional info: It looks like nothing is being spooled. I do not see the printer icon and the printer does not activate. It is like the program sends it into nowhere. There is no error message, and the program continues to run as if it had printed the recipe. If I change it to try to print to a PDF file, it also fails with no error message. If I try to export to a file, it fails with this traceback message: Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/gourmet/threadManager.py", line 97, in run self.do_run() File "/usr/lib/python2.7/site-packages/gourmet/plugin_loader.py", line 372, in _ retval = f(self,*args,**kwargs) File "/usr/lib/python2.7/site-packages/gourmet/exporters/exporter.py", line 568, in do_run e.do_run() File "/usr/lib/python2.7/site-packages/gourmet/exporters/exporter.py", line 82, in do_run self._write_text_() File "/usr/lib/python2.7/site-packages/gourmet/plugin_loader.py", line 373, in _ retval = self.run_post_hook(f.__name__,retval,*args,**kwargs) File "/usr/lib/python2.7/site-packages/gourmet/plugin_loader.py", line 339, in run_post_hook retval = hook(retval,self,*args,**kwargs) File "/usr/lib/python2.7/site-packages/gourmet/plugin.py", line 185, in do_write val = field_fetcher(klass.r) File "/usr/lib/python2.7/site-packages/gourmet/plugins/nutritional_information/export_plugin.py", line 23, in get_nutritional_info_as_text_blob nd = rd.nd AttributeError: RecipeManager instance has no attribute 'nd'
Printing and Exporting to PDF = 'Works for me' I thought that maybe the issue was related to the nutrition data, but testing on my end didn't reveal any problem there. Are you unable to print/export to PDF *ANY* recipe or is it specific to certain recipes? -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
The problem appears to not be limited to certain recipes. When I try to print, it brings up the print dialog, but when I click on Print after selecting my options for layout, etc, the dialog closes and nothing happens.
I selected the option of print to file and it failed there too.
Could you attach a copy of your ~/.gourmet/recipes.db file? Or if you'd prefer, you could mail it to me directly. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
I sent a copy directly per your request.
I am unable to print while running with your database. The schema of your database differs from mine, but that's not unexpected because of the way gourmet performs the database upgrade between versions. I did see the following printed to the console upon starting the application. WARNING: PLUGIN FAILED TO LOAD <nutritional_information.main_plugin.NutritionMainPlugin instance at 0x2e48fc8> Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/gourmet/plugin_loader.py", line 315, in plugin_plugin plugin_instance.activate(self) File "/usr/lib/python2.7/site-packages/gourmet/plugins/nutritional_information/main_plugin.py", line 13, in activate nutritionGrabberGui.check_for_db(pluggable.rd) File "/usr/lib/python2.7/site-packages/gourmet/plugins/nutritional_information/nutritionGrabberGui.py", line 72, in check_for_db elif not db.fetch_one(db.nutrition_table,ndbno=1123).choline: File "/usr/lib/python2.7/site-packages/gourmet/backends/db.py", line 672, in fetch_one return table.select(*make_simple_select_arg(criteria,table)).execute().fetchone() File "/usr/lib64/python2.7/site-packages/sqlalchemy/sql/expression.py", line 2527, in execute return e._execute_clauseelement(self, multiparams, params) File "/usr/lib64/python2.7/site-packages/sqlalchemy/engine/base.py", line 1795, in _execute_clauseelement return connection._execute_clauseelement(elem, multiparams, params) File "/usr/lib64/python2.7/site-packages/sqlalchemy/engine/base.py", line 1271, in _execute_clauseelement return self.__execute_context(context) File "/usr/lib64/python2.7/site-packages/sqlalchemy/engine/base.py", line 1302, in __execute_context context.parameters[0], context=context) File "/usr/lib64/python2.7/site-packages/sqlalchemy/engine/base.py", line 1401, in _cursor_execute context) File "/usr/lib64/python2.7/site-packages/sqlalchemy/engine/base.py", line 1394, in _cursor_execute context) File "/usr/lib64/python2.7/site-packages/sqlalchemy/engine/default.py", line 299, in do_execute cursor.execute(statement, parameters) OperationalError: (OperationalError) no such column: nutrition.choline u'SELECT nutrition.ndbno, nutrition."desc", nutrition.water, nutrition.kcal, nutrition.protein, nutrition.lipid, nutrition.ash, nutrition.carb, nutrition.fiber, nutrition.sugar, nutrition.calcium, nutrition.iron, nutrition.magnesium, nutrition.phosphorus, nutrition.potassium, nutrition.sodium, nutrition.zinc, nutrition.copper, nutrition.manganese, nutrition.selenium, nutrition.vitaminc, nutrition.thiamin, nutrition.riboflavin, nutrition.niacin, nutrition.pantoacid, nutrition.vitaminb6, nutrition.folatetotal, nutrition.folateacid, nutrition.foodfolate, nutrition.folatedfe, nutrition.choline, nutrition.vitb12, nutrition.vitaiu, nutrition.vitarae, nutrition.retinol, nutrition.alphac, nutrition.betac, nutrition.betacrypt, nutrition.lypocene, nutrition.lutzea, nutrition.vite, nutrition.vitk, nutrition.fasat, nutrition.famono, nutrition.fapoly, nutrition.cholestrl, nutrition.gramwt1, nutrition.gramdsc1, nutrition.gramwt2, nutrition.gramdsc2, nutrition.refusepct, nutrition.foodgroup \nFROM nutrition \nWHERE nutrition.ndbno = ?' (1123,) As the error shows, there is, in fact, no column named 'choline' in the table 'nutrition'. Adding that column resolves the above error and printing now works as well. (I will return the modified db file to you via e-mail.) Do you know when the printing issue began? After upgrading from F12/13 to F14 perhaps? Do you know with which version of Fedora or gourmet this db was created? -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
I have gone through some version upgrades both of Fedora and Gourmet since I first started using it. It has been back at least as far as Fedora 12 and probably 10 or 11 when I first tried it. It has been fairly recently, probably with the F14 upgrade, when the printing issue showed up. I had printed out recipes, but had not done so recently until I tried printing out the one for Penzey's Chili Powder which I had just entered, so I am not sure at exactly which point it broke. The one thing that has kept me from using it more intensely is that I have many recipes already in MealMaster. I have found that there are some differences in MealMaster's format and the way Gourmet exports in what is supposed to be MealMaster format. The exported file is not quite right, so if I send it to a friend, it will not import into his/her MealMaster program. However, I have started using it more because of the Web import feature. It has much to like. I appreciate you finding out what was giving me problems. I guess somewhere along the way, there was a change that was needed in the DB structure that didn't take place.
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