@Christopher,
Using the following information:
INPUT (KEYBOARD, MOUSE, JOYSTICK, TOUCHSCREEN) DRIVERS
M: Dmitry Torokhov dmitry.torok...@gmail.com
M: Dmitry Torokhov d...@mail.ru
L: linux-in...@vger.kernel.org
Q: http://patchwork.kernel.org/project/linux-input/list/
T: git
Ari Fogel, just to clarify, one would want a developer who committed to
your device specifically, not just any random committer to any driver
from the mailing list.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Ari Fogel, as outlined in https://wiki.ubuntu.com/Bugs/Upstream/kernel ,
it is best when e-mailing a mailinglist to CC both the driver maintainer
for your device, and anyone who may have submitted a commit towards your
device/driver within the last ~6 months.
--
You received this bug
Christopher,
Thank you for timely response. The best practice you refer to in comment #48
seems to apply to regressions. I don't know precisely what regression
refers to in this context, but I assumed it meant something along the a bug
that was introduced after not existing in a previous
Ari, as I'm the one that most recently revamped that article, I can
comfortably say the methodology would apply to non-regressions as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1168224
In comment #43, I mentioned that I filed another report (this time to
linux-input). Actually, I just discovered that I had filed a similar report
over a year ago to linux-input. For whatever reason, the old report did not
come up when I searched (which is why I filed the new one),, but was
I've sent another report using the contemporary latest upstream kernel:
3.17.0-031700rc7-generic
The report can be found at:
http://www.spinics.net/lists/linux-input/msg33746.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
CORRECTION: the keycode is not 135; that was the key next to it, which
already worked. However, II did find a keycode using the latest kernel.
I will update shortly with the actual keycode.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Note that one of the keys I reported as not working actually works in
this latest kernel version (3.17.0-031700rc7-generic):. the key to the
right of the right-alt key. Its keycode is 135. Unfortunately, I could
not deduce its role, since I was unable to run any commands
(specifically xev) using a
The keycode for the key to the right of the alt key reported by showkey
in kernel 3.17.0-031700rc7-generic is 580.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1168224
Title:
045e:0745 [HP
The bug still exists in the latest kernel (3.13.0-031300rc3-generic)
** Changed in: linux (Ubuntu)
Status: Expired = Confirmed
** Tags removed: kernel-bug-exists-upstream-v3.11.rc4 kernel-request-3.11.0-7.14
** Tags added: kernel-bug-exists-upstream-v3.13.0-031300rc3-generic
--
You
** Tags removed: kernel-bug-exists-upstream-v3.13.0-031300rc3-generic
needs-upstream-testing
** Tags added: kernel-bug-exists-upstream-v3.13-rc3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1168224
Ari Fogel, the issue you are reporting is an upstream one. Could you
please report this problem through the appropriate channel (would check
in with linux-input) by following the instructions _verbatim_ at
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1168224
Ari Fogel, regarding your comments
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1168224/comments/36 :
@Christopher per your comment on 2013-08-22:
http://www.spinics.net/lists/linux-input/maillist.html;
Good. Could you please provide a direct URL to your post specifically,
not just the
Three things:
1.
That was a typo in comment #36.
I meant to say, I reposted in linux-input, not, I reposted in linux-usb.
2.
Per your comment (#38), I have provided below a link to my post in linux-input:
http://www.spinics.net/lists/linux-input/msg27617.html
3.
I will test shortly using the
** Tags removed: kernel-bug-exists-upstream
** Tags added: needs-upstream-testing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1168224
Title:
045e:0745 [HP TouchSmart tm2t-2200] No scancode for
@Joseph I don't see how to retrieve this kernel version. There isn't an
exact match on at the upstream kernel list Christopher posted above.
There is no linux-image-generic-lts-saucy package available for precise
(I assume this would be 3.11). Is there an alternate version I should
test? Or do I
@Christopher per your comment on 2013-08-22:
http://www.spinics.net/lists/linux-input/maillist.html
I originally posted to linux-...@vger.kernel.org, but the response I
received was Care to explain how this is a usb issue. I was busy with
school and work, and just reposted to
I tried installing linux version 3.11.0-8 over my precise installation
from the Ubuntu package repositories website. Unfortunately, neither the
keyboard nor mouse responded at all when booting with this verison. I
suppose I could try a true Saucy environment, but I'm not sure exactly
how to use
Given the number of bugs that the Kernel Team receives during any
development cycle it is impossible for us to review them all. Therefore,
we occasionally resort to using automated bots to request further
testing. This is such a request.
We are approaching release and would like to confirm if
I haven't received any acknowledgment from the kernel team that my
report was received. Is it typical not to receive any response for this
long? I understand that there is nothing for the Ubuntu team to do until
the bug is fixed upstream, but I would like to verify that I've done all
I can on my
Ari Fogel, could you please provide a URL to the mailing list you posted
to?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1168224
Title:
045e:0745 [HP TouchSmart tm2t-2200] No scancode for several
Ari Fogel, the issue you are reporting is an upstream one. Could you
please report this problem through the appropriate channel by following
the instructions _verbatim_ at
https://wiki.ubuntu.com/Bugs/Upstream/kernel#KernelTeam.2BAC8-KernelTeamBugPolicies.Overview_on_Reporting_Bugs_Upstream
?
I've submitted the upstream report to the appropriate team. I cc'ed this
bug, but it does not appear to have updated here. Let me know if there
is anything else to do.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
None of the troubleshooting steps yielded any response when these buttons were
pressed.
There are three input devices that show up with findkeyboards:
input/event3
input/event5
input/js0
All of the regular keyboard buttons yield a response when I use keymap on
event3. The buttons I am interested
Ari Fogel, could you please test for this in the newest mainline kernel
via http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-rc4-saucy/ ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1168224
The results are more or less the same for kernel 3.11.0-031100rc4-generic which
I downloaded from the link you provided.
The only difference is that findkeyboards lists event12 and event14 instead of
event3 and event5 as before (and js0 still appears). The behavior is identical.
The bug
The problem occurs in Saucy.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1168224
Title:
045e:0745 [HP TouchSmart tm2t-2200] No scancode for several keys of
Microsoft Comfort Desktop 5000
To
Ari Fogel, could you please provide the information following
https://wiki.ubuntu.com/Hotkeys/Troubleshooting ?
** Tags added: saucy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1168224
Title:
Ari Fogel, to help further debug, could you please test for this in a
Saucy environment (live is fine) via http://cdimage.ubuntu.com/daily-
live/current/ ?
** Description changed:
- I wanted to map the key directly to the right of the right ALT key to be
- a metakey, but I discovered that this
I'm currently downloading it.. do you need the output of lsusb -v as
well?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1168224
Title:
045e:0745 [HP TouchSmart tm2t-2200] No scancode for several
Ari Fogel:
do you need the output of lsusb -v as well?
No thank you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1168224
Title:
045e:0745 [HP TouchSmart tm2t-2200] No scancode for several keys
33 matches
Mail list logo
