Re: Issue 483275 in chromium: No HID Notification retry after authentication when registration failed

[chro...@googlecode.com]

Updates:
Labels: -Week-1518 Week-1519

Comment #3 on issue 483275 by armans...@chromium.org: No HID Notification
retry after authentication when registration failed
https://code.google.com/p/chromium/issues/detail?id=483275

(No comment was entered for this change.)

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[chro...@googlecode.com]

Comment #7 on issue 483275 by armans...@chromium.org: No HID Notification

retry after authentication when registration failed
https://code.google.com/p/chromium/issues/detail?id=483275

jdufault@: Can you attach system logs, preferably with bluetoothd running
in verbose mode (pass --debug to the command line in the upstart script
/etc/init/bluetoothd.conf)?

[chro...@googlecode.com]

Comment #15 on issue 483275 by ethan...@intel.com: No HID Notification

retry after authentication when registration failed
https://code.google.com/p/chromium/issues/detail?id=483275

From issue description, it's similar
to "https://code.google.com/p/chromium/issues/detail?id=488630". This HID
no function after paring after Bluez stack upgrading.

[chro...@googlecode.com]

Updates:
Labels: M-45

Comment #16 on issue 483275 by dsunk...@chromium.org: No HID Notification

retry after authentication when registration failed
https://code.google.com/p/chromium/issues/detail?id=483275

Issue still exists. 7204.0.0

[chro...@googlecode.com]

Updates:
Labels: -M-43

Comment #17 on issue 483275 by caitlinj...@chromium.org: No HID

Notification retry after authentication when registration failed
https://code.google.com/p/chromium/issues/detail?id=483275

Arman will look at this with new BlueZ patches this week.

[chro...@googlecode.com]

Updates:
Status: Untriaged
Owner: ---
Labels: -M-45

Comment #25 on issue 483275 by kathrelk...@chromium.org: No HID

Notification retry after authentication when registration failed
https://code.google.com/p/chromium/issues/detail?id=483275

(No comment was entered for this change.)

[chro...@googlecode.com]

Updates:
Cc: -dsunk...@chromium.org albe...@chromium.org

Comment #26 on issue 483275 by kathrelk...@chromium.org: No HID

Notification retry after authentication when registration failed
https://code.google.com/p/chromium/issues/detail?id=483275

Bluetooth LE keyboards don't work on ChromeOS right now. Who is a good
owner for this bug?

[chro...@googlecode.com]

Comment #27 on issue 483275 by myle...@chromium.org: No HID Notification

retry after authentication when registration failed
https://code.google.com/p/chromium/issues/detail?id=483275

It's not consistently broken for me.

snippet from /var/log/messages for the failing case:
2016-01-25T13:03:33.283610-08:00 NOTICE dbus[1000]: [system] Rejected send
message, 3 matched rules; type="method_return", sender=":1.6" (uid=1000
pid=1807 comm="/opt/google/chrome/chrome --ppapi-flash-path=/opt/")
interface="(unset)" member="(unset)" error name="(unset)"
requested_reply="0" destination=":1.16" (uid=218 pid=3699
comm="/usr/libexec/bluetooth/bluetoothd --nodetach ")
2016-01-25T13:03:40.302188-08:00 ERR bluetoothd[3699]: Report Map read
failed: Attribute requires authentication before read/write
2016-01-25T13:03:40.437048-08:00 ERR bluetoothd[3699]: Protocol Mode
characteristic read failed: Attribute requires authentication before
read/write
2016-01-25T13:03:40.572956-08:00 ERR bluetoothd[3699]: HID Information read
failed: Attribute requires authentication before read/write
2016-01-25T13:03:40.707942-08:00 ERR bluetoothd[3699]: Read Report
Reference descriptor failed: Attribute requires authentication before
read/write

