045e:0745 [HP TouchSmart tm2t-2200] No scancode for several keys of Microsoft Comfort Desktop 5000

This change was made by a bot.

bot change incorrect - reverted

This change was made by a bot.

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.9 kernel[0]. You will need to install both the linux-image and linux-image-extra .deb packages.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.9-rc6-raring/

I tested with kernel version 3.9.0-030900rc6-generic, and the bug still exists.

Ari Fogel, could you please provide the full computer model as noted on the sticker (ex. HP TouchSmart tm2t-2200 CTO Notebook PC)?

The information for the computer I WAS using is:
Product: XQ322AV
Model: tm2t-2200

However, this problem persists with my current computer, which was built from parts. I have not tried with the upstream kernel for this computer, but I have no reason to believe this bug was fixed. Let me know if you need to me test anything else.

Ari Fogel, it would be helpful if we kept the computer that this keyboard is plugged into static. So, which would you like to debug with the, the HP you originally reported with or the custom one?

Let's debug with the laptop to avoid duplicating work.

(the laptop is the touchsmart)

Ari Fogel, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11-rc3

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

The bug persists in the latest upstream kernel.

Ari Fogel, did this problem not occur in a release prior to Precise?

I am having trouble parsing your question. Do you mean "did this problem occur in a release prior to Precise?" I have no idea. I have only tested this on Precise.
The keyboard is relatively new (2012ish), so I believe Precise was the contemporary Ubuntu version during its release. What are the next steps? I do have some experience with kernel development, so I don't mind hacking a little bit if someone can give me pointers where to start.

Ari Fogel, for regression testing purposes, could you please test for this in Lucid via http://releases.ubuntu.com/lucid/ ?

I tested it with Ubuntu Lucid 10.04.4 Desktop, kernel version 2.6.32-38-generic
The problem occurs in this version as well.

Ari Fogel, could you please unplug all USB devices, plug in just the problematic USB device, and then immediately place the following in a terminal and attach the results:
lsusb -v > lsusb-v.log

Here is the output BEFORE connecting the device.

Here is the output AFTER connecting the device.

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/ ?

I'm currently downloading it.. do you need the output of lsusb -v as well?

Ari Fogel:
>"do you need the output of lsusb -v as well?"

No thank you.

The problem occurs in Saucy.

Ari Fogel, could you please provide the information following https://wiki.ubuntu.com/Hotkeys/Troubleshooting ?

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 in do nothing at all when keymap is running.
Nothing happens with any keypresses when I use keymap on event5
keymap crashes on startup when I try to use it on js0.
I have attached a tarball of some relevant files as discussed in the FAQ.

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/ ?

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 persists.

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 ?

Thank you for your understanding.

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.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

[1]. Summary:
045e:0745 [HP TouchSmart tm2t-2200] No scancode for several keys of
Microsoft Comfort Desktop 5000

[2]. Link to original bug report in launchpad:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1168224

[2]. Bug description:
I wanted to map the keys labeled '1', '2', '3', '4', and '5' above the
F-keys between the camera key and the star key, and directly to the
right of the right ALT key but I discovered that these raise no events
whatsoever via dmesg, xev, nor showkey.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-40-generic 3.2.0-40.64
ProcVersionSignature: Ubuntu 3.2.0-40.64-generic 3.2.40
Uname: Linux 3.2.0-40-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu17.1
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: arifogel 1861 F.... pulseaudio
 /dev/snd/controlC0: arifogel 1861 F.... pulseaudio
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xc4500000 irq 45'
   Mixer name : 'IDT 92HD81B1X5'
   Components : 'HDA:111d7605,103c1486,00100402'
   Controls : 16
   Simple ctrls : 9
Card1.Amixer.info:
 Card hw:1 'Generic'/'HD-Audio Generic at 0xc4420000 irq 47'
   Mixer name : 'ATI R6xx HDMI'
   Components : 'HDA:1002aa01,00aa0100,00100200'
   Controls : 6
   Simple ctrls : 1
Card1.Amixer.values:
 Simple mixer control 'IEC958',0
   Capabilities: pswitch pswitch-joined penum
   Playback channels: Mono
   Mono: Playback [on]
Date: Thu Apr 11 20:50:37 2013
HibernationDevice: RESUME=UUID=e46d0966-e5ee-4f6e-9e3f-1f21a65ac784
MachineType: Hewlett-Packard HP TouchSmart tm2 Notebook PC
MarkForUpload: True
ProcFB:
 0 inteldrmfb
 1 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-40-generic
root=UUID=3be4864c-c530-4049-8cbf-dc74129749b5 ro loop.max_part=63
acpi_osi=Linux acpi_backlight=vendor
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-40-generic N/A
 linux-backports-modules-3.2.0-40-generic N/A
 linux-firmware 1.79.1
