[mt7921e] Cannot turn Bluetooth on in Ubuntu 22.04.01

[Alexandru Bolboaca]

The steps:

* Going to settings -> Bluetooth
* Turn Bluetooth on. Seems to stay on, but can't connect anything to it
* Go to another place in Settings, go back to Bluetooth
* Result: Bluetooth is turned off

Thank you!
Alex

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: bluez 5.64-0ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
Uname: Linux 5.15.0-47-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep 6 11:52:13 2022
InstallationDate: Installed on 2022-06-16 (81 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
InterestingModules: bnep btusb bluetooth
MachineType: ASUSTeK COMPUTER INC. ROG Flow X13 GV301RE_GV301RE
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-47-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/24/2022
dmi.bios.release: 5.24
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: GV301RE.313
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: GV301RE
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 31
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.ec.firmware.release: 3.8
dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrGV301RE.313:bd03/24/2022:br5.24:efr3.8:svnASUSTeKCOMPUTERINC.:pnROGFlowX13GV301RE_GV301RE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGV301RE:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:sku:
dmi.product.family: ROG Flow X13
dmi.product.name: ROG Flow X13 GV301RE_GV301RE
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
hciconfig:
 hci0: Type: Primary Bus: USB
  BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0
  DOWN
  RX bytes:0 acl:0 sco:0 events:0 errors:0
  TX bytes:3 acl:0 sco:0 commands:1 errors:0

[Daniel van Vugt (vanvugt)]

Being machine-specific means this is almost certainly a kernel bug.

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This change was made by a bot.