You are not logged in.

#1 2021-01-26 19:49:22

mushotoku
Member
Registered: 2020-12-11
Posts: 14

Random bluetooth speaker disconnects

Hi everyone,...

I'm trying to tackel an annoying problem with my Bluetooth Speaker, which randomly disconnets.
It happens at least once within 12h, often more than once. Even when the system is idle and not playing any sound.

# journalctl --no-hostname -u bluetooth.service  -b -1

-- Journal begins at Tue 2021-01-26 04:18:12 CET, ends at Tue 2021-01-26 19:54:11 CET. --
Jan 26 06:40:27 systemd[1]: Starting Bluetooth service...
Jan 26 06:40:27 bluetoothd[668]: Bluetooth daemon 5.55
Jan 26 06:40:27 bluetoothd[668]: src/main.c:parse_controller_config() Key file does not have key “BRPageScanType” in group “Controller”
Jan 26 06:40:27 bluetoothd[668]: src/main.c:parse_controller_config() Key file does not have key “BRPageScanInterval” in group “Controller”
Jan 26 06:40:27 bluetoothd[668]: src/main.c:parse_controller_config() Key file does not have key “BRPageScanWindow” in group “Controller”
Jan 26 06:40:27 bluetoothd[668]: src/main.c:parse_controller_config() Key file does not have key “BRInquiryScanType” in group “Controller”
Jan 26 06:40:27 bluetoothd[668]: src/main.c:parse_controller_config() Key file does not have key “BRInquiryScanInterval” in group “Controller”
Jan 26 06:40:27 bluetoothd[668]: src/main.c:parse_controller_config() Key file does not have key “BRInquiryScanWindow” in group “Controller”
Jan 26 06:40:27 bluetoothd[668]: src/main.c:parse_controller_config() Key file does not have key “BRLinkSupervisionTimeout” in group “Controller”
Jan 26 06:40:27 bluetoothd[668]: src/main.c:parse_controller_config() Key file does not have key “BRPageTimeout” in group “Controller”
Jan 26 06:40:27 bluetoothd[668]: src/main.c:parse_controller_config() Key file does not have key “BRMinSniffInterval” in group “Controller”
Jan 26 06:40:27 bluetoothd[668]: src/main.c:parse_controller_config() Key file does not have key “BRMaxSniffInterval” in group “Controller”
Jan 26 06:40:27 bluetoothd[668]: src/main.c:parse_controller_config() Key file does not have key “LEMinAdvertisementInterval” in group “Controller”
Jan 26 06:40:27 bluetoothd[668]: src/main.c:parse_controller_config() Key file does not have key “LEMaxAdvertisementInterval” in group “Controller”
Jan 26 06:40:27 bluetoothd[668]: src/main.c:parse_controller_config() Key file does not have key “LEMultiAdvertisementRotationInterval” in group “Controller”
Jan 26 06:40:27 bluetoothd[668]: src/main.c:parse_controller_config() Key file does not have key “LEScanIntervalAutoConnect” in group “Controller”
Jan 26 06:40:27 bluetoothd[668]: src/main.c:parse_controller_config() Key file does not have key “LEScanWindowAutoConnect” in group “Controller”
Jan 26 06:40:27 bluetoothd[668]: src/main.c:parse_controller_config() Key file does not have key “LEScanIntervalSuspend” in group “Controller”
Jan 26 06:40:27 bluetoothd[668]: src/main.c:parse_controller_config() Key file does not have key “LEScanWindowSuspend” in group “Controller”
Jan 26 06:40:27 bluetoothd[668]: src/main.c:parse_controller_config() Key file does not have key “LEScanIntervalDiscovery” in group “Controller”
Jan 26 06:40:27 bluetoothd[668]: src/main.c:parse_controller_config() Key file does not have key “LEScanWindowDiscovery” in group “Controller”
Jan 26 06:40:27 bluetoothd[668]: src/main.c:parse_controller_config() Key file does not have key “LEScanIntervalAdvMonitor” in group “Controller”
Jan 26 06:40:27 bluetoothd[668]: src/main.c:parse_controller_config() Key file does not have key “LEScanWindowAdvMonitor” in group “Controller”
Jan 26 06:40:27 bluetoothd[668]: src/main.c:parse_controller_config() Key file does not have key “LEScanIntervalConnect” in group “Controller”
Jan 26 06:40:27 bluetoothd[668]: src/main.c:parse_controller_config() Key file does not have key “LEScanWindowConnect” in group “Controller”
Jan 26 06:40:27 bluetoothd[668]: src/main.c:parse_controller_config() Key file does not have key “LEMinConnectionInterval” in group “Controller”
Jan 26 06:40:27 bluetoothd[668]: src/main.c:parse_controller_config() Key file does not have key “LEMaxConnectionInterval” in group “Controller”
Jan 26 06:40:27 bluetoothd[668]: src/main.c:parse_controller_config() Key file does not have key “LEConnectionLatency” in group “Controller”
Jan 26 06:40:27 bluetoothd[668]: src/main.c:parse_controller_config() Key file does not have key “LEConnectionSupervisionTimeout” in group “Controller”
Jan 26 06:40:27 bluetoothd[668]: src/main.c:parse_controller_config() Key file does not have key “LEAutoconnecttimeout” in group “Controller”
Jan 26 06:40:27 systemd[1]: Started Bluetooth service.
Jan 26 06:40:27 bluetoothd[668]: Starting SDP server
Jan 26 06:40:27 bluetoothd[668]: Bluetooth management interface 1.15 initialized
Jan 26 06:40:42 bluetoothd[668]: Endpoint registered: sender=:1.59 path=/MediaEndpoint/A2DPSink/sbc
Jan 26 06:40:42 bluetoothd[668]: Endpoint registered: sender=:1.59 path=/MediaEndpoint/A2DPSource/sbc
Jan 26 06:40:47 bluetoothd[668]: /org/bluez/hci0/dev_0C_A6_94_85_D9_E3/sep1/fd0: fd(36) ready
Jan 26 14:47:46 bluetoothd[668]: src/profile.c:ext_io_disconnected() Unable to get io data for Headset Voice gateway: getpeername: Transport endpoint is not connected (107)
Jan 26 14:48:12 bluetoothd[668]: /org/bluez/hci0/dev_0C_A6_94_85_D9_E3/sep1/fd1: fd(36) ready
Jan 26 16:06:54 bluetoothd[668]: Terminating
Jan 26 16:06:54 systemd[1]: Stopping Bluetooth service...
Jan 26 16:06:54 bluetoothd[668]: profiles/audio/avdtp.c:handle_unanswered_req() No reply to Suspend request
Jan 26 16:06:54 bluetoothd[668]: src/profile.c:ext_io_disconnected() Unable to get io data for Headset Voice gateway: getpeername: Transport endpoint is not connected (107)
Jan 26 16:06:54 bluetoothd[668]: Endpoint unregistered: sender=:1.59 path=/MediaEndpoint/A2DPSink/sbc
Jan 26 16:06:54 bluetoothd[668]: Endpoint unregistered: sender=:1.59 path=/MediaEndpoint/A2DPSource/sbc
Jan 26 16:06:54 bluetoothd[668]: Stopping SDP server
Jan 26 16:06:54 bluetoothd[668]: Exit
Jan 26 16:06:54 systemd[1]: bluetooth.service: Succeeded.
Jan 26 16:06:54 systemd[1]: Stopped Bluetooth service.

