Bluetooth mouse trouble [SOLVED in Wheezy/BROKEN in Jessie]

[ectospasm]

My Microsoft Bluetooth Mouse 5000 had been working flawlessly in
Debian Sid until the following packages were upgraded (gleaned from
/var/log/dpkg.log):

Code: Select all

bluez:amd64 4.101-2 4.101-2+b1
libbluetooth3:amd64 4.101-2 4.101-2+b1

Now, if I let the workstation go idle, the mouse disconnects and will
not reconnect until I pair it again. I had been using blueman to
manage my builtin Bluetooth adapter, but that became cumbersome.
Here's the console script I use now:

Code: Select all

#!/bin/sh
bluez-simple-agent hci0 00:22:48:E1:92:8A remove
bluez-simple-agent hci0 00:22:48:E1:92:8A
bluez-test-device trusted 00:22:48:E1:92:8A
bluez-test-input connect 00:22:48:E1:92:8A

I have to put the mouse into pairing mode to do this, which I'm sure
wastes battery life. I've run it as my normal (non-root) user, and
also as root with no change in behavior. I would have filed a bug
report, but I don't think I have enough information to pinpoint the
problem. My Bluetooth adapter is this (from lsusb):

Bus 003 Device 002: ID 0a5c:2121 Broadcom Corp. BCM2210 Bluetooth

Like I said, it had been working flawlessly (without having to
re-pair) until the upgrade on September 19. Sometimes I get the
following output when trying to pair the mouse:

Code: Select all

RequestPinCode (/org/bluez/2893/hci0/dev_00_22_48_E1_92_8A)
Enter PIN Code: 0000
Release
New device (/org/bluez/2893/hci0/dev_00_22_48_E1_92_8A)
Creating device failed: org.bluez.Error.AlreadyExists: Already Exists
0
Traceback (most recent call last):
  File "/usr/bin/bluez-test-input", line 42, in <module>
    input.Connect()
  File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 70, in __call__
    return self._proxy_method(*args, **keywords)
  File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 145, in __call__
    **keywords)
  File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line
651, in call_blocking
    message, timeout)
dbus.exceptions.DBusException: org.bluez.Error.Failed: Connection refused (111)

That may happen once or twice while trying to pair. Usually I have to
turn the mouse off and back on, and restart the pairing process. When it does pair successfully, I get the following behavior:

Code: Select all

RequestPinCode (/org/bluez/2893/hci0/dev_00_22_48_DE_11_CF)
Enter PIN Code: 0000
Release
New device (/org/bluez/2893/hci0/dev_00_22_48_DE_11_CF)
Creating device failed: org.bluez.Error.AlreadyExists: Already Exists
0

The pairing indicator on the mouse stops flashing, and the mouse works as
expected. This state will continue until I let the computer go idle again, and
I have to repeat the process. The expected behavior is that the mouse
continues to work even after an extended idle period. This was the behavior
prior to the updates above.

I have an identical mouse (with identifier/MAC 00:22:48:DE:11:CF), that
has the same problems. I let the computer idle long enough for
xscreensaver to kick in, and the mouse "went to sleep," and would not come
back without re-pairing the mouse. Thus I think it's something with
the Bluetooth stack on the workstation. Again, I would have filed a
bug if I knew what more information I should have provided.

[ectospasm]

At some point this stopped being an issue. When I'd come back to my computer, my Microsoft Bluetooth Mouse 5000 would work as expected. My only guess is that I upgraded the packages at some point, and the problem ceased.

[Riberto]

Please tell us what you upgraded so I can do the same?

I'm having the very same issues with a "Microsoft Sculpt Touch Mouse".
Everytime I turn on my laptop I MUST go into "settings" "bluetooth" and first disconected it, then re-install it.
Otherwise it will NOT see the mouse.
I have tried this with 3 differents mouses and I have the same issue.

The very same mouse works great with another laptop and a Chromebook.
The portable HP Officejet 100 (bluetooth) printer works great with the same Laptop.
Does jessie have a thing against BT mice?

THANKS for your help!

Rr

[ectospasm]

Sadly, I upgraded to Jessie, and my Bluetooth mouse woes returned. I filed this bug report, where I hopefully included a bunch of useful information. I got this mouse to pair a few times, but it would "go to sleep" when the computer locked. Re-pairing did work for a short while, but now I can't complete the pairing process at all. I've tried two otherwise identical Microsoft Bluetooth Notebook Mouse 5000s, and neither will now pair.

I have ordered a cheap, though highly rated RF mouse to sidestep Bluetooth altogether, since the stack in Jessie is horribly broken from my perspective. I'm hoping that also neatly works around the necessity to have multiple mice on my desk. Instead of one for each computer connected to the KVM, I'm hoping to have one mouse to rule them all.

[ectospasm]

Had these issues off and on; what finally resolved them for me was setting a PIN on the connection. Default PIN for devices that don't have a keyboard is generally 0000 - that corrected all the issues with my MS compact mouse.

Hope this helps -

Where did you set your PIN? It used to prompt for the PIN, but no longer. I know my mice's PINs are 0000, as that has worked in the past. I've tried trusting the device, but that doesn't seem to work.

[ectospasm]

Where did you set your PIN? It used to prompt for the PIN, but no longer. I know my mice's PINs are 0000, as that has worked in the past. I've tried trusting the device, but that doesn't seem to work.

IIRC if you remove the device and then re-add it you should get prompted for a PIN.

In my case, that is NOT working. I can issue the remove command, and I have to "scan on" in order to see it again. For whatever reason, when I pair them I am no longer prompted for a PIN for these two mice. I did try at one point to load a PIN file, maybe that is hanging around and I've forgotten where it is, or how to clear it.