Does anyone have any idea how I can supply enough info to resolve this? Every morning I have to unplug/replug my USB dongle and then open the BT settings an reconnect my mouse. It's getting very old and tiring. I'd be more than happy to supply whatever kind of debug info is necessary to get to a resolution on this. My previous USB BT dongle did not have this problem at all. But it also didn't have BLE support which I now need. Is btmon output useful here or some kind of driver or userspace debug enabled, etc. Any ideas? Cheers, b. On Wed, 2023-12-27 at 16:02 -0500, Brian J. Murrell wrote: > I have a: > > Bus 003 Device 029: ID 0bda:8771 Realtek Semiconductor Corp. > [unknown] > > BT adapter. When I first plug it in I am able to connect my: > > Device 34:88:5D:56:A8:C1 Bluetooth Mouse M557 > > But after some yet unknown amount of time, on the order of a day or > so, > the mouse becomes disconnected and won't reconnect: > > [bluetooth]# connect 34:88:5D:56:A8:C1 > Attempting to connect to 34:88:5D:56:A8:C1 > [bluetooth]# Failed to connect: org.bluez.Error.Failed br-connection- > create-socket > > When the above happens the journal logs: > > Dec 27 15:47:17 pc.interlinx.bc.ca bluetoothd[3754244]: > profiles/input/device.c:ioctl_is_connected() Can't get HIDP > connection info > Dec 27 15:47:22 pc.interlinx.bc.ca bluetoothd[3754244]: > profiles/input/device.c:control_connect_cb() connect to > 34:88:5D:56:A8:C1: Host is down (112) > > If I simply unplug/plug-in the adapter then try to connect using the > GNOME Bluetooth control it will reconnect. > > It will stay connected for a period of time when it will drop and > then > I have to start this palaver all over again. > > The question is what is needed to be able to debug why bluez gets > into > this state with this adapter? > > Cheers, > b. >
Attachment:
signature.asc
Description: This is a digitally signed message part
