[Bug 1603715] [NEW] bluetooth unavailable after rfkill hard (or soft) unblocking and after suspend/resume

Launchpad Bug Tracker 1603715 at bugs.launchpad.net
Sun Jul 17 21:10:39 UTC 2016


You have been subscribed to a public bug:

DELL Latitude E5510 has a hardware switch to disable and enable
bluetooth and wifi devices ("hard blocking" in terms of rfkill). In
terms of wifi, this works great: After hard unblocking, the device
resumes back to normal operation without any manual intervention. That
was also working with bluetooth as of ubuntu 14.04, kernel 4.2.

In ubuntu 16.04, kernel 4.4.0-31-generic, together with systemd, this is
not working any more:

After hard blocking and unblocking

- bluetooth is not working at all
- the applet-indicator remains gray
- bluetooth cannot be enabled with the applet-indicator (see https://storage6.static.itmages.com/i/16/0717/h_1468721829_7715160_83cd33bfba.png). Applet-indicator remains gray
- rfkill list tells me that the kernel knows about the hard unblocking (turns from "yes" to "no"):
rfkill list bluetooth
2: dell-bluetooth: Bluetooth
 Soft blocked: no
 Hard blocked: no
8: hci0: Bluetooth
 Soft blocked: no
 Hard blocked: no

The device is a
sudo lsusb
Bus 002 Device 010: ID 413c:8187 Dell Computer Corp. DW375 Bluetooth Module

Workaround: After a

sudo service bluetooth restart

the bluetooth device turns back to normal operation and the applet-
indicator turns from gray to black (available).

Suggested fix: Make the workaround obsolete.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: systemd 229-4ubuntu6
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: GNOME-Flashback:Unity
Date: Sun Jul 17 04:00:58 2016
InstallationDate: Installed on 2014-11-29 (595 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
MachineType: Dell Inc. Latitude E5510
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-31-generic root=UUID=6408c2d9-1b60-43d7-9a7f-2dceeb40de28 ro rootflags=subvol=@ quiet splash vt.handoff=7
SourcePackage: systemd
UpgradeStatus: Upgraded to xenial on 2016-06-15 (31 days ago)
dmi.bios.date: 12/06/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A16
dmi.board.name: 023HKR
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA16:bd12/06/2013:svnDellInc.:pnLatitudeE5510:pvr0001:rvnDellInc.:rn023HKR:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E5510
dmi.product.version: 0001
dmi.sys.vendor: Dell Inc.

** Affects: systemd
     Importance: Unknown
         Status: New

** Affects: bluez (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: amd64 apport-bug xenial
-- 
bluetooth unavailable after rfkill hard (or soft) unblocking and after suspend/resume
https://bugs.launchpad.net/bugs/1603715
You received this bug notification because you are a member of Bluetooth, which is subscribed to bluez in Ubuntu.



More information about the Ubuntu-bluetooth mailing list