Fedora Account System
Red Hat Associate
Red Hat Customer
Since cups-1.6 the test page has no longer been provided by cups as application/vnd.cups-banner type but by cups-filters as application/vnd.cups-pdf-banner. application/vnd.cups-pdf-banner document is actually a text file beginning with #PDF-BANNER and the test page is created from it with bannertopdf filter (provided by cups-filters as well). This could be a problem when trying to print a test page via ipp://cups-server/printers/printer-queue where cups-server runs cups < 1.6, because the test page is sent to server unprocessed. Steps to Reproduce: 1. have cups-1.6 & cups-filters 2. add ipp://cups-server/printers/printer-queue where cups-server runs cups < 1.6 3. print test page Actual results: #PDF-BANNER Template default.pdf Show printer-name printer-info printer-location printer-make-and-model printer-driver-name ... Expected results: nice and shiny test page with pictures
cups-1.6 still contains the application/vnd.cups-banner banners, we just don't install them and use the banners from cups-filters instead - because they nicely fit into the PDF-workflow. We should probably use the old application/vnd.cups-banner -> postscript banners from cups for couple releases until most of the servers run cups-1.6 and above.
Perhaps we have to set document-format-supported for the queue when creating it explicitly?
How/Where ? How is it supposed to work ?
In CUPS 1.5.x, a printer that has been discovered via CUPS Browsing will have document-format-supported set to the same value as the remote printer. I think I need to adjust cups-browsed to do the same thing.
Ok, so in this case there'll be application/vnd.cups-pdf-banner missing in document-format-supported list for the local queue, which will result in converting the document from pdf-banner to pdf before sending ? Correct ? It should fix the problem for automatically discovered printers but not for manually added queues, do we care ?
That's right. No, for manually added queues I don't think it's a big problem, and is something that ought to be taken care of upstream. There is a reasonably simple work-around anyway: lpadmin -p ... -o document-format-supported=... (whichever formats you want to allow through).
So, my idea was wrong. The document-format-supported attribute is read-only. The only options left are: 1. Revert to vnd.cups-banner for now until the issue is addressed/considered upstream 2. Create the queues with a PPD that will convert vnd.cups-pdf-banner to vnd.cups-banner, and pass all other mime types through
(In reply to comment #7) > 1. Revert to vnd.cups-banner for now until the issue is addressed/considered > upstream Should be fixed with cups-1.6.1-26.fc19 cups-filters-1.0.30-3.fc19
I've just discovered that even cups-1.6 still ships the banners (vnd.cups-banner) it doesn't ship bannertops anymore (http://www.cups.org/str.php?L4120) so the change mentioned in previous comment does not work for local queues. (I'm wondering how the test page printing works on OS X then.) I'm going to revert the previous change.
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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 19 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.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.