after upgrade to hplip-3.14.3, printer only prints first page of each job
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
HPLIP |
New
|
Undecided
|
Unassigned | ||
Debian |
New
|
Undecided
|
Unassigned |
Bug Description
I just updated to Ubuntu 13.10 today, which also upgraded hplip to a newer version. After the upgrade, I noticed that I only get the first page of every print job. Also, the quality is extremely lousy (looks like maybe 200dpi). The problem persists after upgrading to the newest version of hplip (3.14.3) and re-running hp-setup to reconfigure the printer. My printer is an HP OfficeJet Pro 8600.
Two other computers in our household that use Ubuntu 13.10 have the same problem.
More specifically, when I sent a duplex print job, the printer prints out the front of the first page. Then the page sits in the spot where it usually waits for the "ink to dry" for a few seconds. After this, the page is simply ejected and the print job is finished. The back of the first page is never printed, nor are any subsequent pages.
For a simplex job, the first page is printed and ejected immediately, then the print job stops.
This is the same bug as https:/
Since there is no way to make more than one attachment, I am copying and pasting the output from hp-check right here. By the way, the print queue I am using is "color4", which is the most recent one I configured with hplip 3.14.3.
-------
Saving output in log file: /root/hp-check.log
HP Linux Imaging and Printing System (ver. 3.14.3)
Dependency/Version Check Utility ver. 15.1
Copyright (c) 2001-13 Hewlett-Packard Development Company, LP
This software comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to distribute it
under certain conditions. See COPYING file for more details.
Note: hp-check can be run in three modes:
1. Compile-time check mode (-c or --compile): Use this mode before compiling the
HPLIP supplied tarball (.tar.gz or .run) to determine if the proper dependencies
are installed to successfully compile HPLIP.
2. Run-time check mode (-r or --run): Use this mode to determine if a distro
supplied package (.deb, .rpm, etc) or an already built HPLIP supplied tarball
has the proper dependencies installed to successfully run.
3. Both compile- and run-time check mode (-b or --both) (Default): This mode
will check both of the above cases (both compile- and run-time dependencies).
Check types:
a. EXTERNALDEP - External Dependencies
b. GENERALDEP - General Dependencies (required both at compile and run time)
c. COMPILEDEP - Compile time Dependencies
d. [All are run-time checks]
PYEXT SCANCONF QUEUES PERMISSION
Status Types:
OK
MISSING - Missing Dependency or Permission or Plug-in
INCOMPAT - Incompatible dependency-version or Plugin-version
---------------
| SYSTEM INFO |
---------------
Kernel: 3.11.0-18-generic #32-Ubuntu SMP Tue Feb 18 21:11:14 UTC 2014 GNU/Linux
Host: firefly
Proc: 3.11.0-18-generic #32-Ubuntu SMP Tue Feb 18 21:11:14 UTC 2014 GNU/Linux
Distribution: ubuntu 13.10
Bitness: 64 bit
-------
| HPLIP CONFIGURATION |
-------
HPLIP-Version: HPLIP 3.14.3
HPLIP-Home: /usr/share/hplip
HPLIP-Installation: Auto installation is supported for ubuntu distro 13.10 version
Current contents of '/etc/hp/
# hplip.conf. Generated from hplip.conf.in by configure.
[hplip]
version=3.14.3
[dirs]
home=/usr/
run=/var/run
ppd=/usr/
ppdbase=
doc=/usr/
html=/usr/
icon=/usr/
cupsbackend=
cupsfilter=
drv=/usr/
bin=/usr/bin
# Following values are determined at configure time and cannot be changed.
[configure]
network-build=yes
libusb01-build=no
pp-build=no
gui-build=yes
scanner-build=yes
fax-build=yes
dbus-build=yes
cups11-build=no
doc-build=yes
shadow-build=no
hpijs-install=no
foomatic-
foomatic-
foomatic-
hpcups-install=yes
cups-drv-
cups-ppd-install=no
internal-tag=3.14.3
restricted-build=no
ui-toolkit=qt4
qt3=no
qt4=yes
policy-kit=no
lite-build=no
udev_sysfs_rules=no
hpcups-
hpijs-only-build=no
Current contents of '/var/lib/
Plugins are not installed. Could not access file: No such file or directory
Current contents of '~/.hplip/
<Package-name> <Package-Desc> <Required/Optional> <Min-Version> <Installed-Version> <Status> <Comment>
-------
| External Dependencies |
-------
policykit Admin-Policy-
gs Ghostscript REQUIRED 7.05 9.10 OK -
network Network-wget OPTIONAL - 1.14 OK -
scanimage Shell-Scanning OPTIONAL 1.0 1.0.23 OK -
avahi-utils avahi-utils OPTIONAL - 0.6.31 OK -
dbus DBus REQUIRED - 1.6.12 OK -
cups CUPS REQUIRED 1.1 1.7 OK 'CUPS Scheduler is running'
xsane SANE-GUI OPTIONAL 0.9 0.998 OK -
-------
| General Dependencies |
-------
reportlab Python-PDF-Lib OPTIONAL 2.0 2.6 OK -
libcrypto OpenSSL-Crypto-Lib REQUIRED - 1.0.1 OK -
pil Python-Image-Lib OPTIONAL - 1.1.7 OK -
pyqt4-dbus PyQt4-DBUS REQUIRED 4.0 4.10.3 OK -
libjpeg JPEG-Lib REQUIRED - - OK -
libpthread POSIX-Threads-Lib REQUIRED - 2.17 OK -
python-dbus Python-DBUS REQUIRED 0.80.0 1.2.0 OK -
python-devel Python-SDK REQUIRED 2.2 2.7.5 OK -
pyqt4 Python-Qt4 REQUIRED 4.0 4.10.3 OK -
cups-devel CUPS-SDK REQUIRED - 1.7 OK -
sane-devel SANE-SDK REQUIRED - 1.0.23 OK -
libusb USB-Lib REQUIRED - 1.0 OK -
sane Scan-Lib REQUIRED - 1.0.23 OK -
cups-image CUPS-Image-Lib REQUIRED - 1.7 OK -
libnetsnmp-devel SNMP-Networking-SDK REQUIRED 5.0.9 5.7.2 OK -
python-xml Python-XML-Lib REQUIRED - 2.1.0 OK -
python-notify Desktop-
-------
| Compile Time Dependencies |
-------
gcc gcc-Compiler REQUIRED - 4.8.1 OK -
libtool Build-tools REQUIRED - 2.4.2 OK -
make GNU-Build-tools REQUIRED 3.0 3.81 OK -
-------
| Python Extentions |
-------
cupsext CUPS-Extension REQUIRED - 3.14.3 OK -
pcardext PhotoCard-Extension REQUIRED - 3.14.3 OK -
hpmudext IO-Extension REQUIRED - 3.14.3 OK -
-------
| Scan Configuration |
-------
hpaio HPLIP-SANE-Backend REQUIRED - 3.14.3 OK 'hpaio found in /etc/sane.
scanext Scan-SANE-Extension REQUIRED - 3.14.3 OK -
-------
| DISCOVERED SCANNER DEVICES |
-------
device `hpaio:
device `hpaio:
-------
| DISCOVERED USB DEVICES |
-------
No devices found.
-------
| INSTALLED CUPS PRINTER QUEUES |
-------
col
---
Type: Printer
Device URI: hp:/net/
PPD: /etc/cups/
PPD Description: HP Officejet Pro 8600, hpcups 3.13.3
Printer status: printer col is idle. enabled since Sat 29 Mar 2014 08:42:59 PM ADT
color
-----
Type: Unknown
Device URI: dnssd:/
PPD: /etc/cups/
PPD Description: HP Officejet Pro k8600, hpcups 3.13.9
Printer status: printer color is idle. enabled since Sat 29 Mar 2014 08:48:37 PM ADT
color2
------
Type: Printer
Device URI: hp:/net/
PPD: /etc/cups/
PPD Description: HP Officejet Pro 8600, hpcups 3.13.9
Printer status: printer color2 is idle. enabled since Sun 30 Mar 2014 09:00:05 PM ADT
Communication status: Good
color3
------
Type: Printer
Device URI: hp:/net/
PPD: /etc/cups/
PPD Description: HP Officejet Pro 8600, hpcups 3.13.9
Printer status: printer color3 is idle. enabled since Sun 30 Mar 2014 09:04:35 PM ADT
Communication status: Good
color4
------
Type: Printer
Device URI: hp:/net/
PPD: /etc/cups/
PPD Description: HP Officejet Pro 8600, hpcups 3.13.9
Printer status: printer color4 is idle. enabled since Sun 30 Mar 2014 09:17:31 PM ADT
Communication status: Good
fax
---
Type: Fax
Device URI: hpfax:/
PPD: /etc/cups/
PPD Description: HP Fax4 hpcups
Printer status: printer fax is idle. enabled since Sun 13 Jan 2013 09:45:08 PM AST
Officejet_
-------
Type: Fax
Device URI: hpfax:/
PPD: /etc/cups/
PPD Description: HP Fax4 hpcups
Printer status: printer Officejet_
Communication status: Good
--------------
| PERMISSION |
--------------
-----------
| SUMMARY |
-----------
Missing Required Dependencies
-------
None
Missing Optional Dependencies
-------
None
Total Errors: 2
Total Warnings: 2
Done.
I investigated this issue further, and collected additional information that may help in reproducing and finding the cause of this bug.
Specifically, the bug only occurs with files printed from, or saved as PostScript from, Acrobat Reader. As a testfile, I used the attached gridsynth.ps and gridsynth.pdf
* Test 1: print gridsynth.ps from the command line (lpr gridsynth.ps). It prints just fine, at full resolution, and all pages will print. Even duplexing works.
* Test 2: print gridsynth.pdf from within Acrobat Reader. It will print at a much lower resolution (maybe 150dpi), and only the first page will print - the back of the first page will be blank, and there will be no further pages.
* Test 3: print gridsynth.pdf from within Acrobat Reader by "printing to file", with output gridsynth-acro.ps. Then print gridsynth-acro.ps from the command line (using lpr). It will print at a much lower resolution (maybe 150dpi), and only the first page will print. The printer output is the same as for Test 2.
* Test 4: Convert gridsynth.pdf to PostScript using some other method, such as pdf2ps. Printing the resulting PostScript file from the command line, it prints fine, at full resolution, and the printer output is the same as Test 1.
* Test 5: take the file gridsynth-acro.ps from Test 3, convert it to PDF using ps2pdf, then convert the result back to PS using pdf2ps. Print the resulting file from the command line. It prints fine, at full resolution, with the same output as in Test 1.
I repeated similar tests with other input files, and the outcome is the same. All PostScript that was generated by Acrobat Reader will print at low resolution and stop after the first page. All other PostScript will print fine. This shows that there is nothing wrong with the input files per se.
Tests 1 and 4 show that there is nothing wrong with the original input files gridsynth.ps and gridsynth.pdf. Test 5 shows that the PostScript file generated by Test 3 does not lose any actual information; one can re-distill correct PostScript from this file which will print correctly. So it is not the case, for example, that Acrobat Reader itself lowers the resolution of the file.
Nevertheless, any PostScript that is directly generated by Acrobat Reader will print incorrectly.
I don't think that these tests show that the bug is 100% in Acrobat Reader. Rather, they point to some kind of incompatibility between the PostScript generated by Acrobat Reader and the CUPS/HPLIP filters that are supposed to process it. Especially Test 5 shows that the Acrobat-generated PostScript is salvagable.
For reference, I am attaching all the files:
* gridsynth.ps: used in Test 1
* gridsynth.pdf: used in Test 2
* gridsynth-acro.ps: generated by Acrobat Reader from gridsynth.pdf in Test 3
* gridsynth- pdf2ps. ps: generated by ps2pdf from gridsynth.ps in Test 4
* gridsynth- acro-ps2pdf- pdf2ps. ps: generated from gridsynth-acro.ps in Test 5