Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

cant discover older HP OfficeJets at printer boot

Open
  • Is something wrong?
#75 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
go, linux
Domain
backend, devtools

Research direction

Start by reproducing the cold-boot failure with an HP OfficeJet Pro 8710 or 8730 and compare the linked error, success, and fixed logs. Then inspect how ipp-usb handles the init-reset = soft quirk and the reported IPP client-error-bad-request. Done means the affected printers are discovered after boot without requiring a restart or a model-specific workaround.

Written by the indexing model from the issue text.

Description

As ipp-usb got the Ubuntu default, we now utilise it instead of hplip. There quite some HP OfficeJet printers around with different series, where of the following I could reproduce the error:
HP OfficeJet Pro 8710
HP OfficeJet Pro 8730

There are no more models I can test but maybe there are more models poping up in the wild.
Newer models like the HP OfficeJet Pro 9010 are unaffected by this (at least I tested this model without the following problem).

The error occurs if the printer was powered off quite a time (think at least a day, tested it today after the weekend) and gets started after Linux is already up. After the printer successfully started, it wouldnt be detected by the system. After a printer restart, replugging of the usb cable or a simple restart the ipp-usb daemon, it will work. Trying the same scenario again, it works at the first printer start.

I could solve the problem by adding the following quirk:

[HP OfficeJet Pro 8710]
  init-reset = soft

Logs:

error was the first start, success the second which worked ...

03f0-7a12-HP-OfficeJet-Pro-8730_error.log
03f0-7a12-HP-OfficeJet-Pro-8730_success.log
03f0-7c12-HP-OfficeJet-Pro-8710_error.log
03f0-7c12-HP-OfficeJet-Pro-8710_success.log

tried it with the second printer of the same model we have to test with the quirk applied

03f0-7c12-HP-OfficeJet-Pro-8710_fixed.log

Looks like the problem is the following IPP response when the device is finally up:

12-02-2024 08:20:16: ! IPP: IPP: client-error-bad-request

Maybe the device isnt already initialised in this stage but dont know either.

I posted it as a ticket because it looks like a more generic problem with the HP OfficeJet series and maybe it could be solved better than the qurik I've used.

Dominant language
Go
Stars
210
Forks
33
Avg merge
5h 47m
Merged PRs (30d)
1

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from OpenPrinting/ipp-usb

All issues in OpenPrinting/ipp-usb

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.