Bluetooth switches on after restart

Bug #979174 reported by Lars Falk-Petersen
260
This bug affects 1 person
Affects Status Importance Assigned to Milestone
bluez (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

I never use bluetooth on my laptop, so there is no point for it to stay ON. It draws extra power, leaves my system vounrable to attacks, and allows me to be tracked (i.e. blueproximity).

When switching bluetooth off, it only stays off until the next time I reboot. Even if I use the bluetooth-button on my keyboard, which turns off the card entirely.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: gnome-control-center 1:3.4.0-0ubuntu6
ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14
Uname: Linux 3.2.0-22-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.0.1-0ubuntu1
Architecture: amd64
CheckboxSubmission: 621f51bbb855f2649d500c28b87f4a5e
CheckboxSystem: 86f6fcdd6850a813cd5c77b7959e6176
Date: Wed Apr 11 19:41:51 2012
ExecutablePath: /usr/bin/gnome-control-center
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_gnome-control-center:
 activity-log-manager-control-center 0.9.4-0ubuntu2
 deja-dup 22.0-0ubuntu2
 gnome-bluetooth 3.2.2-0ubuntu5
 indicator-datetime 0.3.94-0ubuntu1
---
ApportVersion: 2.0.1-0ubuntu4
Architecture: amd64
CheckboxSubmission: 621f51bbb855f2649d500c28b87f4a5e
CheckboxSystem: 86f6fcdd6850a813cd5c77b7959e6176
DistroRelease: Ubuntu 12.04
InterestingModules: bnep rfcomm btusb bluetooth
MachineType: CLEVO P150HMx
NonfreeKernelModules: nvidia
Package: bluez 4.98-2ubuntu7
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-23-generic root=UUID=cd1c6241-ac6f-4c97-8a1f-41866a7c8cab ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
Tags: precise
Uname: Linux 3.2.0-23-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 02/15/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.4
dmi.board.asset.tag: Not Applicable
dmi.board.name: P150HMx
dmi.board.vendor: CLEVO
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: Not Applicable
dmi.chassis.type: 10
dmi.chassis.vendor: CLEVO
dmi.chassis.version: Not Applicable
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd02/15/2011:svnCLEVO:pnP150HMx:pvrNotApplicable:rvnCLEVO:rnP150HMx:rvrNotApplicable:cvnCLEVO:ct10:cvrNotApplicable:
dmi.product.name: P150HMx
dmi.product.version: Not Applicable
dmi.sys.vendor: CLEVO
hciconfig:
 hci0: Type: BR/EDR Bus: USB
  BD Address: E0:91:53:34:31:42 ACL MTU: 310:10 SCO MTU: 64:8
  DOWN
  RX bytes:868 acl:0 sco:0 events:38 errors:0
  TX bytes:649 acl:0 sco:0 commands:37 errors:0

Revision history for this message
Lars Falk-Petersen (julenissen) wrote :
visibility: private → public
Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

Is this reproducible with your system fully up to date?

I can't reproduce this on my own system. When bluetooth is turned off via the menu or via the killswitch (soft killswitch in my state, via Fn+F2 on a Dell system), bluetooth remains blocked. This is supposed to be taken care of by the rfkill-store/rfkill-restore upstart jobs; and probably needs a bit more investigation (and it would probably be useful for the kernel team to look at it).

Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal:

  apport-collect 979174

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

Changed in bluez (Ubuntu):
status: New → Incomplete
Revision history for this message
Lars Falk-Petersen (julenissen) wrote : BootDmesg.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
Lars Falk-Petersen (julenissen) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Lars Falk-Petersen (julenissen) wrote : Dependencies.txt

apport information

Revision history for this message
Lars Falk-Petersen (julenissen) wrote : Lspci.txt

apport information

Revision history for this message
Lars Falk-Petersen (julenissen) wrote : Lsusb.txt

apport information

Revision history for this message
Lars Falk-Petersen (julenissen) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Lars Falk-Petersen (julenissen) wrote : ProcEnviron.txt

apport information

Revision history for this message
Lars Falk-Petersen (julenissen) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Lars Falk-Petersen (julenissen) wrote : ProcModules.txt

apport information

Revision history for this message
Lars Falk-Petersen (julenissen) wrote : UdevDb.txt

apport information

Revision history for this message
Lars Falk-Petersen (julenissen) wrote : UdevLog.txt

apport information

Revision history for this message
Lars Falk-Petersen (julenissen) wrote : getfacl.txt

apport information

Revision history for this message
Lars Falk-Petersen (julenissen) wrote : rfkill.txt

apport information

Revision history for this message
Lars Falk-Petersen (julenissen) wrote : syslog.txt

apport information

Revision history for this message
Lars Falk-Petersen (julenissen) wrote :

> Mathieu Trudel-Lapierre (mathieu-tl) wrote on 2012-04-16: #2
> Is this reproducible with your system fully up to date?
Partly. When deactivating using the applet, it stays off. When deactivating via hardware button (Fn + F12), it's on again after boot. Seems to me like the hardware button is the most powersaving way of disabling, as there's a LED indicating the bluetooth status. This LED only turns off when using hardware button.

> I can't reproduce this on my own system. When bluetooth is turned off via the menu or via the killswitch (soft killswitch in my state, via Fn+F2 on a Dell system), bluetooth remains blocked. This is supposed to be taken care of by the rfkill-store/rfkill-restore upstart jobs; and probably needs a bit more investigation (and it would probably be useful for the kernel team to look at it).

I uploaded the apport information.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for bluez (Ubuntu) because there has been no activity for 60 days.]

Changed in bluez (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public Security information  
Everyone can see this security related information.

Other bug subscribers

Remote bug watches

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