Description of problem: ipp-everywhere causes problems on Brother printer Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Create printer for ipp-everywhere generic for a Brother HL-L3270CDW printer 2. lpr file.ps prints the file 3. lpr -raw file.jpg prints the file 4. lpr file.jpg will not print. The printer claims to be cancelling the job at the printer. I have no idea if anyone can actually reproduce it since it probably depends on weird quirks of this printer, but just in case.... As far as I can tell from the log, it is trying to use imagetopwg on the file and the print is failing with [Job 121] Send-Document: client-error-document-format-error (client-error-document-format-error) on the result. The printer info shows pwg-raster: /home/arromdee% avahi-browse -rt _ipp._tcp + lo IPv4 Brother HL-L3270CDW series (USB) _ipp._tcp local = lo IPv4 Brother HL-L3270CDW series (USB) _ipp._tcp local hostname = [linux.local] address = [127.0.0.1] port = [60000] txt = ["air=none" "mopria-certified=1.3" "rp=ipp/print" "priority=50" "kind=document,envelope,label,postcard" "PaperMax=legal-A4" "URF=SRGB24,W8,CP1,IS4-1,MT1-3-4-5-8-11,OB10,PQ4,RS600,V1.4,DM1" "UUID=e3248000-80ce-11db-8000-b42200b288c5" "Color=T" "Duplex=T" "note=" "qtotal=1" "pdl=application/octet-stream,image/urf,image/jpeg,image/pwg-raster" "txtvers=1" "adminurl=http://localhost:60000/net/net/airprint.html" "Fax=F" "Scan=F"] I attempted to manually run the filter, hoping to produce the cups intermediate file, and manually try to print the result. My best attempt to do this is cupsfilter -e -i image/jpeg -m image/pwg-raster -p /etc/cups/ppd/Brother-color.ppd adv.jpg > adv.pwg Printing the resulting adv.pwg (with -o raw) fails in the expected way (cancelled at printer). However I am at the limit of my expertise and don't know if I am using the proper command. Interestingly, lpr adv.pwg without -o raw succeeds. Going to https://ftp.pwg.org/pub/pwg/ipp/examples/ and trying to print one of the examples (using lpr -o raw) does succeed.
Created attachment 13984 [details] cups log
Created attachment 13985 [details] adv.jpg
Created attachment 13986 [details] adv.pwg (gzipped to reduce size)
Correction, lpr -o raw
The forum thread... https://forums.mageia.org/en/viewtopic.php?f=24&t=15049
I think I';ve provided substantially more information than in the forum thread. If I use the manufacturer drivers, it'll work, but is too dark (but I may be possible to change printer settings to fix this). Regardless, the manufacturer drivers are not provided with Mageia, the printer *should* be working with IPP-everywhere, and I think "pwg is produced in format that printer cannot handle" has a good chance of being an actual bug, if someone with knowledge could look at it.
Also, the problem doesn't seem to be a lack of filters, as I had assumed in the thread. -raw prints the file; it's the existing filter that prevents it from working.
CC Cups maintainer.
CC: (none) => fri, thierry.vignaud
I see OK attachment comment 2 (JPG image); for comment 3, even ImageMagick could not display the PWG file. Not surprised: "The PWG file extension indicates to your device which app can open the file. However, different programs may use the PWG file type for different types of data." (FWIW, -o raw says: -l Specifies that the print file is already formatted for the desti‐ nation and should be sent without filtering. This option is equivalent to -o raw.) We are going to have to assign this, so changing the CC.
Assignee: bugsquad => thierry.vignaudCC: thierry.vignaud => (none)
@Ken: Did this work on Mageia 8 ?
I held off on buying a new printer until I installed Mageia 9, since I wasn't sure that IPP Everywhere was supported in 8, so I don't know if it would have worked there. Imagemagick isn't able to display the known good pwg from pwg.org either, so that doesn't mean anything. And I just don't know if I created the pwg wrong, if I created it correctly (matching what's done internally in cups) and Mageia messes up the creation process, or if Mageia creates it properly and the printer is just bad at understanding it.