Touchpad settings reset suspend/resume

A few more pieces of infos regarding this issue :
- If I use the "xinput -list-props" command before sleep/hibernate and after resume, I distinctly see that all the values are reset
- If I use the "xinput -list" command after resume, I see that once in a while, the "AlpsPS/2 ALPS DualPoint TouchPad id=14" disappears and is replaced by a "PS/2 ALPS DualPoint TouchPad id=13"

So far, the only workaround I've found is to cron the command bellow to reapply my settings periodically.
xinput --set-prop "AlpsPS/2 ALPS DualPoint TouchPad" [prop] [value]

I have a similar issue, except it only happens after suspend and not hibernate.

Version : Kubuntu 10.04 (clean install) - 32bits
Laptop : DELL Latitude D620
Touchpad :AlpsPS/2 ALPS DualPoint TouchPad

xinput -list will give:

⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ DualPoint Stick id=11 [slave pointer (2)]
⎜ ↳ AlpsPS/2 ALPS DualPoint TouchPad id=12 [slave pointer (2)]
⎜ ↳ Macintosh mouse button emulation id=13 [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)]
    ↳ Video Bus id=7 [slave keyboard (3)]
    ↳ Power Button id=8 [slave keyboard (3)]
    ↳ Sleep Button id=9 [slave keyboard (3)]
    ↳ AT Translated Set 2 keyboard id=10 [slave keyboard (3)]
    ↳ Dell WMI hotkeys id=14 [slave keyboard (3)]

prior to suspend. After suspend, I get

⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ Macintosh mouse button emulation id=13 [slave pointer (2)]
⎜ ↳ DualPoint Stick id=11 [slave pointer (2)]
⎜ ↳ AlpsPS/2 ALPS DualPoint TouchPad id=12 [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)]
    ↳ Video Bus id=7 [slave keyboard (3)]
    ↳ Power Button id=8 [slave keyboard (3)]
    ↳ Sleep Button id=9 [slave keyboard (3)]
    ↳ AT Translated Set 2 keyboard id=10 [slave keyboard (3)]
    ↳ Dell WMI hotkeys id=14 [slave keyboard (3)]

The values are all the same, but listed in a different order. My current workaround is to Alt-F2 and type Touchpad settings and change it manually.

I have the same problem.
Version: Kubuntu 10.04 64bit
Laptop: HP dv7t Select
Touchpad: Synatpics Clickpad

I can confirm this bug too. this is a very grave bug, as it renders the UI behaviour haptically unpredictable.

xinfo --list-props , before suspend:
 Synaptics Move Speed (262): 1.704545, 0.033898, 0.000000, 0.000000
after resume:
 Synaptics Move Speed (262): 0.400000, 0.700000, 0.008970, 40.000000

didn't confirm whether other settings are also reset, if you need to know, please tell.

my current workaround:
"Pointing Devices" dialogue sliders show selected speed, if you move them, xserver settings get updated

Version: Ubuntu 10.10 Maverick Alpha3+updates
Laptop: Lenovo x201s
xserver pointing devices::

⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ SynPS/2 Synaptics TouchPad id=10 [slave pointer (2)]
⎜ ↳ TPPS/2 IBM TrackPoint id=11 [slave pointer (2)]

I think that the best workaround is to modify the 10-synaptics.conf file located in /usr/lib/X11/xorg.conf.d/. All of the options that you place in the "touchpad catchall" section of the file will be applied when the computer resumes from suspend. However, the GUI settings will override these settings when the computer is restarted. The best thing to do is try to match the 10-synaptics.conf options with your GUI so that it will always work the way you want it to. Here is what mine looks like:

Section "InputClass"
 Identifier "touchpad catchall"
 MatchIsTouchpad "on"
 MatchDevicePath "/dev/input/event*"
 Driver "synaptics"
 Option "SHMConfig" "on"
 Option "TapButton2" "3"
 Option "VertEdgeScroll" "0"
 Option "HorizEdgeScroll" "0"
 Option "EmulateTwoFingerMinW" "5"
 Option "EmulateTwoFingerMinZ" "90"
 Option "VertTwoFingerScroll" "1"
 Option "HorizTwoFingerScroll" "1"
 Option "VertScrollDelta" "100"
 Option "HorizScrollDelta" "600"
 Option "CornerCoasting" "1"
 Option "CoastingSpeed" "100"
 Option "PalmDetect" "1"
 Option "PalmMinWidth" "7"
 Option "PalmMinZ" "90"
EndSection

@tob Thanks very much. This worked for me. I needed to add:

Option "MaxTapTime" "0"

to turn off tapping. I wish I understood it all, but I learn a little bit each day.

I confirm that tob's workaround is working for me too ( as long as the "AlpsPS/2 ALPS DualPoint TouchPad" is the touchpad that xorg detects, see post #1)

I have the same issue with ThinkPad 510 and ubuntu 10.10

Same issue, but the settings, if it matters, are set through Synclient, and it's only the right corner clicks and the one, two, and three finger tap events that are reset. All other settings persist, whether set through the GUI or (when this is not available) via startup script.

Fabrice, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p xorg-server REPLACE-WITH-BUG-NUMBER

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

I can confirm this just recently started happening on my Kubuntu 13.10 install. Not sure I want to retest on an alpha version, that would take a bit of time and be a bit unstable I assume. Perhaps on the weekend.

For now I'll try to replicate it on my current install so we can have a baseline for comparison. I'll then use apport to collect info for the bug.

I thought about it a bit more and don't want to spam people with the command. I'll wait until Christopher or another dev responds on whether or not he wants me to run that command while on 13.10. Don't want to needlessly spam. I'm a bit hesitant to go to the alpha mainly due to time to install then downgrade if its unusable.

I can say that what happens on 13.10 is that when I resume Kubuntu, the cursor no longer moves at all. I can still use it to scroll along the right edge up/down a page like on firefox but clicking the buttons or trying to move the cursor position doesn't do anything. It appears to be the same as this bug, just slightly different manifestation. For the record my notebook is a System76 lemur2 model and xinput reports the touchpad as: SynPS/2 Synaptics TouchPad

I would have added this in to the above but LP doesn't let you edit comments? I'm not a big LP user.

I am willing to help if a dev seriously wants to investigate.

Jeremy Pallats, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report by executing the following in a terminal:
ubuntu-bug xorg

Please ensure you have xdiagnose installed, and that you click the Yes button for attaching additional debugging information.

For more on this, please see the official Ubuntu documentation:
Ubuntu X.Org Team, Ubuntu Bug Control, and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report will delay your problem being addressed as quickly as possible.

Thank you for your understanding.

[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.]