On 30.01.23 11:44, Tobias Klausmann wrote: > On Mon, 30 Jan 2023, Benjamin Tissoires wrote: > >> On Mon, Jan 30, 2023 at 10:56 AM Linux kernel regression tracking >> (Thorsten Leemhuis) <regressions@xxxxxxxxxxxxx> wrote: >>> >>> [ccing a few people that CCed to the bug] >>> >>> Hi, this is your Linux kernel regression tracker. >>> >>> On 05.01.23 09:12, Thorsten Leemhuis wrote: >>>> [...] Quoting from https://bugzilla.kernel.org/show_bug.cgi?id=216885 : >>>> >>>>> David Roth 2023-01-04 20:37:22 UTC >>>>> >>>>> Created attachment 303526 [details] >>>>> Libinput record with G903 attached directly to USB >>>>> >>>>> Since >>>>> https://lore.kernel.org/linux-input/20220914132146.6435-1-hadess@xxxxxxxxxx/T/#u >>>>> my Logitech G903 has gained hi res support. While normally a good >>>>> thing, it seems that in this case it leads to generating one normal >>>>> REL_WHEEL with each REL_WHEEL_HI_RES event instead of just a couple >>>>> of REL_WHEEL_HI_RES, followed by the standard REL_WHEEL once a >>>>> notch/tick is reached. This leads to overly sensitive scrolling and >>>>> makes the wheel basically useless. >>> >>> Bastien, Benjamin, Jiri, that problem was reported 25 days ago now and >>> there is still no fix in sight afaics (please correct me if I'm wrong) >>> -- and based on the reports I've seen it seem quite a few people are >>> hitting it. Hence please allow me to ask: >>> >>> Wouldn't it be best to revert that change for now (both in mainline and >>> stable of course) and then reapply it once a fix for this problem is >>> available? Or >> >> Last I heard was that Bastien was actively trying to understand the >> problem. Yup, no complains there. Thx for your work on this, Bastien. But that debugging has already taken some time and it seem more is needed. And apparently it's more than just a single user or two that is affected by this. That's why I think it would be better to revert this temporarily[1], unless a fix suddenly comes into sight. [1] as strongly suggested by https://docs.kernel.org/process/handling-regressions.html , which states that a regression like this should ideally be fixed within a few days after the report; we are long past this... >> I do have a G903 here but it is lacking the feature the >> reporters have, and so I can not reproduce (there is likely a new >> firmware/model around). >> >> After a quick search on >> https://support.logi.com/hc/en-us/search#q=G903&s=all it seems that >> there are 2 G903: M-R0081 and M-R0068. I only own the 68 one which >> explains why I can not reproduce it. :( > > I have an affected mouse and am willing to try patches/fixes, but my > kernel coding fu is weak. Thx for your help, too. Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat) -- Everything you wanna know about Linux kernel regression tracking: https://linux-regtracking.leemhuis.info/about/#tldr If I did something stupid, please tell me, as explained on that page.
