Comment 29 for bug 228054

From the xev log we can see that it is producing scancodes correctly, but looks like they're probably mapped incorrectly, therefore can you please do the following:

(From https://wiki.ubuntu.com/Hotkeys/Troubleshooting):

Exercise the "Fixing broken keys" section in /usr/share/doc/udev/README.keymap.txt

   1. If that was successful, attach your newly created keymap and rule.
   2. If udev's keymap tool shows a correct key symbol, look up the symbolic name in /usr/include/linux/input.h. If it is mapped to a code over 255 (over 0x0ff), then it is outside X's range see bug 313514. In this case, if it is important to have the key mapped, the key should be remapped to an appropriate value < 256.

If you need any help in doing this, please get back to us, or for a quicker response, help with things like this can be found on IRC at irc.freenode.net in the #ubuntu channel.

Thank you.