snippet for the working case:
2016-01-25T13:07:49.834627-08:00 NOTICE dbus[1000]: [system] Rejected send
message, 3 matched rules; type="method_return", sender=":1.6" (uid=1000
pid=1807 comm="/opt/google/chrome/chrome --ppapi-flash-path=/opt/")
interface="(unset)" member="(unset)" error name="(unset)"
requested_reply="0" destination=":1.16" (uid=218 pid=3699
comm="/usr/libexec/bluetooth/bluetoothd --nodetach ")
2016-01-25T13:07:58.155766-08:00 INFO kernel: [ 338.028729] input: Pixel C
Keyboard as /devices/virtual/misc/uhid/input13
2016-01-25T13:07:58.155792-08:00 INFO kernel: [ 338.028983] hid-generic
0005:18D1:5018.0001: input,hidraw0: BLUETOOTH HID v0.01 Keyboard [Pixel C
Keyboard] on B0:10:41:2B:B3:6E

[chro...@googlecode.com]

Comment #28 on issue 483275 by pbath...@chromium.org: No HID Notification

retry after authentication when registration failed
https://code.google.com/p/chromium/issues/detail?id=483275

#27-- Could you let us know what build you are using?

[chro...@googlecode.com]

Comment #29 on issue 483275 by myle...@chromium.org: No HID Notification

retry after authentication when registration failed
https://code.google.com/p/chromium/issues/detail?id=483275

I tried 47 (Stable) and 49 (dev channel). I haven't tried 50 yet. I
posted the log snippets to see if we were talking about the same failure
mode.

[chro...@googlecode.com]

Comment #30 on issue 483275 by kathrelk...@chromium.org: No HID

Notification retry after authentication when registration failed
https://code.google.com/p/chromium/issues/detail?id=483275

let us know what M50 looks like for you. We've found that the bluez update
has fixed the behavior of several of our BLe keyboards, including those
used on our end to repro this bug.

[chro...@googlecode.com]

Updates:
Cc: joseph...@chromium.org

Comment #31 on issue 483275 by joseph...@chromium.org: No HID Notification

retry after authentication when registration failed
https://code.google.com/p/chromium/issues/detail?id=483275

I saw this issue too:

CHROMEOS_RELEASE_CHROME_MILESTONE=50
CHROMEOS_RELEASE_DESCRIPTION=7867.0.0 (Official Build) dev-channel monroe
test

The keyboard I used is Microsoft Universal Foldable Keyboard.

A snippet of /var/log/messages as follows:

2016-01-28T06:47:24.404767+00:00 WARNING bluetoothd[1103]: No cache for
CD:96:1C:EF:09:39
2016-01-28T06:47:24.405504+00:00 ERR kernel: [ 51.270203] Bluetooth: hci0
unexpected SMP command 0x0b from cd:96:1c:ef:09:39
2016-01-28T06:47:24.533004+00:00 NOTICE dbus[269]: [system] Rejected send
message, 3 matched rules; type="method_return", sender=":1.32" (uid=1000
pid=6819 comm="/opt/google/chrome/chrome --enable-prefixed-encryp")

interface="(unset)" member="(unset)" error name="(unset)"

requested_reply="0" destination=":1.18" (uid=218 pid=1103
comm="/usr/libexec/bluetooth/bluetoothd --nodetach ")

2016-01-28T06:47:31.431886+00:00 ERR bluetoothd[1103]: Report Map read

failed: Attribute requires authentication before read/write

2016-01-28T06:47:31.611868+00:00 ERR bluetoothd[1103]: Protocol Mode

characteristic read failed: Attribute requires authentication before
read/write

2016-01-28T06:47:31.641869+00:00 ERR bluetoothd[1103]: HID Information read

failed: Attribute requires authentication before read/write

[chro...@googlecode.com]

Comment #32 on issue 483275 by joseph...@chromium.org: No HID Notification

retry after authentication when registration failed
https://code.google.com/p/chromium/issues/detail?id=483275

Continued from Comment#31:

The keyboard got registered as an input device after 10 mins as follows:

2016-01-28T06:57:41.845621+00:00 INFO kernel: [ 668.607218] input:
UniversalFoldableKb as /devices/virtual/misc/uhid/input9
2016-01-28T06:57:41.846587+00:00 INFO kernel: [ 668.608389] hid-generic
0005:045E:080C.0003: input,hidraw2: BLUETOOTH HID v1.10 Keyboard
[UniversalFoldableKb] on B8:EE:65:42:76:D0


This problem happens on some keyboards. For some other keyboards, such as
Samsung Bluetooth Keyboard EE-BT550, it pairs, connects, and registers as
an input device without any problem every time I try it.