Comment 1 for bug 251247

I also experience this bug. However, renaming 80ubuntu-xmodmap to 999ubuntu-xmodmap does not remedy the problem for me. Is there some other process that is stomping on the modmap later, something not in /etc/X11/Xsession.d?

I'm running up-to-date hardy