Bug#1031188: linux: synaptics speed/sensitivity messed up with 6.1.0-4
Hi Christoph, On Sat, Feb 18, 2023 at 01:35:07AM +0100, Christoph Anton Mitterer wrote: > Hey Salvatore. > > On Wed, 2023-02-15 at 07:12 +0100, Salvatore Bonaccorso wrote: > > Just to be sure, that I understood you correctly. That is if on the > > current system with the issue you roll back just only the kernel back > > to 6.1.8-1, then the issue dissaper? > > Exactly, and the roll back even only in the sense of just booting the > previous one (I do not even reinstall packages or so). > > > > If this is the case, would you be testing as well directly 6.1.8 and > > 6.1.11 upstream (please do as well 6.1.12, 6.1.12-1 though just > > uploaded to unstable earlier today), and if reproducible, bisect the > > changes between the two versions to find the introducing bad commit? > > I've tested 6.1.12 in the meantime, ... still has the problem. > > In fact it seems as if any changes I make with the synclient tool to > the relevant settings e.g.: > $ synclient MinSpeed=0.5 MaxSpeed=1.5 AccelFactor=0.5 > have no longer any effect at all. > > Even if I set extreme values, nothing seems to change. > > > I've also taken the src:linux package (as of 6.1.12) recompiled it just > with: > 6816478c0db15ad0dbe7f9b6ffaff9ad6db5e74d > reverted. > That seemed the most promising one, despite me NOT having an HP > notebook (which that commit is allegedly about, but rather a Fujitsu). > > But no change with that. May you with 6.1.20-1 which should soon reach testing as well? Is the issue still present? > If you want me to test 6.1.8/12 upstream... is it enough to simply take > the Debian source packages and unapply any Debian patches? > I'm always quite reluctant of taking any code which I cannot properly > verify myself (and I don't trust github or https enough ;-) ) Well if at some point we need to bisect, you have to go to upstream git. The tags are signed by Greg, and you find a copy of his key as well in the Debian source in debian/upstream/signing-key.asc . So if 6.1.20 ist still affected, if this is possible for you, bisecting it between the versions can help us pin point the introducing commit and report it upstream. Regards, Salvatore
Bug#1031188: linux: synaptics speed/sensitivity messed up with 6.1.0-4
Hey Salvatore. On Wed, 2023-02-15 at 07:12 +0100, Salvatore Bonaccorso wrote: > Just to be sure, that I understood you correctly. That is if on the > current system with the issue you roll back just only the kernel back > to 6.1.8-1, then the issue dissaper? Exactly, and the roll back even only in the sense of just booting the previous one (I do not even reinstall packages or so). > If this is the case, would you be testing as well directly 6.1.8 and > 6.1.11 upstream (please do as well 6.1.12, 6.1.12-1 though just > uploaded to unstable earlier today), and if reproducible, bisect the > changes between the two versions to find the introducing bad commit? I've tested 6.1.12 in the meantime, ... still has the problem. In fact it seems as if any changes I make with the synclient tool to the relevant settings e.g.: $ synclient MinSpeed=0.5 MaxSpeed=1.5 AccelFactor=0.5 have no longer any effect at all. Even if I set extreme values, nothing seems to change. I've also taken the src:linux package (as of 6.1.12) recompiled it just with: 6816478c0db15ad0dbe7f9b6ffaff9ad6db5e74d reverted. That seemed the most promising one, despite me NOT having an HP notebook (which that commit is allegedly about, but rather a Fujitsu). But no change with that. If you want me to test 6.1.8/12 upstream... is it enough to simply take the Debian source packages and unapply any Debian patches? I'm always quite reluctant of taking any code which I cannot properly verify myself (and I don't trust github or https enough ;-) ) Thanks, Chris.
Bug#1031188: linux: synaptics speed/sensitivity messed up with 6.1.0-4
Control: tags -1 + moreinfo Hi Christoph, On Sun, Feb 12, 2023 at 11:28:52PM +0100, Christoph Anton Mitterer wrote: > Source: linux > Version: 6.1.11-1 > Severity: normal > > > Hey. > > Over the year this has unfortunately happened numerous times, either by > changes > in the Xorg driver, or libinput... and now it seems the kernel caused the > same: > > After upgrading from linux-image-6.1.0-3-amd64 to linux-image-6.1.0-4-amd64 > and > after a reboot, the speed and senstivity of the touchpad were quite messed up. > > Sounds like no issue, but is actually extremely annoying as one typically gets > quite strongly used to those... and it seem I cannot even restore the previous > behaviour by the usual switches. > > No other packages (that have remotely to do with X, libinput or so) were > upgraded > so I think it must be something in the kernel. > OTOH, looking thorough the changelog from .9 to .11 there seems to be nothing > where they write it would change the settings (though there were in fact some > libinput/synaptics related commits). > > Any ideas how the previous behaviour can be gotten back? Just to be sure, that I understood you correctly. That is if on the current system with the issue you roll back just only the kernel back to 6.1.8-1, then the issue dissaper? If this is the case, would you be testing as well directly 6.1.8 and 6.1.11 upstream (please do as well 6.1.12, 6.1.12-1 though just uploaded to unstable earlier today), and if reproducible, bisect the changes between the two versions to find the introducing bad commit? Regards, Salvatore
Bug#1031188: linux: synaptics speed/sensitivity messed up with 6.1.0-4
Source: linux Version: 6.1.11-1 Severity: normal Hey. Over the year this has unfortunately happened numerous times, either by changes in the Xorg driver, or libinput... and now it seems the kernel caused the same: After upgrading from linux-image-6.1.0-3-amd64 to linux-image-6.1.0-4-amd64 and after a reboot, the speed and senstivity of the touchpad were quite messed up. Sounds like no issue, but is actually extremely annoying as one typically gets quite strongly used to those... and it seem I cannot even restore the previous behaviour by the usual switches. No other packages (that have remotely to do with X, libinput or so) were upgraded so I think it must be something in the kernel. OTOH, looking thorough the changelog from .9 to .11 there seems to be nothing where they write it would change the settings (though there were in fact some libinput/synaptics related commits). Any ideas how the previous behaviour can be gotten back? Thanks, Chris. -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable') merged-usr: no Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-3-amd64 (SMP w/16 CPU threads; PREEMPT) Locale: LANG=en_DE.UTF-8, LC_CTYPE=en_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
