I recently upgraded to OpenSUSE 12.1 from 11.4 and have discovered a problem printing. That is, I cannot print FedEx and/or UPS mailing labels. I think that this may have something to do with the fact that these labels have barcodes. In any event, I have two printers as follows:
HP OfficeJet 8500A909a
HP OfficeJet 8500A910
When I print FedEx and/or UPS mailing labels with Firefox, Okular or Evince then only the non-barcoded part of the label prints. For example, when I print a FedEx label then the top part which includes the barcode is omitted (left blank) but the bottom part, which includes FedEx instructions, does print properly. However, when I print with Adobe Acroread then nothing prints and the following errors are found in /var/log/cups/error_log:
[Job 96] printer-state-message="/usr/lib/cups/filter/pstoraster failed"
PID 31000 (/usr/lib/cups/filter/pstoraster) crashed on signal 11.
There are no error_log entries generated when the label is partially printed (without barcode) with Firefox, Okular and Evince. The only time that error_log entries are generated is when I try to print with Acroread where nothing at all is printed.
Printing all other documents works fine without any problems.
I highly suspect that there is a problem with the ghostscript version in OpenSUSE 12.1.
This problem exists right out of the box for OpenSUSE 12.1. As a test, I installed a fresh copy of OpenSUSE 12.1 under VirtualBox and attempted to print the labels immediately after the installation was complete, however, printing failed as described above.
Just to rule out hplip, I installed the most current version of hplip (ver. 3.11.12) from HP Linux Imaging and Printing since the current OpenSUSE hplip version is 3.11.10, however, the problem exists with hplip 3.11.12 as well so hplip probably isn’t the problem.
Also, I have two CentOS 5.7 systems that print these labels to the same two printers successfully with older versions of CUPS and hplip.
I am posting this in hopes that somebody else has experienced this problem and may have a solution. I also plan to file a bug report on this unless somebody comes up with a reasonable explanation.
Thanks,
Gordon