Cannot print high resolution in 12.04 - worked in 11.10

[Aurosutru]

Printing high resolution images with an HP Deskjet D1360 stopped working after upgrading from 11.10 to 12.04 two days ago. The print is stretched about 50% vertically and is black and white, without any color. Low-res image printing seems OK. I have installed all software updates and HPLIP, which previously worked.

I understand the issue is known for some printers, perhaps due to the change from Poppler to Ghostscript discussed in bug 998087. Attempting the workaround described there and in http://ubuntuforums.org/showthread.php?t=2022997 gave strange results for onscreen windows, including inability to move them and loss of the three top buttons, which were fortunately undo-able with the listed reset command.

Thanks.
---
ApportVersion: 2.0.1-0ubuntu13
Architecture: i386
DistroRelease: Ubuntu 12.04
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423)
Lpstat: device for Deskjet_D1300_2: hp:/usb/Deskjet_D1300_series?serial=CN7592J29604ND
MachineType: Dell Inc. Latitude D510
Package: cups 1.5.3-0ubuntu4
PackageArchitecture: i386
Papersize: a4
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   3.3V
  32-bit
  PC Card
PpdFiles: Deskjet_D1300_2: HP Deskjet d1300 Series, hpcups 3.12.9
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-31-generic-pae root=UUID=c2b8b1a0-b394-4dc3-b32f-996073b7f9ad ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.2.0-31.50-generic-pae 3.2.28
Tags: precise running-unity
Uname: Linux 3.2.0-31-generic-pae i686
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo
dmi.bios.date: 04/27/2005
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A01
dmi.board.name: 0N8719
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA01:bd04/27/2005:svnDellInc.:pnLatitudeD510:pvr:rvnDellInc.:rn0N8719:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Latitude D510
dmi.sys.vendor: Dell Inc.
mtime.conffile..etc.cups.cupsd.conf: 2012-10-04T15:17:50.597514

[Aurosutru (2fullnesses)]

Edit: "I understand the issue is known for some printers, perhaps due to the change from Poppler to Ghostscript discussed in bug 998087. "

Better: " I understand there is a general issue known to affect some printers, due to the change from Poppler to Ghostscript discussed in bug 998087."

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1059359/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Book 'em Dano (heymrdjd)]

Thanks for taking the time to report this bug and helping to make Ubuntu better. Could you please add the log files from '/var/log/dist-upgrade/' to this bug report as separate attachments? Please execute the following command, as it will automatically gather debugging information, in a terminal:

  apport-collect 1059359

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

[Till Kamppeter (till-kamppeter)]

Please also follow the instructions of the sections "CUPS error_log" and "Capturing print job data" on https://wiki.ubuntu.com/DebuggingPrintingProblems. Thanks.

[Aurosutru (2fullnesses)]

apport information

[Aurosutru (2fullnesses)]

apport information

[Aurosutru (2fullnesses)]

apport information

[Aurosutru (2fullnesses)]

apport information

[Aurosutru (2fullnesses)]

apport information

[Aurosutru (2fullnesses)]

apport information

[Aurosutru (2fullnesses)]

apport information

[Aurosutru (2fullnesses)]

apport information

[Aurosutru (2fullnesses)]

apport information

[Aurosutru (2fullnesses)]

apport information

[Aurosutru (2fullnesses)]

apport information

[Aurosutru (2fullnesses)]

apport information

[Aurosutru (2fullnesses)]

apport information

[Aurosutru (2fullnesses)]

apport information

[Aurosutru (2fullnesses)]

apport information

[Aurosutru (2fullnesses)]

Hi,

Dano, as you've instructed, I've run apport-collect 1059359 and sent to Launchpad.

Till, I'm also attaching the outputs from DebuggingPrinterProblems, including cups error_logs after trying three prints, the first of which was successful at normal print settings. Also attached is the printer detection section outputs, and a picture of the printer output.

Regards,

Aurosutru

[Aurosutru (2fullnesses)]

Additional Attachment

[Aurosutru (2fullnesses)]

Additional Attachment

[Aurosutru (2fullnesses)]

Additional Attachment

[Aurosutru (2fullnesses)]

Additional Attachment

[Aurosutru (2fullnesses)]

Additional Attachment

[Aurosutru (2fullnesses)]

Additional Attachment

[Till Kamppeter (till-kamppeter)]

The problem is a problem of the printer driver, HPLIP. Ghostscript generates raster images of your pages with 600 dpi resolution and 24-bit RGB in all cases, which is enough to produce a high-quality printed image. The printer reports for the first printout that it uses normal mode and for the others that iut uses "BestPhoto" mode. So the print work flow seems to be correct. Also the detection of your printer seems to be correct.

The problem seems to be inside the driver. It seems that it does not send the correct instructions for resolution and color depth to the printer, probably the instructions work with another printer but not with your particular model. This is a problem in the upstream code od the printer driver. therefore I move this bug to HPLIP and also forward it to the HPLIP developers at HP.

[Till Kamppeter (till-kamppeter)]

Can someone of the HPLIP developers at HP have a look at this? Thanks.