Comment 51 for bug 1224732

As an update, I found this post :-

http://ubuntuforums.org/showthread.php?t=2217890
and bug report https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1302885

Stating "
    The problem is that an incorrect string is set in dconf key: (Example)

    Original (working) value:
    ~$ gsettings get org.gnome.settings-daemon.plugins.media-keys volume-up
    'XF86AudioRaiseVolume'

    After running "unity-control-center keyboard", and setting the shortcut for volume-up key:
    ~$ gsettings get org.gnome.settings-daemon.plugins.media-keys volume-up
    'AudioRaiseVolume'

When I checked with dconf, my media keys were indeed screwed up as in this post. I added the XF86 prefix and they now work.

However, this is only one small part of the bug. (in fact a different bug)
If I try to capture keyboard events with xev, I am not getting any keypresses for keys I have assigned in the control centre gui.

For example, Brightness Up and Down keys - instead of triggering "keypress" and "keyrelease" events, instead trigger "Mapping notify", "focusout", "focusout", "focusin" and "keymapnotify" events.

I have also found that I can get the unresponsive keys to trigger the correct events in xev by pressing them with another key, e.g. press eject and F12, and I will get keypress events for both (and the shortcut assigned to a key sometimes will execute too)

In desperation I have even installed xbindkeys and configured it, but it seems to be too far up the keyboard handling chain to receive the keys before something else has stolen them and done nothing with them.