On 29/05/14 06:28, Mick wrote: > On Wednesday 28 May 2014 20:02:29 Samuli Suominen wrote: >> On 28/05/14 21:42, Mick wrote: >>> Hmm ... am I alone in this quest? >> >> See here, http://bugs.gentoo.org/show_bug.cgi?id=505362 > > Thanks! I missed this bug when I glanced earlier. However, it does not > mention rfcomm is now missing, or the fact that the gentoo rc script fails to > initialise bluethooth and complains about rfcomm service not having > started/exist, or that bluetoothctl now does not work at all. Is all this > down to a missing udev rule? >
No its the fact that bluez 5 has been redesigned to fit in more with the systemd world. it works if: remove rfcomm using rc-update /etc/init.d/bluetoothctl restart (get rid of any existing config) bluetoothctl power on scan on agent on default-agent trust [MAC ADDRESS OF CLIENT] pair [MAC ADDRESS OF CLIENT] enter PIN when requested wait for "Connected: no" exit After this you should have an rfcomm channel available to the client. I have the above in an expect script as bluetoothctl has no inate remote controllability capabilities. No separate pairing app or rfcomm init script needed. BillK
