I had 4.2.4 before and bluetooth worked fine, but with 4.3 I have an error:
Connection to bluez failed.
Bluez daemon is not running blueman-manager cannot continue.
This probably means that there were no bluetooth adapters detected or bluetooth daemon was not started.
When I checked the status for the bluetooth service, it said:
active: inactive (dead)
Condition: start condition unmet at …(the date)
ConditionPathExists=!/var/run/qubes-service/minimal-usbvm was not met
Is this something I can fix or is it needed to be done by the development team?
Disable the minimal-usbvm service for your sys-usb in its Qube Settings → Services tab.
1 Like
Thanks, this indeed solved that issue.
Does anyone know what is that and if in fact it’s safe to disable it?
Also, instead of notification, I get a weird popup when the device is connected, that I must click to close it. Is there a way to make this as notification as it was in 4.2.4?
minimal-netvm:
Default: enabled in NetVM
Performs memory optimizations to make NetVM consume as little RAM as possible. This is done by disabling unnecessary services and keeping a memory reserve for the kernel drivers.
minimal-usbvm:
Default: enabled in USBVM
Disables unnecessary services for USBVM.
qvm-service – Manage (Qubes-specific) services started in VM — Qubes Admin client mm_9d714429-1-g641fbb7 documentation
You may need to increase the initial memory for your sys-usb qube if you disable minimal-netvm so it won’t use swap.