This is no longer required as of noble (actually a release slightly
prior to that but I forget precisely which one). From noble onwards, the
bluetooth module is entirely under the control of the kernel, and pi-
bluetooth is no longer required for activation (on any supported model
of Pi). Simply install bluez, and things should "just work".
Marking fix released as the issue has effectively been fixed, just not
quite in the way the bug describes (a warning is no longer required, but
that's because the underlying issue is no longer present).
** Changed in: bluez (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922792
Title:
Bluez should notify users when they need to reboot to apply changes on
Raspberry Pi
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1922792/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
