Sorry, I believe I may have been unclear, but I have tested this on the
current 3.16.0-25 kernel as well with the same issue, so it is both
mainline and upstream.
However I would like to add that as part of bug #1398533 I reported this
issue to the kernel.org linux-input mailing list. They did not
Okay, no, I'm afraid I am still terrifically confused here. I have never
had to do this process before. The instructions listed seem custom
tailored for that particular example patch. I don't know what file I am
patching even so I'm afraid I can't tailor this example to suit my
needs.
--
You rece
Why, thank you! I was combing through Google trying to figure out the
process myself. This is a handy reference. I will report on my findings
soon.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
Ah, I see why that did not work the first time I tried it. I probably
did not give it enough time to land into the archives and just assumed I
was looking in the wrong place. Thanks for the clarification.
The correspondence begins here with my initial mailing to the linux-input
mailing list:
http
Hello, I just wanted to let you know I've been involved in assisting the
kernel.org folk with this bug and one of the people at Synaptics has
written a patch for it. I wanted to attach that mailing correspondence
to my bug report here on Launchpad in case others want to see it, but I
still do not y
Public bug reported:
Hi,
There is an issue with this clickpad's simulated clicks. Specifically,
the window for double-tapping (tapping the touchpad twice to simulate a
double-click) is remarkably brief. Let me be clear, double-tapping on
the touchpad does work, however if you do not get the secon
As a request, do you think it would be possible to find a workaround for
a double-click issue with the touchpad? Double-tapping does function,
but it seems to only function in one of two ways: firstly, by double-
tapping extremely quickly. There seems to be a <200ms window here, which
is uncomforta
Okay, I sent the email as requested. Unfortunately I don't know nearly
enough about the kernel.org mailing list to provide a URL. Not sure
where to begin to look, I'm afraid. Any instructions there would be
greatly appreciated. Thank you.
--
You received this bug notification because you are a me
** Description changed:
+ Edit (12/07): Updated bug description: clicking the hardware clickpad
+ buttons causes all mouse input to malfunction.
+
Edit: This bug is a possible duplicate of bug #1394869
So far, from what I can gather, the clickpad functions normally when
using the touchpa
Well, I must confess, for me this fix is sufficient. I will only use the
simulated clicks anyway due to the clickpad's design, where the touch-
senstive area covers the buttons which means if I use the hardware
buttons to click on things, then the pointer will frequently deviate in
the process of c
Okay, I have tested the touchpad after entering those commands, tested
through two boots of the 3.16.0-25 kernel. My findings show that when I
first enter those commands after boot, the clickpad hardware clicks
still cause the clickpad to malfunction. However after an xinput
enable/disable cycle wi
Okay, a little embarassing, but I went back to my original kernel
(3.16.0-25) and I realized I could not reproduce the touchpad problems I
had had before. Admittedly double-tap is a little bit finicky and I
probably assumed it was broken but I think the actual problem is just
that the allowed delay
Okay, I have never had to install an upstream kernel before so I hope I am
using the right kernel here. When I enter the terminal command:
uname -r
my kernel version information reads:
3.18.0-031800rc7-generic
Please tell me if this is wrong and I will try to figure out where I went wrong.
Some g
There may have been an easier way of doing this, but I eventually
determined that I would need to reinstall Windows in order to get my
BIOS patched. My Lubuntu install was less than a day old so that was not
too much of a problem, but I was fortunate to have a Windows 8 retail CD
laying around sinc
** Summary changed:
- HP Stream 11 clickpad malfunctions after performing a click in Lubuntu 14.10
+ HP Stream (11-d010nr) clickpad malfunctions after performing a click in
Lubuntu 14.10
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to li
Public bug reported:
Edit: This bug is a possible duplicate of bug #1394869
So far, from what I can gather, the clickpad functions normally when
using the touchpad portion to maneuver the onscreen pointer. However,
the act of using one of the hardware click buttons causes it to
malfunction.
To t
I am having the exact same issue with my HP Stream 11's clickpad in
Lubuntu 14.10. Cursor movement acts fine until I attempt or accidentally
click the clickpad at which point no mouse clicks from any source will
work properly (it triggers a click but only from the point where the
last click was mad
17 matches
Mail list logo
