I installed the above printer using hp-setup but no amount of my messing around will get it to print anything. The printer installs fine, and is visible. When I send a print job, I see the popup message saying “printing”, followed by another saying the job is complete. Nothing remains in the print queue. But the printer doesn’t produce anything. Connection via USB and wifi have the same result. The printer prints fine from another machine using Windows 10. The tail and of the CUPS error log looks like this:
E [12/Nov/2018:15:35:27 +0000] [CGI] cups-brf must be called as rootE [12/Nov/2018:15:35:27 +0000] [cups-deviced] PID 8701 (cups-brf) stopped with status 1!
E [12/Nov/2018:15:35:28 +0000] [cups-deviced] PID 8707 (gutenprint52+usb) stopped with status 1!
E [12/Nov/2018:15:35:32 +0000] [cups-driverd] Bad driver information file \"/usr/share/cups/drv/cupsfilters.drv\"!
E [12/Nov/2018:15:35:32 +0000] [cups-driverd] Bad driver information file \"/usr/share/cups/drv/generic-brf.drv\"!
E [12/Nov/2018:15:35:32 +0000] [cups-driverd] Bad driver information file \"/usr/share/cups/drv/generic-ubrl.drv\"!
E [12/Nov/2018:15:35:32 +0000] [cups-driverd] Bad driver information file \"/usr/share/cups/drv/indexv3.drv\"!
E [12/Nov/2018:15:35:32 +0000] [cups-driverd] Bad driver information file \"/usr/share/cups/drv/indexv4.drv\"!
E [12/Nov/2018:15:35:32 +0000] [cups-driverd] Bad driver information file \"/usr/share/cups/drv/sample.drv\"!
E [12/Nov/2018:15:42:12 +0000] [cups-driverd] Bad driver information file \"/usr/share/cups/drv/cupsfilters.drv\"!
E [12/Nov/2018:15:42:12 +0000] [cups-driverd] Bad driver information file \"/usr/share/cups/drv/generic-brf.drv\"!
E [12/Nov/2018:15:42:12 +0000] [cups-driverd] Bad driver information file \"/usr/share/cups/drv/generic-ubrl.drv\"!
E [12/Nov/2018:15:42:12 +0000] [cups-driverd] Bad driver information file \"/usr/share/cups/drv/indexv3.drv\"!
E [12/Nov/2018:15:42:12 +0000] [cups-driverd] Bad driver information file \"/usr/share/cups/drv/indexv4.drv\"!
E [12/Nov/2018:15:42:12 +0000] [cups-driverd] Bad driver information file \"/usr/share/cups/drv/sample.drv\"!
W [12/Nov/2018:15:42:50 +0000] CreateProfile failed: org.freedesktop.DBus.Error.ServiceUnknown:The name org.freedesktop.ColorManager was not provided by any .service files
W [12/Nov/2018:15:42:50 +0000] CreateProfile failed: org.freedesktop.DBus.Error.ServiceUnknown:The name org.freedesktop.ColorManager was not provided by any .service files
W [12/Nov/2018:15:42:50 +0000] CreateDevice failed: org.freedesktop.DBus.Error.ServiceUnknown:The name org.freedesktop.ColorManager was not provided by any .service files
E [12/Nov/2018:15:51:18 +0000] [CGI] cups-brf must be called as root
E [12/Nov/2018:15:51:18 +0000] [cups-deviced] PID 23570 (cups-brf) stopped with status 1!
E [12/Nov/2018:15:51:18 +0000] [cups-deviced] PID 23576 (gutenprint52+usb) stopped with status 1!
E [12/Nov/2018:15:51:24 +0000] [cups-driverd] Bad driver information file \"/usr/share/cups/drv/cupsfilters.drv\"!
E [12/Nov/2018:15:51:24 +0000] [cups-driverd] Bad driver information file \"/usr/share/cups/drv/generic-brf.drv\"!
E [12/Nov/2018:15:51:24 +0000] [cups-driverd] Bad driver information file \"/usr/share/cups/drv/generic-ubrl.drv\"!
E [12/Nov/2018:15:51:24 +0000] [cups-driverd] Bad driver information file \"/usr/share/cups/drv/indexv3.drv\"!
E [12/Nov/2018:15:51:24 +0000] [cups-driverd] Bad driver information file \"/usr/share/cups/drv/indexv4.drv\"!
E [12/Nov/2018:15:51:24 +0000] [cups-driverd] Bad driver information file \"/usr/share/cups/drv/sample.drv\"!
W [12/Nov/2018:15:52:19 +0000] CreateProfile failed: org.freedesktop.DBus.Error.ServiceUnknown:The name org.freedesktop.ColorManager was not provided by any .service files
W [12/Nov/2018:15:52:19 +0000] CreateProfile failed: org.freedesktop.DBus.Error.ServiceUnknown:The name org.freedesktop.ColorManager was not provided by any .service files
W [12/Nov/2018:15:52:19 +0000] CreateDevice failed: org.freedesktop.DBus.Error.ServiceUnknown:The name org.freedesktop.ColorManager was not provided by any .service files
Clearly something badly wrong! I’m presuming whatever goes down the line doesn’t make sense to the printer because of all this. Can anyone suggest a next step?
fred@localhost:~> lpstat -t
scheduler is running
no system default destination
device for DeskJet_2600: hp:/net/DeskJet_2600_series?ip=192.168.1.32
device for HP_LaserJet_MFP_M227-M231: hp:/net/HP_LaserJet_MFP_M227-M231?ip=192.168.1.24
DeskJet_2600 accepting requests since Mon 12 Nov 2018 15:52:49 GMT
HP_LaserJet_MFP_M227-M231 accepting requests since Mon 15 Oct 2018 11:30:22 BST
printer DeskJet_2600 is idle. enabled since Mon 12 Nov 2018 15:52:49 GMT
printer HP_LaserJet_MFP_M227-M231 is idle. enabled since Mon 15 Oct 2018 11:30:22 BST
The lpstat output looks ok, but we may have a driver-related issue to deal with. I assume you can ping the printer successfully at the configured IP address?
Anyway, the next step involves a more thorough analysis of the CUPS error_log file. It’s useful to put CUPS into debug mode first with
sudo cupsctl --debug-logging
then submit a print job. Examine /var/log/cups/error_log for errors - in particular filter-related errors. Be careful to only examine the current job, by job-id, or using the time stamps.
To share the lengthy logging, you’re best advised to copy/paste it to https://susepaste.org/ , choose a suitable ‘Delete After’ period, and post the link that it provides here so that others can review it and advise further. Alternatively, you can also install the ‘susepaste’ utility (package of the same name), and use like this to upload the file…
susepaste /var/log/cups/error_log
Again, just post the URL to it here.
BTW, if the error_log is too long (too much history), you can delete it before doing any of this with
sudo rm -f /var/log/cups/error_log
and it will be recreated next time CUPS starts eg via
Ping produces no response, which is odd since all other indications are that connection is sound. I can connect to the printer admin via its IP address in a browser. (Also the laser printer, which is working fine, also does not respond to a ping.)
I cleared the log file, and here is the (lengthy!) output for an attempted print job.
Browsing HP’s support site I came across the hp-check utility. I ran it and the first thing I notice is this:
Current contents of '~/.hplip/hplip.conf' file:
[last_used]
device_uri = hp:/net/DeskJet_2600_series?ip=192.168.1.32
printer_name = HP_LaserJet_MFP_M227-M231
working_dir = .
I have two HP printers installed, the new Deskjet I can’t get to print, and a Laserjet which is fine. Is this config file suggesting that it’s pointing jobs at the inkjet but somehow using the LaserJet’s formatting?
As a follow-up to the above, I uninstalled both printers, removed the ~/.hplip/hplip.conf’ file and installed just the new inkjet. It still fails to print. But the interesting thing is that in the process the ~/.hplip/hplip.conf’ file has been recreated and still shows the now uninstalled Laserjet as the printer name, as in my last post. Any ideas as to what’s going on here?
OK. Well to keep things simple, after removing the printers, and pausing and rebooting, I installed just the problem printer on its own (using hp-setup). It still doesn’t produce any output. I get the “job sent” and “job completed” popups, and the printer light flashes as when it’s processing a job, but nothing is actually printed.
I’ve had a good look through the CUPS error_log you posted back in post #7. The filters for the print job all execute with no problems reported…
D [13/Nov/2018:09:47:50 +0000] [Job 184] 2 filters for job:
D [13/Nov/2018:09:47:50 +0000] [Job 184] pdftopdf (application/pdf to application/vnd.cups-pdf, cost 66)
D [13/Nov/2018:09:47:50 +0000] [Job 184] foomatic-rip (application/vnd.cups-pdf to printer/DeskJet_2600, cost 0
there is also conversion from pdf to ps required (by foomatic-rip) and they all complete with no errors reported…
D [13/Nov/2018:09:47:55 +0000] [Job 184] PID 21512 (pstops) exited with no errors.
D [13/Nov/2018:09:47:55 +0000] [Job 184] PID 21511 (pdftops) exited with no errors.
D [13/Nov/2018:09:47:56 +0000] [Job 184] Closing foomatic-rip.
D [13/Nov/2018:09:47:56 +0000] [Job 184] PID 21508 (/usr/lib/cups/filter/foomatic-rip) exited with no errors.
D [13/Nov/2018:09:48:05 +0000] [Job 184] ready to print
The hp backend (used for communication with the printer) also finishes with no errors
D [13/Nov/2018:09:48:05 +0000] [Job 184] PID 21509 (/usr/lib/cups/backend/hp) exited with no errors.
IMHO, this means that although there are no problems with the CUPS workflow, the printer PPD may have some issues that cause improper formatting of the print data perhaps. Many printers will then simply not process the print job. So a bug report may be needed here.