Red Hat Bugzilla – Bug 990308
Secure printing on M5035 does not ask for PIN
Last modified: 2015-02-17 11:27:31 EST
Created attachment 780836 [details]
TCP dump of a document printed with pin enabled
Description of problem:
Printing a document with secure printing enabled prints the document immediately without asking for a PIN
Version-Release number of selected component (if applicable):
3.13.6 and 3.13.7
Steps to Reproduce:
1. Select document to print
2. Enable secure printing in the options and set pin code
3. Hit print button
Printer immediately starts the job without prior asking for the user/PIN code
Printer asks for user and PIN code before printing the document.
I've added the tcp stream of a job printed with and one without secure printing enabled. Obviously the PJL header containing the secure printing hints is missing in both printed documents.
Created attachment 780837 [details]
TCP dump of a document printed with pin disabled
Looks like this only works if the PPD options are sent as job options for the job.
Please use the printing troubleshooter and attach the resulting troubleshoot.txt file.
Created attachment 788194 [details]
Sorry for the long delay, finally I'm back from vacation. I'm attaching the requested troubleshoot.txt
I did a small comparison with Ubuntu, where pin printing works. The big important difference is that in ubuntu hpps filter is invoked and not in fedora. According to the hpps source it is responsible for pin printing and the missing pjl header. So how can we add hpps to the filter list?
The reason for secure printing not working with the M5035 model is the missing filter line
*cupsFilter: "application/vnd.cups-postscript 0 hpps"
in the printer PPD file. As soon as it is added secure printing works fine! So, can you please add it to the official PPD file?
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
Thank you for reporting this bug and we are sorry it could not be fixed.