Recent bluez update broke Bluetooth for setups using a BT dongle

[Saverio Miroddi]

A recent upgrade (seemingly 5.53-0ubuntu3.5) broke Bluetooth functionality for certain setups.

Specifically, the `ConditionPathIsDirectory=` parameter has been added to the `bluetooth` Systemd unit. This breaks setups where users use a Bluetooth dongle, since when the system starts, the BT device may not be connected, and due to the condition, the `bluetooth` unit won't start at all.

[Daniel van Vugt (vanvugt)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:

apport-collect 1960709

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

[Daniel van Vugt (vanvugt)]

BTW, "ConditionPathIsDirectory" is not new. It's been there for two years already in Ubuntu 20.04.

If you have experienced a regression then more often that would come from a kernel update so please try some different kernel versions.

[Saverio Miroddi (64kramsystem)]

Hello!

I think the bug can be closed:

> BTW, "ConditionPathIsDirectory" is not new. It's been there for two years already in Ubuntu 20.04.

On the same date of the bluez package upgrade, I had to revert to an older kernel version due to the amdgpu driver incompatibility, so that should be the cause.

The version was the Ubuntu mainline 5.11.16 (the latest compatible with 20.04 and with the amdgpu official drivers as of today), which I don't know if it's of any interest (if so, I can upload the information).

[Saverio Miroddi (64kramsystem)]

Thanks for the reply, by the way :)