ha! got something if the udev keymap is disabled, the keys work as expected without problems. they show up in acpi_listen and dmesg output as shown above. and when i kill gnome-power-manager, they also show in xev output (using the command from Hotkeys/Troubleshooting) - twice: keycode 233 = (keysym 0x1008ff02, XF86MonBrightnessUp), state = 0x0 keycode 233 = (keysym 0x1008ff02, XF86MonBrightnessUp), state = 0x0 both on keydown, nothing on keyup.
if the udev keymap is enabled, the keys don't show up in dmesg output. they do still show up in acpi_listen. also in xev - but now four times! keycode 232 = (keysym 0x1008ff03, XF86MonBrightnessDown), state = 0x0 keycode 232 = (keysym 0x1008ff03, XF86MonBrightnessDown), state = 0x0 keycode 232 = (keysym 0x1008ff03, XF86MonBrightnessDown), state = 0x0 keycode 232 = (keysym 0x1008ff03, XF86MonBrightnessDown), state = 0x0 when we hit lowest possible brightness, something interesting happens: single press of the BrightnessDown key generates this: keycode 232 = (keysym 0x1008ff03, XF86MonBrightnessDown), state = 0x0 keycode 232 = (keysym 0x1008ff03, XF86MonBrightnessDown), state = 0x0 keycode 233 = (keysym 0x1008ff02, XF86MonBrightnessUp), state = 0x0 keycode 233 = (keysym 0x1008ff02, XF86MonBrightnessUp), state = 0x0 or, in rare cases, this: keycode 233 = (keysym 0x1008ff02, XF86MonBrightnessUp), state = 0x0 keycode 232 = (keysym 0x1008ff03, XF86MonBrightnessDown), state = 0x0 keycode 232 = (keysym 0x1008ff03, XF86MonBrightnessDown), state = 0x0 keycode 233 = (keysym 0x1008ff02, XF86MonBrightnessUp), state = 0x0 this doesn't seem to depend on whether acpid is running: matej...@limetka:/etc/acpi$ ps ax | grep acpi 166 ? S< 0:00 [kacpid] 167 ? S< 0:00 [kacpi_notify] 168 ? S< 0:00 [kacpi_hotplug] 4886 pts/1 R+ 0:00 grep acpi (i also killed hald-addon-acpi, just to be on the safe side) brightness levels still go by one, with and without gnome-power-manager so now i'm thoroughly confused. oh, and when i change brightness on system boot, it works, but types "^...@^@" into the console. once the system is up, this doesn't happen the troubleshooting page says that "if there are too many keypress events then you need to determine where they are being duplicated." but doesn't elaborate much on that. so what now? -- hotkey-setup support for MSI PR200 https://bugs.launchpad.net/bugs/178860 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
