Open Konsole and launch Chromium from it: chromium
Very odd. The good news is it seems reproducible for me on an X1 Carbon Gen 9 and Chromium 96.0.4664.93. The issue does not occur when launching Google Chrome however.
Quoting:
Problems with all BLE devices on kernel 5.9+
Starting with v5.9, the kernel Bluetooth stack tries to use link-layer privacy on BLE connections. If the device works after pairing but does not survive a reboot or suspend, it is probably because of this.
To workaround [2] this issue, open /var/lib/bluetooth/adapter_mac/device_mac/info , remove the following lines, and restart bluetooth.service :
[IdentityResolvingKey]
Key=...
It was supposed to be fixed, but it might be a kernel regression.
I’ll need to try that at some point but that might be a separate issue. In my case, the bluetooth stack seems to sometimes crash and it seems to be reproducible with Chromium.
Thanks @clmbtti, but still no change.
The mouse is well connected but cursor still didn’t react after a reboot or a standby wake up without a power off / power on.
I am going to ping @cscs to help us on this one and improve upon on the script below.
Thanks to Google Translate, I was reading Felix*'s blog on an issue he was having in 2019 with bluez. He noticed the same issue of the topic; if he manually sent a pair command using bluetoothctl, the mouse would stay (re)connected for a while, but eventually would disconnect. He then wrote a python script he kept running in background.
I’ve tested the script : the detection is okay when the laptop resume from sleep. I can this the output Mouse connected, attempt to pair...
but the cursor is still stuck.
I saw a new aur package called rebind devices which seems worth trying. It’s a systemd service to automatically reset devices when resuming from sleep.
If you decide testing it, let us know how it went.
maybe it’s time to update the kernel first before ongoing any troubleshooting. it’s a good choice to update to the newest kernel actually, there are too many changes under the hood.