ipp-usb migration path
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
Research direction
The issue names no files, tests, or entry points, so start by mapping how ipp-usb is installed, enabled, and detects existing legacy print queues. Done would require an agreed migration mechanism and user-facing way to choose or switch between IPP-USB and legacy access.
Written by the indexing model from the issue text.
Description
Hi @tillkamppeter, @zdohnal, @debiantriage, @michaelrsweet and everybody else who may be interested,
I want to create a single discussion point for problems caused by migration from legacy USB drivers to the IPP-USB approach.
The running ipp-usb daemon known to be incompatible with legacy/proprietary printer and scanner drivers.
Although for most users IPP-USB works perfectly well, some people report printing or scanning breakage when system was upgraded, and ipp-usb was automatically installed.
This problem was discussed many times in many places, but we still have not found a good solution.
It was many times proposed, that ipp-usb will claim USB device access only when needed, and release it after use, or will not claim all the IPP-USB interfaces, allowing coexistence with legacy/proprietary drivers. I don't agree with this approach due to the following reasons:
- From the
ipp-usbperspective, it is hard to guess, when device usage was finished - Some devices don't like to be simultaneously accessed via IPP-USB and via legacy interface. See #26, for example
- If
ipp-usbwill fail to claim USB access to the already announced but temporary released device, the behaviour will be quite confusing for users
My proposal is following:
- On a newly installed system,
ipp-usbalways installed and enabled automatically - During upgrade of existent system, if there are already existent print queues, using the legacy USB access, user needs to switch to the
ipp-usbexplicitly - Some UI needs to be created to prompt the user to make such a decision
- UI needs to be provided to let user to switch between
ipp-usband legacy approach at any time
However, I have no idea what mechanisms we already have to implement this proposal, and what missed parts needs to be created.
Any comments welcome!
- 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
-
needs_triage
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 2 days
-
kind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
kubernetes-sigs/cluster-api-provider-ibmcloud#3023 · 1 comment ·
Maintainers usually reply within 1 day
-
[Bug]: message-level cache_control on chat messages is dropped, so Anthropic prompt caching never triggersPossibly taken @Atharva-Kanherkar claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
Maintainers usually reply within 1 day
-
documentation good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
eugenioenko/ttt#1000 ·
Maintainers usually reply within 1 day
-
bug needs-acceptance wg/developer-experience-ecosystem
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
vllm-project/semantic-router#5249 ·
Maintainers usually reply within 1 day