#712119 linux-image-3.9-1-amd64: lenovo thinkpad trackpoint configuration changed after resume

#712119#5
Date:
2013-06-13 06:39:16 UTC
From:
To:
Dear Maintainer,
I use two scripts at boot and login to set some parameters of my trackpoint:

#!/bin/sh
xinput --set-prop "SynPS/2 Synaptics TouchPad" "Synaptics Two-Finger Scrolling" 1 1 || echo fail
xinput --set-prop "SynPS/2 Synaptics TouchPad" "Synaptics Palm Detection" 1 || echo fail

xinput set-int-prop "TPPS/2 IBM TrackPoint" "Evdev Wheel Emulation" 8 1 || echo fail
xinput set-int-prop "TPPS/2 IBM TrackPoint" "Evdev Wheel Emulation Button" 8 2 || echo fail
#xinput set-int-prop "TPPS/2 IBM TrackPoint" "Evdev Wheel Emulation Timeout" 8 200 || echo fail
xinput set-int-prop "TPPS/2 IBM TrackPoint" "Evdev Wheel Emulation Axes" 8 6 7 4 5 || echo fail

#turn off the touchpad
xinput set-int-prop "SynPS/2 Synaptics TouchPad" "Synaptics Off" 8 1 || echo fail

#enable palm detection
xinput set-int-prop "SynPS/2 Synaptics TouchPad" "Synaptics Palm Dimensions" 32 4 100


#enable tap on the touchpad
xinput --set-prop --type=int --format=8  "SynPS/2 Synaptics TouchPad" "Synaptics Tap Action" 0 0 0 0 1 2 3


#!/bin/sh
echo -n 120 > /sys/devices/platform/i8042/serio1/serio2/speed
echo -n 255 > /sys/devices/platform/i8042/serio1/serio2/sensitivity


After resume, sometimes, the settings of the device are different. Usually the sensitivity is reduced and the pointer is very hard to move.
Today I had the touchpad enabled instead (with another script) and after resume the left click was not working, but the scroll using the
middle button was working.

This happens erratically but not infrequently, and has been happening with many kernel versions.

#712119#10
Date:
2021-04-24 15:51:24 UTC
From:
To:
Hi

This bug was filed for a very old kernel or the bug is old itself
without resolution.

If you can reproduce it with

- the current version in unstable/testing
- the latest kernel from backports

please reopen the bug, see https://www.debian.org/Bugs/server-control
for details.

Regards,
Salvatore

#712119#13
Date:
2021-04-24 15:51:24 UTC
From:
To:
Hi

This bug was filed for a very old kernel or the bug is old itself
without resolution.

If you can reproduce it with

- the current version in unstable/testing
- the latest kernel from backports

please reopen the bug, see https://www.debian.org/Bugs/server-control
for details.

Regards,
Salvatore

#712119#18
Date:
2021-04-24 18:04:52 UTC
From:
To:
I have another machine but the issue is still there by the way :d

But yeah feel free to close if it's not worked on.

Ciao

Il sab 24 apr 2021, 17:51 <carnil@debian.org> ha scritto:

#712119#23
Date:
2021-04-24 18:12:23 UTC
From:
To:
Ciao Salvo,

Well in case it is actually still reproducible, then we can keep the
bug open. I'm not sure where to star trackle it to get it moving and
report it upstream though.

Do you have any more insights into it in meanwhile?

Regards,
Salvatore

#712119#30
Date:
2022-05-31 16:03:30 UTC
From:
To:
Which kernel version does that other machine run?
With that info we can update the metadata (and title), so it doesn't come
across (at least to me) as obsolete :-)

#712119#35
Date:
2022-05-31 20:24:10 UTC
From:
To:
Feel free to close,

The issue I had on the newer machine was an hardware issue that got
solved by replacing the keyboard.

Something was wrong with the electronic there and I think it was
confusing the whole bus so also the touchpad, despite being a
different device was affected.

Sorry, I had forgotten about this.

Il giorno mar 31 mag 2022 alle ore 18:03 Diederik de Haas
<didi.debian@cknow.org> ha scritto:

#712119#40
Date:
2022-05-31 22:28:00 UTC
From:
To:
No worries, thanks for responding :-)