Problem printing GMT PostScript

Bug #55694 reported by John M Kuhn
2
Affects Status Importance Assigned to Milestone
gmt (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

I have a problem when printing PostScript files created with GMT (Generic Mapping Tools) using Ubuntu Dapper. I create a PostScript file with the following command:

/usr/lib/gmt/bin/psxy --PAPER_MEDIA=letter -R1/7.5/1/10 -JX6.5i/9i -Ba1f0.25WSne -P /dev/null > test.ps

The resulting test.ps file previews correctly in gv and every other PS viewer I have tried. When I print the file, the resulting page has my figure magnified about 4x such that the lower left of the figure fills the entire page. I get the same result on 4 different printers (all PostScript)
   HP LaserJet 2300dn
   HP LaserJet 8000N
   Xerox Phaser 8400DP
   Xerox Phaser 860N

Other PostScript files generated in OOo or Firefox print correctly.

If I copy the test.ps file to an Ubuntu Hoary system (or old Debian, HP-UX, Mac OSX ...) the file prints correctly on the same 4 printers.

It appears the PostScript command "0.24 0.24 scale" is being ignored resulting in the figure being scaled by a factor of 4.16667. If i run test.ps through ps2ps before printing, it will print correctly.

I have been using GMT for many years and I have not seen this printing problem before.

Revision history for this message
John M Kuhn (john-m-kuhn) wrote :

test.ps file attached

Revision history for this message
John M Kuhn (john-m-kuhn) wrote :

file prints correctly if I use:
   lp -oraw file.ps

If I manually run file.ps through CUPS pstops then view the result, it is 4x too large.

Revision history for this message
Pascal De Vuyst (pascal-devuyst) wrote :

Thanks for your bug report.
Running your file test.ps through pstops does produce a ps file of the same size on my machine.
What version of CUPS are you running?
Please provide the output of the printingbuginfo script that can be found here: https://wiki.ubuntu.com/PrintingBugInfoScript

Changed in cupsys:
status: Unconfirmed → Needs Info
Revision history for this message
John M Kuhn (john-m-kuhn) wrote :

Running cupsys 1.2.2-0ubuntu0.6.06. Output of printingbuginfo attached.

Revision history for this message
Pascal De Vuyst (pascal-devuyst) wrote :

Package versions look ok.
You could have activated some printing option for scaling the output that ps2ps would take into account.
Can you please attach /etc/cups/printers.conf and the output of lpoptions -l
Please edit /etc/cups/cupsd.conf and set ErrorLevel to debug, restart cups with sudo /etc/init.d/cupsys restart and print your GMT postscript file, attach /var/log/cups/error_log

Revision history for this message
John M Kuhn (john-m-kuhn) wrote :
Revision history for this message
John M Kuhn (john-m-kuhn) wrote :

lpoptions for printer lj2300

Revision history for this message
John M Kuhn (john-m-kuhn) wrote :
Revision history for this message
John M Kuhn (john-m-kuhn) wrote :

output from:
   /usr/lib/cups/filter/pstops x x x x x test.ps > pstops_out.ps

Revision history for this message
Pascal De Vuyst (pascal-devuyst) wrote :

I'm able to reproduce your problem now.
If found that the pstops_out.ps you provided was generated with copies set to 0, inside your file is %RBINumCopies: 0. When viewing in gv, indeed this results in 4x magnified output.

Then I have setup a printer queue that prints to file to find out the generated postscript that would normally be sent to your postscript printer. This file doesn't have %RBINumCopies: 0 but when viewing this also results in 4x magnified output.

Your original test.ps seems to be DSC conformant when tested with cupstestdsc.

To me this looks like a bug in CUPS pstops filter, you should file a bug report in the upstream CUPS bug tracker.

Changed in cupsys:
status: Needs Info → Confirmed
Revision history for this message
John M Kuhn (john-m-kuhn) wrote :

Filed bug report upstream:
http://www.cups.org/str.php?L1907

Revision history for this message
John M Kuhn (john-m-kuhn) wrote :

This is a bug in GMT, not CUPS. My original test.ps file is not DSC conformant. This has been corrected in the developers version of GMT and will be in the next release (v 4.1.4?).

Revision history for this message
Martin Pitt (pitti) wrote :

Thanks for checking!

Revision history for this message
William Grant (wgrant) wrote :

4.1.4 is in Feisty.

Changed in gmt:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.