SourcePackage: linux
StagingDrivers: mei
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/18/2011
dmi.bios.vendor: Insyde
dmi.bios.version: F.25
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 1486
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 83.20
dmi.chassis.asset.tag: CNU1120G9K
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnInsyde:bvrF.25:bd02/18/2011:svnHewlett-Packard:pnHPTouchSmarttm2NotebookPC:pvr0587220000242A20000220100:rvnHewlett-Packard:rn1486:rvr83.20:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP TouchSmart tm2 Notebook PC
dmi.product.version: 0587220000242A20000220100
dmi.sys.vendor: Hewlett-Packard
[3]. Keywords (couldn't find authoritative list):
kernel

[4]. Kernel version (/proc/version)
Linux version 3.11.0-031100rc4-generic (apw@gomeisa) (gcc version
4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #20130804...

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 end. Does anyone who has experiencing reporting upstream bugs have any advice?

Ari Fogel, could you please provide a URL to the mailing list you posted to?

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 this bug is still present. Please test again with the latest development kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get dist-upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

Thank you for your help, we really do appreciate it.

@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 have to download a saucy live-cd to test this?

@Christopher per your comment on 2013-08-22:
http://www.spinics.net/lists/linux-input/maillist.html

I originally posted to <email address hidden>, 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 <email address hidden> today. This seemed like a better match. Sorry about the delay.

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 this kernel version with a livecd. Would I have to actually install Saucy? I don't think I'm prepared to do that just now.

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 archive in it's entirety?

>"I originally posted to <email address hidden>, 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 <email address hidden> today."

While linux-usb seems logical, the developer view of it is not as straight forward. If it is a scancode issue, linux-input may be a better place, as the issue is an "input" issue with a USB device, not with the USB protocol stack (i.e. linux-usb). It's silly for whoever responded to you with "care to explain..." when it would have been clear you aren't in a position to do that as you posted a input-input issue into linux-usb. :D

Regarding https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1168224/comments/37 :
>' I suppose I could try a true Saucy environment..."

A Saucy live environment test would be fine.

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 latest Saucy iso on a live-usb boot.

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

The bug still exists in the latest kernel (3.13.0-031300rc3-generic)

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 https://wiki.ubuntu.com/Bugs/Upstream/kernel#KernelTeam.2BAC8-KernelTeamBugPolicies.Overview_on_Reporting_Bugs_Upstream ?

Please provide a direct URL to your post once you have made it so that it may be tracked.

Thank you for your understanding.

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

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 graphical login (mouse moved, but keyboard buttons did nothing). I found the keycode by doing ctrl-alt-f1 to open up a pseudoterminal, then logging in and using showkey. This key does not raise any events with my current kernel version however (3.13.0-36-generic).

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.

The keycode for the key to the right of the alt key reported by showkey in kernel 3.17.0-031700rc7-generic is 580.

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 listed as "previous in thread" with respect to the new report. There are no other messages in the thread.
So it seems that this bug was ignored for more than a year. Is this what is to be expected when filing kernel bugs? Not a jab at anyone here, but is there really any point in me taking time out of my busy schedule to file bugs and do all this testing when no one with the power to fix anything even bothers to even respond? This is very disheartening to say the least.
@Christopher, do you have any advice on what to do at this point?

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.

Christopher,
Thank you for timely response. The best practice you refer to in comment #48 seems to apply to "regression"s. 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 commit". According to this assumed definition, I didn't think this was a regression. That fact, combined with the ubiquitous warnings about "negative unintended consequences," made me decide against emailing anyone else. Since the warning about such consequences still seems salient, I must ask: Is this in fact a "regression"? What is a "regression" in this context?

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.

@Christopher,
Using the following information:
INPUT (KEYBOARD, MOUSE, JOYSTICK, TOUCHSCREEN) DRIVERS
M: Dmitry Torokhov <email address hidden>
M: Dmitry Torokhov <email address hidden>
L: <email address hidden>
Q: http://patchwork.kernel.org/project/linux-input/list/
T: git git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git
S: Maintained
F: drivers/input/
F: include/linux/input.h
F: include/uapi/linux/input.h
F: include/linux/input/
I cloned the linux-input repo, did a git log for the paths starting with "F:" above, filtered for commits in the last 6 months, and filtered out authors that were only responsible for merge commits. This leaves me with a list of 68 authors.. I would very much like to avoid creating a shitstorm by bothering all these people unnecessarily, so I just want to confirm with you that this is the appropriate methodology for finding the appropriate people to contact before firing off these emails.

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.