Touchpad stops responding in MX Linux

Its not a mouse, its the pointer on the screen freezes,
moving it around by the touchpad then becomes impossible.
I can plug in a USB mouse and it will work fine, its just the
touchpad can no longer move the pointer around the screen.

I just don't want to be carrying a mouse around, should really
be able to use the touchpad as expected.
 


Lets see which driver your touchpad is using
Code:
xinput list
you should see something like this - NOTE you may need to install xinput -
Code:
sudo apt install xinput

Code:
Virtual core pointer                        id=2    [master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer                  id=4    [slave  pointer  (2)]
⎜   ↳ PixArt USB Optical Mouse                    id=12    [slave  pointer  (2)]
⎜   ↳ SynPS/2 Synaptics TouchPad                  id=15    [slave  pointer  (2)]

As you can see the touchpad is id=15 on my machine - yours may be different
then type in
Code:
xinput list-props 15
just substitute the 15 for whatever your touchpad is
your output should look something like this
Code:
Device 'SynPS/2 Synaptics TouchPad':
    Device Enabled (188):    1
    Coordinate Transformation Matrix (190):    1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
    Device Accel Profile (319):    1
    Device Accel Constant Deceleration (320):    2.500000
    Device Accel Adaptive Deceleration (321):    1.000000
    Device Accel Velocity Scaling (322):    12.500000
    Synaptics Edges (342):    1645, 5357, 1484, 4414
    Synaptics Finger (343):    25, 30, 0
    Synaptics Tap Time (344):    180
    Synaptics Tap Move (345):    241
    Synaptics Tap Durations (346):    180, 180, 100
    Synaptics ClickPad (347):    1
    Synaptics Middle Button Timeout (348):    0
    Synaptics Two-Finger Pressure (349):    282
    Synaptics Two-Finger Width (350):    7
    Synaptics Scrolling Distance (351):    109, 109
    Synaptics Edge Scrolling (352):    1, 0, 0
    Synaptics Two-Finger Scrolling (353):    1, 0
    Synaptics Move Speed (354):    1.000000, 1.750000, 0.036390, 0.000000
    Synaptics Off (355):    0
    Synaptics Locked Drags (356):    0
    Synaptics Locked Drags Timeout (357):    5000
    Synaptics Tap Action (358):    2, 3, 0, 0, 1, 3, 0
    Synaptics Click Action (359):    1, 3, 0
    Synaptics Circular Scrolling (360):    0
    Synaptics Circular Scrolling Distance (361):    0.100000
    Synaptics Circular Scrolling Trigger (362):    0
    Synaptics Circular Pad (363):    0
    Synaptics Palm Detection (364):    0
    Synaptics Palm Dimensions (365):    10, 200
    Synaptics Coasting Speed (366):    20.000000, 50.000000
    Synaptics Pressure Motion (367):    30, 160
    Synaptics Pressure Motion Factor (368):    1.000000, 1.000000
    Synaptics Resolution Detect (369):    1
    Synaptics Grab Event Device (370):    0
    Synaptics Gestures (371):    1
    Synaptics Capabilities (372):    1, 0, 0, 1, 1, 1, 1
    Synaptics Pad Resolution (373):    1, 1
    Synaptics Area (374):    0, 0, 0, 0
    Synaptics Soft Button Areas (375):    3501, 0, 4038, 0, 0, 0, 0, 0
    Synaptics Noise Cancellation (376):    27, 27
    Device Product ID (312):    2, 7
    Device Node (311):    "/dev/input/event7"

This is from my machine as you can tell it is using Synaptics you may need to try the libinput driver or vice-versa
 
Code:
Mx1@Mx1:~
$ xinput list
⎡ Virtual core pointer                        id=2    [master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer                  id=4    [slave  pointer  (2)]
⎜   ↳ HTIX5288:00 0911:5288 Mouse                 id=9    [slave  pointer  (2)]
⎜   ↳ HTIX5288:00 0911:5288 Touchpad              id=10    [slave  pointer  (2)]
⎣ Virtual core keyboard                       id=3    [master keyboard (2)]
    ↳ Virtual core XTEST keyboard                 id=5    [slave  keyboard (3)]
    ↳ Video Bus                                   id=6    [slave  keyboard (3)]
    ↳ Power Button                                id=7    [slave  keyboard (3)]
    ↳ USB 2.0 Camera: USB Camera                  id=8    [slave  keyboard (3)]
    ↳ Intel HID events                            id=11    [slave  keyboard (3)]
    ↳ Intel HID 5 button array                    id=12    [slave  keyboard (3)]
    ↳ AT Translated Set 2 keyboard                id=13    [slave  keyboard (3)]
    ↳ ACPI Virtual Keyboard Device                id=14    [slave  keyboard (3)]
Mx1@Mx1:~
$

Code:
Mx1@Mx1:~
Mx1@Mx1:~
$ xinput list-props 10
Device 'HTIX5288:00 0911:5288 Touchpad':
    Device Enabled (188):    1
    Coordinate Transformation Matrix (190):    1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
    Device Accel Profile (315):    1
    Device Accel Constant Deceleration (316):    2.000000
    Device Accel Adaptive Deceleration (317):    1.000000
    Device Accel Velocity Scaling (318):    12.500000
    Synaptics Edges (341):    52, 1258, 51, 894
    Synaptics Finger (342):    25, 30, 0
    Synaptics Tap Time (343):    180
    Synaptics Tap Move (344):    71
    Synaptics Tap Durations (345):    180, 180, 100
    Synaptics ClickPad (346):    1
    Synaptics Middle Button Timeout (347):    0
    Synaptics Two-Finger Pressure (348):    282
    Synaptics Two-Finger Width (349):    7
    Synaptics Scrolling Distance (350):    32, 32
    Synaptics Edge Scrolling (351):    1, 1, 1
    Synaptics Two-Finger Scrolling (352):    1, 1
    Synaptics Move Speed (353):    1.000000, 2.000000, 0.075000, 0.000000
    Synaptics Off (354):    1
    Synaptics Locked Drags (355):    0
    Synaptics Locked Drags Timeout (356):    5000
    Synaptics Tap Action (357):    0, 9, 0, 8, 1, 2, 3
    Synaptics Click Action (358):    1, 3, 2
    Synaptics Circular Scrolling (359):    1
    Synaptics Circular Scrolling Distance (360):    0.100000
    Synaptics Circular Scrolling Trigger (361):    7
    Synaptics Circular Pad (362):    0
    Synaptics Palm Detection (363):    0
    Synaptics Palm Dimensions (364):    10, 200
    Synaptics Coasting Speed (365):    8.000000, 50.000000
    Synaptics Pressure Motion (366):    30, 160
    Synaptics Pressure Motion Factor (367):    1.000000, 1.000000
    Synaptics Grab Event Device (368):    0
    Synaptics Gestures (369):    1
    Synaptics Capabilities (370):    1, 0, 0, 1, 1, 0, 0
    Synaptics Pad Resolution (371):    15, 15
    Synaptics Area (372):    0, 0, 0, 0
    Synaptics Soft Button Areas (373):    655, 0, 774, 0, 0, 0, 0, 0
    Synaptics Noise Cancellation (374):    8, 8
    Device Product ID (311):    2321, 21128
    Device Node (312):    "/dev/input/event4"
Mx1@Mx1:~
$ 

$ xinput list-props 10
Device 'HTIX5288:00 0911:5288 Touchpad':
    Device Enabled (188):    1
    Coordinate Transformation Matrix (190):    1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
    Device Accel Profile (315):    1
    Device Accel Constant Deceleration (316):    2.000000
    Device Accel Adaptive Deceleration (317):    1.000000
    Device Accel Velocity Scaling (318):    12.500000
    Synaptics Edges (341):    52, 1258, 51, 894
    Synaptics Finger (342):    25, 30, 0
    Synaptics Tap Time (343):    180
    Synaptics Tap Move (344):    71
    Synaptics Tap Durations (345):    180, 180, 100
    Synaptics ClickPad (346):    1
    Synaptics Middle Button Timeout (347):    0
    Synaptics Two-Finger Pressure (348):    282
    Synaptics Two-Finger Width (349):    7
    Synaptics Scrolling Distance (350):    32, 32
    Synaptics Edge Scrolling (351):    1, 1, 1
    Synaptics Two-Finger Scrolling (352):    1, 1
    Synaptics Move Speed (353):    1.000000, 2.000000, 0.075000, 0.000000
    Synaptics Off (354):    1
    Synaptics Locked Drags (355):    0
    Synaptics Locked Drags Timeout (356):    5000
    Synaptics Tap Action (357):    0, 9, 0, 8, 1, 2, 3
    Synaptics Click Action (358):    1, 3, 2
    Synaptics Circular Scrolling (359):    1
    Synaptics Circular Scrolling Distance (360):    0.100000
    Synaptics Circular Scrolling Trigger (361):    7
    Synaptics Circular Pad (362):    0
    Synaptics Palm Detection (363):    0
    Synaptics Palm Dimensions (364):    10, 200
    Synaptics Coasting Speed (365):    8.000000, 50.000000
    Synaptics Pressure Motion (366):    30, 160
    Synaptics Pressure Motion Factor (367):    1.000000, 1.000000
    Synaptics Grab Event Device (368):    0
    Synaptics Gestures (369):    1
    Synaptics Capabilities (370):    1, 0, 0, 1, 1, 0, 0
    Synaptics Pad Resolution (371):    15, 15
    Synaptics Area (372):    0, 0, 0, 0
    Synaptics Soft Button Areas (373):    655, 0, 774, 0, 0, 0, 0, 0
    Synaptics Noise Cancellation (374):    8, 8
    Device Product ID (311):    2321, 21128
    Device Node (312):    "/dev/input/event4"
Mx1@Mx1:~
$
 
@Here To Learn man, it looks like you're living up to your name.
sudo apt update now shows two packages for update, I think they are wifi drivers,

rtl8812au-dkms/mx,mx 5.6.4.2-1mx21+1 all [upgradable from: 4.2.2-1~mx21+1]
rtl8814au-dkms/mx,mx 5.8.5.1-1~mx21+2 all [upgradable from: 5.8.5.1-1~mx21+1]

then when I try to update them, I get the message telling me they were not updated
and held back, I don't understand this either, my past experience with Linux has
been that updates were installed, never held back.
Yes, they are wifi. Are there any errors indicating why they are held back, like dependencies? We're kind of getting into different territory here.
 
@Here To Learn man, it looks like you're living up to your name.

Yes, they are wifi. Are there any errors indicating why they are held back, like dependencies? We're kind of getting into different territory here.
Yes, I thought they were WiFi drivers, but the WiFi is working, below shows the
results of the upgrade command, I can't see WiFi having anything to do with the
onscreen pointer freezing, not do I have issues with the WiFi so am leaving them alone.
Code:
Mx1@Mx1:~
$ sudo apt update
[sudo] password for Mx1:
Hit:1 http://deb.debian.org/debian bullseye-updates InRelease
Hit:2 http://security.debian.org/debian-security bullseye-security InRelease                       
Hit:3 http://deb.debian.org/debian bullseye InRelease                                             
Hit:4 https://brave-browser-apt-release.s3.brave.com stable InRelease                             
Hit:5 http://mxrepo.com/mx/repo bullseye InRelease                                                 
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
2 packages can be upgraded. Run 'apt list --upgradable' to see them.
Mx1@Mx1:~
$ sudo apt upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following package was automatically installed and is no longer required:
  libllvm11
Use 'sudo apt autoremove' to remove it.
The following packages have been kept back:
  rtl8812au-dkms rtl8814au-dkms
0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
Mx1@Mx1:~
$
 
I also see liblvm11 in the list to autoremove, I left it be for now,
had a look at what that library does, I can't see it causing the onscreen pointer
to freeze, or am I wrong again, is it safe to remove it, seems like its being ignored anyway.

libllvm11_11.0.1-2_amd64.debModular compiler and toolchain technologies, runtime library
 
So we're on the same page, the touchpad works UNTIL you update, then gets weird? I'm thinking you might need to try booting to a previous kernel version, assuming the kernel was updated.
Also, check this out: It's a Gentoo forum, but there seems to be some solutions that might work for you.
 
Well am on battery power now after a fresh install of MX Linux.
Initially the built in software notifier in the panel said up to date.
But when I ran sudo apt update and sudo apt --list upgradable I
got a list of items that I could update.


So, to summarise, in running sudo apt --list upgradable....you went looking for the latest and greatest....and without a doubt you found it.
But, in so doing you have introduced a whole tin full of problems
It may well be that those apps etc that were upgradable, were not included in the Software Notifiers output for good reason. One of those reasons may well be that they break things.......maybe they are untested at this stage......and therefore you take that action at your own risk.

If everything was working as hoped for, I would not have taken that extra step
 
When your touchpad quits try to Enable it by running
Code:
xinput set-prop "HTIX5288:00 0911:5288 Touchpad" "Device Enabled" 1
Does it start to work?
 
Last edited by a moderator:
When your touchpad quits try to Enable it by running
Code:
xinput set-prop "HTIX5288:00 0911:5288 Touchpad" "Device Enabled" 1
Does it start to work?
Thanks for all the answers, I will try the code and see how it works.
If it works, what is the reason for it becoming disabled.
 
I used the package manager to update, I ran the upgrade command to see what would come up, only two items came up this time after a fresh install, they are network drivers, which when I type y, do not
get updated, they are held back, that's the message am getting after
I try and upgrade the wifi module, which is working in any event.
 
Well am on battery power now after a fresh install of MX Linux.
Initially the built in software notifier in the panel said up to date.
But when I ran sudo apt update and sudo apt --list upgradable I
got a list of items that I could update.


So, to summarise, in running sudo apt --list upgradable....you went looking for the latest and greatest....and without a doubt you found it.
But, in so doing you have introduced a whole tin full of problems
It may well be that those apps etc that were upgradable, were not included in the Software Notifiers output for good reason. One of those reasons may well be that they break things.......maybe they are untested at this stage......and therefore you take that action at your own risk.

If everything was working as hoped for, I would not have taken that extra step
No, I did not do the upgrade, as it was for WiFi Kernel modules, I tired as in theory these drives should not have anything to do with the touchpad operation, but I got a message saying they were not updated, and the update was held back, so no upgrade too place.
The promp to do this update came from Mx 's own software notifier.
And no I did not go looking for the latest and greatest, I ran sudo apt update, which is normal, if updates are available then I see no problem with installing them, they would not be in the repo if they were not tested, so I listed them, did not install them, I only installed the ones the Mx software updater found, and would expect them to be tested, the pointer freezing came before that.

And today the pointer frooze again, oddly it worked for hours yesterday evening with no issue, to 49 % battery power, today
I had 95% battery when the pointer frooze.
 
Last edited by a moderator:
No, I did not do the upgrade, as it was for WiFi Kernel modules, I tired as in theory these drives should not have anything to do with the touchpad operation, but I got a message saying they were not updated, and the update was held back, so no upgrade too place.
The promp to do this update came from Mx 's own software notifier.

And today the pointer frooze again, oddly it worked for hours yesterday evening with no issue, to 49 % battery power, today
I had 95% battery when the pointer frooze.
To fix packages that have been held back just run
Code:
sudo apt install package_name
If the dependencies of an installed package have been changed such that it requires installation of new packages, the installed package won’t be upgraded with the system update and you’ll see package kept back error. So in that case you will have to install those one at a time
 
I can't get an account on the Mx Forum, I get a welcome message
after completing the signup, but not able to log in, sent them a message, maybe they need to be made aware o the issue, as other OS 's I tried have not suffered from the issue, though antiX which would not install at all, error after error, had touch pad issues during the try, and now I find out they are related Os 'es
 
To fix packages that have been held back just run
Code:
sudo apt install package_name
If the dependencies of an installed package have been changed such that it requires installation of new packages, the installed package won’t be upgraded with the system update and you’ll see package kept back error. So in that case you will have to install those one at a time
So what do I exactly type to install these packages
Screenshot_2022-05-14_17-06-56.png
 
So what do I exactly type to install these packages
Code:
sudo apt install rtl8812au-dkms_5.6.4.2-1mx21+1_all.deb
Code:
sudo apt install rtl8814au-dkms_5.8.5.1-1~mx21+1_all.deb
 
Just looked at dmesg and see mention of my WiFi failing to load,
this seems odd as the WiFi on the laptop is what is connecting me now to my hotspot.
Is it not strange that MX updater is holding back the WiFi update,
given the OS is stating WiFi load issues.
Code:
[    6.889642] iwlwifi 0000:00:0c.0: firmware: failed to load iwl-debug-yoyo.bin (-2)
[    6.889647] firmware_class: See https://wiki.debian.org/Firmware for information about missing firmware
 
So what do I exactly type to install these packages
Code:
sudo apt install rtl8812au-dkms_5.6.4.2-1mx21+1_all.deb
Code:
sudo apt install rtl8814au-dkms_5.8.5.1-1~mx21+1_all.deb
Rather odd, neither package can be found
Code:
Mx1@Mx1:~
$ sudo apt install rtl8812au-dkms_5.6.4.2-1mx21+1_all.deb
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package rtl8812au-dkms_5.6.4.2-1mx21+1_all.deb
Mx1@Mx1:~
$ sudo apt install rtl8814au-dkms_5.8.5.1-1~mx21+1_all.deb
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package rtl8814au-dkms_5.8.5.1-1~mx21+1_all.deb
Mx1@Mx1:~
$
 
Click on upgrade and enter your password when asked.
Yes, I do have to enter my password, but that message still comes up and the packages are held back, probably could force it to update, but am torn as to why the MX software updater can achieve this if its indeed safe or required to do so.
 

Members online


Top