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
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...
--
You received this bug notification
** Tags added: blocks-hwcert-enablement
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/868400
Title:
Synaptics touchpad stops working - two syndaemon instances
** Tags removed: blocks-hwcert-enablement verification-needed
** Tags added: verification-done
** Tags added: blocks-hwcert-enablement
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
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
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
Looks good. Uploaded.
[ubuntu/oneiric-proposed] gnome-settings-daemon 3.2.2-0ubuntu2.3 (Waiting for
approval)
Unsubscribing ubuntu-sponsors team.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
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
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
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.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
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
** Changed in: oem-priority/oneiric
Status: New = Confirmed
** Changed in: oem-priority
Status: New = Confirmed
** Changed in: gnome-settings-daemon (Ubuntu Oneiric)
Status: Confirmed = In Progress
** Changed in: oem-priority/oneiric
Status: Confirmed = In Progress
** Description changed:
+ 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
+
+
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
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
The patch described in #116 does not be included in gnome-settings-
daemon_3.2.2-0ubuntu2.3 in Oneiric
** Changed in: gnome-settings-daemon (Ubuntu Oneiric)
Status: Fix Committed = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
** Branch linked: lp:~ossug-hychen/gnome-settings-
daemon/fix-868400-oneiric
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/868400
Title:
Synaptics touchpad stops
Proposed a SRU package for oneiric
[Summary]
Patch:
http://bazaar.launchpad.net/~ossug-hychen/gnome-settings-daemon/fix-868400-oneiric/revision/184
bzr branch:
** Also affects: oem-priority
Importance: Undecided
Status: New
** Changed in: oem-priority
Importance: Undecided = High
** Also affects: oem-priority/oneiric
Importance: Undecided
Status: New
** Changed in: oem-priority/oneiric
Importance: Undecided = High
--
You
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
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.
--
You received this bug notification because you are
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
See also https://bugs.launchpad.net/ubuntu/+bug/989689
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/868400
Title:
Synaptics touchpad stops working - two syndaemon
** Changed in: gnome-settings-daemon (Ubuntu Oneiric)
Assignee: Canonical Desktop Team (canonical-desktop-team) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
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
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Mark Grosen [2012-03-25 21:49 -]:
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
Pardon my ignorance, but how do I check for a syndaemon? I tried ps
aux | grep syn but got nothing.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/868400
Title:
Mark Grosen [2012-03-26 16:54 -]:
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
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
** Changed in: gnome-settings-daemon (Ubuntu Oneiric)
Status: Triaged = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/868400
Title:
Synaptics
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
** Changed in: gnome-settings-daemon (Ubuntu Precise)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/868400
Title:
** Branch linked: lp:ubuntu/gnome-settings-daemon
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/868400
Title:
Synaptics touchpad stops working - two syndaemon
** Changed in: gnome-settings-daemon
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/868400
Title:
Synaptics touchpad stops
For what it's worth, also seeing this on a Lenovo W520, and none of the
solutions proposed here solve it for me.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/868400
I have a first g-s-d patch working, sent to upstream for commentary.
** Changed in: gnome-settings-daemon (Ubuntu Precise)
Status: Triaged = In Progress
** Changed in: gnome-settings-daemon (Ubuntu Precise)
Assignee: Canonical Desktop Team (canonical-desktop-team) = Martin Pitt
** Changed in: lightdm (Ubuntu Precise)
Assignee: Robert Ancell (robert-ancell) = Martin Pitt (pitti)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/868400
Title:
** Changed in: lightdm (Ubuntu Precise)
Status: Triaged = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/868400
Title:
Synaptics touchpad stops
** Branch linked: lp:~ubuntu-desktop/lightdm/ubuntu
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/868400
Title:
Synaptics touchpad stops working - two syndaemon
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)
[
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.
** No longer affects: lightdm (Ubuntu Precise)
** No longer affects: lightdm (Ubuntu Oneiric)
** No longer affects:
** Branch linked: lp:ubuntu/lightdm
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/868400
Title:
Synaptics touchpad stops working - two syndaemon instances running
The lightdm fix seems to have caused bug 947713.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/868400
Title:
Synaptics touchpad stops working - two syndaemon
** Changed in: gnome-settings-daemon (Ubuntu)
Milestone: ubuntu-12.04-beta-1 = ubuntu-12.04-beta-2
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/868400
Title:
** Tags added: rls-mgr-p-tracking
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/868400
Title:
Synaptics touchpad stops working - two syndaemon instances running
To
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?
--
You received this bug notification because you are a member
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
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
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
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:
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
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
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
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.
--
You received this bug notification
okhad 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
** Bug watch added: GNOME Bug Tracker #668667
https://bugzilla.gnome.org/show_bug.cgi?id=668667
** Also affects: gnome-settings-daemon via
https://bugzilla.gnome.org/show_bug.cgi?id=668667
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are
** Changed in: gnome-settings-daemon
Status: Unknown = Confirmed
** Changed in: gnome-settings-daemon
Importance: Unknown = Medium
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
** Changed in: gnome-settings-daemon (Ubuntu Precise)
Assignee: Rodrigo Moya (rodrigo-moya) = Canonical Desktop Team
(canonical-desktop-team)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
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
@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
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
@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
--
You
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
@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 ;)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
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
--
You received this bug notification because you are a member of Ubuntu
I haven't seen it in a week or more.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/868400
Title:
Synaptics touchpad stops working - two syndaemon instances running
@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
@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`.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
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)
--
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.
** Changed in: gnome-settings-daemon
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
Desktop Bugs, which is subscribed to gnome-settings-daemon 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
Desktop Bugs, which is subscribed to
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
Desktop Bugs, which is subscribed to gnome-settings-daemon 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
Desktop Bugs, which is subscribed to gnome-settings-daemon 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
Desktop Bugs, 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
Desktop Bugs, which is subscribed to gnome-settings-daemon 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
Desktop Bugs, which is subscribed to gnome-settings-daemon 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
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/868400
Title:
Synaptics touchpad stops working
To manage notifications about this
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
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/868400
Title:
Synaptics touchpad stops
1 - 100 of 150 matches
Mail list logo