[Pkg-bluetooth-discuss] Issue with Bluetooth after upgrade...

[Trey Blancher]

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

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:

#!/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:

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

Thanks in advance,

Trey