Closed FraYoshi closed 2 weeks ago
Please run Solaar at solaar -dd
and see if there are any errors reported. If so, post the errors.
Sure, I've screenshotted the situation and copied each dubug info, from open to close. The 4th and 6th attempts are the ones expected.
01
02
03
04
05
06
Thanks. That looks similar to what I've been seeing recently as well. I don't know the cause - it may even be a fault in the Linux input system - but I'll investigate further in a little while.
This appears to be a bug in the bluetooth input stack or maybe in Python. Solaar is reading from the device and seeing multiple copies of some responses. If this happens when Solaar is building up some internal structures it can result in errors because Solaar assumes, for example, that there is only one response per key/button. I have some changes to Solaar to try to recover from this in some cases, but I haven't uploaded these changes as they are still in process.
For now, I suggest connecting via a receiver if possible.
It's great that you have a lead! A workaround might be if we could somehow override the device auto-detection with a manual one, maybe by loading from a predefined list or a recent device : )
The receiver is certainly a solution, might indeed switch to it ^^b
PR #2591 should help alleviate the effects of the Bluetooth bug.
Indeed It does!
Closed and re-opened 3 times, and 3/3 were the correct configuration!
Great job pfps! 🍻
Information
solaar show
:~/.config/solaar/config.yaml
(or~/.config/solaar/config.json
if~/.config/solaar/config.yaml
not present):Describe the bug While device is connected via bluetooth, and some time is passed, the mouse goes into sleep. Upon wake up, Solaar cannot recognize the device properly and needs to be closed and re-opened multiple times a-la-roulette before the correct device mapping is recognized. What I see, is that not all the options are present. I might have the Scroll Wheel Ratchet Speed, the DPI, the Key Actions, all of them, none of them, and so on... at every close and open.
It has happened for a couple of months.
To Reproduce Steps to reproduce the behavior:
Screenshots Screenshots of 4 different closing and re-openings:
![2024-07-30_23-26](https://github.com/user-attachments/assets/05f58303-15b7-4c53-9cf0-ffea2600a35c)
Additional context It used to work before. Use it simply by changing the base options. Tried deleting the config, no luck. Tried unpairing and repairing, again no-luck..