I can also confirm this for 16.04. I note a very similar error in the syslog:
May 28 17:34:58 afforess-pc pulseaudio[2004]: [pulseaudio] module-bluez5-device.c: Default profile not connected, selecting off profile
May 28 17:35:00 afforess-pc bluetoothd[1009]: /org/bluez/hci0/dev_20_9B_A5_5D_BB_30/fd2: fd(31) ready
May 28 17:35:00 afforess-pc pulseaudio[2004]: [pulseaudio] bluez5-util.c: Transport TryAcquire() failed for transport /org/bluez/hci0/dev_20_9B_A5_5D_BB_30/fd2 (Operation Not Authorized)
May 28 17:35:00 afforess-pc kernel: [91164.555960] input: 20:9B:A5:5D:BB:30 as /devices/virtual/input/input27
I did some digging at one point, and the error from bluez5 seems to originate from DBus, and may be a permissions issue with the bluetooth DBus configuration or pulseaudio DBus configuration.
The workaround suggested by Con Kolivas works, but is very annoying.
I can also confirm this for 16.04. I note a very similar error in the syslog:
May 28 17:34:58 afforess-pc pulseaudio[2004]: [pulseaudio] module- bluez5- device. c: Default profile not connected, selecting off profile hci0/dev_ 20_9B_A5_ 5D_BB_30/ fd2: fd(31) ready hci0/dev_ 20_9B_A5_ 5D_BB_30/ fd2 (Operation Not Authorized) virtual/ input/input27
May 28 17:35:00 afforess-pc bluetoothd[1009]: /org/bluez/
May 28 17:35:00 afforess-pc pulseaudio[2004]: [pulseaudio] bluez5-util.c: Transport TryAcquire() failed for transport /org/bluez/
May 28 17:35:00 afforess-pc kernel: [91164.555960] input: 20:9B:A5:5D:BB:30 as /devices/
I did some digging at one point, and the error from bluez5 seems to originate from DBus, and may be a permissions issue with the bluetooth DBus configuration or pulseaudio DBus configuration.
The workaround suggested by Con Kolivas works, but is very annoying.