This is not really a bug, or it may be a different sort of bug.
Apple firmware simulates the BT keyboard/mouse as USB devices; these are then available after booting Ubuntu through the USB-HID interface (they're listed when running the "sudo lsusb -v" command). Unfortunately, not all functionality is available this way: the fn-key on the keyboard; the scroll ball on the mouse.
In order for them to be treated as Bluetooth devices you must first reset them with the command
$ sudo hciconfig hci0 reset
then (with a temporary USB keyboard/mouse attached) activate the Bluetooth applet and let the BT keyboard/mouse be discovered and paired. Keyboard fn-key and mouse scroll ball are now working, and the "sudo lsusb -v" command does no longer list these devices.
Unfortunately, these BT pairings do not survive a reboot, not even when the line
options hci_usb reset=1
is added to a file like /etc/modprobe.d/options.conf. That would be the real bug...
This is not really a bug, or it may be a different sort of bug.
Apple firmware simulates the BT keyboard/mouse as USB devices; these are then available after booting Ubuntu through the USB-HID interface (they're listed when running the "sudo lsusb -v" command). Unfortunately, not all functionality is available this way: the fn-key on the keyboard; the scroll ball on the mouse.
In order for them to be treated as Bluetooth devices you must first reset them with the command
$ sudo hciconfig hci0 reset
then (with a temporary USB keyboard/mouse attached) activate the Bluetooth applet and let the BT keyboard/mouse be discovered and paired. Keyboard fn-key and mouse scroll ball are now working, and the "sudo lsusb -v" command does no longer list these devices.
Unfortunately, these BT pairings do not survive a reboot, not even when the line
options hci_usb reset=1
is added to a file like /etc/modprobe. d/options. conf. That would be the real bug...