Comment # 4 on bug 899405 from Johannes Meixner

The reason is shown in CUPS error_log in your attachment#608706 [details]
----------------------------------------------------------------------------
... Auto-typing file...
... Request file type is application/postscript.
[...]
... Started filter /usr/lib/cups/filter/pstotiff (PID 31555)
... Started filter /usr/lib/cups/filter/imagetoraster (PID 31556)
... Started filter /usr/lib/cups/filter/hpcups (PID 31557)
... Started backend /usr/lib/cups/backend/hp (PID 31558)
----------------------------------------------------------------------------

Processing PostSript as if it was an image file (like JPEG or PNG)
via pstotiff and imagetoraster is basically wrong - theoretically
it could work but in practice...

This weird kind of PostSript processing comes from problematic
filtering rules in the HPLIP software which get deactivated/hidden
in a fragile way by other ("cheaper") filtering rules from
the cups-filters package that take precedence over HP's
problematic PostSript processing filtering rules.

The root cause is HP's problematic PostSript processing filtering rules
in HP's HPLIP software. I already explained it to HPLIP upstream but
they did not clean up their filtering rules, see
https://bugzilla.suse.com/show_bug.cgi?id=735404#c52
and subsequent comment (at least one HPLIP upstream member
is in the CC list of bug#735404) and see also my comments in
https://answers.launchpad.net/hplip/+question/105997

Please report the issue directly at HPLIP upstream via
http://hplipopensource.com/hplip-web/support.html

I set this issue here as "UPSTREAM", see
http://en.opensuse.org/SDB:How_to_Report_a_Printing_Issue#Background_Information

I would appreciate it if you post here an URL to your upstream bug report.
You do not need to reopen this issue here to add comments.
You can add comments even when it is closed.