[Bug 1213477] New: Update to gutenprint 5.3 broke cups config
https://bugzilla.suse.com/show_bug.cgi?id=1213477 Bug ID: 1213477 Summary: Update to gutenprint 5.3 broke cups config Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Printing Assignee: jsmeix@suse.com Reporter: dheidler@suse.com QA Contact: jsmeix@suse.com Target Milestone: --- Found By: --- Blocker: --- From cups log: E [19/Jul/2023:14:07:42 +0200] Samsung_Samsung_ML-2525W: Datei \"/usr/lib/cups/filter/rastertogutenprint.5.2\" nicht verfügbar: No such file or directory E [19/Jul/2023:14:07:42 +0200] [Job 49] Unable to start filter "rastertogutenprint.5.2" - No such file or directory. E [19/Jul/2023:14:07:42 +0200] [Job 49] Stopping job because the scheduler could not execute a filter. From cups config: <Printer Samsung_Samsung_ML-2525W> PrinterId 45 UUID urn:uuid:70334a01-d800-39ed-5a4e-5e4f45e9c01f Info Samsung Samsung ML-2525W Location MakeModel Samsung ML-2550 - CUPS+Gutenprint v5.2.15 DeviceURI socket://10.131.0.20 State Idle StateTime 1689768462 ConfigTime 1689767864 Type 8392724 Accepting Yes Shared No JobSheets none none QuotaPeriod 0 PageLimit 0 KLimit 0 OpPolicy default ErrorPolicy stop-printer Attribute marker-colors \#000000 Attribute marker-levels 50 Attribute marker-names Toner S/N:CRUM-11000311613 Attribute marker-types toner Attribute marker-change-time 1683056782 </Printer> It seems that the config was not updated breaking the printing driver as the config was still pointing to gutenprint 5.2. This should be somehow prevented - eg by not including the version number in the config or updating the config automatically. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1213477 https://bugzilla.suse.com/show_bug.cgi?id=1213477#c1 --- Comment #1 from Johannes Meixner <jsmeix@suse.com> --- 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. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1213477 Johannes Meixner <jsmeix@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- URL| |https://bugzilla.suse.com/s | |how_bug.cgi?id=637455 -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1213477 https://bugzilla.suse.com/show_bug.cgi?id=1213477#c2 Johannes Meixner <jsmeix@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |WONTFIX Status|NEW |RESOLVED --- Comment #2 from Johannes Meixner <jsmeix@suse.com> --- 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 -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com