I have a Microsoft Bluetooth Mobile Keyboard 6000 which worked fine for several months. Since about yesterday it needs a repairing each time it did go into standby after some minutes of inactivity.
bluetoothctl
[NEW] Controller 00:15:83:53:9A:50 huber-nb-linux.suse [default]
[NEW] Device 7C:1E:52:A8:3E:E5 Microsoft Bluetooth Mobile Keyboard 6000
Agent registered
[bluetooth]# show
Controller 00:15:83:53:9A:50 (public)
Name: huber-nb-linux.suse
Alias: huber-nb-linux.suse
Class: 0x001c0104
Powered: yes
Discoverable: yes
Pairable: yes
UUID: Headset AG (00001112-0000-1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb)
UUID: OBEX File Transfer (00001106-0000-1000-8000-00805f9b34fb)
UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
UUID: OBEX Object Push (00001105-0000-1000-8000-00805f9b34fb)
UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
UUID: IrMC Sync (00001104-0000-1000-8000-00805f9b34fb)
UUID: Audio Source (0000110a-0000-1000-8000-00805f9b34fb)
UUID: Audio Sink (0000110b-0000-1000-8000-00805f9b34fb)
UUID: Vendor specific (00005005-0000-1000-8000-0002ee000001)
UUID: Message Notification Se… (00001133-0000-1000-8000-00805f9b34fb)
UUID: Phonebook Access Server (0000112f-0000-1000-8000-00805f9b34fb)
UUID: Message Access Server (00001132-0000-1000-8000-00805f9b34fb)
UUID: Headset (00001108-0000-1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d0530
Discovering: no
[bluetooth]# devices
Device 7C:1E:52:A8:3E:E5 Microsoft Bluetooth Mobile Keyboard 6000
[bluetooth]# info 7C:1E:52:A8:3E:E5
Device 7C:1E:52:A8:3E:E5 (public)
Name: Microsoft Bluetooth Mobile Keyboard 6000
Alias: Microsoft Bluetooth Mobile Keyboard 6000
Class: 0x00002540
Icon: input-keyboard
Paired: yes
Trusted: yes
Blocked: no
Connected: no
LegacyPairing: yes
UUID: Service Discovery Serve… (00001000-0000-1000-8000-00805f9b34fb)
UUID: Human Interface Device… (00001124-0000-1000-8000-00805f9b34fb)
UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
Modalias: usb:v045Ep0762d0013
I found these error messages in the journal which appeared only recently:
journalctl -r -u bluetooth
– Logs begin at Fri 2017-06-30 10:21:50 CEST, end at Tue 2019-05-21 07:06:01 CEST. –
May 21 07:04:12 huber-nb-linux.suse bluetoothd[1279]: connect error: Host is down (112)
May 21 07:04:07 huber-nb-linux.suse bluetoothd[1279]: Can’t get HIDP connection info
– Logs begin at Fri 2017-06-30 10:21:50 CEST, end at Tue 2019-05-21 07:06:01 CEST. –
May 21 07:04:12 huber-nb-linux.suse bluetoothd[1279]: connect error: Host is down (112)
May 21 07:04:07 huber-nb-linux.suse bluetoothd[1279]: Can’t get HIDP connection info
May 21 06:54:58 huber-nb-linux.suse bluetoothd[1279]: No cache for 7C:1E:52:A8:3E:E5