Synaptics touchpad stops working - two syndaemon instances running

[Mark Shuttleworth]

Proposed a SRU package for oneiric

[Summary]

Patch: http://bazaar.launchpad.net/~ossug-hychen/gnome-settings-daemon/fix-868400-oneiric/revision/184

bzr branch: https://code.launchpad.net/~ossug-hychen/gnome-settings-daemon/fix-868400-oneiric

[IMPACT]

 * touchpad is disabled sometines because 2 syndaemon instances. (one is launched by lightdm, anthoer one is launched by current user.)
 * ALPS touchpad does not use syndaemon, so ALPS users will not be impacted.

[TESTCASE]

 1. kill gnome-settings-daemon
 2. check syndaemon has only 1 instance after gnome-setitngs-daemon re-launched

[Regression Potential]

 * the patch is from gnome-settings-daemon package in precise
 * the risk is low because the patch only add the code to make sure syndaemon be killed if gnome-settings-daemon is killed

[ORIGINAL REPORT]

Synaptic touchpad stops working, seen on a few different Thinkpads.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: xserver-xorg-input-synaptics 1.4.1-1ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
Uname: Linux 3.0.0-12-generic i686
ApportVersion: 1.23-0ubuntu2
Architecture: i386
Date: Wed Oct 5 13:38:37 2011
DistUpgraded: Log time: 2010-07-25 15:41:02.611860
DistroCodename: oneiric
DistroVariant: ubuntu
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100201)
MachineType: LENOVO 4294CTO
ProcEnviron:
 LANG=en_GB.UTF-8
 SHELL=/bin/zsh
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic root=UUID=c4c39ed1-eb48-484a-8729-0600466a83a0 ro quiet splash vt.handoff=7
SourcePackage: xserver-xorg-input-synaptics
UpgradeStatus: Upgraded to oneiric on 2010-07-25 (436 days ago)
dmi.bios.date: 05/18/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 8DET46WW (1.16 )
dmi.board.asset.tag: Not Available
dmi.board.name: 4294CTO
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr8DET46WW(1.16):bd05/18/2011:svnLENOVO:pn4294CTO:pvrThinkPadX220Tablet:rvnLENOVO:rn4294CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 4294CTO
dmi.product.version: ThinkPad X220 Tablet
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.6+bzr20110929-0ubuntu3
version.libdrm2: libdrm2 2.4.26-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 7.11-0ubuntu3
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 7.11-0ubuntu3
version.xserver-xorg: xserver-xorg 1:7.6+7ubuntu7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.0-1ubuntu13
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.15.901-1ubuntu2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110411+8378443-1

[Sebastien Bacher (seb128)]

seems similar to bug #863668, bug #859455

[Timo Aaltonen (tjaalton)]

Install 'evtest', and see if you get any output from a VT when you run it against the input device (sudo evtest /dev/input/eventX,). If yes, at least kernel sees the events, and it's something in X failing.

[Sebastien Bacher (seb128)]

Mark, do you use 2 fingers scrolling? Robert Carr says he's having the issue also and he thinks it might be a geis,2 finger scrolling issue

[Chase Douglas (chasedouglas)]

Bug 804109 is similar in that the trackpad fails to work properly. A workaround there was:

* Install "dconf-tools";
* Launch it
* Search for: /org/gnome/settings-daemon/peripherals/touchpad/
* Check "touchpad-enabled"

I'm not sure the two bugs are the same, though. Please test this workaround a let us know how it goes.

Thanks!

[Sebastien Bacher (seb128)]

Chase, that's not likely, mark said that the g-s-d keybinding to turn the touchpad on and off was "working" but that didn't restore the cursor, xinput also indicated that the touchpad is activated when the issue happens

[Doug McMahon (mc3man)]

Myself & some others see a 'random' occurrence where the touchpad stops responding. For me it seems to be related to the disable touchpad while typing option
Have a new bug here, could be totally invalid/offbase or may not..
Bug 872885

[Kate Stewart (kate.stewart)]

I'm seeing this occurring in random fashion as well. This seems to occur after fresh install.
Work around is to open a terminal, and type: gsettings set org.gnome.settings-daemon.plugins.mouse active false
Then close your session with: gnome-session-quit

[Kate Stewart (kate.stewart)]

Also seeing this on Dell Inspiron, randomly occuring, but once occurs, is persistent.

[Sebastien Bacher (seb128)]

"type: gsettings set org.gnome.settings-daemon.plugins.mouse active false
Then close your session with: gnome-session-quit"

does running "gnome-session-quit" is enough or do you mean that you actually restart your session?

Could somebody get the infos requested before, i.e the evtest log?

[Sebastien Bacher (seb128)]

Kate, does disabling the "disable touchpad while typing" option from the ui workaround the issue for you? do you use 2 fingers gestures?

[Doug McMahon (mc3man)]

While this becomes 'random' after install it almost always happens right after, here typically when setting wireless password.
So did a fresh install with todays daily
Attached is evtest log after/while touchpad stopped working

