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
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 -]:
I seem to have inadvertently narrowed down the
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
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
I experienced this bug multiple times with gnome-shell. Using it since 2
months now.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.launchpad.net/bugs/868400
Title:
Synaptics touchpad
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
Karl [2011-12-16 21:28 -]:
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
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
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;}
}
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
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.
--
You received this bug notification because you are a member
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
** Also affects: gnome-settings-daemon (Ubuntu Precise)
Importance: High
Assignee: Canonical Desktop Team (canonical-desktop-team)
Status: Incomplete
** Also affects: xserver-xorg-input-synaptics (Ubuntu Precise)
Importance: High
Status: Confirmed
--
You received this
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
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
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
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
--
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?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics
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
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).
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
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
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
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
@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
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
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/2S+ 13:45 0:00 grep syndeamon
frohro@frohro-d830:~/Araya Classes/Signals/PSK31$ ps aux | grep syndaemon
frohro
florin@florin-Satellite-C650:~$ ps aux | grep syndaemon
florin4265 0.0 0.0 20064 916 ?S14:54 0:12 syndaemon -i
0.5 -K -R
florin7782 0.0 0.0 14424 908 pts/0S+ 23:56 0:00 grep
--color=auto syndaemon
I will also restart to see what happens on a fresh start
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
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
Oh, and this workaround should be fine for all:
In terminal:
sudo killall -u lightdm syndaemon
synclient Touchpadoff=0
regards
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
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
Florin - please ignore my prior comment, had forgotten I was running syndaemon
separtely from gsd, comment was totally wrong
Sorry about that
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
#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
Workaround of #5 worked for me too.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.launchpad.net/bugs/868400
Title:
Synaptics touchpad stops working
To manage notifications about this bug
Happens randomly, synclient TouchpadOdd=0 fixes it on my T420/11.10
(64bit)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.launchpad.net/bugs/868400
Title:
Synaptics touchpad stops working
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?
--
You
Yes, when the touchpad freezes, an usb mouse (plugged or that I plug
because of the freeze) works perfectly.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.launchpad.net/bugs/868400
Title:
synclient TouchpadOff=0 worked for me as well...
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.launchpad.net/bugs/868400
Title:
Synaptics touchpad stops working
To manage notifications
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?
--
You received this bug
synclient TouchpadOff=0 fixes it on my Aspire 5534
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.launchpad.net/bugs/868400
Title:
Synaptics touchpad stops working
To manage notifications
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
For my Asus M70Vn, synclient TouchpadOff=0 works to repair the freeze.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.launchpad.net/bugs/868400
Title:
Synaptics touchpad stops working
To
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
Karl, thanks you're right, my script did not check the recent comments.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.launchpad.net/bugs/868400
Title:
Synaptics touchpad stops working
To
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,
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.
** Changed in: xserver-xorg-input-synaptics (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a
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
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
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
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,
synclient TouchpadOff=0 worked for me. After update of fglrx driver this
bug appear often than normal
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.launchpad.net/bugs/868400
Title:
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
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
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.
--
You received this bug notification because you are a member of Ubuntu-X,
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
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.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics
For my problem, the workaround described in comment #8 has no effect.
The problem persists.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.launchpad.net/bugs/868400
Title:
Synaptics
Just like Karl, I already have touchpad-enabled checked, so the
workaround from #5 does not help me.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.launchpad.net/bugs/868400
Title:
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
I mostly use a USB mouse, but have noticed this happening on a Dell XPS
M1330 as well.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.launchpad.net/bugs/868400
Title:
Synaptics touchpad
Is anyone working to solve the problem ?? Today touchpad freezing
happened again ( same circumstances as I wrote earlier)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
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
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
--
You received this bug notification because you are a member of Ubuntu-X,
which is
In regards to the workaround in #5, this does not apply to my problem...
Mine is already checked.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.launchpad.net/bugs/868400
Title:
Synaptics
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
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!
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.
--
You received this bug notification because you are a member of
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!
--
You
not sure if bug #878859 is similar, it claims shift-lefclick on the
menus leads to pointer locking
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.launchpad.net/bugs/868400
Title:
Synaptics
Reporting the same issue for ASUS EeePC 1005 HA. But also that
workaround #5 fixed it (so far ;)).
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.launchpad.net/bugs/868400
Title:
Synaptics
FWIW, I've had this problem too. I found a fix for this
(http://ubuntuforums.org/showthread.php?t=1852081page=4styleid=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
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
Happens to me when I'm trying to open dash an search an app
(Transsmission). Killing x server (cntrl+alt+backspace) resolves the
problem
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
Workaround of #5 worked for me (so far)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.launchpad.net/bugs/868400
Title:
Synaptics touchpad stops working
To manage notifications about this
After disable touchpad while typing, I haven't had this bug in two days.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.launchpad.net/bugs/868400
Title:
Synaptics touchpad stops working
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.
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.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
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)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
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
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)
--
You received this bug notification because you are a
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
--
You received this bug notification because you are a member of Ubuntu-X,
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
--
You received this bug notification because you are a
Also seeing this on Dell Inspiron, randomly occuring, but once occurs,
is persistent.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.launchpad.net/bugs/868400
Title:
Synaptics touchpad
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
** Changed in:
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?
**
Kate, does disabling the disable touchpad while typing option from the
ui workaround the issue for you? do you use 2 fingers gestures?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
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 -
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
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
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.launchpad.net/bugs/868400
Title:
Synaptics touchpad stops working
To manage notifications about this bug go to:
seems similar to bug #863668, bug #859455
** Changed in: xserver-xorg-input-synaptics (Ubuntu)
Status: New = Confirmed
** Changed in: xserver-xorg-input-synaptics (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu-X,
which
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.
** Changed in: xserver-xorg-input-synaptics (Ubuntu)
Status: Confirmed = Incomplete
90 matches
Mail list logo
