|
Bugzilla – Full Text Bug Listing |
| Summary: | Update to gutenprint 5.3 broke cups config | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Tumbleweed | Reporter: | Dominik Heidler <dheidler> |
| Component: | Printing | Assignee: | Johannes Meixner <jsmeix> |
| Status: | RESOLVED WONTFIX | QA Contact: | Johannes Meixner <jsmeix> |
| Severity: | Normal | ||
| Priority: | P5 - None | ||
| Version: | Current | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| URL: | https://bugzilla.suse.com/show_bug.cgi?id=637455 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Dominik Heidler
2023-07-19 12:10:31 UTC
First and foremost: SUSE or openSUSE never developed Gutenprint (or any other basic printing software). We provide printing software "as is" from upstream. As far as I know this is unavoidable for a Gutenprint major version upgrade because /usr/sbin/cups-genppdupdate (which is run as RPM post install script) cannot properly regenerate Gutenprint PPD files for existing print queues (i.e. what there is in /etc/cups/ppd/*.ppd) for a Gutenprint major version upgrade. So for a Gutenprint major version upgrade you have to manually re-create the print queues which use Gutenprint as printer driver. When Gutenprint 5.2 PPD files have (long line shown wrapped) ------------------------------------------------------------- *cupsFilter: "application/vnd.cups-raster 100 rastertogutenprint.5.2" ------------------------------------------------------------- versus Gutenprint 5.3 PPD files that have ------------------------------------------------------------- *cupsFilter: "application/vnd.cups-raster 100 rastertogutenprint.5.3" ------------------------------------------------------------- this is very likely intentional by Gutenprint upstream because in general the contents of PPD files must match the specific printer driver software where they belong to. I close it as WONTFIX which means in this case: "The problem described is an issue for the user but it cannot be fixed by openSUSE." So alternatively it might be closed as UPSTREAM which means: "The responsibility for the bug lies upstream." Because I think things behave as intended by Gutenprint upstream it could be also closed as INVALID which would mean in this case: "The problem described is an issue for the user but things behave as intended by the upstream developers." Cf. https://bugzilla.suse.com/page.cgi?id=status_resolution_matrix.html |