** Tags added: kernel-fixed-upstream-3.19-rc1
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1398533
Title:
[HP Stream Notebook - 11-d010nr] clickpad malfunctions after
performing a
D Scott Phillips, it would help immensely if you filed a new report via a
terminal:
ubuntu-bug linux
Please feel free to subscribe me to it.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I have an HP Stream 11 and am also seeing the stuck click problem. I
built with the patch in comment #19 and can confirm that the problem is
now fixed. Also I believe bug #1394869 is about the same issue.
--
You received this bug notification because you are a member of Kernel
Packages, which is
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
Amordea Whiteoak, could you please provide a direct URL to your e-mail
via http://vger.kernel.org/vger-lists.html ?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1398533
Title:
[HP
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:
Amordea Whiteoak, have you tested the patch yet to see if it addresses
your problem? If not, instructions may be found at
https://wiki.ubuntu.com/Kernel/KernelBisection#Testing_a_newly_released_patch_from_upstream
.
--
You received this bug notification because you are a member of Kernel
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.
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
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
Amordea Whiteoak, the next step is to fully reverse commit bisect from
kernel 3.16 to 3.18-rc7 in order to identify the last bad commit,
followed immediately by the first good one that improves on your
touchpad features. Once this commit has been identified, then it may be
reviewed as a candidate
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
Amordea Whiteoak, just to inquire, does executing the following via a terminal
help to address your problem:
synclient RTCornerButton=0
synclient RBCornerButton=0
synclient LTCornerButton=0
synclient LBCornerButton=0
synclient AreaBottomEdge=3900
** Changed in: linux (Ubuntu)
Status:
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
Amordea Whiteoak, just to advise, the commands will not persist through
a reboot.
Despite this, if you are still having a problem, could you please edit
the Description to more accurately define what you are still/now
experiencing?
Otherwise, please mark this report Status Invalid.
** Changed
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
** 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
Amordea Whiteoak:
...if I use the hardware buttons to click on things, then the pointer will
frequently deviate in the process of clicking, leading to undesirable results.
That's not a bug, that's just poor hardware design.
This is actually not a poor hardware design, but a poor driver
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
Amordea Whiteoak, could you please test the latest upstream kernel
available from the very top line at the top of the page (the release
names are irrelevant for testing, and please do not test the daily
folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will
allow additional
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
21 matches
Mail list logo
