pfps
commented
11 months ago Is this error repeatable? The debug output you provided doesn't seem to have an error in it.
Closed Jerther closed 11 months ago
pfps
commented
11 months ago Is this error repeatable? The debug output you provided doesn't seem to have an error in it.
Jerther
commented
11 months ago Yes this is very easily repeatable. I also noticed there was nothing in the console with -dd, let alone an error, so I tried with -ddd to at least get something.
pfps
commented
11 months ago If there is an error, there should be some messages in the output of solaar -ddd, but the interaction with the device shown above appears to be fine. That said, maybe there is a bug in the Solaar code that is misinterpreting the interaction.
Please try solaar -ddd again and capture the debug output when you switch the resolution. Also, try switching the resolution several times as that may produce more debug output.
pfps
commented
11 months ago Your config.yaml file is very big, with lots of devices. Do you have (or had) lots of devices? There are multiple messages for a K810, which appears to be a bug so I've opened #2202 for that.
Jerther
commented
11 months ago The output of solaar -ddd I provided was with a toggle of the 'lock' button. Here's another output but with multiple toggles:
pfps
commented
11 months ago Something weird is definitely going on here. Is that first toggle (of the resolution, not the "lock", I assume) when you see the error?
Jerther
commented
11 months ago Yes, before the first toggle, there is no error:
The toggle switch is disabled now for some reason so I can't use it. I remember it wasn't before. It must have gotten disabled when I fiddled with the lock button next to it. anyways, as soon as I hut the lock button, the exclamation mark appears:
And the lock button cycles through only "lock" and "ignore".
pfps
commented
11 months ago The odd thing is that the M325 doesn't have a feature that supports high resolution as far as I can tell. I suspect that your config.yaml file has some incorrect information. Please stop Solaar, remove that file (which will remove any current settings for your devices), and try Solaar again.
Jerther
commented
11 months ago I have stopped Solaar, removed the config file, started Solaar again. The toggle switch is visible, and enabled:
If I toggle the switch, the same error occurs (no change).
Here's the output of -ddd:
Anyways, if the M325 does not support hi res scrolling, then I guess it's just a display problem and nothing in Solaar will fix my real underlying problem: the scrolling is way too fast ;)
pfps
commented
11 months ago Strange. Please try that again and then quit out of Solaar. Post the entire output of solaar -ddd and the contents of your config.yaml file.
Jerther
commented
11 months ago solaar -ddd > stdout.txt 2> stderr.txt
stderr.txt
stdout.txt
config.zip
(sorry I had to zip the yaml file. Github doesn't like yaml files...)
pfps
commented
11 months ago Your problem occurs because Solaar has an incorrect feature for the M325.
A line in lib/logitech_receiver/descriptors.py should read
_D('Wireless Mouse M325', codename='M325', protocol=2.0, wpid='400A')but instead it lists a setting the M325 does not have.
You can make this change yourself if you can access the Solaar code. I'll put in a PR as well.
pfps
commented
11 months ago To run Solaar with the patch, kill any running Solaar, clone Solaar, and run bin/solaar
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 #2203, 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/2203/head:pull_2203
git checkout pull_2203To 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_2203
git fetch origin pull/2203/head
git reset --hard FETCH_HEADI ran Solaar with the PR. Here's a screenshot. No more confusion.
:thumbsup:
pfps
commented
11 months ago Excellent.
I think that the reason scrolling is fast on this mouse is that it has 36 scroll "events" per turn of the scroll wheel. Many other Logitech mice with this feature have 24 or 18.
Jerther
commented
11 months ago I just tested an M185 and it too scrolls way too fast. In a Chrome debug console viewing source files, one tick of the scroll wheel scrolls 10 lines of code.
I went ahead and tested a Lenovo USB mouse and a Kensington USB mouse and they all scroll 10 lines, so, I think it's an OS issue.
pfps
commented
11 months ago That may be. There is an attempt to do smooth scrolling in Linux for mice that support it. Some Logitech mice do - those with HIRES WHEEL - use solaar show to ckeck. This sometimes goes wrong, particularly if Solaar is running and not ignoring the scrolling
speed setting.
pfps
commented
11 months ago Can you take a look at my question in #2202?
Information
uname -srmo): Linux 6.6.4-200.fc39.x86_64 x86_64 GNU/Linuxsolaar show:~/.config/solaar/config.yaml(or~/.config/solaar/config.jsonif~/.config/solaar/config.yamlnot present):Describe the bug Cannot toggle "Scroll Wheel High Resolution" on the M325
To Reproduce Steps to reproduce the behavior:
Screenshots
Additional context The mouse works fine otherwise.