kernel-packages team mailing list archive

[Simon Fels <simon.busch@xxxxxxxxxxxxx>]

I went again through the logs and came across the following:

 [ 1044.196326] Bluetooth: SMP security requested but not available

which is then followed by a lot messages like:

 Jan 20 08:53:28 samsung930X3G bluetoothd[3988]: Report Map read failed: Attribute requires authentication before read/write
 Jan 20 08:53:28 samsung930X3G bluetoothd[3988]: Error reading Report value: Attribute requires authentication before read/write

What this basically means is that the security checks inside the kernel
stack failed and we couldn't build a secured and trusted connection
which then in the end means the mouse wont connect properly and fails to
work.

There is already an upstream bug about this problem at
https://bugzilla.kernel.org/show_bug.cgi?id=104011 sadly without an
solution other than reverting the change on the kernel side introduced
this problem.

@Pat: You're seeing this with your MX4 right? I will build a kernel then
for it which has the suggested kernel side change reverted just to see
if that helps us in this particular situation.

** Bug watch added: Linux Kernel Bug Tracker #104011
   http://bugzilla.kernel.org/show_bug.cgi?id=104011

** Tags added: bluez-touch

** Tags added: bluez-classic

-- 
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/1531925

Title:
  Can't connect Logitech Living Room Keyboard [LE]

Status in Canonical System Image:
  New
Status in bluez package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  New

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.

  It should be noted that LE keyboard support on touch should be a
  considered a missing feature.

  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