This does not happen with the lts kernel, which runs fine, without any disconnects.

# pacman -Q linux-lts
linux-lts 5.4.92-1

So, I tested the following kernels one after another:

linux-5.10.1.arch1-1-x86_64.pkg.tar.zst
linux-5.9.14.arch1-1-x86_64.pkg.tar.zst
linux-5.8.14.arch1-1-x86_64.pkg.tar.zst
linux-5.7.12.arch1-1-x86_64.pkg.tar.zst
linux-5.6.15.arch1-1-x86_64.pkg.tar.zst
linux-5.5.13.arch2-1-x86_64.pkg.tar.zst

Sadly, all of the above versions are affected by this and had randomly disconnects.
So for now I'm stuck with the LTS Kernel from above, which works.

I also tried to disable various module options, which also did not help

btusb.enable_autosuspend=0
bluetooth.disable_esco=0
bluetooth.disable_ertm=0

Also disabling secure boot had no effect.

Some system info:

# lsusb

Bus 002 Device 003: ID 152d:0578 JMicron Technology Corp. / JMicron USA Technology Corp. JMS578 SATA 6Gb/s
Bus 002 Device 002: ID 17ef:1010 Lenovo ThinkPad Ultra Dock Hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 008: ID 138a:0017 Validity Sensors, Inc. VFS 5011 fingerprint sensor
Bus 001 Device 007: ID 04f2:b52c Chicony Electronics Co., Ltd Integrated Camera
Bus 001 Device 006: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
Bus 001 Device 004: ID 058f:9540 Alcor Micro Corp. AU9540 Smartcard Reader
Bus 001 Device 009: ID 04e8:328b Samsung Electronics Co., Ltd ML-1630 Series
Bus 001 Device 005: ID 17ef:100f Lenovo ThinkPad Ultra Dock Hub
Bus 001 Device 003: ID 17ef:1010 Lenovo ThinkPad Ultra Dock Hub
Bus 001 Device 002: ID 12d1:15c1 Huawei Technologies Co., Ltd. ME906s LTE M.2 Module
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
# lspci

