Bug 60900

Summary: Setting a local raw printer using CUPS does not work
Product: [Unmaintained] kdelibs Reporter: Dominic Jacques <domjacq2000>
Component: print-dialogAssignee: KDEPrint Devel Mailinglist <kde-print-devel>
Status: RESOLVED WORKSFORME    
Severity: normal CC: andrew.crouthamel, chaofeng111
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Compiled Sources   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Dominic Jacques 2003-07-08 04:29:52 UTC
Version:            (using KDE KDE 3.1)
Installed from:    Compiled From Sources
Compiler:          gcc 3.2 
OS:          Linux

It's often necessary to create a raw printer queue on a printer that will be shared using Samba because the driver is on the client side.  However, if we want that this queue prints "raw" documents then we need to uncomment the line "application/octet-stream        application/vnd.cups-raw        0       -" in the /etc/cups/mime.convs file and the line "application/octet-stream" in the /etc/cups/mime.types file.  An other solution is to print using the -oraw option.

When I created a local raw printer with the printing manager, I discovered that it doesn't do this automatically so the newly created raw printed did not work.  I think the printing manager should uncomment these lines when creating a local raw printer or use the -oraw option when printing.

To reproduce, just create a raw printer with these lines commented and try to print a document coming from Samba to the printer.  These lines will appear in the cups log file :
print_job: Unsupported format 'application/octet-stream'!
Hint: Do you have the raw file printing rules enabled?
In my case nothing got printed too.

If this can help you, I'm using a Lexmark Z32 printer (it's not a Postscript printer, but I'll buy one one day...).
Comment 1 Cristian Tibirna 2005-08-22 17:21:17 UTC
UNCONFIRMED (batch reassigning messed this)
Comment 2 Andrew Crouthamel 2018-11-12 02:56:55 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Dominic Jacques 2018-11-12 03:19:23 UTC
I've entered the bug 15 years ago... Please close it, it is probably no more relevant.

Regards,
Dominic
Comment 4 Andrew Crouthamel 2018-11-12 03:31:14 UTC
Thanks for the update!