Ubuntu
linux package

[Intel 9260] apps use speakers when bluetooth headset is active (regression in kernel 5.0, but 5.2 works)

Bug #1838180 reported by jimav on 2019-07-28

This bug affects 1 person

	Status	Importance	Assigned to
bluez (Ubuntu)	Invalid	Undecided	Unassigned
linux (Ubuntu)	Confirmed	Undecided	Unassigned
pulseaudio (Ubuntu)	Invalid	Undecided	Unassigned

Bug Description

Bluetooth headset stopped working after upgrading to 19.04. Worked perfectly with 18.10.

Now, when a BT headset is connected the volume-control widget (seen via the speaker icon in the upper-right corner) displays a headset icon and a volume slider, but the slider has NO EFRFECT on volume and sound still comes out of the speakers.

It seems like the BT headset is active as far as the volume-control GUI knows, BUT sound from apps still goes to the speakers (which were active before the BT headset connected).

syslog shows: bluetoothd[1423]: connect error: Device or resource busy (16)

I will attach the full syslog

The problem does not occur with a wired headset.

STEPS TO REPRODUCE:
1. Reboot
   Turn Bluetooth OFF (speakericon->BTicon->Turn Off)
2. Start Rhythmbox or other sound source; play something, set the volume low but audible
    (should be heard on speakers)
3. Turn on a Bluetoogh headset
4. Turn on Bluetooth in the computer (Speakericon->BTicon->Turn On)
    If necessary, do other stuff to get the BT headset connected
   A "headset icon" should appear next the volume slider (click speaker icon to see it)

RESULTS: Sound continues to come out of speakers; nothing from BT headset
Moving the volume slider has no effect

EXPECTED RESULTS: Switch sound to the BT headset

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: bluez 5.50-0ubuntu2
ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15
Uname: Linux 5.0.0-21-generic x86_64
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Jul 27 22:59:01 2019
InstallationDate: Installed on 2018-04-05 (479 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180403.1)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-21-generic root=UUID=7c21c040-30e8-456e-bcd9-5f4bcfc2fc92 ro quiet splash vt.handoff=1
SourcePackage: bluez
UpgradeStatus: Upgraded to disco on 2019-07-26 (2 days ago)
dmi.bios.date: 12/01/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0605
dmi.board.asset.tag: Default string
dmi.board.name: PRIME Z370-A
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.:bvr0605:bd12/01/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ370-A: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
hciconfig:
hci0: Type: Primary Bus: USB
  BD Address: 48:89:E7:CF:4F:FD ACL MTU: 1021:4 SCO MTU: 96:6
  UP RUNNING PSCAN ISCAN INQUIRY
  RX bytes:14153 acl:154 sco:0 events:971 errors:0
  TX bytes:429273 acl:643 sco:0 commands:229 errors:0

Tags:

Revision history for this message

jimav (james-avera) wrote on 2019-07-28:

syslog Edit (33.7 KiB, text/plain)
CurrentDmesg.txt Edit (68.5 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (2.1 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (12.4 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (464 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (15.3 KiB, text/plain; charset="utf-8")
ProcCpuinfoMinimal.txt Edit (1.3 KiB, text/plain; charset="utf-8")
ProcEnviron.txt Edit (110 bytes, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (12.4 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (6.1 KiB, text/plain; charset="utf-8")
UdevDb.txt Edit (258.8 KiB, text/plain; charset="utf-8")
getfacl.txt Edit (159 bytes, text/plain; charset="utf-8")
rfkill.txt Edit (113 bytes, text/plain; charset="utf-8")
syslog.txt Edit (2.9 KiB, text/plain; charset="utf-8")

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2019-07-29:

The strange thing here is that 18.10 and 19.04 use the same versions of bluez and pulseaudio. So I don't think those are going to be the problem.

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2019-07-29:

It sounds like the log messages relating to the issue are:

  Jul 27 22:54:49 hostname gsd-media-keys[2755]: Unable to get default sink
  ...
  Jul 27 22:55:04 hostname bluetoothd[1423]: Unable to get Headset Voice gateway SDP record: Device or resource busy
  Jul 27 22:55:04 hostname bluetoothd[1423]: connect error: Device or resource busy (16)

Which suggests it's the kernel that's behaving differently, via PulseAudio.

Please try some newer (or older) kernels from:

https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D

and tell us which versions, if any, avoid the bug.

Changed in bluez (Ubuntu):
status:	New → Incomplete
Changed in linux (Ubuntu):
status:	New → Incomplete
Changed in pulseaudio (Ubuntu):
status:	New → Incomplete

Revision history for this message

jimav (james-avera) wrote on 2019-07-29:

Ok, the mis-directed output seems to be fixed with a kernel 5.2.

With the stock 5.0.0-21-generic, disconnecting BT in the Ubuntu gui does not actually disconnect immediately. Instead, the disconnect happens when BT is turned ON again in the gui!

(based on my BT headset's synthesized status-change messages, which say nothing when BT is turned OFF in the gui, but say "disconnected" when BT is turned ON in the gui).

Thereafter, sound goes to the speakers even though the gui shows the BT headset is connected. I found that power-cycling the headset clears the problem, presumably because of the extraneous connection messages when the headset comes back on.

These problem COMPLETELY GO AWAY with kernel 5.2 installed. Now, when I disconnect the headset in the Ubuntu gui, the headset instantly reports being disconnected, and it re-connects propertly when the headset is turned on again in the Ubuntu gui.

There are some remaining gui issues where the switch in the gui snaps back by itself to "off" on the first few tries, but after a while the headset connects correctly. I will file a different bugrep about that with a video.

In conclusion, it sounds like some kernel bug or api mis-match will be resolved with kernel 5.2, but that won't be shipped for while in Ubuntu. ]

Daniel van Vugt (vanvugt) on 2019-07-29

Changed in linux (Ubuntu):
status:	Incomplete → Confirmed
Changed in bluez (Ubuntu):
status:	Incomplete → Invalid
Changed in pulseaudio (Ubuntu):
status:	Incomplete → Invalid
summary:	- apps use speakers when bluetooth headset is active (REGRESSION) + apps use speakers when bluetooth headset is active (regression in kernel + 5.0, but 5.2 works)
summary:	- apps use speakers when bluetooth headset is active (regression in kernel - 5.0, but 5.2 works) + [Intel 9260] apps use speakers when bluetooth headset is active + (regression in kernel 5.0, but 5.2 works)
tags:	added: bluetooth
tags:	added: regression-release

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

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

Ubuntulinux package

[Intel 9260] apps use speakers when bluetooth headset is active (regression in kernel 5.0, but 5.2 works)

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
linux package