Turning off bluetooth via the panel applet disables the wireless instead

Bug #962621 reported by tsj
44
This bug affects 9 people
Affects Status Importance Assigned to Milestone
Linux
Confirmed
Medium
linux (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Trying to turn off bluetooth (which I don't use) through the applet in the top right-hand side panel disables the wireless instead. The wireless won't come back up until I run "sudo rfkill unblock all."

tsj@linux-laptop:~$ lsb_release -rd
Description: Ubuntu precise (development branch)
Release: 12.04

Apt-cache policy indicates there's no bluetooth installed:
tsj@linux-laptop:~$ apt-cache policy bluetooth
bluetooth:
  Installed: (none)
  Candidate: 4.98-2ubuntu6
  Version table:
     4.98-2ubuntu6 0
                500 http://us.archive.ubuntu.com/ubuntu/ precise/universe amd64 Packages

However, according to the Software Centre the following packages are installed:
- Bluetooth
- Bluetooth Transfer
- Bluetooth Device Setup

My wireless card is Broadcom BCM4313 and I use the proprietary wl driver since the brcmsmac driver works intermittently at best with my chipset.

The same problem occurs with the brcmsmac driver (I unblacklisted and loaded the driver to see what happens): clicking on "bluetooth off" disables the wireless.

For what it's worth, upon login I get a message that bluetoothd closed unexpectedly (see bug #857702).

If any more information is needed I'd be happy to provide it.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: bluetooth (not installed)
ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6
Uname: Linux 3.2.0-17-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 1.94.1-0ubuntu2
Architecture: amd64
Date: Thu Mar 22 18:21:30 2012
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: Hewlett-Packard HP Pavilion dm1 Notebook PC
ProcEnviron:
 TERM=xterm
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-17-generic root=UUID=8372f7db-a512-4001-b4de-4dd73156cf41 ro quiet splash vt.handoff=7
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/04/2011
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.01
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 3387
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 36.0A
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnHewlett-Packard:bvrF.01:bd08/04/2011:svnHewlett-Packard:pnHPPaviliondm1NotebookPC:pvr0697100000204600000320100:rvnHewlett-Packard:rn3387:rvr36.0A:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP Pavilion dm1 Notebook PC
dmi.product.version: 0697100000204600000320100
dmi.sys.vendor: Hewlett-Packard
hciconfig:
 hci0: Type: BR/EDR Bus: USB
  BD Address: 94:39:E5:CC:05:7D ACL MTU: 1021:8 SCO MTU: 64:1
  UP RUNNING PSCAN
  RX bytes:878 acl:0 sco:0 events:38 errors:0
  TX bytes:655 acl:0 sco:0 commands:38 errors:0

Revision history for this message
tsj (ts3141592) wrote :
tsj (ts3141592)
description: updated
description: updated
Revision history for this message
tsj (ts3141592) wrote :

Forgot to attach the hci log, here it is.

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

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

Changed in bluez (Ubuntu):
status: New → Confirmed
Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

Rfkill issues, possibly bluetooth and wireless coexistence so the same driver would be driving just one killswitch? Reassigning to 'linux'.

affects: bluez (Ubuntu) → linux (Ubuntu)
Changed in linux (Ubuntu):
status: Confirmed → New
Revision history for this message
Brad Figg (brad-figg) wrote : Test with newer development kernel (3.2.0-23.36)

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get dist-upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

Changed in linux (Ubuntu):
status: New → Confirmed
status: Confirmed → Incomplete
tags: added: kernel-request-3.2.0-23.36
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.4kernel[1] (Not a kernel in the daily directory). Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the other tags). This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4-rc3-precise/

Changed in linux (Ubuntu):
importance: Undecided → Medium
tags: added: needs-upstream-testing
Revision history for this message
tsj (ts3141592) wrote :

Apologies for not responding earlier, took me a while to get to my laptop.

First things first, I just upgraded to the 3.2.0-23-generic kernel & tested with both the wl and the brcmsmac drivers, the issue persists: turning bluetooth off via the panel applet disables the wireless.

I'll test against the mainline kernel and post the results here. Might take me a while until I figure out how to do that.

Cheers.

Revision history for this message
tsj (ts3141592) wrote :

Bug exists in upstream kernel. I'll fix the tags in a minute.

Here's the kernel I'm running right now:

tsj@linux-laptop:~$ uname -r
3.4.0-030400rc3-generic

I loaded the brcmsmac driver (in my setup it's usually blacklisted); running "lspci -k" showed that the kernel driver in use was "bcma-pci-bridge" with some wireless albeit quite weak. Disabling the bluetooth via the applet disconnected the wireless. Here are the results from "rfkill list all" after the wireless disconnected:

0: hci0: Bluetooth
 Soft blocked: yes
 Hard blocked: no
1: hp-wifi: Wireless LAN
 Soft blocked: yes
 Hard blocked: no
2: hp-bluetooth: Bluetooth
 Soft blocked: no
 Hard blocked: no
3: phy0: Wireless LAN
 Soft blocked: no
 Hard blocked: yes

I couldn't get the proprietary wl driver to work with this kernel, either through the Additional Drivers option in System Setting or through building it from Broadcom here http://www.broadcom.com/support/802.11/linux_sta.php

I got some errors during the build and don't know enough to figure out what's wrong (I've built the wl driver before but on a regular ubuntu kernel).

Anyway, looks like the problem is still there. Let me know if you need more testing, I'd be glad to help if I can.

Cheers

tsj (ts3141592)
tags: added: kernel-bug-exists-upstream
removed: needs-upstream-testing
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report at bugzilla.kernel.org [1]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

If you are comfortable with opening a bug upstream, It would be great if you can report back the upstream bug number in this bug report. That will allow us to link this bug to the upstream report.

[1] https://wiki.ubuntu.com/Bugs/Upstream/kernel

Changed in linux (Ubuntu):
status: Confirmed → Triaged
Revision history for this message
tsj (ts3141592) wrote :

Ok, I'll open a bug upstream. Again, might take some time until I figure out how to do that, register, etc. Thanks for the link, that'll help. Once that's sorted out I'll post the bug number. Cheers

Revision history for this message
tsj (ts3141592) wrote :

I found a duplicate bug report upstream albeit with different kernel versions & added some info to it together with a link to this bug report:

https://bugzilla.kernel.org/show_bug.cgi?id=42964

Changed in linux:
importance: Unknown → Medium
status: Unknown → Confirmed
Revision history for this message
Gary M (garym) wrote :

Duplicate of earlier bug 952694?

Revision history for this message
Stéphane Guillou (stephane-guillou) wrote :

This happens on my HP Pavilion dm1 with Ubuntu 12.04 up to date.
It is very annoying as I have no use for the bluetooth function but I can't turn it off as I lose my wifi connection, and my battery life is therefore reduced.
Is there anything I can do to add some information to this bug report?

Revision history for this message
penalvch (penalvch) wrote :

tsj, could you please provide the full computer model as noted on the sticker (ex. HP Pavilion dm1-4050us Entertainment Notebook PC)?

tags: added: bot-stop-nagging needs-full-computer-model needs-upstream-testing
removed: kernel-request-3.2.0-23.36
Changed in linux (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
tsj (ts3141592) wrote :

The laptop was HP Pavilion dm1-4010us.

Took me a while to dig up the information as I don't have that laptop anymore. Can't help with testing either, unfortunately, but would be happy to answer any questions if I can.

Good luck with sorting that bug.

Revision history for this message
penalvch (penalvch) wrote :

tsj, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/962621/comments/15 regarding you no longer have the hardware. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

Changed in linux (Ubuntu):
status: Incomplete → Invalid
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.