00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers (rev 08)
00:02.0 VGA compatible controller: Intel Corporation Skylake GT2 [HD Graphics 520] (rev 07)
00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller (rev 21)
00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP Thermal subsystem (rev 21)
00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI #1 (rev 21)
00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #1 (rev f1)
00:1c.2 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #3 (rev f1)
00:1c.4 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #5 (rev f1)
00:1f.0 ISA bridge: Intel Corporation Sunrise Point-LP LPC Controller (rev 21)
00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21)
00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21)
00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21)
00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection I219-LM (rev 21)
02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS522A PCI Express Card Reader (rev 01)
04:00.0 Network controller: Intel Corporation Wireless 8260 (rev 3a)
05:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983

I'm stuck at this point. How do I track down this problem?
Any help is appreciated.

Offline

#2 2021-02-16 23:43:14

nijode999
Member
Registered: 2021-02-16
Posts: 1

Re: Random bluetooth speaker disconnects

You ever fixed this? Same problem..

Offline

#3 2021-02-18 04:08:08

alatlantic
Member
Registered: 2021-02-18
Posts: 5

Re: Random bluetooth speaker disconnects

Also following this issue. Intel Corp. AX200 Bluetooth.  My logitech bluetooth speakers just started doing this last week and drove me insane trying to fix.  Nothing in any of the wiki pages helps, and I tried it all.  It randomly disconnects, sometimes once an hour, sometimes much more often.  More frustrating, they actually often appear connected and just stop playing sound, which is hell on calls.

The closest I can figure is that it likely isn't the kernel alone.  Solus on 5.10 does -not- have this issue...which leads me to start blaming pulse perhaps?  Trying the pulse bluetooth git modules didn't help a bit, either, sadly.

Unfortunately I absolutely need to be available for calls and didn't have time to resolve, but would be interested in what is found.

Offline

#4 2021-02-18 05:56:39

Damino
Member
Registered: 2021-02-18
Posts: 8

Re: Random bluetooth speaker disconnects

I also have this issue, with an AX200. My Bluetooth headphones started disconnecting around the same time as you guys, despite working on the same kernel for weeks prior. Happens with both PulseAudio and PipeWire.

Offline

#5 2021-02-18 12:22:12

Moopy
Member
Registered: 2020-03-02
Posts: 8

Re: Random bluetooth speaker disconnects

Same issue. My headphones are Sony WH1000XM2. Started only within the last couple days. I haven't tried reverting updates yet but I suspect some update broke it.

Offline

#6 2021-02-18 18:20:57

alatlantic
Member
Registered: 2021-02-18
Posts: 5

Re: Random bluetooth speaker disconnects

I had some time today to look into it, or at least capture some info.

