I installed blueman-manager in a debian 13 minimal and was able to “connect” my bluetooth headset but failed to get the audio and mic to route via the headset. The system could not locate my “connected” headset. There must be a package missing. Which is it?
The minimal templates are intended only for advanced users. Most things will not work out-of-the-box, and you will have to fix them yourself. If you are not prepared to do a lot of reading, searching, learning, and troubleshooting, then you should instead stick to the standard templates, which are perfectly suitable for the vast majority of users. In particular, if you are new to Qubes, you should not attempt to use minimal templates until you have gained more experience.
2 Likes
That’s not very helpful.
Also, bluetooth connection failed with Debian 13 (both XFCE and GNOME). With the minimum, at least it connected.
I tried to connect bluetooth to a debian-based VM. The bluetooth disconnected within a few seconds. these are the logs. Neither minimal or full templates are working with bluetooth, after install blueman.
[2026-04-14 15:58:29] [ 25.823971] vhci_hcd vhci_hcd.0: USB/IP Virtual Host Controller
[2026-04-14 15:58:29] [ 25.824098] vhci_hcd vhci_hcd.0: new USB bus registered, assigned bus number 1
[2026-04-14 15:58:29] [ 25.824149] vhci_hcd: created sysfs vhci_hcd.0
[2026-04-14 15:58:29] [ 25.824235] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.18
[2026-04-14 15:58:29] [ 25.824274] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[2026-04-14 15:58:29] [ 25.824309] usb usb1: Product: USB/IP Virtual Host Controller
[2026-04-14 15:58:29] [ 25.824337] usb usb1: Manufacturer: Linux 6.18.15-1.qubes.fc41.x86_64 vhci_hcd
[2026-04-14 15:58:29] [ 25.824372] usb usb1: SerialNumber: vhci_hcd.0
[2026-04-14 15:58:29] [ 25.825259] hub 1-0:1.0: USB hub found
[2026-04-14 15:58:29] [ 25.825297] hub 1-0:1.0: 8 ports detected
[2026-04-14 15:58:29] [ 25.825542] vhci_hcd vhci_hcd.0: USB/IP Virtual Host Controller
[2026-04-14 15:58:29] [ 25.825672] vhci_hcd vhci_hcd.0: new USB bus registered, assigned bus number 2
[2026-04-14 15:58:29] [ 25.825732] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.
[2026-04-14 15:58:29] [ 25.825804] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 6.18
[2026-04-14 15:58:29] [ 25.825840] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[2026-04-14 15:58:29] [ 25.825875] usb usb2: Product: USB/IP Virtual Host Controller
[2026-04-14 15:58:29] [ 25.825903] usb usb2: Manufacturer: Linux 6.18.15-1.qubes.fc41.x86_64 vhci_hcd
[2026-04-14 15:58:29] [ 25.825938] usb usb2: SerialNumber: vhci_hcd.0
[2026-04-14 15:58:29] [ 25.826065] hub 2-0:1.0: USB hub found
[2026-04-14 15:58:29] [ 25.826089] hub 2-0:1.0: 8 ports detected
[2026-04-14 15:58:29] [ 26.080770] vhci_hcd vhci_hcd.0: pdev(0) rhport(0) sockfd(0)
[2026-04-14 15:58:29] [ 26.080800] vhci_hcd vhci_hcd.0: devid(262148) speed(2) speed_str(full-speed)
[2026-04-14 15:58:29] [ 26.080826] vhci_hcd vhci_hcd.0: Device attached
[2026-04-14 15:58:29] [ 26.242631] vhci_hcd: vhci_device speed not set
[2026-04-14 15:58:29] [ 26.293594] usb 1-1: new full-speed USB device number 2 using vhci_hcd
[2026-04-14 15:58:29] [ 26.355682] vhci_hcd: vhci_device speed not set
[2026-04-14 15:58:29] [ 26.406554] usb 1-1: SetAddress Request (2) to port 0
[2026-04-14 15:58:29] [ 26.430755] usb 1-1: New USB device found, idVendor=8087, idProduct=0033, bcdDevice= 0.00
[2026-04-14 15:58:29] [ 26.430808] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[2026-04-14 15:58:29] [ 26.494649] Bluetooth: Core ver 2.22
[2026-04-14 15:58:29] [ 26.495034] NET: Registered PF_BLUETOOTH protocol family
[2026-04-14 15:58:29] [ 26.495042] Bluetooth: HCI device and connection manager initialized
[2026-04-14 15:58:29] [ 26.495051] Bluetooth: HCI socket layer initialized
[2026-04-14 15:58:29] [ 26.495057] Bluetooth: L2CAP socket layer initialized
[2026-04-14 15:58:29] [ 26.495066] Bluetooth: SCO socket layer initialized
[2026-04-14 15:58:29] [ 26.502799] usbcore: registered new interface driver btusb
[2026-04-14 15:58:29] [ 26.504224] Bluetooth: hci0: Firmware timestamp 2025.20 buildtype 1 build 3882
[2026-04-14 15:58:29] [ 26.504238] Bluetooth: hci0: Firmware SHA1: 0x937bca4a
[2026-04-14 15:58:29] [ 26.508899] Bluetooth: hci0: Found device firmware: intel/ibt-0180-0041.sfi
[2026-04-14 15:58:29] [ 26.508917] Bluetooth: hci0: Boot Address: 0x100800
[2026-04-14 15:58:29] [ 26.508923] Bluetooth: hci0: Firmware Version: 20-49.24
[2026-04-14 15:58:29] [ 26.516546] vhci_hcd: connection closed
[2026-04-14 15:58:29] [ 26.516597] vhci_hcd: stop threads
[2026-04-14 15:58:29] [ 26.516627] vhci_hcd: release socket
[2026-04-14 15:58:29] [ 26.516670] usb 1-1: USB disconnect, device number 2
[2026-04-14 15:58:29] [ 26.516785] Bluetooth: hci0: FW download error recovery failed (-19)
[2026-04-14 15:58:29] [ 26.516933] vhci_hcd: disconnect device
[2026-04-14 15:58:29] [ 26.516933] Bluetooth: hci0: sending frame failed (-19)
[2026-04-14 15:58:29] [ 26.516976] Bluetooth: hci0: Failed to read MSFT supported features (-19)
[2026-04-14 15:58:29] [ 26.616730] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[2026-04-14 15:58:29] [ 26.616745] Bluetooth: BNEP filters: protocol multicast
[2026-04-14 15:58:29] [ 26.616756] Bluetooth: BNEP socket layer initialized
[2026-04-14 15:58:45] [ 42.770251] vhci_hcd vhci_hcd.0: pdev(0) rhport(0) sockfd(0)
[2026-04-14 15:58:45] [ 42.770310] vhci_hcd vhci_hcd.0: devid(262149) speed(2) speed_str(full-speed)
[2026-04-14 15:58:45] [ 42.770367] vhci_hcd vhci_hcd.0: Device attached
[2026-04-14 15:58:46] [ 42.938822] vhci_hcd: vhci_device speed not set
[2026-04-14 15:58:46] [ 42.989529] usb 1-1: new full-speed USB device number 3 using vhci_hcd
[2026-04-14 15:58:46] [ 43.051628] vhci_hcd: vhci_device speed not set
[2026-04-14 15:58:46] [ 43.102677] usb 1-1: SetAddress Request (3) to port 0
[2026-04-14 15:58:46] [ 43.127570] usb 1-1: New USB device found, idVendor=8087, idProduct=0033, bcdDevice= 0.00
[2026-04-14 15:58:46] [ 43.127625] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[2026-04-14 15:58:46] [ 43.148323] Bluetooth: hci0: Firmware timestamp 2025.20 buildtype 1 build 3882
[2026-04-14 15:58:46] [ 43.148379] Bluetooth: hci0: Firmware SHA1: 0x937bca4a
[2026-04-14 15:58:46] [ 43.151936] Bluetooth: hci0: Found device firmware: intel/ibt-0180-0041.sfi
[2026-04-14 15:58:46] [ 43.152062] Bluetooth: hci0: Boot Address: 0x100800
[2026-04-14 15:58:46] [ 43.152082] Bluetooth: hci0: Firmware Version: 20-49.24
[2026-04-14 15:58:46] [ 43.158524] vhci_hcd: connection closed
[2026-04-14 15:58:46] [ 43.158605] vhci_hcd: stop threads
[2026-04-14 15:58:46] [ 43.158641] vhci_hcd: release socket
[2026-04-14 15:58:46] [ 43.158703] usb 1-1: USB disconnect, device number 3
[2026-04-14 15:58:46] [ 43.158847] vhci_hcd: disconnect device
[2026-04-14 15:58:46] [ 43.158871] Bluetooth: hci0: FW download error recovery failed (-19)
[2026-04-14 15:58:48] [ 45.181612] Bluetooth: hci0: Failed to read MSFT supported features (-110)
[2026-04-14 15:58:51] [ 47.941607] vhci_hcd: not connected 4
Look at the guide for setting up a sys-audio qube. You can set up the audio qube to deal with Bluetooth devices which then can be used as regular audio devices by all qubes. In my experience it works quite well (with the caveat that if you make sys-audio disposable you will have to manually copy the pairing info to preserve it across VM reboots).
1 Like
Thank you. I will try. Do you have a link to recent sys-audio setup guidelines to recommend?
@pablob upon reading these guidelines, I felt dizzy. I prefer to try to connect the bluetooth headset to an AppVM directly.
It looks complicated, but in the end the sys-audio VM is definitely worth setting up. If you are just starting with QubesOS, though, I understand you may want to learn more before attempting that.
I noticed a firmware loading error in your logs. Looking for it on the web, there are some comments that it could be caused by trying to load different firmware versions into the device.
I assume you have set up sys-usb during installation, and that the Bluetooth device is USB. In that case, check to make sure that you have the same firmware packages in both sys-usb and your VM. If sys-usb is Fedora-based, that could be causing it on your Debian-based VM (Fedora probably has a newer firmware version than Debian).
1 Like