Comment 10 for bug 377175

Bryce, there may be multiple bugs here, but the most important one (IMO) is that you can't remap this key's behavior in X. Agreed that identifying the volume up key as XF86ScreenSaver could be a product of keyboard driver strangeness. But it should always be possible to remap a key with xmodmap and have it perform a new function. However, remapping this keycode to a new keysym, while it appears to work via xev, does not actually stop the screensaver from running. Someone, somewhere in Xorg or Gnome has hard-coded this behavior to run the screensaver despite the new key mapping.