There is no keypress event, exercise the "Fixing broken keys": == Fixing broken keys ==
In order to make a broken key work on your system and send it back to upstream for inclusion you need to do the following steps: 1. Find the keyboard device. Run /lib/udev/findkeyboards. This should always give you an "AT keyboard" and possibly a "module". Some laptops (notably Thinkpads, Sonys, and Acers) have multimedia/function keys on a separate input device instead of the primary keyboard. The keyboard device should have a name like "input/event3". In the following commands, the name will be written as "input/eventX". 2. Dump current mapping: sudo /lib/udev/keymap input/eventX > /tmp/orig-map.txt 3. Find broken scan codes: sudo /lib/udev/keymap -i input/eventX Press all multimedia/function keys and check if the key name that gets printed out is plausible. If it is unknown or wrong, write down the scan code (looks like "0x1E") and the intended functionality of this key. Look in /usr/include/linux/input.h for an available KEY_XXXXX constant which most closely approximates this functionality and write it down as the new key code. For example, you might press a key labeled "web browser" which currently produces "unknown". Note down this: 0x1E www # Fn+F2 web browser Repeat that for all other keys. Write the resulting list into a file. Look at /lib/udev/keymaps/ for existing key map files and make sure that you use the same structure. 4. Find out your system vendor and product: cat /sys/class/dmi/id/sys_vendor cat /sys/class/dmi/id/product_name 5. Generate a device dump with "udevadm info --export-db > /tmp/udev- db.txt". 6. Send the system vendor/product names, the key mapping from step 3, /tmp/orig-map.txt from step 2, and /tmp/udev-db.txt from step 5 to the bug tracker, so that they can be included in the next release: https://bugs.launchpad.net/udev-extras/+bugs For local testing, copy your map file to /lib/udev/keymaps/ with an appropriate name, and add an appropriate udev rule to /lib/udev/rules.d/95-keymap.rules: * If you selected an "AT keyboard", add the rule to the section after 'LABEL="keyboard_vendorcheck"'. * If you selected a "module", add the rule to the top section where the "ThinkPad Extra Buttons" are. -- [Karmic] Brightness fn keys lost functionality (multiple laptops) https://bugs.launchpad.net/bugs/406515 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
