bluetooth is ON after standby although I've switched it off in the settings
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
AC100_enablement |
New
|
Undecided
|
Unassigned | ||
GNOME Bluetooth |
New
|
Undecided
|
Unassigned | ||
bluez (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
To save battery on my Toshiba AC100 with Ubuntu 12.04 installed on it, I've switched off bluetooth in the settings GUI. But I notice that sometimes bluetooth is again ON. It seems that it becomes ON after I go back from a standby mode.
I'll make an experiment and I will attach an hci.log (as asked) if the bug reoccurs.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: bluetooth (not installed)
Uname: Linux 3.0.27-1-ac100 armv7l
ApportVersion: 2.0.1-0ubuntu8
Architecture: armhf
Date: Wed Jul 18 14:04:53 2012
InterestingModules: bnep rfcomm btusb bluetooth
ProcKernelCmdLine: mem=448M@0M tegrapart=
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
hciconfig:
hci0: Type: BR/EDR Bus: USB
BD Address: 6C:62:6D:17:96:FD ACL MTU: 310:10 SCO MTU: 64:8
UP RUNNING PSCAN
RX bytes:1106 acl:0 sco:0 events:37 errors:0
TX bytes:645 acl:0 sco:0 commands:36 errors:0
tags: | added: power power-management power-saving powermanagement powersaving |
no longer affects: | unity |
tags: |
added: resume suspend removed: 12.04 arm bluetooth power power-management power-saving powermanagement powersaving standby wakeup |
I tried to reproduce this bug--with varying successfulness:
* first, I turned bluetooth again OFF in the settings, and then put the system to standby from the shutdown menu (invoked by oressing hte power button on the computer). After the wakeup, the bluetooth was still OFF -- the expected good behavior.
* Then, I rebooted the system, and bluetooth was still OFF (if I remember correctly) -- the expected good behavior.
* And then, I closed the lid (my settings are to put the system to standby after 10 min of inactivity), and after the wakeup this time bluetooth was again ON -- the bad behavior, which is not as expected!
Also, this last time, the multiload indicator disappeared from the bar above the desktop. (Although it is set up to run automatically, and is expected to be always there.)
Do you have an idea what is causing this bad behavior?
(I'll report if I come up with a dterministic scenario to reproduce this bug.)