Brighten key combo inserts ±

[Kd Jm]

The bug is present in all editors.
Pressing Fn+RightArrow to brighten my monitor also includes the symbol ±

This on my Acer Aspire One, running UNR 9.04. My keyboard model is "Generic 105-key (Intl) PC", using Belgium layout.

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/nautilus
Package: nautilus 1:2.26.2-0ubuntu2
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: nautilus
Tags: ubuntu-unr
Uname: Linux 2.6.28-11-generic i686

[Monkey (monkey-libre)]

I´ve assigned this bug to the udev package. Also I´ve changed the status to Incomplete because the bug need more information. Don´t worry, I´ve put a link for complete it and I´ve removed the needs-reassignment tag. Thank You for making Ubuntu better.
https://wiki.ubuntu.com/Hotkeys/Troubleshooting

[Martin Pitt (pitti)]

Thank you for taking the time to report this bug and helping to make Ubuntu better.

Please exercise the steps at https://wiki.ubuntu.com/Hotkeys/Troubleshooting to determine at which level your hotkey problems occur, and attach the collected information. Thanks!

[Dries (dries-moors)]

Thank you for taking this report serious. Apparently not many people are affected by this, although it is very annoying for me...

a) I ran
  me@here:~§ killall gnome-settings-daemon gnome-power-manager
  me@here:~§ xev | sed -n 's/^.*state \([0-9].*\), keycode *\([0-9]\+\) *\(.*\), .*$/keycode \2 = \3, state = \1/p'
b) and next pressed <Fn>+<Arrow right> once. This resulted in both a brightening of the screen and the logging of these events:
  keycode 126 = (keysym 0xb1, plusminus), state = 0x0
  keycode 126 = (keysym 0xb1, plusminus), state = 0x0
c) Following the guidelines of https://wiki.ubuntu.com/Hotkeys/Troubleshooting, I tried to collect:
  udevadm info --export-db > udev-db.txt
  dmesg > dmesg.log
  sudo lsinput > lsinput.log
  xkbcomp -xkb :0 - > xkbcomp.txt
  setxkbmap -print > xkbmap.txt
d) but not all commands succeeded:
  lsinput.log could not be created, I got the error "sudo: lsinput: command not found". Running "sudo apt-get install lsinput" yielded "E: Couldn't find package lsinput". I don't know what to do next with this.
  Running xkbcompg gave this warning: "Warning: Could not load keyboard geometry for :0
                  BadAlloc (insufficient resources for operation)
                  Resulting keymap file will not describe geometry"

I hope this helps somewhat.

[Martin Pitt (pitti)]

Dries, it seems the problem is in the udev keymaps, or rather, the lack of one for your particular model.

Seems you gave up too early with the wiki page :-)

Can you please follow /usr/share/doc/udev/README.keymap.txt.gz, start wih the "Fixing broken keys" section. In particular, I need th e current scan code -> keycode mapping for the wrong key. Thanks!

[Dries (dries-moors)]

Ok... the wiki text didn't give the impression it was directed to me, but so is a lot of this magic . Here goes:

- Executing "/lib/udev/findkeyboards produced "AT keyboard: input/event5"
- I attached the output of "/lib/udev/keymap input/eventX" (orig-map.txt)
- I then ran "/lib/udev/keymap -i input/event5":
  - Pressing "Brighten screen (Fn+right)" gave "scan code: 0xCE key code: kpplusminus".
    Looking in the file "/usr/include/linux/input.h", I suspect this should correlate with KEY_BRIGHTNESSUP
  - Pressing "Brighten screen (Fn+left)" gave "scan code: 0xEF key code: macro".
    Although the behavior is correct, it does not look like KEY_BRIGHTNESSDOWN, so I don't know what to think of that.
- The "sys_vendor" is "Gateway", the "product_name" is "AOA150"
- I attached the output of "udevadm info --export-db" (udev-db.txt)

[Martin Pitt (pitti)]

Brilliant, thanks! Turns out that this was already fixed recently in lucid, in bug 518496. By the looks of your udev-db.txt you are currently using Ubuntu 9.10, so upgrading to Lucid will fix that for you. Thanks!