Comment 18 for bug 1072120

Hi all,

I know this is thread is way old but since I have the same problem I believe it's worth sharing.

I wasn't able to use the startup command workaround out of the box, and after some digging the cause is that it runs too early, we need to wait for some seconds to run.

This is how it worked for me: I have created a bash script that contains these lines, and call it from the startup applications...

    sleep 3
    xmodmap ~/.Xmodmap

As always YMMV according to your machine speed, and you may need to "sleep" a little longer.

Hope it helps!
  eridal