Bluetooth USB device silently fails to attach to Fedora-based qubes

User Support Hardware Issues
1

EDIT:
I’m trying to attach bluetooth to sys-audio, but the USB device will not attach on Fedora templates, but others will and this works fine on the Debian 13 template. I have confirmed all this through lsusb and qvm-usb. I can’t figure out why one device would fail to connect and another not.

I’ve tried to increase vCPUs to 4 and RAM to 2GB in sys-usb, but this did not work. I can confirm sys-usb is configured correctly, other USB devices work and this one works on Debian. I can confirm sys-audio is configured correctly, I have the same setup with Bluetooth working on another machine and the behavior is observed on other Fedora-based qubes (with different, unmodified template).

Original post

I’m using the NV41 with Heads (error happens both on Novacustom’s firmware and Nitrokey’s firmware).

I’m using sys-audio with the latest RPC permissions, but attaching the USB bluetooth controller from the widget silently fails, and trying to throws an error saying it failed because it wasn’t attached to begin with, even though the widget says it is.

qvm-device usb at sys-audio sys-usb:#-## also fails silently, with qvm-device usb ls showing it is not used by a qube.

I have confirmed this with lsusb in sys-audio.

I’m not even close to familiar enough with qvm-device to know what is happening, and with no error I don’t know where to look.

2

I noticed some problems with device attachments on 4.3 being super slow (multi minutes sometimes) and rough around the edges.

Last time i tested sys-audio was years ago, so i am not super up to date on that front.

However does it attach your devices automatically at boot? On one install of 4.3rc3 or 4 this failed with other hardware to attach my wifi to sys-net as sys-net tried to start before sys-usb and that failed in a pretty similar way.

Could you try killing sys-audio, removing any auto-attach and attaching the device from a running system and see if that works?

An alternative may be to remove sys-audio from the autostart and autostarting it via a script, ensuring it starting after sys-usb, but that may have a chance to break audio stuffs?

3

My bad, I’m still on 4.2, and I don’t know when it began. I know it’s been here for at least a few months, when I tried momentarily and put it off until another day. I manually attach the USB Bluetooth controller, it isn’t automatic.

4

Okay, I’ve confirmed it works in Debian, and that it doesn’t in a clean, up-to-date Fedora template. Should’ve looked at that earlier TBH, my bad. Another user, solene, has confirmed it doesn’t need extra firmware to work. I think this is a template issue.