Description of problem: My LaserJet 4L doesn't print the last page of a document unless I manually press the Test/Eject button. This also means that single-page documents don't print without manual intervention. This is the same for PDF documents and LibreOffice documents. If I print two documents without manually ejecting the first document, I get an intervening page with the following text at the top: ....... (Only the bottom few pixels of the letters can be seen.) @PJL SET DENSITY=3 @PJL SET RET=MEDIUM @PJL SET COPIES=1 @PJL SET ECONOMODE Version-Release number of selected component (if applicable): cups-1.7.0-6.fc20.x86_64 hplip-3.13.11-4.fc20.x86_64 How reproducible: Always Steps to Reproduce: 1. Install Fedora 20 2. Attach the LaserJet 4L into the system using a Centronix (parallel)-to-USB converter. 3. Allow the system to automatically configure the printer. (This works very nicely! I'm impressed.) 4. Optionally, change the configuration to A4 paper. This bug persists regardless of the paper size setting. 4. Print a document. Actual results: For a one page document, a green light turns on (on the printer) to indicate that there is something in memory waiting to print. For a multi-page document, everything prints except for the last page. Expected results: The document or last page prints and the green light turns off. Additional info: $ cat /etc/printcap # This file was automatically generated by cupsd(8) from the # /etc/cups/printers.conf file. All changes to this file # will be lost. LaserJet-4L|Hewlett-Packard LaserJet 4L:rm=xxxx.xxxx.xxx:rp=LaserJet-4L: $ (I replaced the hostname above with xxxx.xxxx.xxx.)
There are several drivers available for this model: Foomatic/ljet4 hpcups CUPS+Gutenprint Foomatic/lj4dith hpijs Which are you currently using? You can find out using system-config-printer -- install it if you don't already have it installed. It will be listed in the "Make and Model" field of the printer properties. Try the other drivers. The order I've listed them above is the preferred order to try them in, i.e. most likely to work at the beginning. Does another driver give better results?
My original configuration used HP LaserJet 4L Foomatic/lj4 [en] (recommended). Changing to HP LaserJet 4L, hpcups 3.13.11 and HP LaserJet 4L Foomatic/lj4dith didn't correct the problem. If I unplug the USB connection, delete the configuration and plug in my other LJ 4L (Yep, I have two of them.), it automatically configures using the recommended driver and the problem persists.
I didn't remember this problem on my old 32-bit system that I upgraded from F19 using fedup with the printer previously configured. (The system I'm reporting about is a new 64-bit laptop that I installed F20 in freshly.) Sure enough, the page ejected as it should on my 32-bit system. So now I've deleted the (32-bit) configuration, and I'm trying again. Unfortunately, the automatic configuration appears to be hung. Looks like I'll have to set up the printer by hand. More when I get it configured...
Okay, my 32-bit system works correctly after I delete the printer and let it install itself again automatically. But it looks like I have some incomplete printing processes on my 64-bit system: $ sudo systemctl status cups.service [sudo] password for fred: cups.service - CUPS Printing Service Loaded: loaded (/usr/lib/systemd/system/cups.service; enabled) Active: active (running) since Sun 2014-01-05 15:18:30 EET; 1 day 7h ago Main PID: 675 (cupsd) CGroup: /system.slice/cups.service ├─ 675 /usr/sbin/cupsd -f └─16293 /usr/lib/cups/notifier/dbus dbus:// Jan 06 21:15:32 xxxx.xxxx.xxx systemd[1]: Started CUPS Printing Service. Jan 06 21:16:03 xxxx.xxxx.xxx systemd[1]: Started CUPS Printing Service. Jan 06 21:16:03 xxxx.xxxx.xxx systemd[1]: Started CUPS Printing Service. Jan 06 21:27:08 xxxx.xxxx.xxx systemd[1]: Started CUPS Printing Service. Jan 06 21:27:09 xxxx.xxxx.xxx systemd[1]: Started CUPS Printing Service. Jan 06 21:27:09 xxxx.xxxx.xxx systemd[1]: Started CUPS Printing Service. Jan 06 21:27:44 xxxx.xxxx.xxx systemd[1]: Started CUPS Printing Service. Jan 06 21:27:44 xxxx.xxxx.xxx systemd[1]: Started CUPS Printing Service. Jan 06 21:30:29 xxxx.xxxx.xxx systemd[1]: Started CUPS Printing Service. Jan 06 21:30:29 xxxx.xxxx.xxx systemd[1]: Started CUPS Printing Service. $
Would be nice to see error_log https://fedoraproject.org/wiki/How_to_debug_printing_problems#Getting_debug_information_by_other_means
Created attachment 847483 [details] /var/log/cups/error_log After printing one page, here is the current systemd status that matches the attached error log. The page is still hiding in the printer's memory: # systemctl status cups.service cups.service - CUPS Printing Service Loaded: loaded (/usr/lib/systemd/system/cups.service; enabled) Active: active (running) since Thu 2014-01-09 07:14:52 EET; 3min 25s ago Main PID: 14939 (cupsd) CGroup: /system.slice/cups.service ├─14939 /usr/sbin/cupsd -f └─14979 /usr/lib/cups/notifier/dbus dbus:// Jan 09 07:14:52 xxxx.xxxx.xxx systemd[1]: Started CUPS Printing Service. Jan 09 07:16:39 xxxx.xxxx.xxx systemd[1]: Started CUPS Printing Service. Jan 09 07:17:10 xxxx.xxxx.xxx systemd[1]: Started CUPS Printing Service. Jan 09 07:17:10 xxxx.xxxx.xxx systemd[1]: Started CUPS Printing Service. #
Hmm. I just had this bug appear on my 32-bit system. It usually works correctly. When I pressed the manual feed button, the last page of a Libre Office Calc spreadsheet printed with a few of the bottom pixel rows missing.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.