As a workaround, I am happy to share my bash script that can be ran
using a keyboard shortcut whenever the touchpad may act up (have to log
in first), please see attached. To assign it to a keyboard shortcut, go
to Settings > Keyboard Shortcuts > scroll down to the end of the
shortcuts and add a
@Kai-Heng, given the amount of investigation and testing we have put
into this, should we mark this bug as confirmed or is it still
technically incomplete?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Califa, I am sorry to hear for you bad experience.
@Kai-Heng, OK so I don't think I have the proper know-how to
successfully set up the systemd oneshot service. However, the best
solution I currently have set up is a keyboard shortcut that runs a bash
script that resets the touchpad on demand
@Califa, I left Windows behind a long time ago, I only use it at work
now due to it being on my work machine. It is a personal preference for
me to use Ubuntu. Yes, I could easily go back to Windows but I will not.
As I said before, I am not absolutely stuck as I have an external mouse.
I would
@Kai-Heng, thanks, much appreciated. I will configure this evening will
let you know how it goes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884288
Title:
LapBook Pro touchpad (HTIX5288:00)
@Kai-Heng, thanks. Just so I don't go and make a mistake along the way,
could you please forward me on a tutorial/blog page that gives a step by
step on how to set up Systemd oneshot. Thank you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
@Kai-Heng, unfortunately that latest kernel you compiled has not solved
it, touchpad is dead with both a cold boot and restart.
Is there a way of running the following:
sudo rmmod i2c_hid
sudo modprobe i2c_hid
automatically at boot?
Apologies if this is what you were trying to do all this
UPDATE:
OK, so routing around some more articles about similar problems, I found
this:
https://askubuntu.com/questions/1041820/touchpad-not-working-on-
ubuntu-18-04
The first answer in the article gives me a partial solution where I can
get the touchpad back working again mid-session:
sudo
The holy grail here is obviously trying to crack what Windows is doing
in the background that has the touchpad working perfectly every time.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884288
@Kai-Heng, are there other potential workarounds that may help with
this? If you need any additional logs from me please don't hesitate to
ask.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884288
@Califa, yes, the same as me, but when you boot Windows the touchpad
works every time, yes?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884288
Title:
LapBook Pro touchpad (HTIX5288:00) sometimes
I stripped my machine of Windows in favour of Ubuntu without a
partition, unfortunately I could not foresee this problem with the
touchpad.
@Califa may be able to answer your question as I think they still have
Windows on their machine.
--
You received this bug notification because you are a
Apologies, I meant Your
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884288
Title:
LapBook Pro touchpad (HTIX5288:00) sometimes does not work when
machine is restarted
To manage notifications
Tour kernel does seem to dramatically lower the chances of the touchpad
not working upon reboot if that makes any sense. The newer Ubuntu kernel
is very hit nad miss with the touchpad after reboot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Likewise when it is working, it will never spontaneously stop working in
the middle of a session.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884288
Title:
LapBook Pro touchpad (HTIX5288:00)
Not working directly after boot, this was always the issue, never in the
middle of usage.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884288
Title:
LapBook Pro touchpad (HTIX5288:00) sometimes
It's an all or nothing bug for my machine, if it doesn't work directly
after boot it will never spontaneously start working again in the middle
of a session.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Kai-Heng, unfortunately after a cold boot this afternoon the touchpad
is not working again. The machine was off for the best part of 15 hours.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884288
@Kai-Heng, both power off and restart are now working with that latest
5.4 kernel you asked me to test.
error: can't find command 'hwmatch' still appears at the powering on
screen but I am not sure if this is important to the larger scheme of
things.
So far so good with the touchpad working both
@Kai-Heng, please see attached a more details relating to machine
hanging on restart, this was where I removed "quiet" in the grub to
display messages.
** Attachment added: "IMG_20200706_184801.jpg"
@Kai-Heng, power off (cold boot) is back working but a restart still
hangs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884288
Title:
LapBook Pro touchpad (HTIX5288:00) sometimes does not work
that's with the 5.4 based kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884288
Title:
LapBook Pro touchpad (HTIX5288:00) sometimes does not work when
machine is restarted
To manage
sorry, I meant to type "hwmatch"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884288
Title:
LapBook Pro touchpad (HTIX5288:00) sometimes does not work when
machine is restarted
To manage
@Kai-Heng, I have my machine pointing to your kernel permanently and so
far so good with a cold reboot.
However, when I go to power it down or restart the machine hangs on the
logo screen, I have to hold down the power button to forcibly shut it
down. Is there something wrong with my GRUB? This
@Kai-Heng, please excuse my lack of knowledge and experience in dealing
with kernels, could you please tell me how to pick your kernel from
GRUB, thank you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Kai-Heng, I installed your kernel files one by one using gdebi and ran
sudo reboot, is that enough to change kernel? Please see most recent
journal log after kernel install.
** Attachment added: "journal.txt"
@Califa, please see steps in link to install kernel:
https://itsfoss.com/install-deb-files-ubuntu/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884288
Title:
LapBook Pro touchpad (HTIX5288:00)
@You-Sheng, please find journal attached.
This was my grub settings to run it, was this correct?
GRUB_DEFAULT=0
GRUB_TIMEOUT_STYLE=hidden
GRUB_TIMEOUT=0
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash hid.debug=1 i2c-hid.debug=1
@Califa, first run the following in terminal:
sudo apt-get update
sudo apt-get install acpi
Then followed by:
sudo acpidump > acpidata.dat
You will then find the .day file saved in your home folder.
I hope this will be of benefit to the developer(s) in trying to solve
our problem.
You have
Apologies, I meant .dat
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884288
Title:
LapBook Pro touchpad (HTIX5288:00) sometimes does not work when
machine is restarted
To manage notifications
Please note, that acpidata.dat dump was ran with the touchpad working,
should I run dump when touchpad is not working or does it matter?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884288
Title:
@Califa, also this:
https://wiki.ubuntu.com/Kernel/Reference/ACPITricksAndTips
Also, to address your doubt about CHUWI, I have also wondered exactly
what you are saying, perhaps this acpidump is the first step in the
right direction.
--
You received this bug notification because you are a
@Kai-Heng Feng, please see acpidata.dat attached.
@Califa, please see https://sarata.com/manpages/acpidump.8.html
** Attachment added: "acpidata.dat"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884288/+attachment/5389157/+files/acpidata.dat
--
You received this bug notification
Update from the laptop manufacturer [CHUWI] regarding BIOS update:
"Hello, it is recommended that you reinstall the factory single windows
system, we did not do any drivers and bios for Linux"
Looks like a BIOS update is out of the question.
--
You received this bug notification because you
No worries, I just hope this can be looked into further by the
developers. I also have not had a reply from Chuwi regarding a potential
BIOS update, not sure how long of a wait to expect.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I think it is best to leave the status of this bug as confirmed as we
have provided enough information to identify the problem, as decided by
@You-Sheng Yang. This status is also the precursor to "In Progress",
meaning that hopefully a developer will pick up on this and work on a
solution.
--
Hi Califa, thank you for your suggestion. Unfortunately this has not
solved my problem. I tried a reboot after updating GRUB file and
touchpad gone again. This is what the GRUB looks like now:
GRUB_DEFAULT=0
GRUB_TIMEOUT_STYLE=hidden
GRUB_TIMEOUT=0
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null
No worries Califa, I was basically saying that it looks like a signal
integrity issue where there are errors with reading the touchpad driver
when laptop is starting up after a restart or shutdown.
An older bug issue on another forum seemed to have come across this, in
both Arch Linux and Ubuntu:
I mean absolutely no disrespect by my last comment in reference to
Windows, I truly love Ubuntu and Open Source projects in general, this
is just an unfortunate issue that I hope I will be able to find a
solution to.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
This link https://bbs.archlinux.org/viewtopic.php?id=231540 although
dated from 2018 appears to be a similar issue, but what is interesting
is the comment at the very bottom of the page regarding a possible
signal integrity issue. What's more interesting is that those who have
dual boots /
@Califa101, yes, I have Ubuntu 20.04 also running on a much older
Samsung laptop, no issues with touchpad. It appears to be specific to
the Chuwi LapBook Pro laptop and whatever way it is configured. I am
just not sure if a BIOS update exists as you correctly pointed out that
the BIOS dates from
I updated the keyboard and mouse configuration to "Enabled" in the BIOS
as opposed to the default "Auto". Results looked promising with 4
restarts but then touchpad failed on the fifth.
I restarted again and it's working. The random pattern of the issue is
frustrating to say the least.
--
You
@Califa101, that potential solution from the unix exchange is for a fix
where touchpad seems to stop working on battery mode but works when
charger is plugged in. I can confirm that this is not my issue, touchpad
can stop working upon restart regardless of being plugged in or not.
As of last
@Califa101, that unix.exchange.com question looks very promising, I will
have a look at it over the next day or two and see if I can get
somewhere with it.
In the meantime, it would be great if one of the programmers and/or
developers that have already assisted with this bug could have a look at
@Califa101, I can also confirm that my BIOS is from 2019.
I do not have a partition set up on my laptop, I completely removed
Windows from it when installing Ubuntu, so unfortunately I will not be
able to test this.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
@Califa101, I raised a ticket on 26/06/2020 with Chuwi to obtain an
update for my BIOS, I haven't received a reply yet so I am not sure if
this is something that Chuwi will issue us with or if it will actually
solve the problem.
--
You received this bug notification because you are a member of
Ok, thanks. Is a BIOS update the only real solution to this issue? In
the event where this may not be possible, is there another possible
solution?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I appended the kernel boot parameters and touchpad is working again,
hopefully that was the solution.
Please find attached journal.txt
** Attachment added: "journal.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884288/+attachment/5387197/+files/journal.txt
--
You received this
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1884288/+attachment/5387047/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884288
Apologies, just realised that it is sent here, please excuse my lack of
experience with reporting of bugs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884288
Title:
LapBook Pro touchpad
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1884288/+attachment/5387041/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1884288/+attachment/5387043/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I ran sudo apport-collect 1884288 and got the following in the terminal:
dpkg-query: no packages found matching linux
This was followed by a problem report GUI where I selected "send problem
report"
Is this saved somewhere on my machine so I can upload it to here or
would you have access to the
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1884288/+attachment/5387008/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884288
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1884288/+attachment/5387036/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884288
Title:
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1884288/+attachment/5387012/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884288
Title:
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1884288/+attachment/5387046/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884288
Title:
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1884288/+attachment/5387040/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884288
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1884288/+attachment/5387039/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884288
Title:
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1884288/+attachment/5387004/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884288
Title:
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1884288/+attachment/5387042/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884288
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1884288/+attachment/5387045/+files/RfKill.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884288
Title:
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1884288/+attachment/5387044/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884288
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1884288/+attachment/5387000/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1884288/+attachment/5387034/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1884288/+attachment/5387002/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884288
Title:
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1884288/+attachment/5387006/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884288
apport information
** Attachment added: "AlsaInfo.txt"
https://bugs.launchpad.net/bugs/1884288/+attachment/5387032/+files/AlsaInfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884288
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1884288/+attachment/5387037/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884288
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1884288/+attachment/5387038/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884288
Title:
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1884288/+attachment/5387009/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1884288/+attachment/5386999/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884288
Title:
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1884288/+attachment/5387033/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884288
Title:
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1884288/+attachment/5387001/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884288
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1884288/+attachment/5387003/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884288
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1884288/+attachment/5387010/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884288
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1884288/+attachment/5387013/+files/WifiSyslog.txt
** Description changed:
Touchpad completely ceases to work sometimes upon startup / restart.
When this happens, I have to plug in an external mouse
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1884288/+attachment/5387007/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Tags added: apport-collected
** Description changed:
Touchpad completely ceases to work sometimes upon startup / restart.
When this happens, I have to plug in an external mouse to navigate as
touchpad is not even recognised as a device when I use xinput command in
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1884288/+attachment/5387005/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884288
Title:
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1884288/+attachment/5387035/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884288
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1884288/+attachment/5387011/+files/RfKill.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884288
Title:
I restarted laptop twice without touching touchpad until I get user
login screen and worked fine. However, on another reboot, I touched the
touchpad several times during the startup screen and it is not working
again. I am not sure if this helps in the testing of this. Anyway, it is
back to the
I restarted the laptop again to see if it helps and it is back working.
I am not sure if this helps but when I move the touchpad around and
pressing the left and right during the startup screen it seems it may
help, I am not sure if this is complete nonsense or not.
It is now listed in the
Unfortunately event 3 is not the touchpad, nor is 4, see below:
EVENT 3:
Input device name: "Intel HID events"
Supported events:
Event type 0 (EV_SYN)
Event type 1 (EV_KEY)
Event code 69 (KEY_NUMLOCK)
Event code 102 (KEY_HOME)
Event code 104 (KEY_PAGEUP)
Event code 107
Please see below results of evtest:
No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0: Lid Switch
/dev/input/event1: Power Button
/dev/input/event2: AT Translated Set 2 keyboard
/dev/input/event3: Intel HID events
I removed 'xserver-xorg-input-synaptics' and upon restart touchpad
stopped working again, I am now using an external mouse to navigate as
touchpad have completely ceased to work. Please see attached journal.txt
** Attachment added: "journal.txt"
** Description changed:
Touchpad completely ceases to work sometimes upon startup / restart.
When this happens, I have to plug in an external mouse to navigate as
touchpad is not even recognised as a device when I use xinput command in
terminal. I removed and reinstalled
Public bug reported:
Touchpad completely ceases to work sometimes upon startup / restart.
When this happens, I have to plug in an external mouse to navigate as
touchpad is not even recognised as a device when I use xinput command in
terminal. I removed and reinstalled xserver-xorg-input-synaptics
89 matches
Mail list logo