Trying to re-install my HP printer. It was working fine for over a year. Then, it started washing a yellow/greenish tint over printed documents. It was suggested to reinstall the drivers and I was pointed here for a new hplip. I followed the directions as instructed (URLs not permitted) I tried this, no luck. I get to Step 12: Select Device, select my printer and it says "error: The device you are trying to setup requires a binary plug-in. Some functionalities may not work as expected without plug-ins. Please run 'hp-plugin' as normal user to install plug-ins. Visit (URLs not permitted) I run 'hp-plugin' and it tells me "Unable to receive key from keyserver". I tell it to install anyway. Then it finishes and says "Plug-in installation successful". I then re-run hp-setup and go through the whole Driver Plug-in thing again. I've installed the plug-in a bunch of times. Wash-rinse-repeat, over and over and over again. I have found a number of people complaining about this same thing, but no answers. Before, I could at least print, even with the color problem, I still has something I could use. Now, it does not show any printer available and I cannot print at all. I have to transfer my documents to another computer for printing.

Hi, Just want to check as when I tried this on my LightDM Distro: Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic but it didn't worked as it shows there was a problem opening the file (this file that has been downloaded from here) My printer is HP Color Laserjet Pro MFP M180n and it is not listed in the Linux Mint. Could you please advise and assist? As I would not be able to contact the support centre through here. Regards. Please assist urgently.

Very complex to get working. Seems strange to install the printer driver separately to the plugin, and the GUI. Stopped working after update to Ubuntu 19.10. The new version for Ubuntu 19.10 says to install Gobject, but there is no version to install. The installed version of HPlip cannot find the printer, when it is immediately found by IP address without HPlip. After days of trying, and repeated reinstalling, the scanner on HP fdn281 says there are ports that should be open. The printer was fine till the upgrade. The new version does not install. IN ubuntu 19.04, this printer installed in 30 seconds. The problem was a spelling error within HPLIP of this printer. I now set up a new computer with Ubuntu 18.04, that used to work with HPLIP, but the latest HPLIP cannot find the printer that is installed an working. Apparently the spelling error remains 2 versions of HPLIP later. It is a pity that later versions of this proprietary software add errors that do not get corrected. All error messages are unrelated to the source of the problem.

Useless stuff. This could not detect my network HP Laserjet 1018 connected to the ASUS RT N-16. Waste of time.

Works with Ubuntu MATE 19.04. Does not work with Ubuntu MATE 19.10. Installed hplip-3.19.10. Restarted system. Turned printer off, then on. Ran hp-setup. It failed. The /var/logs/cups/error_log shown multiple Unknown directive errors showing it was not tested/packaged properly. Illegal option keyword string in the /etc/cups/ppd/HP-OfficeJet-Pro-7740-series.ppd file. FindDeviceById failed: org.freedesktop.ColorManager.NotFound:device id \'cups-HP-OfficeJet-Pro-7740-series\' does not exist. etc... This must not have been tested on a system other than the development machine. Or no one bothered to read the error_log. Ran hp-doctor. It Failed! Looking at config.log I see such errors as: g++: error: unrecognized command line option '-V' g++: fatal error: no input files g++: error: unrecognized command line option '-qversion'; did you mean '--version'? conftest.c:11:10: fatal error: ac_nonexistent.h: No such file or directory conftest.c:27:9: error: unknown type name 'not' conftest.c:27:15: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'universal' conftest.c:27:15: error: unknown type name 'universal' conftest.c:33:12: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'endian' etc... etc... etc... Obviously this code was never tested and the logs were never examined.