Bluetooth WH-1000XM3 headphones disconnects and reconnects

Bug #1929326 reported by Per Larsson
28
This bug affects 5 people
Affects Status Importance Assigned to Milestone
alsa-driver (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

From time to time, my Sony WH-1000XM3 Bluetooth connected headphones automatically disconnect, and then a couple of seconds later reconnects. This started happening after updating Ubuntu from 20.10 to 21.04. This never happened even once when using Ubuntu 20.10, and the headphones are not used or paired to any other device. The only device that has had any changes to it is the computer which is now running Ubuntu 21.04.

It is currently using a custom kernel from https://kernel.ubuntu.com/~kernel-ppa/mainline/ in an attempt to see if that would mitigate the problem. It did not. The issue started to happen when the Ubuntu 21.04 system was running its default kernel.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: alsa-base 1.0.25+dfsg-0ubuntu7
Uname: Linux 5.12.4-051204-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu65
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: per 2734 F.... pulseaudio
 /dev/snd/controlC2: per 2734 F.... pulseaudio
 /dev/snd/controlC0: per 2734 F.... pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sun May 23 12:58:22 2021
InstallationDate: Installed on 2018-11-26 (908 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_Card: WH-1000XM3
Symptom_PulseAudioLog:
 maj 23 11:33:04 perdator systemd[1473]: pulseaudio.service: Succeeded.
 maj 23 11:33:14 perdator systemd[1473]: pulseaudio.socket: Succeeded.
 maj 23 12:35:05 perdator dbus-daemon[1151]: [system] Rejected send message, 0 matched rules; type="method_return", sender=":1.79" (uid=1000 pid=2734 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.5" (uid=0 pid=1147 comm="/usr/lib/bluetooth/bluetoothd ")
 maj 23 12:54:15 perdator dbus-daemon[1151]: [system] Rejected send message, 0 matched rules; type="method_return", sender=":1.79" (uid=1000 pid=2734 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.5" (uid=0 pid=1147 comm="/usr/lib/bluetooth/bluetoothd ")
Symptom_Type: Sound works for a while, then breaks
Title: [WH-1000XM3, playback] fails after a while
UpgradeStatus: Upgraded to hirsute on 2021-05-10 (13 days ago)
dmi.bios.date: 03/11/2021
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5843
dmi.board.asset.tag: Default string
dmi.board.name: ROG STRIX X470-F GAMING
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5843:bd03/11/2021:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXX470-FGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

Revision history for this message
Per Larsson (albatorsk) wrote :
Revision history for this message
Per Larsson (albatorsk) wrote :
affects: ubuntu → alsa-driver (Ubuntu)
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in alsa-driver (Ubuntu):
status: New → Confirmed
Revision history for this message
Dawid Dworak (dawid-dworak) wrote :

Can confirm this on Bose QuietComfort 35 II starting with similar "Rejected send message" entry in journalctl.

Revision history for this message
Per Larsson (albatorsk) wrote :

This appears to be related to a problem with the firmware for the Intel AX200 bluetooth adapter. After installing the linux-firmware package for Ubuntu 21.10, downloaded from https://launchpad.net/ubuntu/+source/linux-firmware/1.198, which contains an updated firmware for that adapter, the problem seems to have gone away. A full power cycle of the computer was required for the firmware to load, not a simple reboot.

I have not done extensive testing since installing the updated linux-firmware package 2 days ago, but I have not since been able to reproduce the problem.

Revision history for this message
jixbo (jixbo) wrote :

I have been having this issue, with an Intel AX200 bluetooth adapter. I got bluetooth disconnected temporarily when 2 devices were connected at the same time, an audio device and a logitech mouse.

Just tried updating the firmware as @albatorsk recommended and the issue is fixed. Thank you!
Hopefully this comes as a regular update soon.

Revision history for this message
Victor Conner (creativecreature) wrote :

Hi, sorry for asking such a simple question, but how would one go about installing that driver package? I'm new to Ubuntu and Linux, but I'm facing the same issue. My headphones disconnect every hour or so.

Revision history for this message
Per Larsson (albatorsk) wrote :

You can do one of two things;

1. Wait for Ubuntu 21.10 to be released and upgrade to that version. That will install the new firmware package automatically.

or

1. Download this file: https://launchpad.net/ubuntu/+source/linux-firmware/1.198/+build/21596077/+files/linux-firmware_1.198_all.deb
2a. Install it by double-clicking on it in a file manager.
or
2b. If you're comfortable using the terminal or a command shell, you can type in the command "sudo dpkg -i /path_to_download_folder/linux-firmware_1.198_all.deb" to accomplish the same thing.
3. You will need to completely power off your computer and power it back on again after the firmware package is installed. A simple reboot is not enough.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.