Elantech touch pad device not detected/working properly

Bug #1725416 reported by Christian González
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
libinput (Ubuntu)
Fix Released
Undecided
Unassigned
linux (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

I just upgraded to Ubuntu 17.10 (hooray, GNOME!). But there are some quirks. Under Unity/Ubuntu 17.04 my built-in Touchpad worked flawlessly - especially the "natural scrolling" mode was working well. As I saw under Ubuntu Gnome 17.04, the corresponding setting in gnome-control-center "Natural scrolling" just targets the mouse and has no effect on the touchpad.

I can see the touchpad using "xinput list":
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ ETPS/2 Elantech Touchpad id=14 [slave pointer (2)]
⎜ ↳ Logitech Performance MX id=12 [slave pointer (2)]

alongside my Logitech mouse on a Unifying receiver.

Is there any chance that this touchpad is detected? Or should I forget about that (WONTFIX) as Xorg is already unsupported?
ATM I am using the prop. nvidia drivers. Currently uninstalling them to see if Wayland is starting using nouveau...
Thanks.
What else do you need from me?

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-control-center 1:3.26.1-0ubuntu4
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct 20 20:20:04 2017
InstallationDate: Installed on 2016-11-27 (327 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
SourcePackage: gnome-control-center
UpgradeStatus: Upgraded to artful on 2017-10-19 (0 days ago)

Revision history for this message
Christian González (droetker) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gnome-control-center (Ubuntu):
status: New → Confirmed
Revision history for this message
Ohto (ohto) wrote :

Dell E6540 with AMD graphics, same thing for me. Works fine with 17.04. Also, now I cannot enable both two finger scrolling and edgescrolling. Everything else (mouse, window sidescroll, arrow down) scrolls down when used, but not touchpad. Damn frustrating.

Revision history for this message
Christian González (droetker) wrote :

I recently installed Debian 9 with GNOME, it worked perfectly there. Upgraded to testing, keeped working. I don't know why Ubuntu is broken here, maybe just check the patch diff to debian. Must be there somewhere?

Again - how can I help here further?

affects: gnome-control-center (Ubuntu) → libinput (Ubuntu)
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Hi Christian,

I've just checked and toggling "Natural Scrolling" does work on touchpads for other people such as myself. You might want to check if the "Natural Scrolling" option is listed under "Touchpad" or under "Mouse". Make sure you set the one under "Touchpad".

If that doesn't fix it then the issue is probably that Ubuntu is mistaking your touchpad for a mouse. So the relevant configuration options you need for "Touchpad" may be missing, or may be misinterpreted.

Please start by providing a screenshot of your Mouse & Touchpad settings. And also you might want to try downgrading your Ubuntu kernel to 4.9 or earlier (so it's more like Debian 9):
  kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D
If Ubuntu is mistaking your touchpad for a mouse then that might fix it.

Changed in libinput (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Christian González (droetker) wrote :

Yes, true, I can see that the touchpad is not detected as own device - so all the settings apply to the mouse AND the (not separated) touchpad.
So the real problem is that thetouchpad is not properly detected.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

OK, then that's either a kernel bug or libinput.

The kernel discussion will happen here. But in case it's a libinput bug then please also report the problem here:
  https://bugs.freedesktop.org/enter_bug.cgi?product=wayland&component=libinput

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Please also try other kernel versions and tell us if some older or newer kernel fixes the problem for you:
  http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Christian González (droetker) wrote :

I just tested it using the bionic live image (couple of days old) - there it works perfectly, with the kernel 4.15. Maybe it's the 17.10 kernel - can't test it as I went back to 16.04 by now.

Changed in libinput (Ubuntu):
status: Incomplete → Fix Released
Changed in linux (Ubuntu):
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.