What also restores the touchpad here is this, no logout required -
synclient Touchpadoff=0
It may be easier to test anything from a new install rather than waiting for it to occur or not occur later - though at least here disabling the above mentioned option seems to prevent
(& or enabling the option instead thru syncdaemon as mentioned in my dupe

[Sebastien Bacher (seb128)]

could the people having the issue try to turn the mouse plugin off as Kate described in comment #8 and run "syndaemon -i 0.5 -K -R" and see if they still get the issue? (that's the command g-s-d is running to enable the "disable while typing")

[Daniel Farrell (dfarrell07)]

I seem to be affected by the same bug. Seemingly randomly, my touchpad on a Lenovo W520 stops working. The red nub keeps working, however. Restarting sometimes fixes it, but sometimes it doesn't. I can use fn+f7 to turn off my red nub, but it has no effect on my touchpad. I haven't tried any fixes mentioned above, or in this (http://bit.ly/qx2da3) thread, because it is working right now. The only fix I've tried is:

gconftool-2 --set --type boolean /desktop/gnome/peripherals/touchpad/touchpad_enabled true

That was not effective, nothing changed. I have disabled the function that disables the touchpad while typing, to see if that helps. Next time it breaks, I will start trying fixes, and report back.

[higuita (higuita)]

i think this bug is a dupe bug #549727, but with 11.10 the "disable touchpad while typing" is the one activating that bug (several apps disabling the touchpad and going out of sync)

[Doug McMahon (mc3man)]

After 2 sets of 4 days over last 2 weeks with the option disabled in system settings - no occurrences
Currently starting the 3rd day running the setting thru syndaemon - no occurrences yet but for here maybe not long enough yet.

The one way I have to get this to occur at will - On a fresh install if setting the wireless passworg before doing anything else suggests the same but is suspect because it only is guaranteed to happen if it is truly the 1st thing done.

Several other I know seeing this are reporting no occurrences since disabling in SS, don't know atm if any have had the chance to set thru syndaemon & ck. there.

[Moritz Heiber (mheiber)]

Just throwing it out there .. reloading the psmouse drive a couple of times "fixed" the issue for me on my end. I don't know if that's a probable solution though. Hope to see this fixed soon.

[Daniel Farrell (dfarrell07)]

After disable touchpad while typing, I haven't had this bug in two days.

[Peter Harvey (pdqharvey)]

My 2 pennyworth:
Wishing to extend the time syndaemon disables the touchpad, I configured a 'startup application' consisting of "syndaemon -i 2 -d -K -t ". The option to 'disable the mouse when typing' (in the mouse settings) was still checked, and as soon as I started typing, the cursor froze. System monitor showed 2 instances of syndaemon running, which seems to have been the issue. Fixed it by unchecking the 'mouse setting option', leaving my startup command to do the job alone. Seems OK so far.

Does ANYONE know where the default settings for syndaemon can be changed, avoiding this workaround? I cannot find them anywhere!

PS
Possibly relevant is that the cursor (using a touchpad) froze both times I started Oneiric for the first time after a clean install. A USB mouse worked fine, and the problem went away on second start up each time.

[gigipin (luigi-pintaldi)]

I have a solution that i've tested before.

My problem was that the touchpad didn't work on start up, but only on log in. In the Xorg's log the SynPS/2 was recognised, but i suppose there may be a link problem with the driver, so i've adjusted the xorg configuration.

I've created a new empty /etc/X11/xorg.conf file and set the following rules in it:

Section "InputClass"
        Identifier "Touchpad" # required
        MatchIsTouchpad "yes" # required
        Driver "synaptics" # required
        Option "MinSpeed" "0.5"
        Option "MaxSpeed" "1.0"
        Option "AccelFactor" "0.075"
        Option "TapButton1" "1"
        Option "TapButton2" "2" # multitouch
        Option "TapButton3" "3" # multitouch
        Option "VertTwoFingerScroll" "1" # multitouch
        Option "HorizTwoFingerScroll" "1" # multitouch
        Option "VertEdgeScroll" "1"
        Option "CoastingSpeed" "8"
        Option "CornerCoasting" "1"
        Option "CircularScrolling" "1"
        Option "CircScrollTrigger" "7"
        Option "EdgeMotionUseAlways" "1"
        Option "LBCornerButton" "8" # browser "back" btn
        Option "RBCornerButton" "9" # browser "forward" btn
EndSection

This is working perfectly for me, is not necessary set all commands like me only the required ones, perhaps the cause is a command line, in /usr/share/X11/xorg.conf.d/50-synaptics.conf, wrong and may be this:

MatchDevicePath "/dev/input/event*"

[Rosca Stefan (sarvigalava)]

Happens to me when I'm trying to open dash an search an app (Transsmission). Killing x server (cntrl+alt+backspace) resolves the problem

[René Moser (resmo)]

Workaround of #5 worked for me (so far)

[Soeren Rabenstein (sorab)]

Reporting the same issue for ASUS EeePC 1005 HA. But also that workaround #5 fixed it (so far ;)).

[Felipe Ochoa (felipeochoa0918)]

FWIW, I've had this problem too. I found a fix for this (http://ubuntuforums.org/showthread.php?t=1852081&page=4&styleid=109) is to run "synclient TouchpadOff=0" from a terminal.

Here is the dmesg output of when this last happened:

[ 365.304496] psmouse.c: TouchPad at isa0060/serio1/input0 lost synchronization, throwing 4 bytes away.
[ 365.827318] psmouse.c: resync failed, issuing reconnect request
[ 387.700302] psmouse.c: TouchPad at isa0060/serio1/input0 lost sync at byte 4
[ 387.701885] psmouse.c: TouchPad at isa0060/serio1/input0 lost sync at byte 1
[ 387.703597] psmouse.c: TouchPad at isa0060/serio1/input0 lost sync at byte 1
[ 387.712677] psmouse.c: TouchPad at isa0060/serio1/input0 lost sync at byte 4
[ 387.715189] psmouse.c: TouchPad at isa0060/serio1/input0 lost sync at byte 1
[ 387.715193] psmouse.c: issuing reconnect request

[Sebastien Bacher (seb128)]

not sure if bug #878859 is similar, it claims shift-lefclick on the menus leads to pointer locking

[Ciccia (present-ense)]

Hi,
I'm using an HP laptop dv6385ea and its mouse touchpad doesn't work once I login with my password. It suddenly works if I login as a "Guest Session". It works before logging into my personal account with my personal password.

[Ciccia (present-ense)]

Hi!
Me again! Just wanted to say I solved my problem with the mouse touchpad on my HP DV6385EA thanks to Kate Stewart's suggestion at comment #8:
"type: gsettings set org.gnome.settings-daemon.plugins.mouse active false
Then close your session with: gnome-session-quit"

Thank you, folks!

[tylnesh (kohutek)]

Yes, Kate Stewart's suggestion at comment #8:

 "type: gsettings set org.gnome.settings-daemon.plugins.mouse active false"

was really helpfull. I was sure it had something to do with my settings, since other accounts were fine, but I could not find the correct "switch". This solves this bug for me! Yay!

[Karl (karl1982)]

I would like to add that this seems to be very much a finger detection issue. I'm having this problem on an Asus G73SW recently upgraded from Natty to Oneiric. I booted the Oneiric LiveCD to see if it was a config issue, and I still have problems, although they're a little different (the three-finger window drag doesn't seem to work from the LiveCD, the window handles don't appear from three-finger clicking either).

My cursor locks up with varying frequency, but everything else is still in full swing. I can click with the physical buttons, an external mouse works perfectly, and the keyboard is still responsive. However I experience an additional symptom that I don't see anyone else describing. After locking up briefly, sometimes it will move erratically on its own. It'll grab a window, jerk it all over the screen, and sometimes leave it positioned halfway off-screen or maximize it (by dragging to top, I believe). I get the impression it thinks there are fingers all over the touchpad, almost like it thinks I'm palming it, but a little different. It seems to think there are several points of contact either stuck or moving erratically.

I have no problems with this touchpad in Windows 7, nor did I in Natty, so there's no question we have a bug in an update.

[Jimmy Merrild Krag (beruic)]

I mostly use a USB mouse, but have noticed this happening on a Dell XPS M1330 as well.

[Rosca Stefan (sarvigalava)]

Is anyone working to solve the problem ?? Today touchpad freezing happened again ( same circumstances as I wrote earlier)

[gregreen (gregreen)]

I have the exact same problem a Karl in post #29. I have an Asus G53 Jw, so our systems are probably very similar. This problem showed up right after an upgrade from 11.04 to 11.10, and then again after a fresh install of 11.10. My touchpad freezes, and when it comes back, it starts grabbing windows and moving them around erratically. The touchpad worked fine in 11.04, so this is a bug in 11.10.

[John Tocher (jmtocher)]

Solution at #5 worked for me too.

It didn't require a restart or logout/in, it started working as soon as I quit the dconf editor.

MSI i7 laptop running 64 bit 11.10, upgraded from a clean install of 11.04

[Karl (karl1982)]

In regards to the workaround in #5, this does not apply to my problem... Mine is already checked.

[gregreen (gregreen)]

Just like Karl, I already have "touchpad-enabled" checked, so the workaround from #5 does not help me.

[Doug McMahon (mc3man)]

The most potentially effective 'workaround' would be as described in comment 8, at least as seen here over the course of several weeks.
I also disable the "disable touchpad while typing option" but it seems here that setting the plugin activation to false is what keeps it from reoccurring over the long haul

[gregreen (gregreen)]

For my problem, the workaround described in comment #8 has no effect. The problem persists.

[Mandar Vaze (mandarvaze)]

Workaround from Bug 804109 does not work for me. Touchpad was already enabled. But workaround from Doug McMahon (mc3man) i.e. "synclient Touchpadoff=0" worked for me.

[Karl (karl1982)]

"synclient TouchpadOff=0" has no effect for me. That setting is toggling correctly as I start/stop typing. Also, I have the exact same problem whether "disable touchpad while typing" is enabled or not.

It isn't just that the touchpad stops responding, it also sometimes goes berserk. The problem seems to worsen the longer the OS is running. Right after booting, it actually works for a couple minutes. By the 10 minute mark, it's so bad I can hardly even work with it using an external mouse.

This is probably unrelated, but I installed gpointing-device-settings to get some additional controls while troubleshooting this problem, and some of its options don't seem to stick. Such as disable touchpad when another device is connected. The setting will be unchecked again after reopening the program, and the setting never takes effect.

[Jimmy Merrild Krag (beruic)]

I tried the solution in #5. I don't know if it works yet, but I noticed that "disable-while-typing" was off in dconf-editor but on in the touchpad settings, until I turned it off and on again in the touchpad settings.

[gregreen (gregreen)]

I've attached an example of what happens when the pointer unfreezes. The video is a bit faster than real life, but notice how the cursor grabs a window, shakes it around and then maximizes it, before returning control to the user. When this starts happening, it occurs very often - up to a few times a minute - making it nearly impossible to get any work done.

[Rosca Stefan (sarvigalava)]

synclient TouchpadOff=0 worked for me. After update of fglrx driver this bug appear often than normal

[Karl (karl1982)]

Thucydides411's video looks about like what I'm experiencing.

I'm starting to think we may be looking at more than one bug in the same place. Tell me this, has anyone who experiences the unresponsiveness followed by erratic movement fixed their problem with synclient TouchpadOff=0? And has anyone who experiences unresponsiveness WITHOUT the erratic movement NOT fixed their problem with that same solution?

I'm not that familiar with the inner workings of Ubuntu's pointer control, but if I'm not mistaken, synclient's TouchpadOff variable toggles based on whether the touchpad has been disabled by either the "disable while typing" setting or the "disable with external device connected" setting, is that correct? Which means if it were to get stuck at 1, and the touchpad is unresponsive, manually flipping it to 0 would re-enable the touchpad... I assume temporarily until the same bug occurs again.

But then, that would have nothing to do with the touchpad freezing and then starting to jump and click and drag everywhere.

[Mikoto (zhwhxxul)]

I'm getting the same error (touching the touchpad = mouse going crazy - it eventually settles in the top right corner and is unresponsive to either clicks or movement, and none of the above work arounds have worked for me.

I've noticed, however, that if I plug in a USB mouse after the bug occurs, I can move the pointer freely, but the system refuses to recognise any mouse clicks, whether from the USB mouse or the touchpad. If I plug in a USB mouse before the error occurs, it works fine until I touch the touchpad, then the above occurs.

In case it helps, I've also been unable to disable the touchpad through any ubuntu settings (including dconf), whether for when typing, or just turning the damn thing off altogether. The function key combo, which is built into the laptop, does work however.

Also, this bug was occurring randomly when first installed (every second or third reboot had it occurring), but since I ran all the latest updates, it now occurs every single time from the first touch of the touchpad.

[Karl (karl1982)]

I tried a little experiment to see if I could get my laptop back in usable condition. I downgraded xserver-xorg-input-synaptic from 1.4.1-1ubuntu2 to the one from Natty (1.3.99+git20110116.0e27ce3a-0ubuntu12) and then restarted and gave it a spin. This had NO EFFECT. It works fine for about 5 minutes, three-finger window dragging and all. Then it goes nuts. I have to type with my hands elevated because if I accidentally palm this huge touchpad, I lose control of the system.

I also can't seem to disable the touchpad. Fn+F9 doesn't work, nor does synclient touchpadoff=1. Even with an external mouse connected, I have to stay completely clear of the touchpad at all times. This is a 4 inch touchpad and I have big hands, so... that's a problem.

Something else I noticed is that when it locks up and won't let go of a window, I can make it release sometimes by giving it one tap. It's almost like I had the window drag-locked and it thought my finger was both on and off at the same time.

What else might I try to fix it? This bug has been on file for over a month and hasn't been fixed, and it's gotten to the point where I have to reclaim my laptop, even if that means reinstalling Natty. I wish I could help more, but I'm not a programmer. If there are any other suggestions, I'll be more than happy to try them.

[gregreen (gregreen)]

I'm experiencing the same frustration with this bug. Needless to say, those experiencing this bug can't wait until 12.04 to regain control of their laptops. If there are any tests we can do to provide more information on this regression, then please tell us. But this bug is much more important that it seems to be perceived as by Ubuntu.

[Bryce Harrington (bryce)]

Hey sabdfl,

Hi, thanks for reporting this issue during the development period of
Ubuntu.

I notice there's not been further comments to the bug report since the
release came out, would you mind updating us on the status of it in the
release?

Are you still able to reproduce the issue? If not, do you think the bug
report can be closed, or do you think we should continue tracking it?

[gregreen (gregreen)]

What just happened? Why is this bug now marked as "incomplete"? It's been confirmed by several people here. Which release are you talking about? This bug is specific to 11.10, the latest release of Ubuntu. I think this has been marked "incomplete" in error. Please change it back to "confirmed." Again, I would be eager to provide any information required on this bug, since it is such a problem for the everyday usability of the OS.

[Karl (karl1982)]

Bryce, please scroll down a bit... as you can see, the last comment was a mere one day before your post.

This bug is confirmed and unresolved.

[Bryce Harrington (bryce)]

Karl, thanks you're right, my script did not check the recent comments.

[florin (florin-arjocu)]

For my Toshiba Satellite C650 running "synclient TouchpadOff=0" when the bug occurs, works. I have disabled the touchpad option "Disable touchpad while typing" and in the last 15 hours I did not get the bug any more, but it's not a good decision not to disable touchpad while typing as it's not a great pleasure to see your pointer moving on the screen while typing texts. In my case there were no "window strange movements".

[ThierryM (thierry-munoz)]

For my Asus M70Vn, "synclient TouchpadOff=0" works to repair the freeze.

[gregreen (gregreen)]

I think we may be looking at two separate (but perhaps related?) problems here, since one group of users is reporting that their mouse completely freezes, and that "synclient TouchpadOff=0" works to unfreeze the mouse, while another group - including myself - reports that the mouse and keyboard temporarily lock up (a few seconds at most), and then behave erratically afterwards (clicking and dragging windows uncontrollably).

[Eric Hax (someweirdchaothing)]

"synclient TouchpadOff=0" fixes it on my Aspire 5534

[agnul (sucrabu)]

Happens randomly, "synclient TouchpadOdd=0" fixes it on my T420/11.10 (64bit)

[TomasHnyk (sup)]

I think I experience this and
synclient TouchpadOff=0
fixes this for me.

I am not sure whether it was mentioned but trackpad and a external bluetooth mouse work fine after the touchpad freezes. Does it work for other the same. I.e. touchpad freezes and mouse/trackpad continous to work?

[ThierryM (thierry-munoz)]

Yes, when the touchpad freezes, an usb mouse (plugged or that I plug because of the freeze) works perfectly.

[Dereck Wonnacott (dereck)]

"synclient TouchpadOff=0" worked for me as well...

[florin (florin-arjocu)]

As I can see, the simple activation of touchpad works for all of us with the bug in "version 1", without window movement/etc.

I have uncheckd "disabled touchpad while typing" but writing is a nightmare like this.

Does anyone know if thee is any solution to be seen soon?

[OldbadBear (oldbadbear)]

Workaround of #5 worked for me too.

[Doug McMahon (mc3man)]

florin wrote >
> I have uncheckd "disabled touchpad while typing" but writing is a nightmare like this.
>Does anyone know if thee is any solution to be seen soon?

You can try this - YMMV
Set up the touchpad as you'd like as far as the 'disable while typing' & 'tap to click' options
Then inactivate the mouse plugin itself, the setting prior to making the plugin inactive will be held.

If needing to re-adjust the plugin setting you must re-activate the mouse first
To deactivate the mouse plugin

gsettings set org.gnome.settings-daemon.plugins.mouse active false

[Doug McMahon (mc3man)]

Florin - please ignore my prior comment, had forgotten I was running syndaemon separtely from gsd, comment was totally wrong
Sorry about that

[florin (florin-arjocu)]

#Doug McMahon
No problem, thanks for trying. Just a thought: bugs like this one make people go to stable and mature OS's; it makes no sense to develop fancy windows managers when basic things do not work as expected. And this bug is probably affecting 90+% of laptop users (I think Synaptic touchpads are the most used by manufacturers).

Can we do something to make it easier to trace this bug?

[sven (post-svennielsen)]

lightdm starts a syndameon instance which is not terminated upon session startup.

So there is the conflict: two syndaemon instances, one from lightdm and one from logged in user.
Just experienced this problem after going from gdm back to lightdm.

This does not happen with gdm.

lightdm syndaemon instance must be terminated before starting session (and user's syndaemon instance)

Regards

[sven (post-svennielsen)]

Oh, and this workaround should be fine for all:

In terminal:

sudo killall -u lightdm syndaemon
synclient Touchpadoff=0

regards

[Rob Frohne (frohro)]

Hi All,

For the last couple of weeks I worked around this bug by assigning the keyboard shortcut CTRL-F9 to the command:

synclient TouchpadOff=0

but tonight that didn't work. I even typed that in at the terminal window to no avail. So then I went and got a USB mouse and when I connected it and clicked and moved around I found the touch pad worked again.

I find that the bug often occurs just after booting up, or resuming.

Rob

[sven (post-svennielsen)]

I am a little surprised this prominent bug seems so "quiet".

To emphasize my last post:

SOLUTION!

for this bug is:

lightdm starts a syndaemon instance which MUST be terminated upon session startup.

Otherwise two syndaemon instances compete for disabling/enabling touchpad, and will eventually get out of sync.
This was simply overlooked when switching from gdm to lightdm as login manager.

PLEASE FIX.

Regards
Sven

[florin (florin-arjocu)]

@sven - do you know any reason for getting "no process found" when running your fix?

florin@florin-Satellite-C650:~$ sudo killall -u lightdm syndaemon
syndaemon: no process found

[Rob Frohne (frohro)]

You might try grepping for it in the output of ps. I think Sven has possibly found the problem. I have two syndaemons running too.

frohro 10334 0.0 0.0 5660 800 pts/2 S+ 13:45 0:00 grep syndeamon
frohro@frohro-d830:~/Araya Classes/Signals/PSK31$ ps aux | grep syndaemon
frohro 3008 0.0 0.0 3524 768 ? S 09:59 0:04 syndaemon -i 0.5 -K -R
frohro 3143 0.0 0.0 3524 772 ? S 09:59 0:04 syndaemon -i 0.5 -K -R
frohro 10376 0.0 0.0 5664 804 pts/2 S+ 13:47 0:00 grep syndaemon
frohro@frohro-d830:~/Araya Classes/Signals/PSK31$

Rob

[florin (florin-arjocu)]

florin@florin-Satellite-C650:~$ ps aux | grep syndaemon
florin 4265 0.0 0.0 20064 916 ? S 14:54 0:12 syndaemon -i 0.5 -K -R
florin 7782 0.0 0.0 14424 908 pts/0 S+ 23:56 0:00 grep --color=auto syndaemon

I will also restart to see what happens on a fresh start up.

My system runs this:
uname -a
Linux florin-Satellite-C650 3.0.0-13-generic #22-Ubuntu SMP Wed Nov 2 13:27:26 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux

[sven (post-svennielsen)]

Apologies for being a little direct on the last post.

I think that in many cases this bug might just be caused by those two syndaemon instances running, which would make sense as oneiric made the switch from lightdm to gdm, and this does not happen on my laptop if I use gdm (whoch does NOT start its own syndaemon instance).

Of course, it is possible some people have the same bug behaviour with other causes.

Regards
Sven

[gregreen (gregreen)]

Thanks for looking into this Sven. On my system, there is only one instance of syndaemon open when the touchpad starts acting up, so this does not appear to be the cause for me. Sven, do you experience erratic mouse behavior after the pointer unfreezes, and does synclient TouchpadOff=0 work for you?

[sven (post-svennielsen)]

> do you experience erratic mouse behavior after the pointer unfreezes,

no, mouse is fine always

> and does synclient TouchpadOff=0 work for you?

well, it does, though I did not check if the freeze reoccurs after some time, or if it is viable as a workaround for the complete session.

sven

[Sebastien Bacher (seb128)]

Sven, you should open a bug on lightdm about your issue, it doesn't seem syncdaemon from lightdm is running for most users after login though, what greeter do you use?

[gregreen (gregreen)]

Do other people for whom synclient TouchpadOff=0 works have multiple instances of syndaemon running? It would be useful to see if this is related to the difference between systems that experience erratic mouse behavior and those which don't. Currently, it seems that we have two different types of bug behavior among subscribers to this report, and now at least two root causes.

[florin (florin-arjocu)]

Does anyone know how to test if "Disable touchpad while typing" works? In the last 24 hours I have it active and the bug did not occur (yet).

[Rob Frohne (frohro)]

I find all except once, the synclient TouchpadOff=0 worked for me, and I found two instances of of syndaemon running. See post #69.

Rob

[Doug McMahon (mc3man)]

After going 5 weeks with no occurrences using " org.gnome.settings-daemon.peripherals.touchpad disable-while-typing false", I re-enabled the option.

Got a cursor freeze out of the blue in the midst of a 6 hr. session. At the time of the freeze a 2nd instance of syndaemon was found to be running. A log out/in then shows only 1 instance as per the gsetting

[Anders Frisk (anders-frisk650)]

I think Sven is right in his assumption that the touchpad freeze is caused by two syndaemon instances getting out of sync.
On my system I find consistent correlation between touchpad freezing and two syndaemon instances running.
What puzzles me is why I don't always have two syndaemon instances running. I have found that if I cold boot and log in as "UserA" or "UserB" I most of the time have only one syndaemon instance and have no problem. If I log out from UserA and then log in as UserB I still (most of the time) have only one syndaemon instance. If I then log out UserB and log in as UserA again, I always have two syndaemon instances and I consistently get a touchpad freeze if my first keyboard activity in the new session is ctrl-alt-T followed by arrow up.

[David Velazquez (lemonsforlemonade)]

Posting from a Dell Vostro 1500 here. Synclient touchpadoff=0 works for me to resolve the unresponsive mouse issue. Per the previous comments about multiple instances of syndaemon, I went ahead and checked and it appears that I do.

[Doug McMahon (mc3man)]

Just to re-affirm
Here when the freeze occurs 'randomly' there are always 2 syndaemon instances but NO indication that lightdm is involved.
There are however 2 scenarios where lightdm is involved, but they are very limited. One is sometimes on a live session, the other is the very first login after a new install.
That can be seen here -

~$ ps aux |grep syndaemon |grep -v grep
lightdm 1366 0.0 0.0 3524 772 ? S 21:02 0:01 syndaemon -i 0.5 -K -R
doug 1503 0.0 0.0 3524 772 ? S 21:02 0:01 syndaemon -i 0.5 -K -R

This only happens on the first login on a new install and then never occurs again .

So 5+ weeks of having the option disabled in gnome-control-center - no occurrences

1+ week of having the option disabled in gnome-control-center but starting syndaemon directly from a Startup Application - no occurrences

This has been tested on both 11.10 & 12.04 A1

[florin (florin-arjocu)]

I've disabled the feature "Disable touchpad while typing" for some weeks and this bug did not occur. Today was the first time I got it since I changed back. Just now I restarted the machine and on startup I had the bug. There are 2 syndaemon running:

ps aux |grep syndaemon |grep -v grep
florin 1538 0.0 0.0 20064 916 ? S 17:56 0:00 syndaemon -i 0.5 -K -R
florin 1612 0.0 0.0 20064 916 ? S 17:56 0:00 syndaemon -i 0.5 -K -R

The fix works.
F.

[florin (florin-arjocu)]

Until a complete fix, maybe a trick could make a temporary fix: the syndaemon should check on start if there is another instance of the daemon.

Something like (logical scheme, I have no idea how the daemon real code looks like):

onStart(){
  isAnotherInstance(){return;}
  else {startDaemon;}
}

[Karl (karl1982)]

I seem to have inadvertently narrowed down the cause of my bug. The problem is with Unity, not the synaptic driver. I installed a clean and updated copy of 11.10 and still have the same touchpad malfunction with Unity. The touchpad malfunction DOES NOT happen under GNOME 3. I've logged several hours of touchpad usage with GNOME 3 without incident. If I switch back to Unity, it takes only a few minutes for me to lose control of the system and end up forcibly restarting from another tty.

[Martin Pitt (pitti)]

Karl [2011-12-16 21:28 -0000]:
> I seem to have inadvertently narrowed down the cause of my bug. The
> problem is with Unity, not the synaptic driver. I installed a clean and
> updated copy of 11.10 and still have the same touchpad malfunction with
> Unity. The touchpad malfunction DOES NOT happen under GNOME 3. I've
> logged several hours of touchpad usage with GNOME 3 without incident.
> If I switch back to Unity, it takes only a few minutes for me to lose
> control of the system and end up forcibly restarting from another tty.

Thanks Karl. Under GNOME 3 do you also have two syndaemons running?

Martin

--
Martin Pitt | http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)

[siloko (siloko1)]

I know this is an Ubuntu bug but I have had this problem under Gnome 3
in Linux MINT. I have used the 'fix' stated above and it hasn't appeared
since (only a few days though).

On 17/12/11 07:27, Martin Pitt wrote:
> Karl [2011-12-16 21:28 -0000]:
>> I seem to have inadvertently narrowed down the cause of my bug. The
>> problem is with Unity, not the synaptic driver. I installed a clean and
>> updated copy of 11.10 and still have the same touchpad malfunction with
>> Unity. The touchpad malfunction DOES NOT happen under GNOME 3. I've
>> logged several hours of touchpad usage with GNOME 3 without incident.
>> If I switch back to Unity, it takes only a few minutes for me to lose
>> control of the system and end up forcibly restarting from another tty.
> Thanks Karl. Under GNOME 3 do you also have two syndaemons running?
>
> Martin
>

[Karl (karl1982)]

Martin, I have actually experienced both of these bugs. I have had the touchpad stop responding with two syndaemons. What I've been doing to fix it is kill the one with the higher PID and then run synclient touchpadoff=0. This has happened under Unity and GNOME 3.

The other issue is the touchpad locking up for brief moments and eventually becoming unresponsive and/or going wild. It gets progressively worse as time goes on, until it's become mostly unresponsive between fits of... I don't even have a word for it. It three-finger-grabs a window and rapidly jerks it all over the screen. The more I use the touchpad, the more rapidly the problem progresses, but it's fine with an external mouse if I stay off the touchpad. This happens under Unity but DOES NOT happen with GNOME 3.

[florin (florin-arjocu)]

Just a thought: for me the bug appears very random, I do not have any idea when it will occur next. One time I did not see the bug for more than a week. Other times it occurred a few times a day, and sometimes not even once in a few days (like now).

When people say they did not experience the bug in Gnome 3/etc. there should be a long time of testing, not to confuse the developers.

[Felix (apoapo)]

I experienced this bug multiple times with gnome-shell. Using it since 2 months now.

[Martin Pitt (pitti)]

This generally seems to happen when two syndaemons are running. They are being spawned by gnome-settings-daemon.

Comment 69 is the case where there are two instances from the user. This could happen if g-s-d crashes and then respawns, as right now g-s-d only checks its internal variable manager->priv->syndaemon_spawned, it doesn't actually check if there is a running instance. This confirms the g-s-d task.

Comment 81 is the case where syndaemon gets started from lightdm, and keeps running in the user session. I think the best and easiest solution would be to change g-s-d gsettings in lightdm to not start syndaemon at all, it's not really necessary/useful in the greeter and just overhead.

[Martin Pitt (pitti)]

syndaemon runs on its own, once it's started it does not need to be controlled from outside. So it would work if g-s-d used pidof instead of manager->priv->syndaemon_spawned, then it can also grab the pid to know what to kill if the user changes the setting.

[Teunis Peters (teunis)]

Still very much present - on eeepc 1215N for instance. It's not unity-specific unity does not function on a dual-video-chip laptop.
It may be kernel-specific - 3.2.0.5 does it sometimes, 3.2.0.6 does it every boot without "Failure" (or more precisely, with near 100% failure within minutes)

[z06gal (z06gal)]

I am having the same issue in Mint 12 regardless of what DE I am running. It occurs randomly and I have to do a hard shutdown since the keyboard does not work. I hope this gets resolved soon. It is so annoying.

Robin

[Rob Frohne (frohro)]

I haven't seen it in a week or more.

[z06gal (z06gal)]

@Teunis, I am running the 2.6.39.4 kernel in Mint 12. The default kernel runs so hot on my laptop and the downgraded kernel runs normally so I don't think it is kernel related. I just tried florin's "fix" in post 70 and will see how it goes. This bug is maddening. Mine has frozen 3 times today alone. Insane

[florin (florin-arjocu)]

@z06gal
Actually I did not play with killing processes. For me and probably most of us here, the temporary solution is to manually activate the touchpad by running:
`synclient TouchpadOff=0`.

[z06gal (z06gal)]

@florin

The problem I have is nothing works at all when the mouse freezes. I cannot get to a terminal or anything. I have to do a hard shutdown. I had 5 instances yesterday. Last night, I decided to upgrade my nvidia driver just to see if that helps any. I'm out of ideas. Lol

[florin (florin-arjocu)]

I guess it is not related to this bug, but it is something else. When I tried different kernels I got a bug that the system was almost blocked. In my case the cause was that kernel was writing gigabyte log files. I am no expert, but I guess it is kernel related, you should try using different kernels and see what happens on your hardware. And check the system (memory, cpu temp, hdd for bad clusters, etc.) also.

uname -a
Linux florin-Satellite-C650 3.0.0-14-generic #23-Ubuntu SMP Mon Nov 21 20:28:43 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux

[z06gal (z06gal)]

@florin

I have tried 4 kernels and the same thing happens. I have not had an episode since upgrading my nvidia to the latest driver. I'll keep my fingers crossed. Thanks ;)

[z06gal (z06gal)]

Upgraded my nvidia driver yesterday and all went well. I had everything disabled except the touchpad. I decided to enable the mouse plug in in the gnome session settings and activate the "disable touchpad while typing" just to see how it would do. The system froze about 2 hours after enabling things. I am going to disable the mouse plug in and see how it goes. I am so sick of this issue. When mine freezes, nothing extravagant happens with the mouse movement or anything. It just stops working along with the keyboard. I have kept an eye on my temps and they are fine so it isn't overheating.

[Felix (apoapo)]

@z06gal: Your issue is a different one i guess. Your System freezes. Please report a new bug. This bug is only about -the touchpad- (not the external mouse or intern/extern keyboard!) freezing

[Jeffrey Flaker (jflaker)]

ok....had the same thing happen. I was playing with the function keys (hot keys for networking, etc). On my Aspire One, the hot key for the wireless FN-F7 actually turns off the touch pad.

Maybe others are hitting a key assuming it was going to do one thing, but actually does something else....

[Christopher Kyle Horton (christhehorton)]

Got this issue today shortly after installing Precise Alpha 2 over my 11.10 partition on my Toshiba A505 S6960 laptop. The 11.10 partition was upgraded from 11.04 and did not have the same problem.

The "synclient TouchpadOff=0" workaround works for me too.

[wayneoutthere (taylor-wayne-r)]

Just want to make a layman's post on this bug: first, for those like me using unity and don't know where to mess with your touchpad (mouse area) settings, just search 'system settings' in your dash. Then you'll see 'mouse and touchpad'. Now my update: it seems that by unchecking the 'disable touchpad while typing' box the freezing of touchpad (and Skype, interestingly) seems tohave been resolved. I have done about three reboots and have not seen the freeze yet. I'm on an Aspire One Acer 257-1814 with Ubuntu 11.10. If I don't post back, it worked.

[Alex Wolfson (awolfson)]

I found something, that might help to debug the bug. If I uncheck 'disable touchpad while typing' as suggested in #103 and move my finger on touchpad, while typing garbage fast, I see the cursor to do a jerk movement once in a while instead of staying still.
It is 100% reproducible, unlike the bug, whichI have only ocasionally.
I have Lenovo T410 with Synaptic

[florin (florin-arjocu)]

Most of the time when this happens I thought it is a hyper-sensitivity of the touchpad and I am touching it while typing. Don't know if it is the same issue #105 described, but writing is quite difficult, as the touchpad clicks where the pointer is and pressing keys at the same time makes you do things you don't plan to.
PS: Sensitivity is set to lowest possible.

[Alex Wolfson (awolfson)]

That might be related:

https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/801763
Typing causes cursor to stick

This bag fix introduced 0.5 sec delay in gsd instead of 2.0

* debian/patches/10_smaller_syndaemon_timeout.patch:
    - Use a smaller timeout for syndaemon (LP: #801763)

Relevant upstream gnome code is located at:
http://git.gnome.org/browse/gnome-settings-daemon/tree/plugins/mouse/gsd-mouse-manager.c#n504

I have that 2 syndaemon issue once in a while, but can not reproduce it fast. If somebody wants to test if increasing delay fixes the bug, look at
http://ubuntuwiki.net/index.php/Touchpad,_disabling_while_typing

The modified command to execute:
syndaemon -i 2.0 -K -R

[wayneoutthere (taylor-wayne-r)]

Hi again. Turns out my issue in #104 above must not be related to this as it persists. I'll have to search more on skype and hardware I guess... Thanks for all your contributions here regardless

[Alex Wolfson (awolfson)]

I tried a solution from #107 at HP mini. On that laptop the bug was 100% reproducible, if as a first thing after reboot you open chromium and start typing. After implementing #107 bug did not happened, or at least it is not 100% reproducible any more.
If user checks the "the disable while typing" settings - he ends up with 2 instances of the syndaemon running, but touchpad still works. If you uncheck settings, the later daemon with 0.5 sec disappears. So looks like bug might existed for a long time, but was masked by default setting of 2.0 sec, till debian/patches/10_smaller_syndaemon_timeout.patch were applied to the g-s-d.

According to the bug 801763 it happened on 2011-08-22: in the package gnome-settings-daemon - 3.1.5-0ubuntu3

[D Allan (dallan507-deactivatedaccount)]

I've just installed 64bit 11.10 on Aspire One D255 and the touchpad worked for about 30mins and then froze. None of the above suggestions work. I can't drag a mouse around with me on the train - there's no room! Is there a solution?

[Launchpad Janitor (janitor)]

This bug was fixed in the package lightdm - 1.1.4.is.1.1.3-0ubuntu2

---------------
lightdm (1.1.4.is.1.1.3-0ubuntu2) precise; urgency=low

  [ Matt Fischer ]
  * debian/lightdm.dirs:
    - Add /etc/X11/ so lightdm.postinst doesn't fail on systems without X
      installed (LP: #921169)

  [ Martin Pitt ]
  * debian/lightdm.postinst: Disable disable-while-typing touchpad setting for
    GNOME; we do not really need this feature in lightdm, and multiple
    syndaemon instances cause the touchpad to stop working sometimes. Add
    libglib2.0-bin dependency for this. (LP: #868400)
 -- Martin Pitt <email address hidden> Mon, 05 Mar 2012 12:36:04 +0100

[Martin Pitt (pitti)]

Removing lightdm task. The unity greeter already disables the mouse plugin these days, so it's fixed in unity-greeter, lightdm itself is not affected, and the g-s-d task remains.

[Mario Limonciello (superm1)]

The lightdm fix seems to have caused bug 947713.

[Martin Pitt (pitti)]

I have a first g-s-d patch working, sent to upstream for commentary.

[Jens Finkhäuser (finkhaeuser-consulting)]

For what it's worth, also seeing this on a Lenovo W520, and none of the solutions proposed here solve it for me.

[Launchpad Janitor (janitor)]

This bug was fixed in the package gnome-settings-daemon - 3.3.91-0ubuntu4

---------------
gnome-settings-daemon (3.3.91-0ubuntu4) precise; urgency=low

  * Add 01_fix_multiple_syndaemons.patch: Ensure that a spawned syndaemon gets
    killed when settings-daemon exists due to a crash, a keyboard interrupt,
    etc. This avoids having multiple syndaemons run at the same time, which
    can lead to the trackpad malfunctioning. (LP: #868400)
 -- Martin Pitt <email address hidden> Wed, 14 Mar 2012 11:22:21 +0100

[Mark Grosen (3y9m2vcwq6l-mark-fkzsxrqg2c8)]

I am still having this problem on hp dv6t laptop running 12.04. I believe I have the latest gnome-settings-daemon:

linux% dpkg-query -l | grep gnome-settings
ii gnome-settings-daemon 3.3.92-0ubuntu2 daemon handling the GNOME session settings

It seems to happen after waking from suspend. From a fresh reboot, things work fine, but soon after a wakeup, the lost sync messages start coming and the keyboard is annoyingly hard to use.

[Martin Pitt (pitti)]

Mark Grosen [2012-03-25 21:49 -0000]:
> It seems to happen after waking from suspend. From a fresh reboot,
> things work fine, but soon after a wakeup, the lost sync messages start
> coming and the keyboard is annoyingly hard to use.

Did you check whether you have two syndaemons running at that time?

[Mark Grosen (3y9m2vcwq6l-mark-fkzsxrqg2c8)]

Pardon my ignorance, but how do I check for a "syndaemon"? I tried "ps aux | grep syn" but got nothing.

[Martin Pitt (pitti)]

Mark Grosen [2012-03-26 16:54 -0000]:
> Pardon my ignorance, but how do I check for a "syndaemon"? I tried "ps
> aux | grep syn" but got nothing.

That's correct. So you have a different bug then. Thanks for checking!

Martin
--
Martin Pitt | http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)

[Mark Grosen (3y9m2vcwq6l-mark-fkzsxrqg2c8)]

I fixed my problem related to this bug by following the suggestion in a different bug report:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/717970/comments/26

Mark

[Jens Finkhäuser (finkhaeuser-consulting)]

See also https://bugs.launchpad.net/ubuntu/+bug/989689

[Amos Blanton (lightnin9)]

I did a clean install of 12.04, followed by a deja-dup restore of a backup of my home directory. I then enabled "disable touchpad while typing." Then I began having these symptoms.

Previously, (when I was on 11.10 , from which the backup was made) I had created a custom syndaemon launcher startup because the normal "disable touchpad while typing" didn't work very well (cursor would still jump sometimes when I brushed the touchpad while typing).

I didn't realize this would persist in "startup applications preferences" after the clean install followed by restore. Apparently it did, and so I got this error - two syndaemons running. Just posting on the off chance others make the same mistake.

[sds (sds-gnu)]

thinkpad t520: after upgrade to 12.04 - touchpad no longer works.

modprobe -r psmouse && modprobe psmouse proto=imps

as root restored touchpad but without two-finger scrolling and the mouse/touchpad settings menu now misses the touchpad tab.

[Tanmay Mudholkar (t-k-mudholkar)]

Here is something that might be of interest to the bug trackers: I am facing the same problem on an HP dv6 touchpad. On my laptop, this problem seems correlated with another problem with my wifi button. My wifi button does not work on my laptop after I log in - somehow I have to press the button before I get to the login screen if I want to activate my wifi. I have noticed that on the occasion that I need to use wifi, whenever I activate the button, my mouse pointer may freeze from the login screen onwards. This problem goes away after I reboot twice or thrice.

[Hsin-Yi, Chen (hychen) (ossug-hychen)]

The patch described in #116 does not be included in gnome-settings-daemon_3.2.2-0ubuntu2.3 in Oneiric

[Hsin-Yi, Chen (hychen) (ossug-hychen)]

Proposed a SRU package for oneiric

[Summary]

Patch: http://bazaar.launchpad.net/~ossug-hychen/gnome-settings-daemon/fix-868400-oneiric/revision/184

bzr branch: https://code.launchpad.net/~ossug-hychen/gnome-settings-daemon/fix-868400-oneiric

[IMPACT]

 * touchpad is disabled sometines because 2 syndaemon instances. (one is launched by lightdm, anthoer one is launched by current user.)
 * ALPS touchpad does not use syndaemon, so ALPS users will not be impacted.

[TESTCASE]

 1. kill gnome-settings-daemon
 2. check syndaemon has only 1 instance after gnome-setitngs-daemon re-launched

[Regression Potential]

 * the patch is from gnome-settings-daemon package in precise
 * the risk is low because the patch only add the code to make sure syndaemon be killed if gnome-settings-daemon is killed

[James M. Leddy (jm-leddy)]

I've requested a merge into oneiric proposed and subscribed ~ubuntu-sponsors:

https://code.launchpad.net/~ossug-hychen/gnome-settings-daemon/fix-868400-oneiric/+merge/117358

[Anthony Wong (anthonywong)]

Hi developers, mind giving the merge request a review? We are in need of the fix for our last set of oneiric oem projects, thanks.

[Sebastien Bacher (seb128)]

James, Anthony: do you really need those fixes to land in the official archive? Our resources are limited and at this point we need to focus on precise LTS and quantal rather than Oneiric, having to build and test all those Oneiric backports has a cost. I'm keeping the bug open in case somebody is still interested to sponsor Oneiric updates but I can't justify spending extra time helping on those myself, I would recommend you consider updating to the LTS or building your own overlay ppa with the fixes you need for that project.

[James M. Leddy (jm-leddy)]

Hi Sebastien,

The OEM has already shipped a custom version with the fix. As long as we have commitment that this will be fixed _if ever_ an SRU for oneiric is released, then we don't need to issue an SRU now. Or if no other g-s-d issues come up and we never issue an SRU for oneiric that's fine too.

[Sebastien Bacher (seb128)]

> As long as we have commitment that this will be fixed _if ever_ an SRU for oneiric is released

our current process doesn't permit us to commit to that sorry, we will try our best to think about that fix if we do a SRU (not likely), but it could well be that e.g the security team issue a security fix and doesn't include any other fix with it

[Dimitri John Ledkov (xnox)]

Looks good. Uploaded.
[ubuntu/oneiric-proposed] gnome-settings-daemon 3.2.2-0ubuntu2.3 (Waiting for approval)

Unsubscribing ubuntu-sponsors team.

[Brian Murray (brian-murray)]

Hello Mark, or anyone else affected,

Accepted gnome-settings-daemon into oneiric-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/gnome-settings-daemon/3.2.2-0ubuntu2.3 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please change the bug tag from verification-needed to verification-done. If it does not, change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

[Chris Halse Rogers (raof)]

The verification of this Stable Release Update has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions.

[Launchpad Janitor (janitor)]

This bug was fixed in the package gnome-settings-daemon - 3.2.2-0ubuntu2.3

---------------
gnome-settings-daemon (3.2.2-0ubuntu2.3) oneiric-proposed; urgency=low

  * debian/patches/52_kill_syndaemon_when_gsd_die.patch:
    - Ensure that a spawned syndaemon gets killed when settings-daemon exists
      due to a crash, a keyboard interrupt, etc. This avoids having multiple
      syndaemons run at the same time, which can lead to the trackpad be
      unexpected disabled. (LP: #868400)
 -- Hsin-Yi Chen (hychen) <email address hidden> Thu, 09 Aug 2012 14:28:59 +0800

[downward (invisioslice)]

This bug also affect Ubuntu 12.04 After a clean Install the touchpad suddenly stopped working in Ubuntu!!!???

UBUNTU 12.04: here it is a partial solution: https://answers.launchpad.net/touchpad-indicator/+question/195181 but my touchpad scroll is dead...

[cybermujahidz (cybermujahidz-n)]

the problem also shows in precise. My touchpad suddenly stopped when i (may) accidentally make a gesture which disable my touchpad (not for the click function). When i did, it displays an osd box(looks like a notification) and then my touchpad is disabled.

when i run dconf-tools and looks for /desktop/gnome/peripherals/touchpad/touchpad_enabled the value is "true".
Then i re-enable it by setting it to false, then true. and my touchpad went normal again.
i think it's because disable touchpad while type feature's bug.