| Summary: | Gourmet refuses to print | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Stephen Haffly <hafflys> |
| Component: | gourmet | Assignee: | Jef Spaleta <jspaleta> |
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 16 | CC: | jeff.raber, jspaleta |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-12-09 15:55:00 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
I am marking this as closed. Something has been updated, and printing now works again, making this report moot. Stephen, Thanks for the great bug report and for your recent update. And sorry that I have not responded until now. It was likely an update to the pypoppler package that fixed Gourmet for you. See bug 747481. I'm going to mark this as a duplicate of that bug. *** This bug has been marked as a duplicate of bug 747481 *** |
Description of problem: Gourmet will not print, displaying instead an error box: Unable to print, no print plugins are active. When the OK button is pressed, another box pops up that states: Error printing Well this is embarassing. Something went wrong printing your recipe. When the Details drop-down is selected, it contains this information: Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/gourmet/exporters/printer.py", line 76, in print_recipes **kwargs) File "/usr/lib/python2.7/site-packages/gourmet/exporters/printer.py", line 15, in __init__ raise NotImplementedError NotImplementedError Version-Release number of selected component (if applicable): gourmet-0.15.9-1.fc16.noarch python-2.7.2-5.2.fc16.x86_64 kernel 3.1.1-2.fc16.x86_6 How reproducible: Attempt to print a recipe. Steps to Reproduce: 1. Open Gourmet 2. Select a recipe 3. Attempt to print Actual results: Printing fails with error messages specified above. Expected results: Gourmet should format and then print the recipe as it did previously with Fedora 15 and prior versions. Additional info: This appears to have cropped up when I upgraded Fedora 15 to Fedora 16 via preupgrade. This also occurs with a netbook which is also running F16 X86_64. Installing in a virtual machine pulls these dependencies: PyRTF gnome-python2-extras gnome-python2-gnomeprint gnome-python2-gtkspell gtkspell libgnomecups libgnomeprint22 libgnomeprintui22 metakit pypoppler python-reportlab python-sqlalchemy python-sqlite2 When I try to install them in my main system where printing fails, I get the following: Package PyRTF-0.45-12.fc15.noarch already installed and latest version Package gnome-python2-extras-2.25.3-37.fc16.x86_64 already installed and latest version Package gnome-python2-gnomeprint-2.32.0-5.fc16.x86_64 already installed and latest version Package gnome-python2-gtkspell-2.25.3-37.fc16.x86_64 already installed and latest version Package gtkspell-2.0.16-2.fc15.x86_64 already installed and latest version Package libgnomecups-0.2.3-9.fc15.x86_64 already installed and latest version Package libgnomeprint22-2.18.8-2.fc15.x86_64 already installed and latest version Package libgnomeprintui22-2.18.6-2.fc15.x86_64 already installed and latest version Package metakit-2.4.9.7-10.fc15.x86_64 already installed and latest version Package pypoppler-0.12.1-15.fc16.x86_64 already installed and latest version Package python-reportlab-2.5-3.fc15.x86_64 already installed and latest version Package python-sqlalchemy-0.7.3-1.fc16.x86_64 already installed and latest version Package 1:python-sqlite2-2.3.5-4.fc15.x86_64 already installed and latest version Nothing to do The alternative that works is to export the recipe to a text or other type document, then open the document and print from there. Therefore, I have graded the severity as low since there is a workaround. However, it would be good to not have to use it, but print directly.