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 Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1922792
Title:
Bluez should notify users when they need to reboot to apply changes on
Raspberry Pi
Status in bluez package in Ubuntu:
Fix Released
Status in bluez package in Debian:
New
Bug description:
In the case of upgrading or installing bluez for the first time on
certain raspberry pi devices, a reboot may be required to apply the
changes. We should add a check for this scenario in the postinst
script.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1922792/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
