[MediaTek 0e8d:0616] Logitech MX Master 3S and MX Keys S cannot connect via Bluetooth after every restart
This bug report will be marked for expiration in 49 days if no further activity occurs. (find out why)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Incomplete
|
Undecided
|
Unassigned |
Bug Description
Since the beginning of the week I've been experiencing a weird bug - my Bluetooth mouse and keyboard, Logitech MX Keys S and MX Master 3S lose connectivity to Ubuntu via Bluetooth after every restart of the system.
The mouse connects and disconnects multiple times per second, while the keyboard cannot connect at all, even when trying to manually connect via Bluetooth settings page.
This makes me unpair and repair the devices again and it works until the next restart.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: bluez 5.72-0ubuntu5
ProcVersionSign
Uname: Linux 6.8.0-38-generic x86_64
ApportVersion: 2.28.1-0ubuntu3
Architecture: amd64
CasperMD5CheckR
Date: Wed Jul 24 09:02:22 2024
ExecutablePath: /usr/libexec/
InstallationDate: Installed on 2024-05-22 (63 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: ASRock X670E Steel Legend
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/13/2024
dmi.bios.release: 5.32
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: 3.01
dmi.board.
dmi.board.name: X670E Steel Legend
dmi.board.vendor: ASRock
dmi.board.version: Default string
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.family: Default string
dmi.product.name: X670E Steel Legend
dmi.product.sku: Default string
dmi.product.
dmi.sys.vendor: ASRock
hciconfig:
hci0: Type: Primary Bus: USB
BD Address: A8:3B:76:4E:D9:74 ACL MTU: 1021:6 SCO MTU: 240:8
UP RUNNING PSCAN
RX bytes:248200 acl:11130 sco:0 events:1679 errors:0
TX bytes:22457 acl:551 sco:0 commands:218 errors:0
Changed in linux (Ubuntu): | |
status: | New → Incomplete |
BlueZ hasn't changed in almost 4 months so it probably doesn't make sense to assign the bug there if it's only started this week.
What has changed in the last couple of weeks is the kernel, if not hardware/ environmental conditions...