Created attachment 124726 [details] xinput list-props Dell Inspiron 3147 Ubuntu 16.04 after some time (about 3 or 4 hours) of using the laptop the quality of the tuchpad input seems to degrade. When i slide my finger over the touch pad it tries to select everything. instead of just moving across the screen it creates select windows as if i have the left button held. Once I restart the laptop it works fine for a few hours and eventually happens again Incidentally I did enable touch to click when i first installed libinput.
does the touchpad reset when you just restart X? if so then it's likely a libinput problem, otherwise it's probably a hardware issue. you can grab the libinput repo from http://cgit.freedesktop.org/wayland/libinput/ and build it (./autogen.sh && make). Make sure you have gtk+-devel installed to build ./tools/event-gui and run that as root. This shows how libinput interprets the events coming from the kernel. But it's a new libinput instance so when your touchpad degrades and you run the event-gui and that behaves normally, then again this would indicate a hw issue
No response for many moons, closing
Please reopen. I'm having this issue. I built libinput from source and ran the event-gui as root but the touchpad still becomes more and more unpredictable, jittery and eventually I have to issue: `sudo modprobe -r psmouse` and use my laptop touchscreen or reboot. The touchpad goes stupid usually after an increase in CPU cycles -- I know this because when I hear my laptop fan kick on almost immediately the touchpad starts acting up. Here's my info: Linux Mint 18.1 running on HP Envy 4-core `/proc/bus/input/devices/` I: Bus=0011 Vendor=0002 Product=0001 Version=0000 N: Name="PS/2 Synaptics TouchPad" P: Phys=isa0060/serio1/input0 S: Sysfs=/devices/platform/i8042/serio1/input/input181 U: Uniq= H: Handlers=mouse0 event6 B: PROP=1 B: EV=7 B: KEY=70000 0 0 0 0 B: REL=3 `dmsg` after `modprobe -r psmouse && modprobe psmouse` psmouse serio1: synaptics: Touchpad model: 1, fw: 8.1, id: 0x1e2b1, caps: 0xd00123/0x840300/0x12e800/0x0, board id: 2960, fw id: 1619168 [ 20.564628] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input5
modprobe removes the kernel module and resets the touchpad, the question is whether just restarting X/Wayland is sufficient. If so, that would indicate a userspace issue, right now, I suspect it's a kernel issue.
I booted up with LM 18 via USB thumb drive to see if I had the same issue (at first it didn't appear so) then I decided to create a new LM boot partition as soon as the laptop fan kicked on the mousepad became erratic. I have a number of kernels I've tried and all have the same issue. I even built 4.9 from source with some custom configs to see if I could get this worked out. I think this may be a hardware issue. My next step is to take my laptop apart and make sure all connections are solid (unless you have a different suggestion). Thanks for taking the time to look into this issue. It's gotten to the point that the modprobe reset solution no longer works or works for a very short time.
yeah, if the module removal changes or stops working that does suggest that there's a hardware issue involved. You could try with the battery removed or only on battery, with the battery fully charged etc. Sometimes electrical interference can cause similar issues. Other than that I don't have any good suggestions, sorry. But for now, I'll close this bug again, it does look like a hw issue.
Sorry for my lack of response on this. Yes Peter the touch pad issue did reset after restarting X, but further to this i noticed that I didn't actually have to restart X but just drop out to a TTY then back in to the Desk top environment ant the touch pad jitters went away. Strange thing is that a short while after this bug seemed to go away by its self. I haven had the problem in ages. It could possibly be the result of one of many other issues that I had to iron out when setting up my laptop. When I read Ryans comment about noticing a correlation between his fan speed and the touch pad jitters it got me wondering if it could have something to do with C-states. Forgive me if I am way off track (Im way over my head here) but the reason I mention it is that one of the fixes I had to do to my laptop after moving to ubuntu was to use kernel boot parameter:intel_idle.max_cstate=1. This was to fix a freezing problem that only happened when playing videos. I think the GPU or CPU uses more power when needed and this was causing the whole computer to completely freeze. the only way to recover was a total hard reboot. But after using the kernel boot parameter intel_idle.max_cstate=1 it stopped happening. And now im wondering if that is what fixed the erratic touch pad behavior. Again sorry if im way off track here I really have no idea what Im talking about... I only learned the basics to get my laptop working with ubuntu :/
Because I was having wifi issues (https://bugzilla.kernel.org/show_bug.cgi?id=191601) I actually had the intel_idle.max_cstate=1 as one of my boot parameters at one time. I figured out the wifi issue but will try the intel_idle.max_cstate=1 to see if it helps the touchpad problem and report back. Something else of note. I noticed if I have my wireless mouse plugged in that the touchpad behaves much better (not perfect and usually it takes longer to degrade).
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.