Description of problem: Upgrading from 4.10.5-200.fc25.x86_64 to 4.10.12-200.fc25.x86_64 caused the touchpad/trackpad on my Dell Latitude E7370 (identified by Fedora as an AlpsPS/2 ALPS DualPoint TouchPad) to stop functioning correctly. The right-hand portion of the trackpad (pretty much everything above the right-hand button) stopped working. Booting back to 4.10.5-200.fc25.x86_64 fixes the problem. Version-Release number of selected component (if applicable): 4.10.12-200.fc25.x86_64 How reproducible: I rebooted the laptop numerous times (between the 4.10.12 and 4.10.5 kernels). When booted using 4.10.12, the trackpad's right side does not function as expected. When booted using 4.10.5, the trackpad functions as expected. Steps to Reproduce: 1. Boot a Dell Latitude E7370 running F25 and the 4.10.12-200.fc25.x86_64 kernel. 2. Try to use the right-hand portion of the trackpad. Moving the cursor *may* occasionally work; two-finger scrolling will *not* work. 3. Reboot the laptop using the 4.10.5-200.fc25.x86_64 kernel and the entire touchpad will work correctly. Actual results: Two finger scrolling on the right-hand side of the trackpad stops working entirely. Most cursor movement on the right-hand side of the trackpad also stops working. Expected results: Cursor movement and two-finger scrolling would work across the entire trackpad surface, as it does under 4.10.5-200.fc25.x86_64. Additional info: I don't have any other hardware on which to test this issue. It may be specific to this particular model of laptop or trackpad; I can't really verify. I can verify that 4.10.5 works and 4.10.12 does not with no other changes to the system.
Can you provide the output of 'xinput --list' please?
Sure. Here's the output from `xinput --list`: ⎡ Virtual core pointer id=2 [master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] ⎜ ↳ xwayland-pointer:13 id=6 [slave pointer (2)] ⎜ ↳ xwayland-relative-pointer:13 id=7 [slave pointer (2)] ⎜ ↳ xwayland-touch:13 id=9 [slave pointer (2)] ⎣ Virtual core keyboard id=3 [master keyboard (2)] ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)] ↳ xwayland-keyboard:13 id=8 [slave keyboard (3)] The output of this command is the same under 4.10.5 (where I'm running now in order to maintain touchpad functionality) and 4.10.12.
There were at least two changes to the AlPS driver during that window so one of those might have broken things. Can you test these two scratch builds and let me know if either of them make your touchpad work? https://koji.fedoraproject.org/koji/taskinfo?taskID=19464430 https://koji.fedoraproject.org/koji/taskinfo?taskID=19464460
I'm traveling for business (with only my Fedora laptop with me) and can't afford to be without a functional laptop, so I'll test this when I'm back in my office. Unfortunately, that won't be for another 12 days or so. I apologize for the delay and will test this as soon as it is safe for me to do so.
Sorry for the delays, I have time to test builds this week while I'm in my office. Looks like these scratch builds have expired.
I just tested with 4.10.17-200 and it exhibits the same behavior as 4.10.12-200.
https://koji.fedoraproject.org/koji/taskinfo?taskID=19785415 https://koji.fedoraproject.org/koji/taskinfo?taskID=19785422 are the updated scratch builds (still building)
I just tested these updated scratch builds. 4.11.3-201 DOES NOT address the problem with the trackpad (behavior is the same as under 4.10.12 and 4.10.17). 4.11.3-202 DOES address the problem with the trackpad (restores behavior found in 4.10.5, last working kernel version I've tested). Should I revert to 4.10.5 until this change is backported appropriately (or until it makes it into a released version)?
One additional note (it may be of no consequence, but wanted to be sure to point it out): both of these scratch builds introduce a new log entry pertaining to the iwlwifi driver that wasn't present in 4.10.5 (visible using `journalctl -b`): iwlwifi 0000:6d:00:0: capa flags index 3 larger than supported by driver Limited testing does not show any noticeable impact to wireless functionality or performance.
Thanks for testing and reporting. The wifi warning is harmless, if annoying, and can be ignored. This means that https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e7348396c6d51b57c95c6646c390cd078e038e19 is the change which broke your touchpad. I can report this upstream to the developers or you can do so yourself, whichever you prefer.
Thanks, Laura. I'm not familiar with the process for reporting to the upstream developers. If you don't mind doing it, then I'd appreciate it.
Upstream made a request to try another test https://koji.fedoraproject.org/koji/taskinfo?taskID=19873270
This latest build (4.11.3-203-testalpspatch) does not fully resolve the issue. Cursor movement seems to work, but there are intermittent two-finger scrolling issues on the right-hand side of the touchpad. There are no issues with cursor movement or two-finger scrolling on the left-hand side of the touchpad. This is an improvement from 4.11.3-201 (which had consistent cursor movement and two-finger scrolling issues on the right-hand side of the touchpad), but a regression from 4.11.3-202 (which had no issues with cursor movement or two-finger scrolling). With 4.11.3-203-testalpspatch, cursor movement works but two-finger scrolling is spotty (doesn't work consistently).
Yet another test build https://koji.fedoraproject.org/koji/taskinfo?taskID=20002908
I just tested 4.11.4-201.testalpspatch, and it appears as if this resolves all remaining touchpad issues. Cursor movement works as expected, both on the left-hand and right-hand sides of the touchpad, and I did not see any issues with two-finger scrolling on either side of the touchpad. Behavior with this test build appeared to be identical to 4.10.5, the last "official" kernel release to work with my touchpad. Let me know if you need additional information.
Laura, Any other information needed?
The discussion has been happening upstream but the upstream maintainers don't really seem to have a good grasp on the problem.
ok so still ongoing?
I'm not quite sure what you mean by ongoing. The last response was "Wow, this is weird ... Values that cause scrolling issues for you work fine for me." and a request for another reporter to print out values in the kernel.
by "ongoing" I just meant: "is the conversation is still happening and hasn't died?" You've answered my question. Thank you!
Okay upstream came back with a proposal that worked for someone else who had the same problem, https://koji.fedoraproject.org/koji/taskinfo?taskID=20633752 is the test build
Hi Laura, I won't have time to test this build until the week of 31 July. I've downloaded the test builds from the link above (so I have them in case the links/builds expire before 31 July). I'll report back once I've had the chance to test.
Hello all, sorry for the delay in responding back. I've had a chance to test the 4.11.11-201 builds, and here's what I've found. With the exception of a small (finger-width) section along the right-hand side of the trackpad, everything seems to work as expected. However, within that small finger-width section on the right-hand side, there is no pointer movement (using a single finger) or scrolling (using two fingers).
Oh, I should add this note: regarding the finger-width section, pointer movement and scrolling only fail if the action *originates* within that section. If you move into that section from elsewhere on the trackpad, pointer movement and scrolling still seem to work. It's only when the action starts within that space (and stays within that space) that the action fails.
Thanks for testing. I'm guessing the bad section is related to some part of the tracking that's still not quite accurate. I can't tell if the person who gave the fix didn't have the same problem or just didn't test it. The fix is getting picked up by the input maintainer though so getting this refined will involve more back and forth with the maintainer.
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.