Bluetooth cannot be activated on several devices

Bug #1530807 reported by Dubstar_04 on 2016-01-04
78
This bug affects 14 people
Affects Status Importance Assigned to Milestone
Canonical Pocket Desktop
High
Unassigned
Canonical System Image
Critical
Alejandro J. Cura
The Avila project
Critical
Alejandro J. Cura
indicator-bluetooth (Ubuntu)
Critical
Unassigned
ubuntu-system-settings (Ubuntu)
Critical
Unassigned

Bug Description

Using RC proposed 04/01/2016 bluetooth cannot be enabled.

Tested on a nexus 7.

Expected behavior:
Bluetooth slider is moved to on
Bluetooth activates
Available devices appear in the list

Experienced behavior:
Bluetooth slider is moved to on
Activity spinners appear
Bluetooth slider moves to off.

Related branches

Marius Quabeck (marius.quabeck) wrote :

seems to be solved in the most recent update. I would love to add a log but i have no idea where i can find that. so heres just a screenshot of the devices showing up now

Dubstar_04 (dubstar-04) wrote :

Bluetooth on = not discoverable

Dubstar_04 (dubstar-04) wrote :

Bluetooth off = discoverable

Dubstar_04 (dubstar-04) wrote :

Bluetooth off = discoverable

Pat McGowan (pat-mcgowan) wrote :

The images show that in neither case is the Bluetooth indicator shown in the top panel

Changed in canonical-devices-system-image:
assignee: nobody → Alejandro J. Cura (alecu)
status: New → Confirmed
Pat McGowan (pat-mcgowan) wrote :

Cannot reproduce on any other devices, could be specific to the N7 or the current state of the specific device.

Charles Kerr (charlesk) on 2016-01-04
Changed in indicator-bluetooth (Ubuntu):
assignee: nobody → Charles Kerr (charlesk)
Randall Ross (randall) wrote :

I am (I think) able to observe the slider behaviour referenced in the
bug on my N7, running r329. My device initially discoverable, even when
the slider reverts to "off" by itself. Shortly after (maybe a few
minutes later), the N7 is no longer discoverable and turning the slider
back to "on" has no effect. And, if I wait a few more minutes, I can
once again make the device discoverable with the slider.

Checkbox output attached.

Dubstar_04 (dubstar-04) wrote :

I can confirm this affects rc proposed r332.

Dubstar_04 (dubstar-04) wrote :

Problem persists with r334

Dubstar_04 (dubstar-04) wrote :

I can confirm that the Nexus 4 isn't affected. Seems isolated to the Nexus 7.

Michael Zanetti (mzanetti) wrote :

some more information: Bluetooth only appears being off in the indicator and the settings. It is, in fact on and working just fine.

This screenshot was taken while a Bluetooth keyboard was connected and functional: http://i.imgur.com/EIUnG9n.png

Note the hciconfig output in the terminal. It shows that it is up and running, and even doing the inquiry as instructed by the systemsettings app. It's just that the app and indicator think its off.

Kugi Eusebio (kugi-igi) wrote :

I've experienced this before and was fixed I think when bluez5 landed.
However I experience it again sometimes in the recent rc-proposed images.
A couple of reboots fix the issue though.

Other users who experience the problem suggest that reboots fix the issue.
That doesn't seem to work for me.

It has been confirmed that bluetooth does work just the ui is broken so I
will try to connect a device using terminal.

Thanks,

Dan

On Tuesday, 12 January 2016 15:08:44 UTC, Kugi Eusebio wrote:
> I've experienced this before and was fixed I think when bluez5 landed.
> However I experience it again sometimes in the recent rc-proposed images.
> A couple of reboots fix the issue though.
>

--
Sent using Dekko from my Ubuntu device

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in indicator-bluetooth (Ubuntu):
status: New → Confirmed
Randall Ross (randall) wrote :

Adding my experience to comment #12, reboots will sometimes fix the issue, but anecdotally I'd estimate the frequency at 10%. (i.e. one in ten reboots clears it.)

kevin gunn (kgunn72) on 2016-01-12
Changed in indicator-bluetooth (Ubuntu):
importance: Undecided → High
Changed in canonical-pocket-desktop:
importance: Undecided → High
Changed in canonical-devices-system-image:
importance: Undecided → High
kevin gunn (kgunn72) wrote :

fwiw, my current workflow to workaround this is to log onto the device shell and "restart indicator-bluetooth"
the list of available devices always instantly appears.

Charles Kerr (charlesk) wrote :

I'm seeing similar buggy behavior with the indicator on a Xenial desktop with bluez 5.36 and indicator-bluetooth 0.0.6+15.10.20150929-0ubuntu1 installed.

summary: - Bluetooth cannot be activated.
+ Bluetooth cannot be activated on Nexus 7

Pat, this problem also affects the nexus 4 I believe.

Víctor R. Ruiz (vrruiz) wrote :

I confirm that this bug also happens in mako.

current build number: 355
device name: mako
channel: ubuntu-touch/rc-proposed/ubuntu

