Description of problem:
I have the problem with printing PDF file without extension PDF
Version-Release number of selected component (if applicable):
phracek@kiasportyw-kiasportyw: ~/Downloads$ file skoleni_ridicu.pdf
skoleni_ridicu.pdf: PDF document, version 1.5
Steps to Reproduce:
1. Create the PDF file witout extension .pdf
2. print over DocumentViewer
3. On Fedora 20 I see a lot off messages like "Printing <pdf_name> on printer"
File can not be printed
File can be printed
I'm experiencing the same issue on my Fedora 19.
Created attachment 817851 [details]
example document that is able to trigger the issue
Created attachment 817853 [details]
output of the system-config-printer -> troubleshoot
Created attachment 817891 [details]
successful print on different printer via the same cups server
I can see that too using brno1-1st-entrance printer via (BrowsePoll) cups.brq.redhat.com
Strange that other printers (brno1-2nd-cafe, brno1-3rd-cafe) I've tried are ok.
One more note: printing directly via AppSocket/JetDirect works OK.
That queue -- brno1-1st-entrance -- is configured on the server not to accept jobs at the moment. In that case, we retry the job until it does accept it. Is that unexpected?
As far as the document itself goes: this is an application/vnd.cups-pdf-banner format file, so isn't this the same as bug #919489?
(In reply to Tim Waugh from comment #5)
> That queue -- brno1-1st-entrance -- is configured on the server not to
> accept jobs at the moment.
http://cups.brq.redhat.com:631/printers/brno1-1st-entrance -> 'Rejecting Jobs'
I'll try to fill some ticket.
> In that case, we retry the job until it does
> accept it. Is that unexpected?
That's not unexpected IMHO.
What's unexpected is that the printing dialog (for example in firefox) allows me to print on that printer in the first place. The printing dialog seems to not see the 'rejecting jobs' status of the remote queue.
We tried this in RHEL-6 and the printing dialog there doesn't allow us to print because it knows the queue rejects jobs.
> As far as the document itself goes: this is an
> application/vnd.cups-pdf-banner format file, so isn't this the same as bug
Sure, but that's not a problem here.
What I think is happening here is that the remote queue is not accepting jobs but the local queue (the one that cups-browsed created to point to the remote one) *is* accepting them.
We need to avoid that situation somehow, either by having cups-browsed copy over the printer-is-accepting-jobs state or else by it treating a remote rejecting queue as not existing (and so deleting a local queue if the remote queue starts rejecting jobs).
I'll see what the upstream opinion is.
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.