Yes, but it is only for printers that support IPP. The Internet Printing Protocol (IPP) is a “zeroconf” protocol that allows clients to query printers (usually via a network connection) for configuration details. Airprint and Mopria are examples if zeroconf protocols compatible with IPP. ipp-usbsupports IPP using USB, and is not applicable to printers that don’t support IPP.
1 Like
Well, since it is unlikely that ipp-usb will work, I guess it is back to trying to get CUPS to connect over the USB port directly. I really have no idea why that hp:/... device URI is not working. The following still looks like the core of the problem to me:
error: Unable to communicate with device (code=12): hp:/usb/Deskjet_1000_J110_series?serial=CN29F19KDY05YD
error: Device not found
error: Communication status: Failed
There is some documentation about what sort of device URIs CUPS will accept here: http://localhost:631/help/spec-ipp.html?QUERY=device-uri#device-uri
Among the options is to specify the USB device node directly with usb:/dev/....
Unfortunately, the /dev/bus/usb/... path will change every time the device is reconnected or the PC is rebooted.
This person has shown what might be a viable workaround by using a udev rule: https://forums.gentoo.org/viewtopic-p-3754212.html#3754212
I guess that would be the next thing I would try. (Note that the initial udev rule shown in that post is invalid. You’ll have to experiment with that a bit to get it working first.)
I have not read through the entire thread, but do use HP printers with hplip.
When I have had issues I simply used the printer panel in gnome settings to remove all defined printers. I then used hp-setup (or rather the gui equivalent provided by hplip-gui) to redefine the printer. I have done it both ways and it works for me with either, though I prefer the gui approach.
I have noted that on my system and with my printer avahi is unable to properly configure the printer to actually print. I always have one functioning printer that I defined with hplip and one non-functioning printer that is automatically defined by the system.
I’ve never used hp-setup. I think it was complaining about some missing dependencies, so I wasn’t sure that it worked. I’ve always used the CUPS web interface, but I always set up network printers and, for many years, I’ve been using the IPP protocol to connect to them (though some of them do still use the HPLIP drivers rather than the universal driver).
If you know how to do it with the hp-setup command, then that might have a chance of success. Thanks.
The hp-setup command basically walks the user through the config. Very first screen opened up selects the connection type and when you select next it searches for the printer. The last step is to define the printer name and print spool with an option to print a test page.
Personally I always ensure the names I use do not conflict with the automatically assigned names so there should never be an issue in identifying which printer I send jobs to.
I have found that if I leave the default names it gets confused with the printer that is defined automatically by avahi and that does not work for me.
You may chose to not run avahi, and CUPS would not auto-configure the printers.
True. I had done that earlier, but when I did a clean install of f39 it came back and I did not bother making the change again.
Hi George,
you are right HP1000 would’nt be supportet - Source: IPP Everywhere™ Printers - Printer Working Group – IPP Everywhere™ Printers
1 Like
Thank you for your contributions - below are the results of my tests:
-
Cockpit + Cockpit client installed - I’m going to find out what I can do with it
-
HPLIP-GUI installed - the attempt to print a test page resulted in:
Unable to communicate with printer Deskjet-1000-J110-series.
-
Under HPLIP - HP Deskjet 1000 j110 Series | hp's Developer Portal - I found that Fedora supports versions 15, 16 and 17 -??? worked until recently up to version 39
-
avahi installed - don’t know yet what I can do with it - don’t know how to start it
-
Followed instructions on: Find your systems easily on a LAN with mDNS - Fedora Magazine
[athauta@fedora ~]$ ping predator.local -- changed pollux to predator (my machine)
PING predator.local (192.168.8.108) 56(84) bytes of data.
64 bytes from predator (192.168.8.108): icmp_seq=1 ttl=64 time=0.035 ms
64 bytes from predator (192.168.8.108): icmp_seq=2 ttl=64 time=0.077 ms
64 bytes from predator (192.168.8.108): icmp_seq=3 ttl=64 time=0.098 ms
64 bytes from predator (192.168.8.108): icmp_seq=4 ttl=64 time=0.113 ms
64 bytes from predator (192.168.8.108): icmp_seq=5 ttl=64 time=0.092 ms
64 bytes from predator (192.168.8.108): icmp_seq=6 ttl=64 time=0.086 ms
64 bytes from predator (192.168.8.108): icmp_seq=7 ttl=64 time=0.075 ms
64 bytes from predator (192.168.8.108): icmp_seq=8 ttl=64 time=0.078 ms
64 bytes from predator (192.168.8.108): icmp_seq=9 ttl=64 time=0.077 ms
64 bytes from predator (192.168.8.108): icmp_seq=10 ttl=64 time=0.090 ms
64 bytes from predator (192.168.8.108): icmp_seq=11 ttl=64 time=0.080 ms
64 bytes from predator (192.168.8.108): icmp_seq=12 ttl=64 time=0.050 ms
64 bytes from predator (192.168.8.108): icmp_seq=13 ttl=64 time=0.078 ms
64 bytes from predator (192.168.8.108): icmp_seq=14 ttl=64 time=0.078 ms
64 bytes from predator (192.168.8.108): icmp_seq=15 ttl=64 time=0.088 ms
64 bytes from predator (192.168.8.108): icmp_seq=16 ttl=64 time=0.076 ms
64 bytes from predator (192.168.8.108): icmp_seq=17 ttl=64 time=0.097 ms
As your printer doesn’t support network, the avahi server is irrelevant for this problem, and so is ipp and mDNS. mDNS can be useful for other things, but not for finding USB connected printers.
The webpages from hp may be a bit outdated, so the fact it doesn’t mention Fedora versions beyond 17 may not mean anything.
@computersavvy is using hplip and I don’t so you may listen to advice he might give.
1 Like
Ok! Many thanks!
I checked for support with hplip at All Supported Printer Models | hp's Developer Portal
and found
It certainly should be supported with the current hplip version 3.24.4 on fedora 40.
As I noted above the automatic config probably does not work and it is possible that ipp-usb may interfere and possibly should be removed.
Removed ipp-usb - restart - ca’nt see anything changes.
Then I removed the printer and install again - as you described in an earlier post. But - the printer does’nt print.
Since I’m stuck with Fedora, the next step is to install Ubuntu and then Debian on my second laptop. I want to find out if the printer works on these distributions.
Bin gespannt, ob das was bringt! Als letzte Option teste ich den Drucker noch auf einer Windowd-Maschine von einem Freund. Sollte es dort auch nicht funktionieren, gehe ich davon aud dass der Drucker kaputt ist, auch wenn ich es nicht glauben möchte.
Sorry, does’nt translate. Here in English.
I’m curious to see if that helps! As a last resort, I’ll test the printer on a Windows machine belonging to a friend. If it doesn’t work there either, I’ll assume that the printer is broken, even though I don’t want to believe it.
I would like to express my sincere thanks to everyone who helped me with my problem.
As previously announced, I made two more attempts – one with Debian 12 and the other with Ubuntu 24. Unfortunately, I was unsuccessful in both cases – which I should have realized, because all distributions work with the same HP-LIP modules, so the results are identical.
As I read in various older forums, there have always been problems with the HP Deskjet 1000, dating back to 2011.
Thank you again for your friendly and persistent help - I wish you more success in solving your problems.
1 Like
It seems unlikely that there is really a problem with the printer; especially since you even purchased another one. The problem seems to be with the newer versions of HP-LIP. It seems like the hp:/<whatever> device URIs no longer work. I did suggest trying a different form of device URI – usb:/<whatever> – in an earlier post that might still be a viable workaround. But I don’t blame you if you don’t feel like messing with it anymore. 
That said, if you do find a workaround and share it here, you might make a lot of other people happy as well.
Thank you for reminding me, I had lost sight of the USB-URI – I will try it out in the next few days and report back.
2 Likes
Hi Greg,
now I’ve installed the printer on USB - and I also installed IPP-USB again - and unfortunately, the printer still doesn’t do what it’s supposed to.
| Beschreibung: | HP Deskjet 1000 J110 series |
|---|---|
| Ort: | localhost |
| Treiber: | HP Deskjet 1000 j110 Series, hpcups 3.24.4 (farbig, 2-seitiges Drucken) |
| Verbindung: | usb://HP/Deskjet%201000%20J110%20series?serial=CN1AJ21K8205D2 |
| Standardeinstellungen: | job-sheets=none, none media=iso_a4_210x297mm sides=one-sided |
What I noticed: the serial number of the printer (CN1AJ21K82) has been given the addition in the parameters: 05D2 (see above) - why, what for? This is only a marginal phenomenon.
Is there a log showing the activities of the print function? I found a log that shows me the CUPS activities:
sudo journalctl -u cups --since=2024-10-26 --until=2027-10-27 > cups.txt
Is there a way to limit this to 5-10 minutes?
Yes, you should be able to use --since=-5min.
There are several forms for those device URIs. The usb://<vendor>/<identifier> form is one valid form. But since that didn’t work (either), I’d suggest to try the last USB form – usb:/dev/<filename> (note that there is only one slash after the colon). You’ll have to create a udev rule first. The udev rule is just a file you need to create under /etc/udev/rules.d. I would name the file 99-printer0.rules and add the following line to the file:
BUS=="usb", SYSFS{serial}=="CN1AJ21K8205D2", NAME="%k", SYMLINK="printer0"
After you’ve created the file, run sudo udevadm trigger and see if a printer0 symlink shows up under /dev. The symlink should point to the real device node that goes to your USB printer. If it doesn’t work, try changing the rule to leave off that 05D2 part that you were not sure about. You might also check the dmesg logs to see if you can find the correct serial number or even look for it on a sticker on the printer.
Once you get that symlink to show up under /dev, you should be able to use usb:/dev/printer0 as the device URI when configuring CUPS to connect to your printer and hopefully that will work. 
The CUPS print log is now available – it’s 231 pages in Word, even though I reduced the output to 3 minutes – what do I need to pay attention to or should I send you the file somehow?