[MediaTek 0e8d:0616] Logitech MX Master 3S and MX Keys S cannot connect via Bluetooth after every restart

Bug #2073947 reported by George Salukvadze

This bug report will be marked for expiration in 49 days if no further activity occurs. (find out why)

8
This bug affects 1 person
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
ProcVersionSignature: Ubuntu 6.8.0-38.38-generic 6.8.8
Uname: Linux 6.8.0-38-generic x86_64
ApportVersion: 2.28.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
Date: Wed Jul 24 09:02:22 2024
ExecutablePath: /usr/libexec/bluetooth/bluetoothd
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=/boot/vmlinuz-6.8.0-38-generic root=UUID=bb2b1552-447b-4184-8136-fdba0f9b165d ro quiet splash vt.handoff=7
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.asset.tag: Default string
dmi.board.name: X670E Steel Legend
dmi.board.vendor: ASRock
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr3.01:bd05/13/2024:br5.32:svnASRock:pnX670ESteelLegend:pvrDefaultstring:rvnASRock:rnX670ESteelLegend:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: X670E Steel Legend
dmi.product.sku: Default string
dmi.product.version: Default string
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

Revision history for this message
George Salukvadze (giosal90) wrote :
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

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...

affects: bluez (Ubuntu) → linux (Ubuntu)
summary: - Logitech MX Master 3S and MX Keys S cannot connect via Bluetooth after
- every restart
+ [MediaTek 0e8d:0616] Logitech MX Master 3S and MX Keys S cannot connect
+ via Bluetooth after every restart
Revision history for this message
George Salukvadze (giosal90) wrote :

@vanvugt. thank you for your reply and my apologies for assigning the bug incorrectly, I wasn't aware of the fact the BlueZ hasn't changed.

Any suggestions as for which steps I could undertake in order to debug the issue and try to find the actual reason?

Thank you

Revision history for this message
AaronMa (mapengyu) wrote :

@giosal90

Could you confirm the last kernel version that was working?

There are no changes for mediatek firmware or bluetooth in kernel.

AaronMa (mapengyu)
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
George Salukvadze (giosal90) wrote :

Hello, @mapengyu,

I assume it was 6.8.0-36 as it's the previous kernel installed.

I have a feeling that it even worked on the 6.8.0-38 that I have now. I'm trying to upgrade to 6.8.0-39 that just arrived as an update and will report back as soon as I do

Revision history for this message
George Salukvadze (giosal90) wrote :

I still have the same issue.
Please see attached video that show the connection/disconnections when moving my Bluetooth mouse that tries to reconnect to my computer

Revision history for this message
AaronMa (mapengyu) wrote :

The video clip in #6 is not able to download, could you change the file name to english, and upload again?

Could you try 6.8.0-36 to confirm if it's a regression of 6.8.0-38?

Thanks.

Revision history for this message
George Salukvadze (giosal90) wrote (last edit ):

I'll have to install 6.8.0-36 in order to do so as it was already removed from my system.

Meanwhile, here's the recording with a changed name.

Revision history for this message
George Salukvadze (giosal90) wrote :

I've installed the kernel version in question, but I don't have any drivers installed when I boot using this kernel.
So I must have done something wrong, still need to check out how to properly install the kernel

Revision history for this message
George Salukvadze (giosal90) wrote :

Could you please be so kind to direct me towards instructions on how to install the specific version of the kernel with the drivers ?

Because I've tried to install 6.8.0-36 but there were no drivers at all, neither for display, nor for sound or Bluetooth or WiFi.

Revision history for this message
George Salukvadze (giosal90) wrote :

The bug is still present in 6.8.0-40

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.