Bluetooth adapter has disappeared, no BT in 17.10

I have a Dell Latitude 3580 and the internal bluetooth has suddenly stopped working. It originally stopped working after a resume from suspend but now even after several reboots it’s as if the adapter isn’t there at all. I tried it out on my live USB of Ubuntu-Mate and had no problems. The laptop is a Kably Lake Intel setup. I have no idea what’s going on here.

The kernel I’m using is:
Linux Trinity 4.13.0-32-generic #35-Ubuntu SMP Thu Jan 25 09:13:46 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

I’ve tried:

sudo service bluetooth restart

Without any luck.

Here’s the outputs of a few commands. As you’ll see, the BT adapter just isn’t seen:

hcitool dev
shows nothng

lsusb | grep -i "bl``uetooth"
shows nothing

Here’s the output of

journalctl -xb | grep blue

Jan 29 17:10:10 Trinity NetworkManager[874]: [1517271010.5670] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so)
Jan 29 17:10:44 Trinity dbus[842]: [system] Activating via systemd: service name=‘org.bluez’ unit=‘dbus-org.bluez.service’
– Subject: Unit bluetooth.service has begun start-up
– Unit bluetooth.service has begun starting up.
Jan 29 17:10:54 Trinity bluetoothd[1852]: Bluetooth daemon 5.46
Jan 29 17:10:54 Trinity dbus[842]: [system] Successfully activated service ‘org.bluez’
– Subject: Unit bluetooth.service has finished start-up
– Unit bluetooth.service has finished starting up.
Jan 29 17:10:54 Trinity bluetoothd[1852]: Starting SDP server
Jan 29 17:10:55 Trinity bluetoothd[1852]: Bluetooth management interface 1.14 initialized
Jan 29 17:10:55 Trinity NetworkManager[874]: [1517271055.0725] bluez: use BlueZ version 5
Jan 29 17:10:57 Trinity dbus-daemon[1377]: Activating via systemd: service name=‘org.bluez.obex’ unit=‘dbus-org.bluez.obex.service’
Jan 29 17:10:58 Trinity dbus-daemon[1377]: Successfully activated service ‘org.bluez.obex’
Jan 29 17:10:58 Trinity dbus[842]: [system] Activating service name=‘org.blueman.Mechanism’ (using servicehelper)
Jan 29 17:10:59 Trinity org.blueman.Mechanism[842]: Unable to init server: Could not connect: Connection refused
Jan 29 17:10:59 Trinity org.blueman.Mechanism[842]: Unable to init server: Could not connect: Connection refused
Jan 29 17:10:59 Trinity blueman-mechanism[2048]: Starting blueman-mechanism
Jan 29 17:10:59 Trinity dbus[842]: [system] Successfully activated service ‘org.blueman.Mechanism’
Jan 29 17:10:59 Trinity blueman-mechani[2048]: gtk_icon_theme_get_for_screen: assertion ‘GDK_IS_SCREEN (screen)’ failed
Jan 29 17:11:00 Trinity blueman-mechanism[2048]: loading RfKill
Jan 29 17:11:00 Trinity blueman-mechanism[2048]: loading Ppp
Jan 29 17:11:00 Trinity blueman-mechanism[2048]: loading Rfcomm
Jan 29 17:11:00 Trinity blueman-mechanism[2048]: loading Network
Jan 29 17:11:30 Trinity blueman-mechanism[2048]: Exiting
Jan 29 17:13:53 Trinity dbus[842]: [system] Activating service name=‘org.blueman.Mechanism’ (using servicehelper)
Jan 29 17:13:53 Trinity org.blueman.Mechanism[842]: Unable to init server: Could not connect: Connection refused
Jan 29 17:13:53 Trinity org.blueman.Mechanism[842]: Unable to init server: Could not connect: Connection refused
Jan 29 17:13:53 Trinity blueman-mechanism[2560]: Starting blueman-mechanism
Jan 29 17:13:53 Trinity dbus[842]: [system] Successfully activated service ‘org.blueman.Mechanism’
Jan 29 17:13:53 Trinity blueman-mechani[2560]: gtk_icon_theme_get_for_screen: assertion ‘GDK_IS_SCREEN (screen)’ failed
Jan 29 17:13:53 Trinity blueman-mechanism[2560]: loading RfKill
Jan 29 17:13:53 Trinity blueman-mechanism[2560]: loading Ppp
Jan 29 17:13:53 Trinity blueman-mechanism[2560]: loading Rfcomm
Jan 29 17:13:53 Trinity blueman-mechanism[2560]: loading Network
Jan 29 17:14:23 Trinity blueman-mechanism[2560]: Exiting

Any help at all is appreciated!

UPDATE

It started working a while ago, after resuming from suspend, then it stopped again after resuming from suspend, and just now it’s working again after resuming from suspend. So I guess the nature of the problem is intermittent. Still, if this problem is solvable I’d sincerely appreciate some help.

Sounds like a driver regression issue, since an earlier kernel doesn’t show the problem.
You should submit a bug report against your kernel or the package containing /usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so

I’ll do that. Thanks.