UPDATE: There is a full patch released now by the devs. Upgrade to the latest version to get the fix.
Briefly describe your issue below:
The touchpad doesn’t work after the latest update to 4.6.
What version of Parrot are you running? (include version, edition, and architecture)
Parrot GNU/Linux 4.6 x86_64
uname -a
Linux workstation 4.19.0-parrot3-28t-amd64 #1 SMP Parrot 4.19.28-2parrot3.28t (2019-04-14) x86_64 GNU/Linux
What method did you use to install Parrot? (Debian Standard / Debian GTK / parrot-experimental)
Debian GTK
Configured to multiboot with other systems? (yes / no)
Yes
If there are any similar issues or solutions, link to them below:
Debian Wiki Synaptics Touchpad
If there are any error messages or relevant logs, post them below:
Laptop is Dell XPS 15 9570 with synaptics trackpad
sudo dmesg | grep -i synaptics
[ 3.197568] psmouse serio1: synaptics: Unable to query device: -5
[ 8.893644] input: PS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input6
egrep -i 'synap|alps|etps|elan' /proc/bus/input/devices
N: Name="PS/2 Synaptics TouchPad"
Contents of /usr/share/X11/xorg.conf.d
drwxr-xr-x 1 root root 292 Apr 17 04:43 .
drwxr-xr-x 1 root root 104 Apr 14 16:27 ..
-rw-r--r-- 1 root root 92 Feb 7 13:19 10-amdgpu.conf
-rw-r--r-- 1 root root 1099 Aug 23 2018 10-evdev.conf
-rw-r--r-- 1 root root 1350 Oct 25 11:15 10-quirks.conf
-rw-r--r-- 1 root root 92 Feb 7 13:17 10-radeon.conf
-rw-r--r-- 1 root root 1429 Mar 30 18:56 40-libinput.conf
-rw-r--r-- 1 root root 113 Mar 11 2018 50-multitouch.conf
-rw-r--r-- 1 root root 1753 Aug 23 2018 70-synaptics.conf
-rw-r--r-- 1 root root 2747 Jun 26 2017 70-wacom.conf
lrwxrwxrwx 1 root root 50 Mar 25 22:40 nvidia-drm-outputclass.conf -> /etc/alternatives/glx--nvidia-drm-outputclass.conf
From what I’ve found online, this might be a conflict between xserver-xorg-input-libinput
and xserver-xorg-input-syaptics
, but it’s probably just because of the update to 4.6.
Copying everything from /usr/share/X11/xorg.conf.d
except 70-synaptics.conf
doesn’t fix the trackpad into /etc/X11/xorg.conf.d
doesn’t seem to have any effect either.
Is there any way to fix this issue? Or should I just wait for the next update?