Bug 682216 - Images inverted using HPLIP/cups driver on HP Deskjet (use hpijs instead)
Summary: Images inverted using HPLIP/cups driver on HP Deskjet (use hpijs instead)
Status: RESOLVED DUPLICATE of bug 630696
Alias: None
Product: openSUSE 11.4
Classification: openSUSE
Component: Printing (show other bugs)
Version: Final
Hardware: All openSUSE 11.4
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Johannes Meixner
QA Contact: Johannes Meixner
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-24 09:11 UTC by Daniel Morris
Modified: 2011-03-24 09:44 UTC (History)
0 users

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Daniel Morris 2011-03-24 09:11:40 UTC 
User-Agent:       Mozilla/5.0 (compatible; Konqueror/4.6; Linux) KHTML/4.6.0 (like Gecko) SUSE

The included HPLIP package seems buggy, bitmap images appear to have their colour inverted, looking like old fashioned negatives. There are various reports around the place. The workaround is to use the hpijs driver instead. I hit the problem with a DeskJet 5150, one machine had been upgraded and previously worked fine with the driver from openSUSE 11.3, the second was a clean install.

There's an upstream report, see:- https://bugs.launchpad.net/hplip/+bug/718494

I also saw corrupted text from a two page document printed directly from LibreOffice and also from the pdf created.

Reproducible: Always

Steps to Reproduce:
1. Default install, either configure via cups or hp-setup
2. Print test-page from hp-toolbox, or a real images
3.
Actual Results:  
Bad image

Expected Results:  
Good image!
Comment 1 Johannes Meixner 2011-03-24 09:44:06 UTC 
Various issues in the HPCUPS driver are known
but bugs in printer drivers can only be fixed upstream.
See in particular
https://bugzilla.novell.com/show_bug.cgi?id=630696#c1

*** This bug has been marked as a duplicate of bug 630696 ***