Bluez Utilities

[regression] Logitech M337 mice are automatically disconnected after connected

Bug #1773897 reported by Leon Liao
42
This bug affects 8 people
Affects Status Importance Assigned to Milestone
Bluez Utilities
Confirmed
Medium
OEM Priority Project
Incomplete
Medium
Unassigned
bluez (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

The BT 3.0 mouse is disconnected automatically after connected with the notebook.
The fail rate is around 9/10.

1. The bug only occurs on the machine with intel 8265 module.
 I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265).
 This bug can not be reproduced on the machine with Killer 1435.

2. This bug can be reproduced since bluez 5.46.
 Using bluez 5.45, this bug can not be reproduced.

Notebook: Dell XPS 13
Wi-Fi/BT module: intel 8265, 8087:0a2b
bluez: 5.48
BT mouse: logitech M337
---
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2018-05-29 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
InterestingModules: rfcomm bnep btusb bluetooth
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 8087:0a2b Intel Corp.
 Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp.
 Bus 001 Device 004: ID 27c6:5385
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. XPS 13 9370
Package: bluez 5.48-0ubuntu3 [origin: unknown]
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=d6251f09-cbb5-4635-8f42-31e6c32f1c03 ro quiet splash vt.handoff=1
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Tags: third-party-packages bionic
Uname: Linux 4.15.0-22-generic x86_64
UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 11/03/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 0.3.13
dmi.board.name: 0173S1
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr0.3.13:bd11/03/2017:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0173S1:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 13 9370
dmi.sys.vendor: Dell Inc.
hciconfig:
 hci0: Type: Primary Bus: USB
  BD Address: D4:25:8B:4F:7E:D6 ACL MTU: 1021:4 SCO MTU: 96:6
  UP RUNNING PSCAN ISCAN
  RX bytes:61781 acl:382 sco:0 events:536 errors:0
  TX bytes:7985 acl:69 sco:0 commands:168 errors:0

See original description
Revision history for this message
Leon Liao (lihow731) wrote :

The attached file is the .snoop when I reproduced this bug.

Changed in oem-priority:
importance: Undecided → Critical
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Sounds similar to bug 1771733 (which will hopefully expire) or bug 1651433 (which is also XPS 13).

Fortunately I have multiple Logitech M337's here, so I will test them with various laptops over the coming days.

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

In the meantime, please run 'apport-collect 1773897' on the problematic machine to send us more information about it.

Changed in bluez (Ubuntu):
status: New → Incomplete
Changed in oem-priority:
status: New → Incomplete
Changed in bluez (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Please also attach the kernel log (dmesg) and the system log (journalctl -b) from the affected machine, capturing a period of time when the problem happens.

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

You may also wish to try a preview of BlueZ 5.49 from here:
https://launchpad.net/~bluetooth/+archive/ubuntu/bluez

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

Another idea is to try installing 'linux-firmware', if not already, to ensure the wifi chip's firmware is up to date.

Revision history for this message
Leon Liao (lihow731) wrote :

More information:
This issue does not cause by single commit.

since "6b34bdd96 ("shared/gatt-client: Fix not removing services that had disappeared", 2017-05-24)", this bug can be reproduced with low fail rate (around 1/10 or lower).
This commit is between 5.45 and 5.46.
Before this commit, I don't reproduce this bug (maybe the reproduce rate is very low.).

tags: added: bionic
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Please answer all the above questions, and if you find it's still a problem in 5.49 (https://launchpad.net/~bluetooth/+archive/ubuntu/bluez) then please report the bug upstream here:

https://bugzilla.kernel.org/enter_bug.cgi?product=Drivers&component=Bluetooth

Revision history for this message
Leon Liao (lihow731) wrote : CurrentDmesg.txt

apport information

tags: added: apport-collected third-party-packages
description: updated
Revision history for this message
Leon Liao (lihow731) wrote : Dependencies.txt

apport information

Revision history for this message
Leon Liao (lihow731) wrote : Lspci.txt

apport information

Revision history for this message
Leon Liao (lihow731) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Leon Liao (lihow731) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Leon Liao (lihow731) wrote : ProcEnviron.txt

apport information

Revision history for this message
Leon Liao (lihow731) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Leon Liao (lihow731) wrote : ProcModules.txt

apport information

Revision history for this message
Leon Liao (lihow731) wrote : UdevDb.txt

apport information

Revision history for this message
Leon Liao (lihow731) wrote : getfacl.txt

apport information

Revision history for this message
Leon Liao (lihow731) wrote : rfkill.txt

apport information

Revision history for this message
Leon Liao (lihow731) wrote : syslog.txt

apport information

Revision history for this message
Leon Liao (lihow731) wrote : Re: Bluetooth 3.0 mouses are automatically disconnected after connected

The attached file is the output of "journalctl -b".

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

Thanks. Please try 5.49 (https://launchpad.net/~bluetooth/+archive/ubuntu/bluez). If the problem continues in 5.49 then please report the bug upstream here:

https://bugzilla.kernel.org/enter_bug.cgi?product=Drivers&component=Bluetooth

mentioning that it seems to be a regression starting at 6b34bdd96.

Revision history for this message
Leon Liao (lihow731) wrote :

This bug still can be reproduced in BlueZ 5.49.

Revision history for this message
In , leon.liao (leon.liao-linux-kernel-bugs) wrote :

The BT 3.0 mouse is disconnected automatically after connected with the notebook.
The fail rate is around 9/10.

1. The bug only occurs on the machine with intel 8265 module.
 I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265).
 This bug can not be reproduced on the machine with Killer 1435.

2. This bug can be reproduced since bluez 5.46.
 I verified the bluez 5.49, this bug still can be reproduced.
 This bug can not be reproduced in bluez 5.45.

Notebook: Dell XPS 13
Wi-Fi/BT module: intel 8265, 8087:0a2b
bluez: 5.48
BT mouse: logitech M337

Revision history for this message
Leon Liao (lihow731) wrote :

Filed a upstream bug: https://bugzilla.kernel.org/show_bug.cgi?id=199873

Daniel van Vugt (vanvugt)
Changed in bluez (Ubuntu):
status: Incomplete → New
Revision history for this message
In , leon.liao (leon.liao-linux-kernel-bugs) wrote :

In bluez git, since "6b34bdd96 ("shared/gatt-client: Fix not removing services that had disappeared", 2017-05-24)", this bug can be reproduced with low fail rate (around 1/10 or lower).
This commit is between 5.45 and 5.46.
Before this commit, I don't reproduce this bug (maybe the reproduce rate is very low.).

Daniel van Vugt (vanvugt)
summary: - Bluetooth 3.0 mouses are automatically disconnected after connected
+ [regression] Bluetooth 3.0 mouses are automatically disconnected after
+ connected
Changed in oem-priority:
status: Incomplete → New
tags: added: regression-release
Daniel van Vugt (vanvugt)
summary: - [regression] Bluetooth 3.0 mouses are automatically disconnected after
+ [regression] Logitech M337 mice are automatically disconnected after
connected
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in bluez (Ubuntu):
status: New → Confirmed
Revision history for this message
In , phil+kernbugz (phil+kernbugz-linux-kernel-bugs) wrote :

I can also reproduce the bug.

Notebook: HP Spectre x360 Convertible W2Q33AV
Wi-Fi/BT module: 8087:0a2a Intel
BlueZ: 5.50 (bluez-5.50-1.fc28.x86_64)
BT Mouse: Logitech M535

Log:
[bluetooth]# scan on
Discovery started
[CHG] Controller C8:21:58:16:95:58 Discovering: yes
[NEW] Device 34:88:5D:89:64:81 Bluetooth Mouse M336/M337/M535
[bluetooth]# trust 34:88:5D:89:64:81
[CHG] Device 34:88:5D:89:64:81 Trusted: yes
Changing 34:88:5D:89:64:81 trust succeeded
[bluetooth]# connect 34:88:5D:89:64:81
Attempting to connect to 34:88:5D:89:64:81
[CHG] Device 34:88:5D:89:64:81 Connected: yes
[CHG] Device 34:88:5D:89:64:81 Modalias: usb:v046DpB016d1203
[CHG] Device 34:88:5D:89:64:81 UUIDs: 00001000-0000-1000-8000-00805f9b34fb
[CHG] Device 34:88:5D:89:64:81 UUIDs: 00001124-0000-1000-8000-00805f9b34fb
[CHG] Device 34:88:5D:89:64:81 UUIDs: 00001200-0000-1000-8000-00805f9b34fb
[CHG] Device 34:88:5D:89:64:81 ServicesResolved: yes
[CHG] Device 34:88:5D:89:64:81 Paired: yes
Connection successful

# Mouse is powered off and then back on

[CHG] Device 34:88:5D:89:64:81 ServicesResolved: no
[CHG] Device 34:88:5D:89:64:81 Paired: no
[CHG] Device 34:88:5D:89:64:81 Connected: no
[CHG] Device 34:88:5D:89:64:81 Class: 0x00000580
[CHG] Device 34:88:5D:89:64:81 Icon: input-mouse
[CHG] Device 34:88:5D:89:64:81 Connected: yes
[CHG] Device 34:88:5D:89:64:81 Connected: no
[CHG] Device 34:88:5D:89:64:81 Connected: yes
[CHG] Device 34:88:5D:89:64:81 Connected: no
[CHG] Device 34:88:5D:89:64:81 Connected: yes
[CHG] Device 34:88:5D:89:64:81 Connected: no
[CHG] Device 34:88:5D:89:64:81 Connected: yes
[CHG] Device 34:88:5D:89:64:81 Connected: no
[CHG] Device 34:88:5D:89:64:81 Connected: yes
[CHG] Device 34:88:5D:89:64:81 Connected: no

Bug Watch Updater (bug-watch-updater)
Changed in bluez:
importance: Unknown → Medium
status: Unknown → Confirmed
Revision history for this message
Michał Sawicz (saviq) wrote :

Not sure what's changed, but I've recently had much better luck with the mouse connecting properly by itself.

Revision history for this message
In , jswxxuyuan (jswxxuyuan-linux-kernel-bugs) wrote :

I can also reproduce this bug.

Notebook: Dell XPS 13 (9370)
Wi-Fi/BT module: not sure...
bluez: 5.50
BT mouse: logitech M336 (M337)

Log:
[bluetooth]# paired-devices
Device 34:88:5D:92:FC:0C Bluetooth Mouse M336/M337/M535
// try to connect the mouse
[bluetooth]# connect 34:88:5D:92:FC:0C
Attempting to connect to 34:88:5D:92:FC:0C
Failed to connect: org.bluez.Error.Failed
// try to connect in discovery mode
[bluetooth]# connect 34:88:5D:92:FC:0C
Attempting to connect to 34:88:5D:92:FC:0C
[CHG] Device 34:88:5D:92:FC:0C Connected: yes
[CHG] Device 34:88:5D:92:FC:0C ServicesResolved: yes
Failed to connect: org.bluez.Error.NotAvailable
[CHG] Device 34:88:5D:92:FC:0C ServicesResolved: no
[CHG] Device 34:88:5D:92:FC:0C Connected: no
// moving around the mouse
[CHG] Device 34:88:5D:92:FC:0C Connected: yes
[CHG] Device 34:88:5D:92:FC:0C Connected: no
[CHG] Device 34:88:5D:92:FC:0C Connected: yes
[CHG] Device 34:88:5D:92:FC:0C Connected: no
[CHG] Device 34:88:5D:92:FC:0C Connected: yes
[CHG] Device 34:88:5D:92:FC:0C Connected: no

Revision history for this message
Michał Sawicz (saviq) wrote :

I'm back to having to re-pair a handful of times each boot. It seems every once in a while the pairing "sticks" and works until I have to reconnect it again.

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Michał, does this happen to intel Bluetooth USB controller?

Revision history for this message
Michał Sawicz (saviq) wrote :

lsusb says "Bus 002 Device 003: ID 8087:07dc Intel Corp." here.

Revision history for this message
Chris (crassd) wrote :

I have the same issue. Running Linux Mint with latest kernel.
Kernel: Linux 4.19.9-041909-generic #201812130432 SMP Thu Dec 13 09:34:53 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

It takes me disabling bluetooth, deleting the profile, re-enabling bluetooth, and putting the mouse back in pairing mode to fix.

Only began happening after updating from Linux Mint 19 from Linux Mint 18.3 (I assume due to the Bluez version)

dmesg:
[ 9094.174854] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 9113.487898] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 9129.243872] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 9145.487806] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 9155.351840] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 9171.601996] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 9187.474873] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 9193.843245] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[ 9193.843255] Bluetooth: HIDP socket layer initialized
[ 9194.686585] hid-generic 0005:046D:B016.0002: unknown main item tag 0x0
[ 9194.686700] input: Bluetooth Mouse M336/M337/M535 Mouse as /devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:046D:B016.0002/input/input27
[ 9194.687692] input: Bluetooth Mouse M336/M337/M535 Consumer Control as /devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:046D:B016.0002/input/input28
[ 9194.687919] input: Bluetooth Mouse M336/M337/M535 Keyboard as /devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:046D:B016.0002/input/input31
[ 9194.688328] hid-generic 0005:046D:B016.0002: input,hidraw1: BLUETOOTH HID v12.03 Mouse [Bluetooth Mouse M336/M337/M535] on a4:34:d9:e0:9c:d1

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Seems like Bluez 5.50 fixes the issue, tried re-repairing BT mouse 5 times and it seems to work so far.

I guess this commit fixes the issue:
commit a07eb3a5e96d7f23a2aa554088d3cc3a9e57744f
Author: Andrzej Kaczmarek <email address hidden>
Date: Thu Mar 22 16:21:00 2018 +0100

    shared/gatt-client: Fix discovery of discontinuous database

A simple Disco rebuild for Bionic PPA for testing:
https://launchpad.net/~kaihengfeng/+archive/ubuntu/lp1773897

Revision history for this message
Michał Sawicz (saviq) wrote :

@Feng could you please rebuild for cosmic, too? I'll try it out then.

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

Cosmic already has BlueZ 5.50

Revision history for this message
Michał Sawicz (saviq) wrote :

Ah indeed...

$ LANG=C apt policy bluez
bluez:
  Installed: 5.50-0ubuntu1
  Candidate: 5.50-0ubuntu1
  Version table:
 *** 5.50-0ubuntu1 500
        500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
        100 /var/lib/dpkg/status

In that case I don't think I can confirm this fixes it, or maybe mine is a different issue (M535 mouse here). I've certainly had trouble pairing since I've upgraded to cosmic.

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Mime is M585 and seems like it works with Bluez 5.50.
There are lots of fixes in Bluez master, maybe some commits fix the issue?

Revision history for this message
Corrado Mencar (corrado-mencar) wrote :

Same issue with a fresh new install of Mint 19.1 (booted from USB) on a Dell Inspiron 7778 and bluetooth mouse HP Z5000. No problems with Mint 18.3

Revision history for this message
In , lkorg (lkorg-linux-kernel-bugs) wrote :

I too have had the same issue...

Notebook: Dell XPS 13 9360
bios: tested with 2.9.1 and 2.10.0
OS: Debian stretch 9.8
Kernel: 4.9.0-8 debian 4.9.144-3
Wi-Fi/BT module: Intel Dual Band wirelss AC 8265, rev=0x230
Firmware: iwlwifi-8265-22.ucode
BlueZ: 5.43-2+deb9u1
BT Mouse: Logitech MX anywhere 2s

------

When attempting to pair one of 4 things will happen:

1. the bluetooth module locks up and stops responding - time out messages are seen in dmesg

2. The wifi will reset but will return to a normal state with a failed bluetooth as above

3. wifi and bluetooth will disappear and stop responding but wifi is recoverable by invoking rfkill via the wifi hot key ( fn f12 )

4. The entire device stops responding and shortly after the machine will freeze - there may be a panic but i can't see it due to lock up ( nothing written to logs )

The pairing process will not complete as the device stops responding before then.

Resetting the pci device via the /sys interface results in an instant hang

Other two xps devices i have contain ath10k cards and dont seem affected, mouse can also be paired to an android device without issue.

tried bios upgrade to no avail. attempted using firmware direct from linux-firmware repsitory instead of firmware-iwlwifi package ( 20161130-4 ) no change

only fix i've found for this was to add the bt_coex_active=0 option when loading the module ( modprobe: options iwlwifi bt_coex_active=0 )

this allows a connection to occur and for the device to pair however the mouse movement on screen seems to be quite jittery at times.

Revision history for this message
In , kai.heng.feng (kai.heng.feng-linux-kernel-bugs) wrote :

Do you folks use gnome-control-center to pair?

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Seems like it's because Logitech Far East mice need to be paired.

Please add this to /usr/share/gnome-bluetooth/pin-code-database.xml:

<device vendor="logitech far east" type="mouse" pin="0000"/>

Revision history for this message
In , kai.heng.feng (kai.heng.feng-linux-kernel-bugs) wrote :

Take a look at [1] if gnome-control-center is used:

[1] https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1773897/comments/43

Revision history for this message
In , phil+kernbugz (phil+kernbugz-linux-kernel-bugs) wrote :

(In reply to Kai-Heng Feng from comment #5)
> Do you folks use gnome-control-center to pair?

I certainly did use gnome-control-center.
I've just tried again with Fedora 29 (gnome-control-center-3.30.3-1.fc29.x86_64 + bluez-5.50-3.fc29.x86_64) and out of five remove, add, force reconnect) I only received a single failure.
/usr/share/gnome-bluetooth/pin-code-database.xml does not seem to have any tweak applying to this mouse.

Revision history for this message
In , lkorg (lkorg-linux-kernel-bugs) wrote :

I tried the pairing via the gnome control center, command line ( bluetoothctl ) and via blueman. These were done while in a gnome session however

All three attempts failed as above.

Revision history for this message
In , kai.heng.feng (kai.heng.feng-linux-kernel-bugs) wrote :

My intention is to ask you to try adding this entry to pin-code-database.xml:
<device vendor="logitech far east" type="mouse" pin="0000"/>

Revision history for this message
In , bugzilla (bugzilla-linux-kernel-bugs) wrote :

(In reply to Kai-Heng Feng from comment #9)
> My intention is to ask you to try adding this entry to pin-code-database.xml:
> <device vendor="logitech far east" type="mouse" pin="0000"/>

See https://gitlab.gnome.org/GNOME/gnome-bluetooth/merge_requests/14

Daniel van Vugt (vanvugt)
Changed in gnome-bluetooth (Ubuntu):
status: New → Confirmed
Changed in oem-priority:
status: New → Confirmed
Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Please backport this two MR:
https://gitlab.gnome.org/GNOME/gnome-bluetooth/merge_requests/13
https://gitlab.gnome.org/GNOME/gnome-bluetooth/merge_requests/14

Changed in bluez (Ubuntu):
status: Confirmed → Invalid
Revision history for this message
Will Cooke (willcooke) wrote : Automatically added comment

Added to Trello: https://trello.com/c/4fDA1uYR/291-bug1773897-regression-logitech-m337-mice-are-automatically-disconnected-after-connected

tags: added: desktop-trello-import
tags: removed: desktop-trello-import
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

I am using a Logitech M337 on Ubuntu 18.04 via Intel 8265 right now and cannot reproduce any bug.

If the problem ever was specific to Intel 8265 then it might have been fixed in firmware updates already here:

  https://launchpad.net/ubuntu/+source/linux-firmware

While comment #50 is interesting, I don't think it is relevant to this bug at all. And this bug doesn't seem to exist any more anyway.

no longer affects: gnome-bluetooth (Ubuntu)
Changed in oem-priority:
status: Confirmed → Incomplete
Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

No it's not specific to Intel 8265.

Can your M337 reconnect automatically after system suspend or system reboot?

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

This bug is not about suspending and resuming.

And I can't test resuming because my system becomes too unstable (for other reasons). As for system reboot, I have always had problems with some Bluetooth devices reconnecting on reboot. But that problem is not confined to mice. It happens with audio too.

I think the mice fixes in comment #50 are worth having, but this is the wrong bug to discuss them in.

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

As mentioned in the bug description, this bug only ever occurred on Intel 8265 with the M337 on bionic. All other issues should be discussed in other bugs.

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

> This bug is not about suspending and resuming.
The root cause is the same: the key doesn't get stored because it uses "Connect" instead of "Pair" for SSP devices.

> As mentioned in the bug description, this bug only ever occurred on Intel 8265 with the M337 on bionic.
It happens on multiple BT controllers and BT mice, with the same root cause.

But yea we can use another bug to track SRU status.

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

See bug 1822533 instead.

Revision history for this message
In , jswxxuyuan (jswxxuyuan-linux-kernel-bugs) wrote :

It seems like the bug has been fixed in bluez 5.50-6. My Logitech M336 works now.

Revision history for this message
Sebastien Bacher (seb128) wrote :

I've backported the is_trusted/pair pointer devices changes in a bionic SRU and used bug #1779289 for the update (the bug here seems like it's not only about that)

Yuan-Chen Cheng (ycheng-twn)
Changed in oem-priority:
importance: Critical → Medium
Rex Tsai (chihchun)
tags: added: oem-priority
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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