Bug 1180859

Summary: cups client sends incorrect mime type
Product: [Fedora] Fedora Reporter: Adam Pribyl <covex>
Component: cupsAssignee: Tim Waugh <twaugh>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: jpopelka, twaugh
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 23:59:59 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Adam Pribyl 2015-01-11 09:10:46 UTC
Description of problem:
When I try to print a test page from the F20 client to printer attached to the server with F20 it fails on the server with "SpliX Cannot open job". The real reason is, that the client sends file that is already converted to QPL with mime type set to application/vnd.cups-raster. If I try to send file stored in server spool to printer it works. If I test them with "file" utility, it is gziped HP Printer Job Language data not a cups-raster.

F19 clients work OK! The splix version is unchanged for several Fedora releases.

Description: Samsung SCX-4500
Location: server
Driver: Samsung SCX-4500, 2.0.0 (grayscale, 2-sided printing)
Connection: dnssd://Samsung%20SCX-4500%20Series%20%40%20server._ipp._tcp.local/cups
Defaults: job-sheets=none, none media=iso_a4_210x297mm sides=one-sided 

E [11/Jan/2015:09:49:46 +0100] [Job 451] SpliX Cannot open job
E [11/Jan/2015:09:49:46 +0100] [Job 451] SpliX Error while rendering the request. Check the previous message
E [11/Jan/2015:09:49:54 +0100] [Job 451] Job stopped due to filter errors; please consult the error_log file for details.
D [11/Jan/2015:09:49:54 +0100] [Job 451] The following messages were recorded from 09:49:46 AM to 09:49:54 AM
D [11/Jan/2015:09:49:54 +0100] [Job 451] Adding start banner page "none".
D [11/Jan/2015:09:49:54 +0100] [Job 451] Queued on "Samsung-SCX-4500-Series" by "anonymous".
D [11/Jan/2015:09:49:54 +0100] [Job 451] File of type application/vnd.cups-raster queued by "anonymous".
D [11/Jan/2015:09:49:54 +0100] [Job 451] Adding end banner page "none".
D [11/Jan/2015:09:49:54 +0100] [Job 451] time-at-processing=1420966186
D [11/Jan/2015:09:49:54 +0100] [Job 451] 1 filters for job:
D [11/Jan/2015:09:49:54 +0100] [Job 451] rastertoqpdl (application/vnd.cups-raster to printer/Samsung-SCX-4500-Series, cost 0)


Version-Release number of selected component (if applicable):
F20 cups server cups-1.7.5-11.fc20.x86_64
F20 cups client cups-1.7.5-11.fc20.x86_64
F19 cups client cups-1.6.4-10.fc19.i686 but before upgrade of the client to F20 it worked also on x86_64


How reproducible:
always

Comment 1 Tim Waugh 2015-01-12 10:43:41 UTC
As a work-around, the queues on the clients can be made 'raw' with 'lpadmin -p ... -m raw'.

Comment 2 Adam Pribyl 2015-01-13 09:55:41 UTC
I tried to set the printer on the client to "raw" but this makes printer unmaintainable and unusable on client. The client cups administration changes the device URL in printer list to dnssd://Samsung%20SCX-4500%20Series%20%40%20server._ipp._tcp.local/cups which is inaccesable, applications are not able to find the printer state and refuse to print on that printer.

lpoptions before lpadmin -p SCX-4500 -m raw:
copies=1 device-uri=dnssd://Samsung%20SCX-4500%20Series%20%40%20server._ipp._tcp.local/cups finishings=3 job-hold-until=no-hold job-priority=50 job-sheets=none,none marker-change-time=0 number-up=1 printer-commands=none printer-info='Samsung SCX-4500' printer-is-accepting-jobs=true printer-is-shared=false printer-location=server printer-make-and-model='Samsung SCX-4500, 2.0.0' printer-state=3 printer-state-change-time=1420965889 printer-state-reasons=none printer-type=2240580 printer-uri-supported=ipp://localhost:631/printers/SCX-4500

after:
copies=1 device-uri=dnssd://Samsung%20SCX-4500%20Series%20%40%20server._ipp._tcp.local/cups finishings=3 job-hold-until=no-hold job-priority=50 job-sheets=none,none marker-change-time=0 number-up=1 printer-info=SCX-4500 printer-is-accepting-jobs=true printer-is-shared=false printer-location=server printer-make-and-model='Remote Printer' printer-state=3 printer-state-change-time=1420966206 printer-state-reasons=none printer-type=2228230 printer-uri-supported=dnssd://Samsung%20SCX-4500%20Series%20%40%20server._ipp._tcp.local/cups

Comment 3 Tim Waugh 2015-01-13 11:28:59 UTC
As an additional workaround for clients not using new-style discovery, you'll need to change that URI to once using the ipp: scheme, ipp://host-or-ip:631/printers/SCX-4500. Alternatively, you could enable the cups-browsed service and configure it to discover DNS-SD queues advertised by CUPS and update local queues to point to them.

Comment 4 Adam Pribyl 2015-01-13 17:20:50 UTC
OK, thanks. I allowed to DNS-SD autodiscovery and thru this it seems to work OK. Nevertheles this is just a workaround.

Comment 5 Fedora End Of Life 2015-05-29 13:36:03 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 '20'.

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 20 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.

Comment 6 Fedora End Of Life 2015-06-29 23:59:59 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.