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

provide GUI mechanism (Qubes Manager, Settings, etc) for USB passthrough #2328

Open
mfc opened this Issue Sep 20, 2016 · 5 comments

Comments

@mfc
Member

mfc commented Sep 20, 2016

I couldn't find a ticket tracking this. The options available to the user in attaching a single USB device to a qube (USB passthrough) should be available to the user through a GUI, with appropriate warning. This is especially important for webcam passthrough, which has previously been seen a blocker for user adoption.

@boring-stuff

This comment has been minimized.

Show comment
Hide comment
@boring-stuff

boring-stuff Feb 20, 2017

Anything against me starting on this?
I know it's a minor issue, but it might be one of the few tasks I might use to learn GUI programming (with Gtk) and Qubes at the same time. Code would be shared with/taken from #910 as well.
Edit: please also consider if my code style from 910 is appropriate (i.e. unit tests are going to be integrated in the build process and actually checked and maintained for future code development).

boring-stuff commented Feb 20, 2017

Anything against me starting on this?
I know it's a minor issue, but it might be one of the few tasks I might use to learn GUI programming (with Gtk) and Qubes at the same time. Code would be shared with/taken from #910 as well.
Edit: please also consider if my code style from 910 is appropriate (i.e. unit tests are going to be integrated in the build process and actually checked and maintained for future code development).

@andrewdavidwong

This comment has been minimized.

Show comment
Hide comment
@andrewdavidwong

andrewdavidwong Feb 20, 2017

Member

Thanks, @boring-stuff! I can see no problem with you starting on it. @marmarek?

Member

andrewdavidwong commented Feb 20, 2017

Thanks, @boring-stuff! I can see no problem with you starting on it. @marmarek?

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Feb 20, 2017

Member

This is somehow a duplicate of #2132 - where the same widget will be used to assign any type of device (block, usb etc). See here:
#2132 (comment)
@kalkin what is the current status of it?

Member

marmarek commented Feb 20, 2017

This is somehow a duplicate of #2132 - where the same widget will be used to assign any type of device (block, usb etc). See here:
#2132 (comment)
@kalkin what is the current status of it?

@mfc mfc added P: major and removed P: minor labels Apr 6, 2017

@mfc

This comment has been minimized.

Show comment
Hide comment
@mfc

mfc Apr 6, 2017

Member

this is not a duplicate of #2132. just as the Qubes VM Manager has Attach/Detach audio-input to the VM, this would create an Attach/Detach webcam to the VM entry. this is continually listed as one of the remaining usability / adoption challenges for Qubes.

I don't think waiting for Release 4.0 and the new Decomposed Qubes Manager is realistic for this, I think this should be added to Release 3.2 update milestone.

Member

mfc commented Apr 6, 2017

this is not a duplicate of #2132. just as the Qubes VM Manager has Attach/Detach audio-input to the VM, this would create an Attach/Detach webcam to the VM entry. this is continually listed as one of the remaining usability / adoption challenges for Qubes.

I don't think waiting for Release 4.0 and the new Decomposed Qubes Manager is realistic for this, I think this should be added to Release 3.2 update milestone.

@mfc

This comment has been minimized.

Show comment
Hide comment
@mfc

mfc Apr 20, 2017

Member

hey @boring-stuff you still have some time for this? it is actually quite an important issue for new users and would help a lot with user retention of less technical users. R3.2 is going to be around for a while (supported for a year after R4.0 is released) and it would be really good to have this be part of it.

Member

mfc commented Apr 20, 2017

hey @boring-stuff you still have some time for this? it is actually quite an important issue for new users and would help a lot with user retention of less technical users. R3.2 is going to be around for a while (supported for a year after R4.0 is released) and it would be really good to have this be part of it.

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