** Description changed:
- Trying to pair this device and bluetoothd crashed on my Wily laptop and
- the N4 running latest proposed
+ Cannot connect a Logitech Illuminated Living Room keyboard to a device
+ running bluez5. There are two versions of the keyboard, a unifying
+ receiver version, and a Bluetooth version. The latter has a BT symbol
+ on the 'del' key. To put the BT version in pairing mode, power on the
+ keyboard, then briefly hold the FN and 'del' key together and release.
+ A green LED at the top right of the keyboard should start flashing
+ quickly.
- build number: 107
- device name: mako
- channel: ubuntu-touch/rc-proposed/ubuntu-pd
- last update: 2016-01-07 11:30:20
- version version: 107
- version ubuntu: 20160107
- version device: 20150911
- version custom: 20150929-2-vivid
+ Once in pairing mode, the device will become visible on desktop using
+ the BT settings UI, however it's *never* shown in the UI on a device
+ running the latest Touch ( OTA9.1+ ). Note, this includes devices
+ running a silo version of bluez 5.37, including both arale and krillin.
+ On both devices, the keyboard *is* viewable using bluetoothctl.
- The device is a Logitech Illuminated Living Room keyboard K830 (
- Bluetooth Smart version; !Unifying version ) with an integrated
- trackpad.
+ Here's the reported attributes of the device from my macair running
+ 15.10 + bluez 5.37:
- Device DF:08:A9:A0:13:91
- Name: K830
- Alias: K830
- Appearance: 0x03c1
- Icon: input-keyboard
- Paired: no
- Trusted: no
- Blocked: no
- Connected: no
- LegacyPairing: no
- UUID: Human Interface Device (00001812-0000-1000-8000-00805f9b34fb)
- RSSI: -43
+ Device DF:08:A9:A0:13:93
+ Name: K830
+ Alias: K830
+ Appearance: 0x03c1
+ Icon: input-keyboard
+ Paired: yes
+ Trusted: no
+ Blocked: no
+ Connected: yes
+ LegacyPairing: no
+ UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
+ UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
+ UUID: Device Information (0000180a-0000-1000-8000-00805f9b34fb)
+ UUID: Battery Service (0000180f-0000-1000-8000-00805f9b34fb)
+ UUID: Human Interface Device (00001812-0000-1000-8000-00805f9b34fb)
+ UUID: Vendor specific (00010000-0000-1000-8000-011f2000046d)
+ Modalias: usb:v046DpB335d0010
- The device would come and go in the devices list from bluetoothctl
- A manual scan would bring it back
- I then tried to manually pair and it failed with
- Failed to pair: org.freedesktop.DBus.Error.NoReply
+ From bluetoothctl on both my laptop and my desktop, I'm able to pair,
+ trust and connect the device, and info reflects these changes, however
+ the device never actually connects, it's LED remains blinking fast, and
+ the keyboard cannot be used.
- On the latop dmesg reports
- [357895.395029] traps: bluetoothd[790] general protection ip:56419e2c0306
sp:7ffefd2b6760 error:0 in bluetoothd[56419e217000+105000]
+ Note, before pairing, I issued the command 'agent KeyboardOnly' and
+ 'default-agent'.
** Also affects: canonical-devices-system-image
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1531925
Title:
Can't connect Logitech Living Room Keyboard [LE]
Status in Canonical System Image:
New
Status in bluez package in Ubuntu:
Confirmed
Bug description:
Cannot connect a Logitech Illuminated Living Room keyboard to a device
running bluez5. There are two versions of the keyboard, a unifying
receiver version, and a Bluetooth version. The latter has a BT symbol
on the 'del' key. To put the BT version in pairing mode, power on the
keyboard, then briefly hold the FN and 'del' key together and release.
A green LED at the top right of the keyboard should start flashing
quickly.
Once in pairing mode, the device will become visible on desktop using
the BT settings UI, however it's *never* shown in the UI on a device
running the latest Touch ( OTA9.1+ ). Note, this includes devices
running a silo version of bluez 5.37, including both arale and
krillin. On both devices, the keyboard *is* viewable using
bluetoothctl.
Here's the reported attributes of the device from my macair running
15.10 + bluez 5.37:
Device DF:08:A9:A0:13:93
Name: K830
Alias: K830
Appearance: 0x03c1
Icon: input-keyboard
Paired: yes
Trusted: no
Blocked: no
Connected: yes
LegacyPairing: no
UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
UUID: Device Information (0000180a-0000-1000-8000-00805f9b34fb)
UUID: Battery Service (0000180f-0000-1000-8000-00805f9b34fb)
UUID: Human Interface Device (00001812-0000-1000-8000-00805f9b34fb)
UUID: Vendor specific (00010000-0000-1000-8000-011f2000046d)
Modalias: usb:v046DpB335d0010
From bluetoothctl on both my laptop and my desktop, I'm able to pair,
trust and connect the device, and info reflects these changes, however
the device never actually connects, it's LED remains blinking fast,
and the keyboard cannot be used.
Note, before pairing, I issued the command 'agent KeyboardOnly' and
'default-agent'.
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1531925/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
