Bluetooth connection to headset works for volume buttons but not tests
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
bluez (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
bluetooth worked fine under 19.10.
Now, when bluetooth connects to my headset, I can hear noises from the increase/ decrease volume keys, but the "test" for Output Device in Sound settings makes sound on my laptop, not the headset.
And all applications send sound to the laptop, not the headset.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: bluetooth (not installed)
ProcVersionSign
Uname: Linux 5.4.0-28-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckR
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 30 19:39:09 2020
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-11-26 (156 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: LENOVO 20BX001PUS
ProcKernelCmdLine: BOOT_IMAGE=
SourcePackage: bluez
UpgradeStatus: Upgraded to focal on 2020-04-26 (4 days ago)
dmi.bios.date: 09/13/2017
dmi.bios.vendor: LENOVO
dmi.bios.version: JBET66WW (1.30 )
dmi.board.
dmi.board.name: 20BX001PUS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0E50510 WIN
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.
dmi.modalias: dmi:bvnLENOVO:
dmi.product.family: ThinkPad T450s
dmi.product.name: 20BX001PUS
dmi.product.sku: LENOVO_
dmi.product.
dmi.sys.vendor: LENOVO
hciconfig:
hci0: Type: Primary Bus: USB
BD Address: DC:53:60:42:C0:97 ACL MTU: 1021:5 SCO MTU: 96:6
UP RUNNING
RX bytes:22321 acl:74 sco:0 events:1206 errors:0
TX bytes:257018 acl:319 sco:0 commands:403 errors:0
syslog:
Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1866194, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.