Stephen M. Webb (bregma) wrote :

Definitely happens on mako using the -pd image (r127) which renders it completely useless as a -pd image.

Changed in canonical-pocket-desktop:
status: New → Confirmed
summary: - Bluetooth cannot be activated on Nexus 7
+ Bluetooth cannot be activated on several devices
Changed in avila:
status: New → Confirmed
importance: Undecided → Critical
milestone: none → ww06-2016
Changed in canonical-devices-system-image:
milestone: none → ww08-2016
John McAleely (john.mcaleely) wrote :

This also occurs on frieza, OEM bug: #1534318

Changed in canonical-devices-system-image:
importance: High → Critical
John McAleely (john.mcaleely) wrote :

Additional OEM bug that's probably a dupe: bug #1544084

Changed in indicator-bluetooth (Ubuntu):
importance: High → Critical
Dave Morley (davmor2) on 2016-02-12
tags: added: qa-frieza
Changed in avila:
assignee: nobody → Alejandro J. Cura (alecu)
Changed in canonical-devices-system-image:
milestone: ww08-2016 → ww04-2016
Changed in avila:
milestone: ww06-2016 → ww04-2016
Changed in indicator-bluetooth (Ubuntu):
status: Confirmed → In Progress
Charles Kerr (charlesk) wrote :

I think there is an indicator-datetime issue herer wrt the on/off toggle in the indicator, but there is also a separate issue with the Discoverable / Not Discoverable status being shown in system-settings. indicator-bluetooth doesn't advertise that state; system-settings is getting that from talking to bluez.

Changed in ubuntu-system-settings (Ubuntu):
status: New → Confirmed
importance: Undecided → Critical
Changed in avila:
status: Confirmed → In Progress
Alejandro J. Cura (alecu) wrote :

My bq 4.5 does not seem to have this problem in normal usage, so here's how I managed to reproduce it:

1) disable autostart of the bluetooth daemon:
$ echo "manual" | sudo tee /etc/init/bluetooth.override

2) reboot your phone

3) wait until everything is loaded, then run:
$ sudo start bluetooth

After that, the on/off switch in indicator and system settings don't seem to match each other, just like described above in the bug.
Also, the bluetooth connection seems to be independent of changes to the switches, since it keeps being discoverable for other devices even any or both of those switches are off.

Simon Fels (morphis) wrote :

BlueZ will react either on the "Powered" property of its org.bluez.Adapter1 interface being switch (false/true) or the bluetooth rfkill being changed. If none of both happen the Bluetooth power status will not change and the device will be kept discoverable if the "Discoverable" property was set to true from settings.

John McAleely (john.mcaleely) wrote :

Is the linked branch believed to be a fix, or simply part of the puzzle?

John McAleely (john.mcaleely) wrote :

This in silo 79

John McAleely (john.mcaleely) wrote :

(which worked for me on my frieza device -and seems to fix this bug)

Changed in avila:
milestone: ww04-2016 → ww06-2016
Changed in canonical-devices-system-image:
status: Confirmed → Fix Committed

Maybe some of the issues here are a duplicate of bug #1546137 ?

summary: - Bluetooth cannot be activated on several devices
+ [FHD] Bluetooth cannot be activated on several devices

Hi all;

This issue is still reproducible in r6 firmware version, I attached a new record with the actual result.

Please, check it.

Thank you.

Jason Yen (jasonyen) on 2016-03-16
Changed in avila:
milestone: backlog → ww10-2016
Jason Yen (jasonyen) on 2016-04-07
Changed in avila:
status: In Progress → Fix Committed
Charles Kerr (charlesk) on 2016-04-26
Changed in indicator-bluetooth (Ubuntu):
status: In Progress → Confirmed
Noemí (noemi-gallego) on 2016-05-30
summary: - [FHD] Bluetooth cannot be activated on several devices
+ Bluetooth cannot be activated on several devices
Jose Ferrera (jose-ferrera) wrote :

Hello all,

 Using ths DUT at least 20 minutes, then trying to turn on the BT. DUT cannot turning on by itself, user need to reboot the DUT to be able to connect any BT device.

Fw: Ubuntu 15.04 (r10)

John McAleely (john.mcaleely) wrote :

I think it will be helpful to have a short new bug for this discussion, so I've opened: bug #1587366. Please continue the discussion there.

Changed in indicator-bluetooth (Ubuntu):
status: Confirmed → Fix Committed
Changed in canonical-pocket-desktop:
status: Confirmed → Fix Committed
Charles Kerr (charlesk) wrote :

Reopening for workitem found by dobey to see if https://code.launchpad.net/~morphis/indicator-bluetooth/fix-lp1530807/+merge/290022 should still be landed

Changed in indicator-bluetooth (Ubuntu):
assignee: Charles Kerr (charlesk) → Rodney Dawes (dobey)
status: Fix Committed → Triaged
dobey (dobey) on 2017-04-24
Changed in indicator-bluetooth (Ubuntu):
assignee: Rodney Dawes (dobey) → nobody
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers