Hide Forgot
Description of problem: when using the current version with a canon Imagerunner Advance Printer (commonly used in large comapnies) one gets only one line of output: "Unknown device: opvp" Version-Release number of selected component (if applicable): ghostscript-9.53.3-1.fc32.x86_64.rpm How reproducible: just print Actual results: no correct output Expected results: correct output Additional info: by adding --with-openprinting to %configure one gets a version which prints OK. ghostscript changed that default to exclude opvp with https://github.com/ArtifexSoftware/ghostpdl/commit/66c2469c7d4543f32d6dc93edf1d649e809b8419
above patch got reverted by https://github.com/ArtifexSoftware/ghostpdl/commit/c6ce09aa5c9ed0c66c597478a2c4fb75aa25267f which is not yet released
Here are scratch build with the upstream patch to test: F34: https://koji.fedoraproject.org/koji/taskinfo?taskID=56207580 F33: https://koji.fedoraproject.org/koji/taskinfo?taskID=56208959 F32: https://koji.fedoraproject.org/koji/taskinfo?taskID=56208971
works for me
Fixed in https://src.fedoraproject.org/rpms/ghostscript/c/871182c9e4bd7094250c4b8b913b68915c126314?branch=master f32 update - https://bodhi.fedoraproject.org/updates/FEDORA-2020-fe8b2ff8cd f33 update - https://bodhi.fedoraproject.org/updates/FEDORA-2020-891bd8c276
Over at bug 1909950 we are getting a report that the new builds in fact do not solve the opvp issue. Could anyone here confirm that ghostscript-9.53.3-3 did solve it? If not, please check out the test builds for ghostscript-9.53.3-4 in that bug.
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.
sorry for the late reply: for me the new verson fixed that problem. i have a canon UFRII printer and printed today without any problem. my ghostscript is now: [cheese@cheese ~]$ rpm -qi ghostscript Name : ghostscript Version : 9.53.3 Release : 4.fc33 Architecture: x86_64 Install Date: Tue 26 Jan 2021 09:16:18 AM CET Group : Unspecified Size : 40909 License : AGPLv3+ Signature : RSA/SHA256, Wed 13 Jan 2021 04:54:24 PM CET, Key ID 49fd77499570ff31 Source RPM : ghostscript-9.53.3-4.fc33.src.rpm Build Date : Wed 13 Jan 2021 04:43:19 PM CET Build Host : buildvm-x86-32.iad2.fedoraproject.org Packager : Fedora Project Vendor : Fedora Project URL : https://ghostscript.com/ Bug URL : https://bugz.fedoraproject.org/ghostscript Summary : Interpreter for PostScript language & PDF
This message is a reminder that Fedora 32 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '32'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 32 is 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 change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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.
Note: this has been fixed on F32 and up in ghostscript-9.53.3-4 So I suggest closing this one.
Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.