Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Printing fails on 3.22.10-1 rev810 (HP LaserJet 1010) #9

Open
jlbribeiro opened this issue Sep 18, 2023 · 0 comments
Open

Printing fails on 3.22.10-1 rev810 (HP LaserJet 1010) #9

jlbribeiro opened this issue Sep 18, 2023 · 0 comments

Comments

@jlbribeiro
Copy link

jlbribeiro commented Sep 18, 2023

First of all, I want to thank you all for this project; I've deployed this in my parents' home to ease the use of the printer by their many devices, and it's been a lifesaver so far, no more drivers!

Today they reported the printer was no longer working, everything getting enqueued with errors.
After many off/on, disconnect/connect cycles, "Print Test Page" attempts (via the web UI) automatically followed by "Aborted at ...", and removal + "add printer" attempts, I just checked the installed snap version and noticed I was on the edge channel (by mistake), which at the time of writing installs

latest/edge:      3.22.10-1 2023-09-05 (810)

Since their last printing job had been roughly two weeks ago, I uninstalled + installed the stable channel version, at the time of writing

latest/stable:    3.22.10-1 2023-07-14 (789)

(the date of the last commit in this repo?). Everything is working again.

Some loose notes:

  • during one of the removal + add printer attempts (via the web UI), the printer was not listed at all; lsusb kept reporting the device just fine;
  • the most suspicious line in snap logs hplip-printer-app -n=all is hp[nnnn]: io/hpmud/musb.c 2101: Invalid usb_open: Operation not permitted; however, I can find that line in two log lines from 2023-02-12 (don't know whether errors were occurring at the time, nor the installed version). Every other occurrence of that error (many) is from today.

As I did all this remotely (and in an urgent attempt of fixing it), I completely apologize in advance for the lack of detail in this report, as I don't have physical access to the equipment. Just wanted to leave a datapoint on whether something has been broken between revs.

If there's any info I can provide you from "after the fact" (logs, etc.), please feel free to request so. Once again, thank you!


(For someone with the same issue, I've temporarily held automatic updates using snap refresh --hold=forever hplip-printer-app in the meantime.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant