On Wed, 2013-12-11 at 15:13 -0500, Brian J. Murrell wrote: > On Wed, 2013-12-11 at 21:25 +0200, Johan Hedberg wrote: > > Hi Brian, > > Hi Johan, > > > I'm not sure if I'm interpreting this right, but it seems the device is > > in HID mode and not HCI (normal Bluetooth) mode? > > I dunno. I'm just the user. :-) > > > Have you tried running > > the hid2hci tool (part of BlueZ)? > > Not yet. It wasn't installed by default on F20. When I did though, > things went much better: > > $ bluetoothctl > [NEW] Controller 00:02:72:1E:E0:12 pc.interlinx.bc.ca-0 [default] > [NEW] Device 00:0D:E6:68:B4:6F Samsung WEP850 > [NEW] Device 70:F3:95:3E:92:34 brian-laptop > [NEW] Device 7C:1E:52:6E:59:D2 Microsoft Sculpt Touch Mouse <snip> > So it looks like it's a gnome bluetooth-wizard problem. I will raise > some tickets. I don't see why it would be a problem in the wizard. You basically didn't have a Bluetooth adapter before you installed bluez-hid2hci. > > Maybe that was somehow auto-run with > > your previous installation? > > I don't really know. It was F19. And that means bluez4. So I guess > this is going to be a transition issue/bug I need to raise on F20. bluez-hid2hci was already an optional package in F19. -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
