bluetooth settings not remembered on reboot

[Jobin Raju George]

[ The bug ]
Bluetooth always remains "on" when I boot ubuntu, though it switches off when I switch it off. However, if I switch bluetooth off, in the next boot, it will be "on".

[ How to reproduce ]
Reboot ubuntu. The bluetooth will be "on". Switch it off manually using the bluetooth icon on the status menu indicator- it switches off. Now reboot ubuntu- bluetooth will be on.

[ What did I expect to happen ]
Bluetooth will remember whether it was on or off in the previous boot.

[ What actually happened ]
Bluetooth switches off if manually switched off. However, it remains "on" on each reboot.

[ Environment ]
lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu Trusty Tahr (development branch)
Release: 14.04
Codename: trusty

 apt-cache policy gnome-bluetooth
gnome-bluetooth:
  Installed: 3.8.2.1-0ubuntu4
  Candidate: 3.8.2.1-0ubuntu4
  Version table:
 *** 3.8.2.1-0ubuntu4 0
        500 http://in.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
        100 /var/lib/dpkg/status
---
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
DistroRelease: Ubuntu 14.04
InstallationDate: Installed on 2014-03-17 (8 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140316)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: Hewlett-Packard HP 630 Notebook PC
Package: bluez 4.101-0ubuntu10
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-19-generic root=UUID=e65dde38-8db3-4375-af07-da5265597b0a ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.13.0-19.39-generic 3.13.6
Tags: trusty
Uname: Linux 3.13.0-19-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip kvm libvirtd lpadmin plugdev sambashare sudo www-data
_MarkForUpload: True
dmi.bios.date: 07/22/2011
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.1A
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 3672
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 23.24
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnHewlett-Packard:bvrF.1A:bd07/22/2011:svnHewlett-Packard:pnHP630NotebookPC:pvr058A100000004C10002600000:rvnHewlett-Packard:rn3672:rvr23.24:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP 630 Notebook PC
dmi.product.version: 058A100000004C10002600000
dmi.sys.vendor: Hewlett-Packard
hciconfig:
 hci0: Type: BR/EDR Bus: USB
  BD Address: D0:DF:9A:9F:A1:9A ACL MTU: 1022:8 SCO MTU: 121:3
  DOWN
  RX bytes:505 acl:0 sco:0 events:23 errors:0
  TX bytes:329 acl:0 sco:0 commands:22 errors:0

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1296554/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Jobin Raju George (jobin-rv)]

specified package name

[Mathieu Trudel-Lapierre (cyphermox)]

Thanks for filing this bug. Unfortunately, in the current state that it is, it's a little be difficult to figure out exactly what's up.

Could you please run the following command on your system after reproducing the issue?

apport-collect 1296554

Also, could you tell us more about exactly how you switch bluetooth off? Are you doing this via the indicator or via some button on your keyboard or a switch on your computer?

Thanks!

[Jobin Raju George (jobin-rv)]

apport information

[Jobin Raju George (jobin-rv)]

apport information

[Jobin Raju George (jobin-rv)]

apport information

[Jobin Raju George (jobin-rv)]

apport information

[Jobin Raju George (jobin-rv)]

apport information

[Jobin Raju George (jobin-rv)]

apport information

[Jobin Raju George (jobin-rv)]

apport information

[Jobin Raju George (jobin-rv)]

apport information

[Jobin Raju George (jobin-rv)]

apport information

[Jobin Raju George (jobin-rv)]

apport information

[Jobin Raju George (jobin-rv)]

apport information

[Jobin Raju George (jobin-rv)]

apport information

[Jobin Raju George (jobin-rv)]

apport information

[Jobin Raju George (jobin-rv)]

apport information

[Jobin Raju George (jobin-rv)]

Running

apport-collect 1296554

asks me to install bluez-hcidum, which I did. But then it asked me to run

sudo hcidump -XYt > $HOME/hci.log

and reproduce the bug which I can't since I'll have to reboot.

[Jobin Raju George (jobin-rv)]

I can confirm that this bug persists on linux kernel version 3.14.0-031400rc8-generic.

[ Steps taken to confirm the bug persist on 3.14 ]
1) Downloaded linux-headers from http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.14-rc8-trusty/linux-headers-3.14.0-031400rc8-generic_3.14.0-031400rc8.201403242335_amd64.deb

and linux-image from http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.14-rc8-trusty/linux-image-3.14.0-031400rc8-generic_3.14.0-031400rc8.201403242335_amd64.deb

2) Installed linux-image using

sudo dpkg -i linux-image-3.14.0-031400rc8-generic_3.14.0-031400rc8.201403242335_amd64.deb

3) Rebooted

4) Confirm that I am on 3.14 using

uname -a

which returns

Linux stepup 3.14.0-031400rc8-generic #201403242335 SMP Tue Mar 25 03:36:22 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

5) Switched off bluetooth using indicator. Bluetooth is now off.

6) Rebooted to the same kernel version

7) Checked if bluetooth was on- it was "on".

[Alexey Kulik (doctor-rover)]

It seems that this bug is a duplicate of Bug #1296114

[Amr Ibrahim (amribrahim1987)]

This is not fixed in Trusty, or later.

[Amr Ibrahim (amribrahim1987)]

Please set back to confirmed.