qubes-issues
qubes-issues copied to clipboard
QubesOS
Create a `sys-bluetooth` qube during installation
The problem you're addressing (if any)
For security reasons, Bluetooth needs to be handled in a separate VM.
The solution you'd like
Installer should create a sys-bluetooth qube if it detects a Bluetooth device.
This is not a duplicate of #7750 because #7750 also requires a bunch of other work that is not specific to Bluetooth.
The value to a user, and who that user might be
Users will be able to use Bluetooth easier.
It would be great because bluetooth audio is quite common nowadays but still is not supported by default installation of Qubes OS.
As a note, most bluetooth adapters are enumerated as USB devices, unlike sound, usb, and integrated network devices. Pretty much every intel Bluetooth chip, for instance.
The current system allows persistent usb device attachment, but it's by an arbitrary numbering system, so it "works" (i have Bluetooth auto-attach to my sys-audio-disposable qube at boot, as long as I don't have external usb devices plugged in to change the numbering), but I can't imagine it being programmatically stable (if I plug too many things in at boot, I may find suddenly my external SSD is forcibly attached to sys-audio-disposable instead).
We could try making a sys-audio implementation a selectable option, and putting it in the default sys-usb qube, but that's not a good idea, putting a LOT of things in one basket at that point. Can you think of anything better?
@bi0shacker001 I think you pointed out a problem with the USB device numbering system.
@bi0shacker001 I think you pointed out a problem with the USB device numbering system.
I'm not gonna lie, I had thought that the issues with the USB system were a case of "this is the best we can do with this system", given how flaky USB is, so it hadn't occurred to me until today that it wasn't already known about. I've considered the persistent USB system to be an advanced feature (if it's not in the gui, I assume that it's only really safe for use if you know what you're doing), and so haven't used it for anything but my bluetooth chip (and with that, I have to make sure that I don't have anything plugged in during startup
@bi0shacker001 I think you pointed out a problem with the USB device numbering system.
I'm not gonna lie, I had thought that the issues with the USB system were a case of "this is the best we can do with this system", given how flaky USB is, so it hadn't occurred to me until today that it wasn't already known about.
I’d noticed it before, but I also had not considered that it could be fixed.
I've considered the persistent USB system to be an advanced feature (if it's not in the gui, I assume that it's only really safe for use if you know what you're doing), and so haven't used it for anything but my bluetooth chip (and with that, I have to make sure that I don't have anything plugged in during startup
Yeah, that should be fixed.