-
-
Notifications
You must be signed in to change notification settings - Fork 48
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
qui-devices widget don't notice some attach/detach #5505
qui-devices widget don't notice some attach/detach #5505
Comments
Dom0 monitors only /qubes-usb-devices qubesdb path itself, not the whole tree - VM side is supposed to do an empty write there after doing series of writes. Udev scripts advertising devices do that, but it was missing in usb-export script. Add missing write. QubesOS/qubes-issues#5505
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
Or update dom0 via Qubes Manager. |
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
Qubes OS version
R4.0, R4.1
Affected component(s) or functionality
usb proxy
Brief summary
When device is detached spontaneously (for example because device is reset by the driver), or when attached by directly calling relevant qrexec service, qui-devices widget won't notice it. Calling
qvm-usb
tool properly display the state.Expected behavior
qui-devices widget properly reflect the system state, as
qvm-usb
does.Actual behavior
qui-devices gets desynchronized.
Additional context
It's because events are sent only when the action is triggeder via dom0 qubesd code. When it's done some other means, events are missing, even though qubesd do receive notifications about the change.
Solutions you've tried
Alternative: refresh more info if any info about devices changes: QubesOS/qubes-desktop-linux-manager#87
This is kind of similar to what
qvm-usb
does - it retrieve all the info from scratch on eatch call.Related, non-duplicate issues
#4626
Reported by @rmol
The text was updated successfully, but these errors were encountered: