You are not logged in.

#1 2017-10-21 05:58:35

tsar_dean
Member
Registered: 2017-10-21
Posts: 1

Bluetooth broken after GNOME 3.26 update

After updating to GNOME 3.26, my bluetooth stopped working.  If I have just booted up, I can connect to my bluetooth speakers without a problem, and audio will play for ~5 seconds.  After this time, the speakers will disconnect, and when I try to access bluetooth through gnome_settings, the settings will hang for a few minutes, then crash. 


I tried restarting bluetooth.service, but after a few minutes the daemon won't shutdown:

$ systemctl status bluetooth.service                                                                           [1:29:14]
● bluetooth.service - Bluetooth service
   Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Sat 2017-10-21 01:29:07 EDT; 17s ago
     Docs: man:bluetoothd(8)
  Process: 25284 ExecStart=/usr/lib/bluetooth/bluetoothd (code=exited, status=1/FAILURE)
 Main PID: 25284 (code=exited, status=1/FAILURE)
   Status: "Starting up"
    Tasks: 1 (limit: 4915)
   CGroup: /system.slice/bluetooth.service
           └─333 /usr/lib/bluetooth/bluetoothd

Oct 21 01:23:06 dancypants bluetoothd[25284]: Unable to get on D-Bus
Oct 21 01:23:06 dancypants systemd[1]: bluetooth.service: Main process exited, code=exited, status=1/FAILURE
Oct 21 01:24:36 dancypants systemd[1]: bluetooth.service: State 'stop-sigterm' timed out. Killing.
Oct 21 01:24:36 dancypants systemd[1]: bluetooth.service: Killing process 333 (bluetoothd) with signal SIGKILL.
Oct 21 01:26:07 dancypants systemd[1]: bluetooth.service: Processes still around after SIGKILL. Ignoring.
Oct 21 01:27:37 dancypants systemd[1]: bluetooth.service: State 'stop-final-sigterm' timed out. Killing.
Oct 21 01:27:37 dancypants systemd[1]: bluetooth.service: Killing process 333 (bluetoothd) with signal SIGKILL.
Oct 21 01:29:07 dancypants systemd[1]: bluetooth.service: Processes still around after final SIGKILL. Entering failed mode.
Oct 21 01:29:07 dancypants systemd[1]: bluetooth.service: Failed with result 'exit-code'.
Oct 21 01:29:07 dancypants systemd[1]: Failed to start Bluetooth service.

Here's the relevant lines from journalctl:

Oct 21 01:29:07 dancypants systemd[1]: bluetooth.service: Processes still around after final SIGKILL. Entering failed mode.
Oct 21 01:29:07 dancypants systemd[1]: bluetooth.service: Failed with result 'exit-code'.
Oct 21 01:29:07 dancypants polkitd[260]: Unregistered Authentication Agent for unix-process:25126:79823686 (system bus name :1.4017, object pa
Oct 21 01:29:07 dancypants systemd[1]: Failed to start Bluetooth service.
-- Subject: Unit bluetooth.service has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit bluetooth.service has failed.

My machine is a Lenovo t470s with an intel AC 8260 wifi+bluetooth controller, running with the iwlwifi driver.  The bluetooth worked fine before the recent GNOME update.  I've been searching for related issues, but haven't been able to find anything helpful.  Any help is appreciated!

Thanks.

Offline

#2 2017-10-27 13:29:17

in0ni
Member
Registered: 2017-10-27
Posts: 13

Re: Bluetooth broken after GNOME 3.26 update

Any luck? I am also experiencing issues. In my case I am able to connect to my device, but it will disconnect after a few minutes. There is zero output in journal, also the system still thinks it's connected. Happened immediately after 3.26 upgrade.

Offline

#3 2017-10-27 14:24:36

seth
Member
Registered: 2012-09-03
Posts: 50,012

Re: Bluetooth broken after GNOME 3.26 update

I'd look into dmesg and I doubt that this is related to a gnome update, but rather depends on the kernel version (=> check the linux-lts kernel behavior)

Offline

#4 2017-10-27 15:11:58

in0ni
Member
Registered: 2017-10-27
Posts: 13

Re: Bluetooth broken after GNOME 3.26 update

Was just about to post the same -- doubt it's gnome related. Just tested again after linux-firmware update (20171009.bf04291-1) and seems to working just fine!

Offline

#5 2017-10-27 16:14:14

in0ni
Member
Registered: 2017-10-27
Posts: 13

Re: Bluetooth broken after GNOME 3.26 update

I spoke too soon... before connection would drop after a few minutes, this time lasted over an hour. I checked dmesg and lost connectivity around 11:05am -- but don't really see much that coincidences with that time in the logs hmm Any suggestions of where elsewhere I could check to see if I can at least catch an error? Could that last item (logitec-hidpp-device connected) be related?

Much appreciated!

[Fri Oct 27 09:50:55 2017] Bluetooth: hci0: Bootloader revision 0.0 build 26 week 38 2015
[Fri Oct 27 09:50:55 2017] Bluetooth: hci0: Device revision is 16
[Fri Oct 27 09:50:55 2017] Bluetooth: hci0: Secure boot is enabled
[Fri Oct 27 09:50:55 2017] Bluetooth: hci0: OTP lock is enabled
[Fri Oct 27 09:50:55 2017] Bluetooth: hci0: API lock is enabled
[Fri Oct 27 09:50:55 2017] Bluetooth: hci0: Debug lock is disabled
[Fri Oct 27 09:50:55 2017] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[Fri Oct 27 09:50:55 2017] Bluetooth: hci0: Found device firmware: intel/ibt-12-16.sfi
[Fri Oct 27 09:50:55 2017] usbcore: registered new interface driver usbhid
[Fri Oct 27 09:50:55 2017] usbhid: USB HID core driver
[Fri Oct 27 09:50:55 2017] media: Linux media interface: v0.10
[Fri Oct 27 09:50:55 2017] Linux video capture interface: v2.00
[Fri Oct 27 09:50:55 2017] uvcvideo: Found UVC 1.00 device 720p HD Camera (2232:1083)
[Fri Oct 27 09:50:55 2017] uvcvideo 1-7:1.0: Entity type for entity Extension 4 was not initialized!
[Fri Oct 27 09:50:55 2017] uvcvideo 1-7:1.0: Entity type for entity Processing 2 was not initialized!
[Fri Oct 27 09:50:55 2017] uvcvideo 1-7:1.0: Entity type for entity Camera 1 was not initialized!
[Fri Oct 27 09:50:55 2017] input: 720p HD Camera: 720p HD Camera as /devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.0/input/input12
[Fri Oct 27 09:50:55 2017] usbcore: registered new interface driver uvcvideo
[Fri Oct 27 09:50:55 2017] USB Video Class driver (1.1.1)
[Fri Oct 27 09:50:55 2017] logitech-djreceiver 0003:046D:C52B.0004: hiddev0,hidraw1: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:00:14.0-3/input2
[Fri Oct 27 09:50:56 2017] input: Logitech M335 as /devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.2/0003:046D:C52B.0004/0003:046D:4050.0005/input/input13
[Fri Oct 27 09:50:56 2017] logitech-hidpp-device 0003:046D:4050.0005: input,hidraw2: USB HID v1.11 Keyboard [Logitech M335] on usb-0000:00:14.0-3:1
[Fri Oct 27 09:50:56 2017] [drm] RC6 on
[Fri Oct 27 09:50:56 2017] Console: switching to colour frame buffer device 240x67
[Fri Oct 27 09:50:56 2017] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
[Fri Oct 27 09:50:56 2017] usb 1-6: USB disconnect, device number 3
[Fri Oct 27 09:50:56 2017] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC256: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
[Fri Oct 27 09:50:56 2017] snd_hda_codec_realtek hdaudioC0D0:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
[Fri Oct 27 09:50:56 2017] snd_hda_codec_realtek hdaudioC0D0:    hp_outs=1 (0x21/0x0/0x0/0x0/0x0)
[Fri Oct 27 09:50:56 2017] snd_hda_codec_realtek hdaudioC0D0:    mono: mono_out=0x0
[Fri Oct 27 09:50:56 2017] snd_hda_codec_realtek hdaudioC0D0:    inputs:
[Fri Oct 27 09:50:56 2017] snd_hda_codec_realtek hdaudioC0D0:      Mic=0x19
[Fri Oct 27 09:50:56 2017] snd_hda_codec_realtek hdaudioC0D0:      Internal Mic=0x12
[Fri Oct 27 09:50:56 2017] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[Fri Oct 27 09:50:56 2017] Bluetooth: BNEP filters: protocol multicast
[Fri Oct 27 09:50:56 2017] Bluetooth: BNEP socket layer initialized
[Fri Oct 27 09:50:56 2017] input: HDA Intel PCH Mic as /devices/pci0000:00/0000:00:1f.3/sound/card0/input14
[Fri Oct 27 09:50:56 2017] input: HDA Intel PCH Headphone as /devices/pci0000:00/0000:00:1f.3/sound/card0/input15
[Fri Oct 27 09:50:56 2017] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input16
[Fri Oct 27 09:50:56 2017] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input17
[Fri Oct 27 09:50:56 2017] input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input18
[Fri Oct 27 09:50:56 2017] input: HDA Intel PCH HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input19
[Fri Oct 27 09:50:56 2017] input: HDA Intel PCH HDMI/DP,pcm=10 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input20
[Fri Oct 27 09:50:56 2017] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
[Fri Oct 27 09:50:57 2017] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
[Fri Oct 27 09:50:57 2017] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
[Fri Oct 27 09:50:57 2017] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
[Fri Oct 27 09:50:58 2017] Bluetooth: hci0 command 0xfc09 tx timeout
[Fri Oct 27 09:51:00 2017] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
[Fri Oct 27 09:51:02 2017] wlp1s0: authenticate with 18:d6:c7:e0:49:be
[Fri Oct 27 09:51:02 2017] wlp1s0: send auth to 18:d6:c7:e0:49:be (try 1/3)
[Fri Oct 27 09:51:02 2017] wlp1s0: authenticated
[Fri Oct 27 09:51:02 2017] wlp1s0: associate with 18:d6:c7:e0:49:be (try 1/3)
[Fri Oct 27 09:51:02 2017] wlp1s0: RX AssocResp from 18:d6:c7:e0:49:be (capab=0x431 status=0 aid=2)
[Fri Oct 27 09:51:02 2017] wlp1s0: associated
[Fri Oct 27 09:51:02 2017] IPv6: ADDRCONF(NETDEV_CHANGE): wlp1s0: link becomes ready
[Fri Oct 27 09:51:06 2017] device-mapper: uevent: version 1.0.3
[Fri Oct 27 09:51:06 2017] device-mapper: ioctl: 4.37.0-ioctl (2017-09-20) initialised: dm-devel@redhat.com
[Fri Oct 27 09:51:06 2017] Bluetooth: hci0: Failed to send firmware data (-110)
[Fri Oct 27 09:51:06 2017] EXT4-fs (sda1): re-mounted. Opts: data=ordered,commit=600
[Fri Oct 27 09:51:08 2017] NET: Registered protocol family 38
[Fri Oct 27 09:51:08 2017] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)
[Fri Oct 27 09:51:09 2017] fuse init (API version 7.26)
[Fri Oct 27 09:51:10 2017] rfkill: input handler disabled
[Fri Oct 27 09:51:32 2017] usb 1-6: new full-speed USB device number 6 using xhci_hcd
[Fri Oct 27 09:51:32 2017] Bluetooth: hci0: Bootloader revision 0.0 build 26 week 38 2015
[Fri Oct 27 09:51:32 2017] Bluetooth: hci0: Device revision is 16
[Fri Oct 27 09:51:32 2017] Bluetooth: hci0: Secure boot is enabled
[Fri Oct 27 09:51:32 2017] Bluetooth: hci0: OTP lock is enabled
[Fri Oct 27 09:51:32 2017] Bluetooth: hci0: API lock is enabled
[Fri Oct 27 09:51:32 2017] Bluetooth: hci0: Debug lock is disabled
[Fri Oct 27 09:51:32 2017] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[Fri Oct 27 09:51:32 2017] Bluetooth: hci0: Found device firmware: intel/ibt-12-16.sfi
[Fri Oct 27 09:51:33 2017] EXT4-fs (sda1): re-mounted. Opts: data=ordered,commit=600
[Fri Oct 27 09:51:33 2017] EXT4-fs (dm-0): re-mounted. Opts: data=ordered,commit=600
[Fri Oct 27 09:51:34 2017] Bluetooth: hci0: Waiting for firmware download to complete
[Fri Oct 27 09:51:34 2017] Bluetooth: hci0: Firmware loaded in 1425275 usecs
[Fri Oct 27 09:51:34 2017] Bluetooth: hci0: Waiting for device to boot
[Fri Oct 27 09:51:34 2017] Bluetooth: hci0: Device booted in 11725 usecs
[Fri Oct 27 09:51:34 2017] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-12-16.ddc
[Fri Oct 27 09:51:34 2017] Bluetooth: hci0: Applying Intel DDC parameters completed
[Fri Oct 27 09:51:34 2017] Bluetooth: RFCOMM TTY layer initialized
[Fri Oct 27 09:51:34 2017] Bluetooth: RFCOMM socket layer initialized
[Fri Oct 27 09:51:34 2017] Bluetooth: RFCOMM ver 1.11
[Fri Oct 27 09:51:35 2017] EXT4-fs (sda1): re-mounted. Opts: data=ordered,commit=600
[Fri Oct 27 09:51:35 2017] EXT4-fs (dm-0): re-mounted. Opts: data=ordered,commit=600
[Fri Oct 27 09:51:37 2017] EXT4-fs (sda1): re-mounted. Opts: data=ordered,commit=600
[Fri Oct 27 09:51:37 2017] EXT4-fs (dm-0): re-mounted. Opts: data=ordered,commit=600
[Fri Oct 27 09:51:52 2017] input: 08:DF:1F:D4:1E:C1 as /devices/virtual/input/input21
[Fri Oct 27 10:37:27 2017] logitech-hidpp-device 0003:046D:4050.0005: HID++ 4.5 device connected.

Offline

#6 2017-10-29 23:04:56

in0ni
Member
Registered: 2017-10-27
Posts: 13

Re: Bluetooth broken after GNOME 3.26 update

seth wrote:

I'd look into dmesg and I doubt that this is related to a gnome update, but rather depends on the kernel version (=> check the linux-lts kernel behavior)

linux-lts been working great, thanks!

Offline

#7 2017-10-30 06:42:07

seth
Member
Registered: 2012-09-03
Posts: 50,012

Re: Bluetooth broken after GNOME 3.26 update

You should check your pacman log for the last kernel update to narrow the regression - if it remains it will make it into the lts kernel at some point.

Offline

#8 2017-10-31 04:09:55

in0ni
Member
Registered: 2017-10-27
Posts: 13

Re: Bluetooth broken after GNOME 3.26 update

[2017-10-11 12:11] [ALPM] upgraded linux (4.12.13-1 -> 4.13.5-1) -- it was after this update that the issue started. Guess, I should check if not create bug report, no?

Offline

#9 2017-10-31 06:30:39

seth
Member
Registered: 2012-09-03
Posts: 50,012

Re: Bluetooth broken after GNOME 3.26 update

You'll have to bisect the issue to find the breaking commit, see https://bbs.archlinux.org/viewtopic.php … 1#p1682931 for a pattern