Here are the relevant logs when the break happens.  Actually, the log burst follows the audio cut out by about 10 seconds, if that matters.

 
Feb 18 11:45:14 hostname dbus-daemon[631]: [system] Rejected send message, 0 matched rules; type="method_return", sender=":1.57" (uid=1000 pid=1231 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.1" (uid=0 pid=630 comm="/usr/lib/bluetooth/bluetoothd ")
Feb 18 11:45:14 hostname gsd-media-keys[1439]: Unable to get default sink
Feb 18 11:45:14 hostname /usr/lib/gdm-x-session[1110]: (II) config/udev: removing device Logi Z207 (AVRCP)
Feb 18 11:45:14 hostname /usr/lib/gdm-x-session[1110]: (**) Option "fd" "54"
Feb 18 11:45:14 hostname /usr/lib/gdm-x-session[1110]: (II) event16 - Logi Z207 (AVRCP): device removed
Feb 18 11:45:14 hostname /usr/lib/gdm-x-session[1110]: (II) UnloadModule: "libinput"
Feb 18 11:45:14 hostname /usr/lib/gdm-x-session[1110]: (II) systemd-logind: releasing fd for 13:80
Feb 18 11:45:14 hostname kernel: input: Logi Z207 (AVRCP) as /devices/virtual/input/input27
Feb 18 11:45:14 hostname systemd-logind[633]: Watching system buttons on /dev/input/event16 (Logi Z207 (AVRCP))
Feb 18 11:45:14 hostname /usr/lib/gdm-x-session[1110]: (II) config/udev: Adding input device Logi Z207 (AVRCP) (/dev/input/event16)
Feb 18 11:45:14 hostname /usr/lib/gdm-x-session[1110]: (**) Logi Z207 (AVRCP): Applying InputClass "libinput keyboard catchall"
Feb 18 11:45:14 hostname /usr/lib/gdm-x-session[1110]: (II) Using input driver 'libinput' for 'Logi Z207 (AVRCP)'
Feb 18 11:45:14 hostname /usr/lib/gdm-x-session[1110]: (II) systemd-logind: got fd for /dev/input/event16 13:80 fd 54 paused 0
Feb 18 11:45:14 hostname /usr/lib/gdm-x-session[1110]: (**) Logi Z207 (AVRCP): always reports core events
Feb 18 11:45:14 hostname /usr/lib/gdm-x-session[1110]: (**) Option "Device" "/dev/input/event16"
Feb 18 11:45:14 hostname /usr/lib/gdm-x-session[1110]: (**) Option "_source" "server/udev"
Feb 18 11:45:14 hostname /usr/lib/gdm-x-session[1110]: (II) event16 - Logi Z207 (AVRCP): is tagged by udev as: Keyboard
Feb 18 11:45:14 hostname /usr/lib/gdm-x-session[1110]: (II) event16 - Logi Z207 (AVRCP): device is a keyboard
Feb 18 11:45:14 hostname /usr/lib/gdm-x-session[1110]: (II) event16 - Logi Z207 (AVRCP): device removed
Feb 18 11:45:14 hostname /usr/lib/gdm-x-session[1110]: (**) Option "config_info" "udev:/sys/devices/virtual/input/input27/event16"
Feb 18 11:45:14 hostname /usr/lib/gdm-x-session[1110]: (II) XINPUT: Adding extended input device "Logi Z207 (AVRCP)" (type: KEYBOARD, id 16)
Feb 18 11:45:14 hostname /usr/lib/gdm-x-session[1110]: (II) event16 - Logi Z207 (AVRCP): is tagged by udev as: Keyboard
Feb 18 11:45:14 hostname /usr/lib/gdm-x-session[1110]: (II) event16 - Logi Z207 (AVRCP): device is a keyboard

I downgraded bluez from 5.55-2 to 5.55-1 and so far has been running uninterrupted for about an hour, which is a new record for this week.  Will update later today if it holds up.
(fresh install, so shouldn't be some old file/setting stuck)

Edit - I was streaming music for 3 hours uninterrupted, then it happened again sad.  Seems this isn't the fix either.

Last edited by alatlantic (2021-02-18 20:30:43)

Offline

#7 2021-02-18 19:51:44

Damino
Member
Registered: 2021-02-18
Posts: 8

Re: Random bluetooth speaker disconnects

I can confirm that BlueZ 5.55-1 does not fix the issue for me.

Offline

#8 2021-02-18 21:06:16

Damino
Member
Registered: 2021-02-18
Posts: 8

Re: Random bluetooth speaker disconnects

I can't reboot my PC right now, but I wonder if anyone having issues recently (myself included) would benefit from downgrading the linux-firmware package.
Looks like there was an update for the AX200 10 days ago.

Offline

#9 2021-02-18 21:45:34

alatlantic
Member
Registered: 2021-02-18
Posts: 5

Re: Random bluetooth speaker disconnects

Damino wrote:

I can't reboot my PC right now, but I wonder if anyone having issues recently (myself included) would benefit from downgrading the linux-firmware package.
Looks like there was an update for the AX200 10 days ago.

Downgraded to linux-firmware-20201218.646f159-1 and put bluez back.  Will report if I find anything.

Edit:
1.5 days, zero disconnects - this definitely fixed it for me.  Thank you!

Last edited by alatlantic (2021-02-19 22:20:58)

Offline

#10 2021-02-19 00:43:07

aldeano
Member
Registered: 2009-09-04
Posts: 30

Re: Random bluetooth speaker disconnects

I also got this problem with pipewire and bluetooth.

Journalctl at the moment of the disconnect shows this:

pipewire-media-session[1077]: a2dp-sink 0x5570f565da88: error 24
plasmashell[852]: org.kde.plasma.pulseaudio: No object for name "bluez_input.08:EB:ED:AD:45:83.a2dp-sink"

sudo journalctl shows this

pipewire-media-session[1077]: a2dp-sink 0x5570f565da88: error 24
dbus-daemon[440]: [system] Rejected send message, 0 matched rules; type="method_return", sender=":1.50" (uid=1000 pid=1077 comm="/usr/bin/pipewire-media-session ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.3" (uid=0 pid=454 comm="/usr/lib/bluetooth/bluetoothd ")
plasmashell[852]: org.kde.plasma.pulseaudio: No object for name "bluez_input.08:EB:ED:AD:83.a2dp-sink"
bluetoothd[454]: src/profile.c:ext_io_disconnected() Unable to get io data for Hands-Free Voice gateway: getpeername: Transport endpoint is not connected (107)
bluetoothd[454]: profiles/audio/avdtp.c:cancel_request() Open: Operation canceled (125)
bluetoothd[454]: profiles/audio/avdtp.c:cancel_request() Open: Operation canceled (125)
dbus-daemon[440]: [system] Rejected send message, 0 matched rules; type="method_return", sender=":1.50" (uid=1000 pid=1077 comm="/usr/bin/pipewire-media-session ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.3" (uid=0 pid=454 comm="/usr/lib/bluetooth/bluetoothd ")
pipewire-media-session[1077]: bluez5-device: failed to switch codec (-19), setting fallback profile

Using plasma 5.21.0-1, pipewire and pipewire-pulse 0.3.21-1

Last edited by aldeano (2021-02-19 00:44:03)

Offline

#11 2021-02-19 00:51:42

Damino
Member
Registered: 2021-02-18
Posts: 8

Re: Random bluetooth speaker disconnects

I was able to reboot. I've been running for 80 minutes with downgraded firmware and my audio just cut out for 5-10 seconds.
That being said, it came back without disconnecting, and my logs don't indicate any problems. Maybe I can rest easy and consider that a separate issue, as I'm using the Git versions of PipeWire from the AUR.

EDIT: With both repo and AUR PipeWire, my headphones still disconnect. Seems the downgraded firmware doesn't fix anything.
EDIT 2: After 3.5 hours, PulseAudio also disconnects.

Last edited by Damino (2021-02-19 05:13:19)

Offline

#12 2021-02-19 15:26:40

TheStrix
Member
Registered: 2021-02-19
Posts: 1

Re: Random bluetooth speaker disconnects

Can confirm the issue, fixed it temporarily by downgrading linux-firmware (20210208.b79d239-1 -> 20201218.646f159-1).
Have been using my Sony WH1000XM4 with AX200 for a long time now, seems to not disconnect now.

Offline

#13 2021-02-20 00:14:44

Damino
Member
Registered: 2021-02-18
Posts: 8

Re: Random bluetooth speaker disconnects

I've been going a few hours today with no problems. Here's my list of downgrades:

  • linux-firmware: 20201218.646f159-1

  • pipewire, pipewire-pulse, pipewire-alsa, pipewire-jack: 1:0.3.20-1

  • bluez, bluez-libs: 5.50-7

  • gst-plugin-pipewire: 1:0.3.20-1

  • alsa-card-profiles: 1:0.3.20-1

Not sure if all of these are relevant, but I'll try to incrementally upgrade and see what happens.

Update: I've upgraded the pipewire and bluez packages to their current repo versions, and have gone the day without disconnecting.

Update 2: I've upgraded everything but linux-firmware to their current repo versions and have been using my headphones flawlessly for over 5 hours so far.

Last edited by Damino (2021-02-21 01:11:47)

Offline

#14 2021-02-20 19:17:34

aldeano
Member
Registered: 2009-09-04
Posts: 30

Re: Random bluetooth speaker disconnects

i've tried with the new pipewire 0.3.22-1 and another bluetooth speaker, same random disconnects.

journalctl

pipewire-media-session[1113]: a2dp-sink 0x55b5eaee7f88: error 24
pipewire-media-session[1113]: Failed to release transport /org/bluez/hci0/dev_E8_07_BF_12_20_A4/sep1/fd2: Method "Release" with signature "" on interface "org.bluez.MediaTransport1" doesn't exist
kdeconnectd[885]: org.kde.pulseaudio: No object for name "bluez_output.E8_07_BF_12_20_A4.a2dp-sink"
plasmashell[863]: qrc:/plasma/plasmoids/org.kde.plasma.volume/contents/ui/ListItemBase.qml:153: TypeError: Value is undefined and could not be converted to an object
plasmashell[863]: qrc:/plasma/plasmoids/org.kde.plasma.volume/contents/ui/ListItemBase.qml:153: TypeError: Value is undefined and could not be converted to an object
plasmashell[863]: org.kde.plasma.pulseaudio: No object for name "bluez_output.E8_07_BF_12_20_A4.a2dp-sink"

sudo journalctl

pipewire-media-session[1113]: a2dp-sink 0x55b5eaee7f88: error 24
bluetoothd[490]: src/profile.c:ext_io_disconnected() Unable to get io data for Hands-Free Voice gateway: getpeername: Transport endpoint is not connected (107)
pipewire-media-session[1113]: Failed to release transport /org/bluez/hci0/dev_E8_07_BF_12_20_A4/sep1/fd2: Method "Release" with signature "" on interface "org.bluez.MediaTransport1" doesn't exist
dbus-daemon[444]: [system] Rejected send message, 0 matched rules; type="method_return", sender=":1.50" (uid=1000 pid=1113 comm="/usr/bin/pipewire-media-session ") interface="(unset)" member="(unset)" error n>
kdeconnectd[885]: org.kde.pulseaudio: No object for name "bluez_output.E8_07_BF_12_20_A4.a2dp-sink"
plasmashell[863]: qrc:/plasma/plasmoids/org.kde.plasma.volume/contents/ui/ListItemBase.qml:153: TypeError: Value is undefined and could not be converted to an object
plasmashell[863]: qrc:/plasma/plasmoids/org.kde.plasma.volume/contents/ui/ListItemBase.qml:153: TypeError: Value is undefined and could not be converted to an object
plasmashell[863]: org.kde.plasma.pulseaudio: No object for name "bluez_output.E8_07_BF_12_20_A4.a2dp-sink"

At the moment of reconnect:

bluetoothd[490]: /org/bluez/hci0/dev_E8_07_BF_12_20_A4/sep1/fd3: fd(53) ready
kernel: input: NO Bounds (AVRCP) as /devices/virtual/input/input23
systemd-logind[458]: Watching system buttons on /dev/input/event18 (NO Bounds (AVRCP))

Offline

#15 2021-02-25 04:30:58

jocheem67
Member
Registered: 2009-11-09
Posts: 243

Re: Random bluetooth speaker disconnects

Same here, with intel AX200and EDIFIER speakers

04:00.0 Network controller: Intel Corporation Wi-Fi 6 AX200 (rev 1a)
	Subsystem: Intel Corporation Device 0084
	Physical Slot: 0
	Flags: bus master, fast devsel, latency 0, IRQ 69, IOMMU group 12
	Memory at d0600000 (64-bit, non-prefetchable) [size=16K]
	Capabilities: [c8] Power Management version 3
	Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+
	Capabilities: [40] Express Endpoint, MSI 00
	Capabilities: [80] MSI-X: Enable+ Count=16 Masked-
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [14c] Latency Tolerance Reporting
	Capabilities: [154] L1 PM Substates
	Kernel driver in use: iwlwifi
	Kernel modules: iwlwifi

Journal with disconnect message, pretty much the same as others:

Feb 20 19:47:54 lenovo dbus-daemon[626]: [system] Rejected send message, 0 matched rules; type="method_return", sender=":1.55" (uid=1000 pid=1711 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.14" (uid=0 pid=727 comm="/usr/lib/bluetooth/bluetoothd ")

I'm wondering if anyone knows what this message is actually telling us?

What did I try?

* I think I ruled out pulse as part of the problem by playing internet radio with

 mpv --ao=alsa 

-> same disconnects

* I disabled GDM and am starting xfce through Xinit -> this seems to help. I have to check on timings for disconnects. It happened about every 15 minutes and that's much better now
* I'm using the LTS kernel and sometimes switch to regular, with no noticeable difference
* I' m using Audacious now instead of MPD with a bigger than standard buffersize and started from CLI with

 audacious -V 

-> have to check this beter than I did 'till now

[EDIT]

There has indeed been some changes regarding bluetooth with the 08-02 linux-firmware for the AX200 chip as stated above. It's kind of safe to assume that that would give us the issues. Reading the posts above a bit better now, all other possible causes are too diverse, I feel. I' m actually not sure how to address this (bug report), anyone does?

Last edited by jocheem67 (2021-02-25 04:47:04)

Offline

#16 2021-02-25 21:52:44

alatlantic
Member
Registered: 2021-02-18
Posts: 5

Re: Random bluetooth speaker disconnects

As an update...since both Linux and bluez updated recently, I went ahead and updated linux-firmware.  No disconnects so far, so that may have been a red herring.

Offline

#17 2021-02-26 05:48:43

Megarock90
Member
Registered: 2012-01-18
Posts: 37

Re: Random bluetooth speaker disconnects

Same symptoms on the same AX200 board with some Avantree headphones. Downgrading the firmware package to 20201218 helped.

Offline

#18 2021-02-26 15:58:20

larntz
Member
Registered: 2021-02-26
Posts: 2

Re: Random bluetooth speaker disconnects

I'm also having this issue with an AX200, and it just started within the past few weeks.  I downgraded linux-firmware (20201218.646f159-1) but it did not fix the issue.

My journalctl output looks similar to others also.

Feb 26 10:45:48 desktop dbus-daemon[296]: [system] Rejected send message, 0 matched rules; type="method_return", sender=":1.79" (uid=1000 pid=1094 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.18" (uid=0 pid=402 comm="/usr/lib/bluetooth/bluetoothd ")
Feb 26 10:45:51 desktop bluetoothd[402]: /org/bluez/hci0/dev_88_D0_39_97_9B_09/sep1/fd4: fd(39) ready

Offline

#19 2021-02-26 18:09:55

mudkipz
Member
Registered: 2021-01-11
Posts: 2

Re: Random bluetooth speaker disconnects

I had the same issue beginning with the latest full system upgrade. I downgraded both linux and linux-firmware and it resolved the issue for me so far. I went to version

linux-firmware-20201218.646f159-1
linux-5.10.12.arch1-1

edit: It looks like only linux-firmware needed to be downgraded. No reason to downgrade the kernel as well.

Last edited by mudkipz (2021-03-02 17:53:33)

Offline

#20 2021-02-28 02:02:07

Megarock90
Member
Registered: 2012-01-18
Posts: 37

Re: Random bluetooth speaker disconnects

So after reading https://bbs.archlinux.org/viewtopic.php?id=264066 and updating the kernel to 5.11.2 (zen build) I decided to try and upgrade the firmware as well.
I'm currently into about 2 hours of uninterrupted playback.

Edit:
Aaaaand just happened again. Unrelated from the kernel then, downgrading the firmware again.

Last edited by Megarock90 (2021-03-03 04:00:18)

Offline

#21 2021-03-01 01:21:48

filotek
Member
Registered: 2018-08-15
Posts: 19

Re: Random bluetooth speaker disconnects

I'm so glad I've found this thread.  I only use my bluetooth earbuds sparingly but noticed throughout the last couple weeks that my earbuds would randomly disconnect (multiple times a day).

After having downgraded the linux-firmware package to the previous version (20201218.646f159-1) I haven't had any issues since -- (Lenovo T14s with Intel AX201 chipset for bluetooth).

Not sure yet where to report linux-firmware bugs.  Also not sure I have enough for a bug report ?

Offline

#22 2021-03-04 01:31:39

tombh
Member
Registered: 2021-02-28
Posts: 4

Re: Random bluetooth speaker disconnects

Unfortunately I've not had success with the downgrade to linux-firmware (20201218.646f159-1), I'm on a Dell XPS 13 from 2020, chipset is AX1650i. Though I'm still on the latest kernel 5.11.2.arch1-1

Offline

#23 2021-03-04 12:48:54

larntz
Member
Registered: 2021-02-26
Posts: 2

Re: Random bluetooth speaker disconnects

larntz wrote:

I'm also having this issue with an AX200, and it just started within the past few weeks.  I downgraded linux-firmware (20201218.646f159-1) but it did not fix the issue.

My journalctl output looks similar to others also.

Feb 26 10:45:48 desktop dbus-daemon[296]: [system] Rejected send message, 0 matched rules; type="method_return", sender=":1.79" (uid=1000 pid=1094 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.18" (uid=0 pid=402 comm="/usr/lib/bluetooth/bluetoothd ")
Feb 26 10:45:51 desktop bluetoothd[402]: /org/bluez/hci0/dev_88_D0_39_97_9B_09/sep1/fd4: fd(39) ready

For the past few days I've been on linux-lts kernel 5.10.19-1-lts and linux-firmware 20201218.646f159-1 and I've only had 1 disconnect.  I tried the newest version of linux-firmware and my bluetooth speakers wouldn't connect at all so I downgraded again.

Offline

#24 2021-03-05 15:27:49

4johnny
Member
Registered: 2021-03-05
Posts: 12

Re: Random bluetooth speaker disconnects

I've downgraded my system by following the arch wiki archive guide: https://wiki.archlinux.org/index.php/Ar … cific_date
My mirrorlist file now looks like this (Note: I also had to disable signature checking: https://wiki.archlinux.org/index.php/Pa … _checking):

/etc/pacman.d/mirrorlist

Server=https://archive.archlinux.org/repos/2020/12/16/$repo/os/$arch

Note the date I've used is set to "2020/12/16", I previously tried setting it to "2020/12/31" but that didn't solve the issue for me, though it seemed to happen less often... (I suspect that version 20201218... already contained the issue?)!
My linux packages are now the following:

local/linux 5.9.14.arch1-1
    The Linux kernel and modules
local/linux-api-headers 5.8-1
    Kernel headers sanitized for use in userspace
local/linux-firmware 20201120.bc9cd0b-1
    Firmware files for Linux
local/linux-headers 5.9.14.arch1-1
    Headers and scripts for building modules for the Linux kernel
local/linux-lts-headers 5.4.83-1
    Headers and scripts for building modules for the LTS Linux kernel

I did this action 3-4 days ago and haven't had a disconnect since.

Offline

#25 2021-03-11 11:56:27

cars10
Member
Registered: 2014-03-11
Posts: 27

Re: Random bluetooth speaker disconnects

Downgrading to linux-firmware 20201218.r1803.646f159-1 did not fix the issue for me. Using an AX200 Wifi Card with bluetooth and wireless bluetooth headphones.

Offline

Board footer

Powered by FluxBB