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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1492441

Title:
  Cannot connect to 1byone bluetooth keyboard (after successfully
  pairing)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1492441/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to