On Fri, 2013-12-13 at 14:17 -0200, Anderson Lizardo wrote: > Hi, > > On Fri, Dec 13, 2013 at 1:56 PM, Szymon Janc <szymon.janc@xxxxxxxxx> wrote: > >> [bluetooth]# connect 7C:1E:52:6E:59:D2 > >> Attempting to connect to 7C:1E:52:6E:59:D2 > >> Failed to connect: org.bluez.Error.NotReady > >> > >> I have this same problem with my previously paired headset also. Not > >> connected and won't connect. > > > > Is your adapter powered?:) > > I agree it looks like it's missing "power on" command on bluetoothctl > here Hrm. [bluetooth]# power on [CHG] Controller 00:02:72:1E:E0:12 Class: 0x0c0104 Changing power on succeeded [CHG] Controller 00:02:72:1E:E0:12 Powered: yes [CHG] Device 7C:1E:52:6E:59:D2 Connected: yes And now the mouse works. I wonder what happened in the first place to make it stop running. Certainly the unplugging/plugging in of the dongle might have been enough to need it powering on so it's not clear that it just spontaneously lost power or anything like that. > (assuming there is no UI applet running that should take care of > powering it up automatically.) Which is an interesting point. What is the UI applet for all of this supposed to be now in F20? b.
Attachment:
signature.asc
Description: This is a digitally signed message part
