For years I have used a Snapstream Firefly mini to control Mythtv installations, configuring it as a USB keyboard device (as described
http://www.mythtv.org/wiki/Snapstream_firefly_mini) to avoid setting up a 2nd Lirc instance.
The mini as keyboard, using xmodmap to set keycodes to keyboard keys works perfectly in Slackware 12.2. Beginning with Slack 13.0 and continuing through at least 13.1, xmodmap seems to be partially broken. Though xmodmap always appears to execute properly, it can only map certain keys. With other keys, xev shows nothing is being mapped after xmodmap executes.
For example:
xmodmap -e "keycode 160 = F9"
will work fine.
xmodmap -e "keycode 164 = Escape"
maps nothing. Among the other keys that xmodmap doesn't appear to be able to map are p, m, r, and several other random keys. In each case, xmodmap appears to execute, but xev confirms that nothing was mapped.
I've tried this with clean installs of 13.0 and 13.1, and xmodmap fails as described.
If, however, I take a 13.1 Slack install, remove everything X related, and instead install the "x" and "xap" packages from Slackware 12.2 on top of this 13.1 installation, the 12.2 version of xmodmap with the Slack 12.2 version of X will function correctly in Slack 13.1
Nor does the behavior appear to be dependent on desktop environment or WM in use: xmodmap behaves as described in Blackbox, Xcfe, and fvwm (the various environments that I've tried).
Can anyone else confirm this odd behavior of current versions of X and xmodmap? I was unable to find any solid references for odd xmodmap/X behavior on the web.