twowheeler, your problem is not the foomatic-filters bug reported by the original poster. The Ghostscript command line which you have posted in your comment is of the pstopdf CUPS filter.
Please report a new bug (package "cups") and tell also how you configured your printer on the Windows client. Also disable and clean your print queue with
cupsdisable <print queue name>
cancel -a
then print a job from the Windows client
and save the incoming job file
sudo -s
cp /var/spool/cups/d* /tmp
chmod 777 /tmp/d*
exit
twowheeler, your problem is not the foomatic-filters bug reported by the original poster. The Ghostscript command line which you have posted in your comment is of the pstopdf CUPS filter.
Please report a new bug (package "cups") and tell also how you configured your printer on the Windows client. Also disable and clean your print queue with
cupsdisable <print queue name>
cancel -a
then print a job from the Windows client
and save the incoming job file
sudo -s
cp /var/spool/cups/d* /tmp
chmod 777 /tmp/d*
exit
and attach the file to this bug.
After that, run
cupsenable <print queue name>
This way we can use your file for further tests.