closing as fixed
** Changed in: xserver-xorg-input-synaptics (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/240738
Title:
syndaemon sometimes fails
Thanks Peter! I did't get notification of your updates to this bug but just
upgraded to 12.04 LTS and can confirm that the trackpad is successfully
disabled while typing! Thank you so much!!!
Plus I noticed I can click-and-hold with one finger while sliding another
finger for click-and-drag func
Launchpad has imported 8 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=39226.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help
tryptamine, I'm sure you are trying to be helpful but I'm not sure you
have a good understanding of this bug. If it isn't affecting you then
perhaps your hardware has a built-in system that handles accidental
touchpad clicks automatically. Consider yourself fortunate. Maybe
reading some of the dupl
Tim, try this page: https://help.ubuntu.com/community/UbuntuBootupHowto
(I don't want to state something incorrect :) ).
I'm still a little confused as to why using syndaemon is necessary at
all, though, when synclient doesn't seem to be affected by whether it's
running or not and has many more us
I'm also affected by this seemingly small, but extremely annoying bug
and it took me a couple of days before finding this report.
My MacBook 5,1 and Asus Eee PC are both affected by it and it already
made me upgrade to Oneiric in the hope it was fixed and then back to OS
X before giving it a new t
I'm terribly sorry for the dumb double-post, but I forgot to specify
that these settings are located in xorg.conf's input section or in a
more flexible xorg.conf.d rule file. This could also probably be
accomplished with an init rule, although that seems a bit heavy-handed,
especially if the target
Could you please expand on how palm detection is unreliable? I agree
that setting a two second delay sucks as a general cure for wandering
hands and fingers, but as far as I know the PalmMinZ/PalmMinWidth (I
think those are correct) and general touch sensitivity settings still
work--or are they the
** Changed in: xserver-xorg-input-synaptics
Status: Unknown => Confirmed
** Changed in: xserver-xorg-input-synaptics
Importance: Unknown => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
** Bug watch added: freedesktop.org Bugzilla #39226
http://bugs.freedesktop.org/show_bug.cgi?id=39226
** Also affects: xserver-xorg-input-synaptics via
http://bugs.freedesktop.org/show_bug.cgi?id=39226
Importance: Unknown
Status: Unknown
--
You received this bug notification beca
I just marked another 3 duplicates and agree that many people could be
affected.
I tested a Samsung SF510 with an Elantech touchpad where this bug really
hurts: its palm detection is very unreliable. Finger clicks are detected
if a palm is 3 mm *ABOVE* the touchpad surface! Even worse: the
clickab
This affects me as well on my MacBook Pro.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/240738
Title:
syndaemon sometimes fails to disable the touchpad
To manage notifications about this bug go to
I believe there are a lot more people affected. This is the only reason
that I am still using OS X since I got the MCP about 9 months ago.
I also think this is a problem affecting all the laptops with large
touchpad. Before I bought the MBP, I tried the HP Envy 15, with exactly
the same problem. I
Well, I decided to add myself as this is seriously annoying. I have a
MacBook Pro with a HUGE trackpad and anytime I go near a the y, u, 6 or
7 keys the cursor moves and my text ends up being inserted elsewhere.
Othertimes it will randomly copy a block of text and then the next key
press deletes/r
Here is the bug for summing the number of people affected by a bug and its
duplicates. I realize this doesn't belong here but figured others might want to
see it or mark themselves as affected :)
https://bugs.launchpad.net/launchpad/+bug/678090
--
You received this bug notification because you
that's a very good point bitinerant. I think I'll check to see if a
feature-request exists in Launchpad to add those totals together :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/240738
Title:
sy
There are also 18 people affected by the various duplicates of this bug,
but it's hard to know how many of those are unique.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/240738
Title:
syndaemon som
I think the problem is that most people never actually figure out what
is happening well enough to be able to locate this bug report. I agree
--it must be affecting many more people. As well as the MacBook
mentioned at the top, it also affects both of our two other laptops.
That is 100% of our la
I'm sure it affects many more people.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/240738
Title:
syndaemon sometimes fails to disable the touchpad
To manage notifications about this bug go to:
htt
I am puzzled why there are only ten people affected by this bug. It
drives me absolutely crazy and I am forced to disable touchpad clicks.
How can so few people be complaining? Is it hardware-specific? Do other
laptop touchpads disable themselves in the hardware rather than relying
on the synaptics
Hello,
I am running ubuntu 10.10 on a Dell Inspiron laptop n 5010. I get exactly the
same touchpad problem as described by everyone else even though I've ticked the
Disable touchpad while typing option.
I also think this is an extremely frustrating issue and the importance of
resolving it must
In the meantime i also spent some time on analysing, and found out,
that
Option "SHMConfig" "On" (not "true")
solved the issue of not beeing able to adjust fingerHigh/fingerLow with
synclient for me.
The sensitivity settings one can make in the kde-gui-touchpad are still not
useful and when the n
@itismike
Well, it might be sort of related. I'm pretty sure it worked when I booted from
the live CD (as did the screen backlight keys, but I'm not sure it was using
nvidia at the time), so something is different from that state and it may well
be that the difference is the SHMConfig flag. If s
That's odd. I had no problem disabling the "touch" in the touchpad
settings after I noticed it was enabled by default from a clean Natty
install. Sounds like a separate bug if you can't disable it through the
GUI.
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
@itismike - thanks for the hint in #743352
However, I'm a but stumped as I've failed to figure out the correct way
to enable SHMConfig in Natty. Things appear to have changed both inside
the bcm5974 and with the .fdi files recently so none of the tricks I
know allow synclient to connect.
In the o
Hi Goofy. I marked your bug (#57764) a dupe of this primarily because of the
following statements:
"When i change the settings in kcm-touchpad module and check with "synclient
-l" the settings are indeed changed, however, they have no effect..."
and:
"Under Windows the pad works as expected, but
Thx, i have an Acer NB and i'am not sure if/why my bugs has been marked
as a duplicate of this one, since the problem is even worse than this -
it does not only fail to disable, it also is not able to set the
sensitivity of the touchpad at all, can't find the reference to my bug
anymore, but it has
Ok this is a really big problem for a lot of users. Please mark the
importance to a level higher.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/240738
Title:
syndaemon sometimes fails to disable the
"it's very frustrating to work in such a way and it may be a reason to
continue to use Windows instead Linux!"
Is it possible to add this to the 100 papercuts project, or at least be
raised from low importance?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
I've installed Ubuntu 10.10 on a MacBook Pro and i'm getting hit by this
bug.
It's terrible to work with it, so I must disable mouse clicks with
touchpad, or use and external keyboard.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
Also affects Ubuntu Natty Narwhal Alpha 3. This is a problem because
11.04 has "Enable mouse clicks with touchpad" pre-selected on a standard
installation.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
** Changed in: xserver-xorg-input-synaptics (Ubuntu)
Status: Triaged => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/240738
Title:
syndaemon sometimes fails to disable the touchpad
Thank you itimike for your activity on trying to solve this issue.
I support your request to experts to find a good solution since it's
very frustrating to work in such a way and it may be a reason to
continue to use Windows instead Linux!
Claudio :)
--
You received this bug notification becaus
I wrote to Peter Osterlund, still listed on the Man pages as the author
(but he is no longer the maintainer of it.) This is his response:
"I was not aware of this problem (I don't normally use syndaemon), but I
was able to reproduce the problem on my fedora machine. The problem is
that the default
duplicates of this bug are more than 5 years old, and at least for me it
causes significant annoyances while typing. In my opinion it should not
be classified as "Low" importance. Can it get more attention please?
Also, how can it be both "Triaged" and "Unassigned"? Is this a bug
within Launchpad?
** Tags added: hardy
--
syndaemon sometimes fails to disable the touchpad
https://bugs.launchpad.net/bugs/240738
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubun
This problem has not been fixed in Intrepid.
--
syndaemon sometimes fails to disable the touchpad
https://bugs.launchpad.net/bugs/240738
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubunt
This will probably be fixed with the XRecord changes upstream.
** Changed in: xserver-xorg-input-synaptics (Ubuntu)
Importance: Undecided => Low
Status: New => Triaged
--
syndaemon sometimes fails to disable the touchpad
https://bugs.launchpad.net/bugs/240738
You received this bug noti
This problem is even more apparent to me when running syndaemon -i 0.5
-k
About every third keystroke doesn't trigger the Disable/Enable. While
typing, for example, "fff...", quickly, it is still very possible to
use the trackpad, although it is jumpy. I know syndaemon used to work
correctly
39 matches
Mail list logo
