That sounds like an excellent workaround. It's probably not a fix though. A fix would involve finding out why the config has confused bluez.
Actually this sounds like an "old" bug that was fixed after 16.04 since newer releases aren't being reported. If we could figure out what fixed it then we could backport that fix to 16.04. You can search the code here: https://git.kernel.org/pub/scm/bluetooth/bluez.git
That sounds like an excellent workaround. It's probably not a fix though. A fix would involve finding out why the config has confused bluez.
Actually this sounds like an "old" bug that was fixed after 16.04 since newer releases aren't being reported. If we could figure out what fixed it then we could backport that fix to 16.04. You can search the code here: /git.kernel. org/pub/ scm/bluetooth/ bluez.git
https:/