New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 661112 link

Starred by 6 users
Status: Duplicate
Owner:
█ mcchou@chromium.org
Last visit > 30 days ago
Closed: Nov 2016
Cc:
fukino@chromium.org
r...@chromium.org
█ mcchou@chromium.org
█ tdander...@chromium.org
sgabr...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Discovering Bluetooth devices doesn't work on ToT.

Project Member Reported by fukino@chromium.org, Nov 1 2016 
Google Chrome: Canary 56.0.2905.0 (Official Build) canary (64-bit)
PLatform: 8947.0.0 (Official Build) canary-channel samus, chell

What steps will reproduce the problem?
(1) In chrome://settings, make sure to "Enable bluetooth" is checked.
(2) Open "Add Bluetooth device" dialog by clicking "Add a device".
  => (issue 1) Immediately "Device scan stopped." is shown and no device is listed.
(3) From system tray, click "Bluetooth enabled" to open BT device list.
  => ( issue 2 ) The BT list in system tray and in settings flickered, and they disappeared.

You can see the video at https://goo.gl/photos/27R5jTCgEQzLPCmj6.

Comment 1 by fukino@chromium.org, Nov 1 2016 

PLatform: 8940.0.0 doesn't have this issue.
This seems to be a recent regression.

Comment 2 by jbanavatu@chromium.org, Nov 1 2016 

Issue is also seen in latest ToT 56.0.2905.0/8952.0.0 dev channel falco, glimmer and spring.

Comment 3 by fukino@chromium.org, Nov 1 2016 

Pushing the latest Chrome on Platform 8952.0.0 reproduces the issue.
Pushing the latest Chrome on Platform 8940.0.0 doesn't reproduces the issue.
It seems this is caused by a change in Platform side (not Chrome).

Comment 4 by ortuno@chromium.org, Nov 1 2016

Cc: mcchou@chromium.org st...@chromium.org

Comment 5 by st...@chromium.org, Nov 1 2016

Owner: mcchou@chromium.org
Status: Assigned (was: Available)
Miao, could this be related to the BlueZ uprev? assigning to you tentatively.

Comment 6 by rvdp...@vitachrome.nl, Nov 4 2016 

Also have this issue with 56.0.2908.0
Bluetooth keeps flipping on off when scanning.

Comment 8 by gkihumba@google.com, Nov 9 2016 

mcchou@: any updates?

Comment 9 by mcchou@chromium.org, Nov 9 2016 

This issue is caused by the BlueZ uprev which landed in build 8945.0.0. The fixed has landed few days ago (see https://bugs.chromium.org/p/chromium/issues/detail?id=662144), so builds start from 8970 should be fine. I will merge this into issue 662144. Feel free to reopen this if you still see this issue with the latest build. Thanks.

Comment 10 by mcchou@chromium.org, Nov 9 2016

Mergedinto: 662144
Status: Duplicate (was: Assigned)

Comment 11 by mcchou@chromium.org, Nov 9 2016 

To correct comment #9, builds starting from 8972 should be fine, since https://chromium-review.googlesource.com/#/c/407861/ lands at 8972.0.0.

Comment 12 by rvdp...@vitachrome.nl, Nov 15 2016 

8986.0.0 seems to partially solve the issue, Bluetooth is available and functioning again, only for a few hours, then Bluetooth goes of again, or disappears completely.

Comment 13 by st...@chromium.org, Mar 3 2017

Cc: r...@chromium.org

Comment 14 by st...@chromium.org, Mar 3 2017

Cc: -st...@chromium.org
►

Sign in to add a comment