Closed plaets closed 2 years ago
pfps
commented
2 years ago As you have discovered, Solaar remembers settings that cause problems and does not retry them. So please quit out of Solaar, clear that value out of config.json, and run Solaar as solaar -ddd and post the output.
plaets
commented
2 years ago Output from solaar -ddd:
pfps
commented
2 years ago I have the business version of this trackball. It appears to have a bug in how it implements adjustable DPI, which is needed for DPI sliding. I'll add a patch to Solaar to handle this bug, which may help you as well.
pfps
commented
2 years ago The problem appears to be that DPI sliding was checking to see if the device was a mouse, which the M575 is not. This check is not really needed so instead of loosening it I removed it entirely.
PR #1445 should solve your problem. You will need to quit out of Solaar and then remove the _absent information in ~/.config/Solaar/config.json. Then run PR #1445.
To clone and use Solar from its GitHub repository
git clone https://github.com/pwr-Solaar/Solaar.git
cd SolaarRun Solaar as bin/solaar from this directory.
To run PR #1445, first clone Solaar if you have not already done so and cd to the clone directory. The first time you download the pull request, fetch it into a new branch and checkout that branch, as in:
git fetch origin pull/1445/head:pull_1445
git checkout pull_1445To download a new version of the pull request, fetch it and then set your pull branch to the new fetch, as in:
git checkout pull_1445
git fetch origin pull/1445/head
git reset --hard FETCH_HEADThis PR solves it, thank you very much. Closing the issue.
Information
solaar --versionorgit describe --tagsif cloned from this repository): 1.1.1-80-gf938d34uname -srmo):Linux 5.13.0-28-generic x86_64 GNU/Linuxsolaar show:Describe the bug
DPI Sliding works normally on M575 back in commit 6d3d3e2086305f78994efd1003610e4b420fa9e8. In more recent versions, it seems to be influenced by the
absentkey in/home/$USER/.config/solaar/config.json.To Reproduce Steps to reproduce the behavior:
absentkey in config to an empty list.git checkout 6d3d3e2086305f78994efd1003610e4b420fa9e8python3 setup.py build; ./bin/solaarWith the following settings, pressing the forward button switches between two DPI options.git checkout f938d3430eba086b040d8aa9bb8df7ffde67e408(or cb14c2eec9724f421f06185d51d867d4f35d03ce)Additional context
Looking at the diff, I noticed, that this could be relevant
https://github.com/pwr-Solaar/Solaar/blob/f938d3430eba086b040d8aa9bb8df7ffde67e408/lib/logitech_receiver/settings_templates.py#L1031
print(absent)prints this:I have managed to temporarily fix the problem by manually clearing the
absentand_dpi_slidingkey in/home/$USER/.config/solaar/config.json. Switching to bluetooth, back to unifying and restarting Solaar reverts theabsentto the values pasted above, with 'dpi-sliding' included.