Logitech M535 mouse only pairs successfully after 4-5 tries

[Michał Sawicz]

I've had my mouse (Logitech M535) paired and working since upgrading to 18.04. I had to re-do the pairing after connecting to a different machine and now it takes 4-5 tries of pair/remove to connect the mouse, on every reboot / sleep cycle.

The logs show:
cze 15 07:45:37 michal-laptop bluetoothd[4168]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16)
cze 15 07:46:14 michal-laptop bluetoothd[4168]: Can't get HIDP connection info

But neither actually seem critical as this is shown upon successful pairing as well.

a bluetoothctl session of a failed pairing:
[bluetooth]# pair 34:88:5D:3E:A1:A4
Attempting to pair with 34:88:5D:3E:A1:A4
[CHG] Device 34:88:5D:3E:A1:A4 Connected: yes
[CHG] Device 34:88:5D:3E:A1:A4 Modalias: usb:v046DpB014d1200
[CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 00001000-0000-1000-8000-00805f9b34fb
[CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 00001124-0000-1000-8000-00805f9b34fb
[CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 00001200-0000-1000-8000-00805f9b34fb
[CHG] Device 34:88:5D:3E:A1:A4 ServicesResolved: yes
[CHG] Device 34:88:5D:3E:A1:A4 Paired: yes
Pairing successful
[CHG] Device 34:88:5D:3E:A1:A4 ServicesResolved: no
[CHG] Device 34:88:5D:3E:A1:A4 Connected: no

The mouse continues in pairing mode.

When using the gnome-control-center Bluetooth module:
cze 15 08:23:40 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16)
cze 15 08:23:40 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16)
cze 15 08:23:41 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16)
cze 15 08:23:41 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16)
cze 15 08:23:42 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16)
cze 15 08:23:42 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16)
cze 15 08:23:43 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16)

Finally when it connects:
[NEW] Device 34:88:5D:3E:A1:A4 Bluetooth Mouse M336/M337/M535
[CHG] Device 34:88:5D:3E:A1:A4 Trusted: yes
[CHG] Device 34:88:5D:3E:A1:A4 Connected: yes
[CHG] Device 34:88:5D:3E:A1:A4 Modalias: usb:v046DpB014d1200
[CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 00001000-0000-1000-8000-00805f9b34fb
[CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 00001124-0000-1000-8000-00805f9b34fb
[CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 00001200-0000-1000-8000-00805f9b34fb
[CHG] Device 34:88:5D:3E:A1:A4 ServicesResolved: yes
[CHG] Device 34:88:5D:3E:A1:A4 Paired: yes

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: bluez 5.48-0ubuntu3
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Jun 15 07:46:38 2018
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: Dell Inc. XPS 12-9Q33
ProcKernelCmdLine: BOOT_IMAGE=/ROOT/ubuntu@/boot/vmlinuz-4.15.0-23-generic root=ZFS=username-laptop/ROOT/ubuntu ro quiet splash vt.handoff=1
SourcePackage: bluez
UpgradeStatus: Upgraded to bionic on 2018-02-07 (127 days ago)
dmi.bios.date: 03/03/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A08
dmi.board.name: XPS 12-9Q33
dmi.board.vendor: Dell Inc.
dmi.board.version: A08
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: dmi:bvnDellInc.:bvrA08:bd03/03/2015:svnDellInc.:pnXPS12-9Q33:pvrA08:rvnDellInc.:rnXPS12-9Q33:rvrA08:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: XPS 12-9Q33
dmi.product.version: A08
dmi.sys.vendor: Dell Inc.
hciconfig:
 hci0: Type: Primary Bus: USB
  BD Address: 5C:51:4F:1D:50:3C ACL MTU: 1021:5 SCO MTU: 96:5
  UP RUNNING PSCAN ISCAN
  RX bytes:16702 acl:290 sco:0 events:716 errors:0
  TX bytes:44162 acl:142 sco:0 commands:427 errors:0

[Daniel van Vugt (vanvugt)]

I wonder if there is any relation to bug 1773897 here...

[Daniel van Vugt (vanvugt)]

What Ubuntu version did you upgrade from?

[Michał Sawicz (saviq)]

Most recently from 17.10.

[Michał Sawicz (saviq)]

It does look similar to that other bug, will dupe and we'll see if it improves when that's fixed.

[Daniel van Vugt (vanvugt)]

That might be premature. Bug 1773897 regressed in 17.10, not from 17.10.

[Launchpad Janitor (janitor)]

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

[Daniel van Vugt (vanvugt)]

Can you still reproduce this bug with the latest updates? I can't seem to reproduce bug 1773897.

[Michał Sawicz (saviq)]

Yes, I just removed the mouse under gnome-control-center, went into `bluetoothctl` and tried to pair it again:

[bluetooth]# scan on
Discovery started
[NEW] Device 49:4E:A7:0B:A0:51 49-4E-A7-0B-A0-51
[NEW] Device 34:88:5D:3E:A1:A4 Bluetooth Mouse M336/M337/M535
[bluetooth]# pair 34:88:5D:3E:A1:A4
Attempting to pair with 34:88:5D:3E:A1:A4
[CHG] Device 34:88:5D:3E:A1:A4 Connected: yes
[CHG] Device 34:88:5D:3E:A1:A4 Modalias: usb:v046DpB014d1200
[CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 00001000-0000-1000-8000-00805f9b34fb
[CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 00001124-0000-1000-8000-00805f9b34fb
[CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 00001200-0000-1000-8000-00805f9b34fb
[CHG] Device 34:88:5D:3E:A1:A4 ServicesResolved: yes
[CHG] Device 34:88:5D:3E:A1:A4 Paired: yes
Pairing successful
[CHG] Device 34:88:5D:3E:A1:A4 ServicesResolved: no
[CHG] Device 34:88:5D:3E:A1:A4 Connected: no
[bluetooth]# pair 34:88:5D:3E:A1:A4
Attempting to pair with 34:88:5D:3E:A1:A4
Failed to pair: org.bluez.Error.AlreadyExists
[bluetooth]# connect 34:88:5D:3E:A1:A4
Attempting to connect to 34:88:5D:3E:A1:A4
Failed to connect: org.bluez.Error.Failed
[bluetooth]# version
Version 5.50
[bluetooth]# quit

$ uname -a
Linux michal-laptop 4.18.0-16-generic #17-Ubuntu SMP Fri Feb 8 00:06:57 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

bluetoothctl claims it pairs it, but then disconnects again. The mouse continues to blink, remaining in pairing mode.

Even when it does pair successfully, only every 10 times or so does the pairing "persist" across suspend/reboot cycles. Most often I have to re-pair from scratch every boot/resume.

[Michał Sawicz (saviq)]

When it does pair, bluetoothctl doesn't report "ServicesResolved: no" or "Connected: no".

[Daniel van Vugt (vanvugt)]

Sounds like this might be related to these:

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

[Daniel van Vugt (vanvugt)]

The above merge requests are included in gnome-bluetooth 3.32.1 so please subscribe to bug 1822533.

[Daniel van Vugt (vanvugt)]

Please try Ubuntu 19.04 when you can, which when updated now has gnome-bluetooth 3.32.1 to solve a few pairing problems.

[Michał Sawicz (saviq)]

Hey @vanvugt, just upgraded to 19.04 and indeed the problems seem to have gone. The mouse pairs every time, and persistently.

[Daniel van Vugt (vanvugt)]

Awesome.

I guess the only remaining question is whether you can confirm that downgrading to gnome-bluetooth 3.32.0 reintroduces the problem?

[Daniel van Vugt (vanvugt)]

The previous version (3.32.0) is here:

https://launchpad.net/ubuntu/+source/gnome-bluetooth/3.32.0-1/+build/16486213

[Michał Sawicz (saviq)]

Yup, looks like it. Downgrading made it unstable, upgrading stable again. I wonder how was `bluetoothctl` affected? Probably the GNOME menu still interacted with bluez even if the commands were invoked on `bluetoothctl`?

[Sebastien Bacher (seb128)]

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)

[Sebastien Bacher (seb128)]

The bionic fix landed with that SRU
https://launchpad.net/ubuntu/+source/gnome-bluetooth/3.28.0-2ubuntu0.2
(another bug number was used for the SRU so closing manually)