Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 117029
Summary: | Printing from eog doesn't work | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Daniel Malmgren <dm> |
Component: | eog | Assignee: | Christopher Aillon <caillon> |
Status: | CLOSED UPSTREAM | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rawhide | CC: | dasergatskov, johan.dahl, johan.dahl, julo42, marius.andreiana, tagoh |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-09-03 20:35:55 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 114963, 123268 |
Description
Daniel Malmgren
2004-02-27 16:27:36 UTC
Same result in 2.5.6. Might be a libgnomeprint issue. This is still the same. Now running eog 2.6.0-2 and libgnomeprint22 2.6.0-1. The bug is still in Fedora Core 2. Perhaps sombody can change the version from "devel" to "2" Well, it's still there in devel too, so I see no real reason to change it. I too think that a bug like this should have been fixed before a major release though... Mark as UPSTREAM? http://bugzilla.gnome.org/show_bug.cgi?id=101805 EOG has never had printing support in a working state and has had most of the code removed for almost a year now. Closing this as UPSTREAM since the feature request in recorded in GNOME bugzilla. *** Bug 136354 has been marked as a duplicate of this bug. *** |