Offline

#10 2017-11-01 20:09:17

problame
Member
Registered: 2017-11-01
Posts: 1

Re: Bluetooth broken after GNOME 3.26 update

Temporary workaround from https://bbs.archlinux.org/viewtopic.php?id=230366

rmmod iwlwifi # may need to remove dependant modules first
sudo insmod /lib/modules/4.13.9-1-ARCH/kernel/drivers/net/wireless/intel/iwlwifi/iwlwifi.ko.gz bt_coex_active=0
# disable and reenable bluetooth and wifi

Offline

#11 2017-11-01 20:15:42

seth
Member
Registered: 2012-09-03
Posts: 50,012

Offline

#12 2017-11-10 07:32:22

rgzfxf6bhu
Member
Registered: 2015-10-30
Posts: 100

Re: Bluetooth broken after GNOME 3.26 update

For now the only solution seems to be to disable bt_coex_active.

But there are upstream bug reports already:
https://bugs.archlinux.org/task/55796#comment163300

Offline

#13 2017-11-26 00:12:10

cribari
Member
From: Recife, Brazil
Registered: 2016-01-28
Posts: 83
Website

Re: Bluetooth broken after GNOME 3.26 update

It could be related to this upstream bug: https://bugzilla.kernel.org/show_bug.cgi?id=197039


Linux, street photography and Baroque music enthusiast.

Offline

#14 2017-11-26 04:05:45

jkohler
Member
Registered: 2017-11-26
Posts: 5

Re: Bluetooth broken after GNOME 3.26 update

I think this is likely related to https://bbs.archlinux.org/viewtopic.php … 1#p1751311, since the 8260 and 8265 seem to share the same firmware.  I posted a solution there that resolved similar issues for me.  It seems the latest Windows driver from Intel has an updated firmware file (370c1206001a260f00.sfi), which persists after a warm reboot and bluetooth works fine with it.  Dmesg reports it as

[   10.467348] Bluetooth: hci0: Firmware revision 0.1 build 151 week 24 2017

whereas the firmware from linux-firmware, loaded after a cold start, is reporting

[   10.227703] Bluetooth: hci0: Firmware revision 0.1 build 103 week 50 2016

If I copy the firmware file from windows over intel/ibt-12-16.sfi then do a cold start, bluetooth works fine again, and dmesg reports the newer firmware revision.  I guess this needs to be updated in linux-firmware upstream, but they seem very clear about needing appropriate license documentation.  Does anyone know where to find that? I could only find the new firmware in the Windows driver distribution.

Offline

#15 2017-11-27 19:50:21

jkohler
Member
Registered: 2017-11-26
Posts: 5

Re: Bluetooth broken after GNOME 3.26 update

I opened a bug report on the upstream kernel (https://bugzilla.kernel.org/show_bug.cgi?id=197997), and the Intel folks provided a pre-release firmware update there which also resolves the problem for me.

Offline

Board footer

Powered by FluxBB