bluetooth keeps turning off

Bug #1762603 reported by Aurélien PIERRE
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
connman (Ubuntu)
Undecided
Unassigned

Bug Description

the bluetooth worked well right after install. After a few reboots, it's impossible to keep it on and to connect devices.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: bluez 5.48-0ubuntu3
ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
Uname: Linux 4.15.0-15-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr 9 23:24:56 2018
InstallationDate: Installed on 2018-04-08 (1 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180408)
InterestingModules: bnep btusb bluetooth
MachineType: LENOVO 20HHCTO1WW
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic.efi.signed root=UUID=f6fc1852-25c6-47a6-9776-4ed8b8d6b70e ro quiet splash elevator=noop vt.handoff=1
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/26/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: N1UET46W (1.20 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20HHCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0Q40112 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: dmi:bvnLENOVO:bvrN1UET46W(1.20):bd02/26/2018:svnLENOVO:pn20HHCTO1WW:pvrThinkPadP51:rvnLENOVO:rn20HHCTO1WW:rvrSDK0Q40112WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad P51
dmi.product.name: 20HHCTO1WW
dmi.product.version: ThinkPad P51
dmi.sys.vendor: LENOVO
hciconfig:

Revision history for this message
Aurélien PIERRE (aurelienpierre) wrote :
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Do you mean reboots or suspending and resuming?

Changed in bluez (Ubuntu):
status: New → Incomplete
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Also, please elaborate on what you mean by "off" vs "on". Is there some part of the GUI that shows it is off, or is it shown as on and just not working?

Revision history for this message
Aurélien PIERRE (aurelienpierre) wrote :

I mean reboots.

So, on boot, the airplane mode is turned on by default (for an unknwon reason).

The rfkill output is attached above. I have to trigger several `sudo rfkill unblock all` to actually have them unlocked (in command line). But then, the GUI still shows the bluetooth switch as OFF. When I try to enable the BT in the GUI, the gnome-control-center window freezes but no device detection happens. Closing and re-opening the gnome-control-center shows that BT is still OFF.

Using the BT hotkey from the laptop chenges nothing.

Revision history for this message
Aurélien PIERRE (aurelienpierre) wrote :

Also I have tried with blueman instead, with and without acpi-calls-dkms, tp-smapi-dkms, tlp installed, the issue remains.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Sounds possibly like bug 1738838(?). I'm not sure the upstream fix for that has been released yet, or if it works sufficiently.

Revision history for this message
Aurélien PIERRE (aurelienpierre) wrote :

Yes it looks like the same bug (at least for the GUI part), and it's a Thinkpad as well.

Revision history for this message
Aurélien PIERRE (aurelienpierre) wrote :

Ok I troubleshot this problem.

Apparently, it came from the package `connman`, an Intel utility to manage wlan and bluetooth that I installed wrongly since it's intended for embedded systems.

Removing it solved all my problems.

affects: bluez (Ubuntu) → connman (Ubuntu)
Changed in connman (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers