Dear Maintainer,
The problem happens on resume. Only by deleting the mouse from the gnome bluetooth control panel, shifting the bluetooth dongle to another USB port, and re-pairing can I get it operational again.
Here is the hardware at issue. It is attached to an Intel NUC via a USB3 hub, but the same problem happens whether it's directly attached or on the hub.
# hciconfig -a
hci0: Type: BR/EDR Bus: USB
BD Address: 00:15:83:0C:BF:EB ACL MTU: 339:8 SCO MTU: 128:2
UP RUNNING PSCAN
RX bytes:187334 acl:12144 sco:0 events:395 errors:0
TX bytes:1647 acl:36 sco:0 commands:43 errors:0
Features: 0xff 0x3e 0x85 0x30 0x18 0x18 0x00 0x00
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF
Link mode: SLAVE ACCEPT
Name: 'debian'
Class: 0x000104
Service Classes: Unspecified
Device Class: Computer, Desktop workstation
HCI Version: 2.0 (0x3) Revision: 0xc5c
LMP Version: 2.0 (0x3) Subversion: 0xc5c
Manufacturer: Cambridge Silicon Radio (10)
Yet this problem also happens when I install a different usb adapter.
An ancillary problem is that in the Power settings for the gnome control panel, when I select the Bluetooth "On" and leave the "Power Saving" screen, and return to that screen, it goes back to "Off."
As a workaround, I have placed a script to run on resume as implied by this veyr similar (old) bug on Ubuntu:
https://bugs.launchpad.net/ubuntu/+source/bluez-gnome/+bug/285007