Dear Maintainer,

   * What led up to the situation?

Registered a plain BT mouse.

   * What exactly did you do (or not do) that was effective (or
     ineffective)?

Used blueman (blueman-applet) to pair the device. Used it for a while.
Let it alone at the desk, came back, mouse no longer works.

Checked the log, used the Device manager of blueman - triggered
"Connect" there and it was stuck for a while and said "IO error".

Tried to upgrade bluez to latest version (before: Sid, now:
Experimental). Restarted blueman. Still not helping. The daemon.log
says:

Dec 25 20:58:56 amerix systemd[1]: Starting Bluetooth management mechanism...
Dec 25 20:58:56 amerix blueman-mechanism[21764]: Unable to init server: Could not connect: Connection refused
Dec 25 20:58:56 amerix blueman-mechanism[21764]: Unable to init server: Could not connect: Connection refused
Dec 25 20:58:56 amerix systemd[1]: Started Bluetooth management mechanism.
Dec 25 20:59:15 amerix bluetoothd[21271]: Can't get HIDP connection info
Dec 25 20:59:21 amerix bluetoothd[21271]: connect error: Host is down (112)
Dec 25 20:59:26 amerix systemd[1]: blueman-mechanism.service: Succeeded.

   * What outcome did you expect instead?

a) NOT break down completely after a short break.

b) Tell me, the user, something HELPFUL in the log (what am I supposed
to do with "Host is down"? Which host? What may make it up again?? Which
clues to look for?)

I do not claim that my configuration is totally clean, and I am not
using a fancy desktop environment but hey, with this kind of support
from the tools, I am totally lost.

Best regards,
Eduard.