printing job is stuck in the "Printer queue"
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
- debian, go, linux
- Domain
- backend, operating-systems
Research direction
Reproduce the issue on MX Linux with sysvinit by starting ipp-usb standalone -bg, printing with lp, restarting the printer, and printing again. Investigate the printer queue behavior after the device reconnects; done means a job submitted after the restart prints without remaining stuck and without requiring manual recovery.
Written by the indexing model from the issue text.
Description
I use sysvinit in MX Linux (debian 10 based).
Here is what works:
- I start MX Linux
- I start the HP printer
- I run the command
sudo ipp-usb standalone -bg
-> The printer is created (ipp://mx.local:60000/ipp/print) - I print with the command
lp -d HP_ENVY_5540_series_341375_USB_ /home/Golddouble/loschDruckversuch.txt
-> It prints. All is as expected.
Then I turn my printer off and immediately start it again.
Here is what does not work:
I just repeat the command lp -d HP_ENVY_5540_series_341375_USB_ /home/Golddouble/loschDruckversuch.txt
-> It does not print. There is no error or warning in the terminal. But the printing job just is stuck in the printing queue.
What can I do? Thank you.
Edit:
ipp-usb is installed, but
ippusbxd is not installed. Do I need ippusbxd?
Edit2:
It doesn't matter if I use
ipp-usb_0.9.19-1+50.2_amd64.deb or
ipp-usb_0.9.17-1+48.2_amd64.deb
Same behaviour.
- Dominant language
- Go
- Stars
- 210
- Forks
- 35
- 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
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from OpenPrinting/ipp-usb
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
OpenPrinting/ipp-usb#136 ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
OpenPrinting/ipp-usb#124 · 5 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 32/100
OpenPrinting/ipp-usb#123 · 10 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
OpenPrinting/ipp-usb#122 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
OpenPrinting/ipp-usb#116 · 2 comments ·
All issues in OpenPrinting/ipp-usb
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
chaitin/agent-compose#770 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
kind/bug
Difficulty 1/5 1-3 hours Newbie friendliness 85/100
kubernetes-sigs/vsphere-csi-driver#4351 ·
Maintainers usually reply within 1 day
-
component/gpu-kubelet-plugin component/helm needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
kubernetes-sigs/dra-driver-nvidia-gpu#1559 ·
Maintainers usually reply within 1 day
-
workflow: redundant goroutine in scheduleRetryPossibly taken @moodbased claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 2 days