Bluetooth indicator comes back on reboot

Bug #1232828 reported by Omer Akram
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Bluez Utilities
indicator-bluetooth (Ubuntu)
Fix Released

Bug Description

1. disable the bluetooth indicator by pulling out the menu, it will go away.
2. reboot the phone.

1. What happens:
The bluetooth indicator comes back

What should happen:
If I disable the indicator it should really be disabled, reboot should not change that.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: indicator-bluetooth 0.0.6+13.10.20130924.2-0ubuntu1
Uname: Linux 3.4.0-3-mako armv7l
ApportVersion: 2.12.4-0ubuntu1
Architecture: armhf
Date: Sun Sep 29 17:24:44 2013
InstallationDate: Installed on 2013-09-27 (2 days ago)
InstallationMedia: Ubuntu Saucy Salamander (development branch) - armhf (20130927)
MarkForUpload: True
 PATH=(custom, no user)
SourcePackage: indicator-bluetooth
UpgradeStatus: No upgrade log present (probably fresh install)

Related branches

Revision history for this message
Omer Akram (om26er) wrote :
Omer Akram (om26er)
Changed in indicator-bluetooth:
importance: Undecided → Low
Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

confirmed with 20130929

Changed in indicator-bluetooth (Ubuntu):
status: New → Confirmed
Changed in indicator-bluetooth:
status: New → Confirmed
Omer Akram (om26er)
Changed in indicator-bluetooth:
assignee: nobody → Charles Kerr (charlesk)
Omer Akram (om26er)
tags: added: rls-t-incoming
tags: added: testcase
description: updated
Revision history for this message
Adrien Béraud (aberaud) wrote :

I think the real issue is not the indicator "coming back" but the bluetooth state being reset on reboot (the indicator should stay here and bluetooth be disabled on reboot if it was previously disabled).

This is a (quite serious) power management issue since bluetooth eat energy.

Revision history for this message
Charles Kerr (charlesk) wrote :

I've confirmed this is still the case on a 2013-12018 update before touching /userdata/.writable_image, but bluetooth stays off after the image becomes writable.

This sounds a little like bug #1230275; however, indicator-bluetooth no longer pokes /dev/rfkill directly. Instead, it just powers the default bluez adapter on/off via bluez' dbus API.

Is it possible that bluez is making changes that aren't getting saved due to permissions issues?

Revision history for this message
Charles Kerr (charlesk) wrote :

Reassigning to bluez as per cyphermox request

affects: indicator-bluetooth → bluez
Changed in bluez:
assignee: Charles Kerr (charlesk) → nobody
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package indicator-bluetooth - 0.0.6+14.04.20140207-0ubuntu2

indicator-bluetooth (0.0.6+14.04.20140207-0ubuntu2) trusty; urgency=medium

  * Toggle rfkill again so that we have a chance of persisting the bluetooth
    state across reboots. (LP: #1232828)
 -- Mathieu Trudel-Lapierre <email address hidden> Thu, 10 Apr 2014 15:38:13 -0400

Changed in indicator-bluetooth (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.