Using the bluez v5.37-1 on the Intel NUC running UC 16. I sideloaded the snap with --devmode and all appears to work fine. I can sudo "bluez.bluetoothctl " and interact with the controller including pairing devices.
The problem I disovered is that if I do not "*sudo*" bluetoothctl, then I cannot enter anything in the command interface... no keyboard input. I can ctrl-c out, but cannot provide any command input to bluetoothctl.
From Simon:
(1) This isn't a bug but intended. As the user situation on snappy is unclear and the ubuntu user will be removed soon we disabled the capability within the bluez interface that a normal user can talk with the bluetoothd daemon over dbus. You have to be root for now but that is
the case for all snaps on a real Ubuntu Core situation. The situation on the desktop with the bluez interface is a bit different though.
(2) Report a bug to make it more visible to the user that he has to use sudo in order to use the bluetoothctl command. We have a small wrapper script around bluetoothctl which we can adjust to
check for the UID of root and if not error out with a proper message pointing the user to use sudo or run as root.
https:/
https:/