Re: [Gimp-print-devel] Bug when connecting windows10 to rasp-pi cups server

[Johannes M. <js...@su...>]

Hello,

On Jun 2 21:04 Peter Bischofberger wrote (excerpt):
> - raspberry pi 3b+ (raspbian) with cups ...
> following this guide:
> https://pimylifeup.com/raspberry-pi-print-server/

this guide looks as if there is a printer model specific driver
installed both on the CUPS server system and also on the
Windows client system.

Normally this cannot work because now two drivers
(first the one on the Windows client system and
then the other one on the CUPS server system)
are run one after the other.

> - connected printer is: DNP DS-620   (testpage printed from inside cups works)
> - windows 10 client, printer installed with this scheme:
> http://192.168.1.121:631/printers/DS620
>
> when trying to print a page via windows,
> it shows on raspberry cups interface under jobs:
>
> canceled at
> Sun Jun 2 20:44:51 2019
> "Unrecognized header data format @0!"

This seems to prove what I wrote above.
The "Unrecognized header data format @0!" seems to come from the 
printer specific data that was produced by the Windows driver.

For background information see
https://en.opensuse.org/SDB:Printing_from_Windows_to_Linux

Therein see the section "Using Samba and CUPS" that talks about
how to enforce "raw" printing for Samba via "cups options = raw"
in /etc/samba/smb.conf which seems to be missing in
https://pimylifeup.com/raspberry-pi-print-server/
as far as I see.


Kind Regards
Johannes Meixner
-- 
SUSE LINUX GmbH - HRB 21284 (AG Nuernberg)
GF: Felix Imendoerffer, Mary Higgins, Sri Rasiah