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

qvm-usb return invalid speed when sys-usb lacks qubes-usb-proxy #3335

Closed
pietrushnic opened this Issue Nov 24, 2017 · 1 comment

Comments

Projects
None yet
2 participants
@pietrushnic

Qubes OS version:

R4.0-rc2

Affected TemplateVMs:

dom0, sys-usb


Steps to reproduce the behavior:

Make sure that qubes-usb-proxy is not installed in sys-usb and run below command in dom0

qvm-usb a <appvm> <usb-device>

Expected behavior:

Information about missing qubes-usb-proxy package or other message with true reason of failure.

Actual behavior:

Confusing message:

Device attach failed: invalid speed received

General notes:

I believe that salt states shall verify if required package is installed on sys-usb.

I thought that there is something wrong with support for my device and I was prepared to debug that by my own, but there is no documentation how to approach that. Digging Python scripts with so many levels of abstraction was also not pleasure. --verbose option didn't helped in that way. I believe there should be some note in documentation how to approach debugging of USB related problems. Or maybe I missing something and there is some debugging documentation out there ?


Related issues:

@andrewdavidwong

This comment has been minimized.

Show comment
Hide comment
@andrewdavidwong

andrewdavidwong Nov 25, 2017

Member

This appears to be a duplicate of #3026. If you believe this is not really a duplicate, please leave a comment briefly explaining why. We'll be happy to take another look and, if appropriate, reopen this issue. Thank you.

Member

andrewdavidwong commented Nov 25, 2017

This appears to be a duplicate of #3026. If you believe this is not really a duplicate, please leave a comment briefly explaining why. We'll be happy to take another look and, if appropriate, reopen this issue. Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment