Bluetooth 3.0 mouses are automatically disconnected after connected

https://bugzilla.kernel.org/show_bug.cgi?id=199873

[email protected] changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]

--- Comment #3 from [email protected] --- 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

You are receiving this mail because:
You are the assignee for the bug.

https://bugzilla.kernel.org/show_bug.cgi?id=199873

antK ([email protected]) changed:

What |Removed |Added
----------------------------------------------------------------------------

                 CC|                            |[email protected]
                   |                            |k

--- Comment #4 from antK ([email protected]) --- 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.

You are receiving this mail because:
You are the assignee for the bug.

https://bugzilla.kernel.org/show_bug.cgi?id=199873

--- Comment #5 from Kai-Heng Feng ([email protected]) --- Do you folks use gnome-control-center to pair?

You are receiving this mail because:
You are the assignee for the bug.

https://bugzilla.kernel.org/show_bug.cgi?id=199873

--- Comment #6 from Kai-Heng Feng ([email protected]) --- Take a look at [1] if gnome-control-center is used:

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

You are receiving this mail because:
You are the assignee for the bug.

https://bugzilla.kernel.org/show_bug.cgi?id=199873

--- Comment #7 from Philippe Troin ([email protected]) --- (In reply to Kai-Heng Feng from comment #5)

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.

You are receiving this mail because:
You are the assignee for the bug.

https://bugzilla.kernel.org/show_bug.cgi?id=199873

--- Comment #8 from antK ([email protected]) ---
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.

You are receiving this mail because:
You are the assignee for the bug.

https://bugzilla.kernel.org/show_bug.cgi?id=199873

--- Comment #9 from Kai-Heng Feng ([email protected]) --- 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"/>

You are receiving this mail because:
You are the assignee for the bug.

https://bugzilla.kernel.org/show_bug.cgi?id=199873

Bastien Nocera ([email protected]) changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]

--- Comment #10 from Bastien Nocera ([email protected]) --- (In reply to Kai-Heng Feng from comment #9)

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

You are receiving this mail because:
You are the assignee for the bug.

https://bugzilla.kernel.org/show_bug.cgi?id=199873

--- Comment #11 from Andrew Xu ([email protected]) ---
It seems like the bug has been fixed in bluez 5.50-6. My Logitech M336 works now.

You are receiving this mail because:
You are the assignee for the bug.