Does the keyboard need to be in pairing mode to connect (vs actually pair?). It seemed to help me today, but I had thought that when I first reported this bug I had also tried putting it in pairing mode.
Without the keyboard in pairing mode: bluetoothd[4848]: src/device.c:connect_profiles() /org/bluez/hci0/dev_08_73_00_13_CC_45 (all), client :1.147 bluetoothd[4848]: profiles/input/device.c:input_device_connect() bluetoothd[4848]: Can't get HIDP connection info bluetoothd[4848]: src/service.c:change_state() 0x556055ffed90: device 08:73:00:13:CC:45 profile input-hid state changed: disconnected -> connecting (0) bluetoothd[4848]: src/adapter.c:connect_failed_callback() hci0 08:73:00:13:CC:45 status 4 bluetoothd[4848]: plugins/policy.c:conn_fail_cb() status 4 bluetoothd[4848]: src/adapter.c:bonding_attempt_complete() hci0 bdaddr 08:73:00:13:CC:45 type 0 status 0x4 bluetoothd[4848]: src/device.c:device_bonding_complete() bonding (nil) status 0x04 bluetoothd[4848]: src/device.c:device_bonding_failed() status 4 bluetoothd[4848]: src/adapter.c:resume_discovery() bluetoothd[4848]: connect error: Host is down (112) bluetoothd[4848]: src/service.c:change_state() 0x556055ffed90: device 08:73:00:13:CC:45 profile input-hid state changed: connecting -> disconnected (-5) bluetoothd[4848]: src/device.c:device_profile_connected() input-hid Input/output error (5) bluetoothd[4848]: src/device.c:device_profile_connected() returning response to :1.147 With the device in pairing mode (it connected! Yay! But now it appears paired and connected, but won't actually type any letters in... so something is still wrong): bluetoothd[4848]: src/device.c:connect_profiles() /org/bluez/hci0/dev_08_73_00_13_CC_45 (all), client :1.147 bluetoothd[4848]: profiles/input/device.c:input_device_connect() bluetoothd[4848]: Can't get HIDP connection info bluetoothd[4848]: src/service.c:change_state() 0x556055ffed90: device 08:73:00:13:CC:45 profile input-hid state changed: disconnected -> connecting (0) bluetoothd[4848]: src/adapter.c:connected_callback() hci0 device 08:73:00:13:CC:45 connected eir_len 17 bluetoothd[4848]: src/service.c:change_state() 0x556055ffed90: device 08:73:00:13:CC:45 profile input-hid state changed: connecting -> connected (0) bluetoothd[4848]: src/device.c:device_profile_connected() input-hid Success (0) bluetoothd[4848]: src/device.c:device_profile_connected() returning response to :1.147 bluetoothd[4848]: src/service.c:btd_service_ref() 0x556055ffed90: ref=3 bluetoothd[4848]: plugins/policy.c:service_cb() Added input-hid reconnect 0 bluetoothd[4848]: src/adapter.c:bonding_attempt_complete() hci0 bdaddr 08:73:00:13:CC:45 type 0 status 0x5 bluetoothd[4848]: src/device.c:device_bonding_complete() bonding (nil) status 0x05 bluetoothd[4848]: src/device.c:device_bonding_failed() status 5 bluetoothd[4848]: src/adapter.c:resume_discovery() bluetoothd[4848]: src/device.c:search_cb() 08:73:00:13:CC:45: No service update bluetoothd[4848]: src/device.c:device_svc_resolved() /org/bluez/hci0/dev_08_73_00_13_CC_45 err 0 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1492441 Title: Cannot connect to 1byone bluetooth keyboard (after successfully pairing) Status in bluez package in Ubuntu: New Bug description: I own a 1byone bluetooth keyboard/touchpad combo device. I'm using wily. I have managed to successfully pair it (the UI did not work for this -- bug 1492443). But doing it via the console did pair it: $ bluetoothctl [NEW] Device 08:73:00:13:CC:45 1byone Keyboard [bluetooth]# agent on Agent registered [bluetooth]# default-agent Default agent request successful [bluetooth]# pair 08:73:00:13:CC:45 Attempting to pair with 08:73:00:13:CC:45 [CHG] Device 08:73:00:13:CC:45 Connected: yes [agent] PIN code: 420005 [CHG] Device 08:73:00:13:CC:45 Modalias: usb:v04E8p7021d011B [CHG] Device 08:73:00:13:CC:45 UUIDs: 00001000-0000-1000-8000-00805f9b34fb [CHG] Device 08:73:00:13:CC:45 UUIDs: 00001124-0000-1000-8000-00805f9b34fb [CHG] Device 08:73:00:13:CC:45 UUIDs: 00001200-0000-1000-8000-00805f9b34fb [CHG] Device 08:73:00:13:CC:45 Paired: yes Pairing successful [CHG] Device 08:73:00:13:CC:45 Connected: no [CHG] Device 60:03:08:C9:C0:87 RSSI: -59 [CHG] Device 60:03:08:C9:C0:87 RSSI: -48 [CHG] Device 60:03:08:C9:C0:87 RSSI: -60 [CHG] Device 60:03:08:C9:C0:87 RSSI: -48 etc, etc (kept outputting RSSI bits every now and then) OK. So it paired. (which means it's not bug 1490347) But now I can't connect. You can see above that it says "Connected: no". If I go to the Bluetooth panel in System Settings, its "Connection" switch is set to Off and disabled. But it otherwise seems to be successfully paired. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3 Uname: Linux 4.1.0-3-generic x86_64 ApportVersion: 2.18-0ubuntu9 Architecture: amd64 CurrentDesktop: Unity Date: Fri Sep 4 15:16:58 2015 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20120703-2 EcryptfsInUse: Yes InstallationDate: Installed on 2013-01-09 (967 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20120703-15:08 InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Dell System XPS L322X ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.1.0-3-generic root=UUID=0719ea95-7c02-4d0a-a969-1ba285c420f2 ro quiet splash vt.handoff=7 SourcePackage: bluez SystemImageInfo: current build number: 0 device name: channel: daily last update: Unknown UpgradeStatus: Upgraded to wily on 2013-01-31 (945 days ago) dmi.bios.date: 12/03/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0CK86J dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA06:bd12/03/2012:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0CK86J:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L322X dmi.sys.vendor: Dell Inc. hciconfig: hci0: Type: BR/EDR Bus: USB BD Address: C4:85:08:FB:58:0A ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:19494 acl:0 sco:0 events:721 errors:0 TX bytes:3449 acl:0 sco:0 commands:234 errors:1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1492441/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp