F18 - xmodmap settings unset after suspend/resume

[mayostard]

I recently upgraded by thinkpad X220 from F17 using fedup --network, and since then my xmodmap settings are undone every time I suspend/resume the laptop.

Something similar was reported previously:

https://bugzilla.redhat.com/show_bug.cgi?id=692760

however, I've never noticed this before.

For now I'm just leaving a terminal window open and manually re-running xmodmap after each resume, there's got to be a better way, right?

thanks,

[natros]

The same here, but with a desktop.

[virtualeyes]

See this thread to solve your xmodmap binding woes in Gnome 3:
https://bbs.archlinux.org/viewtopic.php?id=151926

Was driving me insane

[mayostard]

That's an absurd workaround, but thanks for the pointer.

[virtualeyes]

Well, sure, but if it saves manually doing the same task over and over and over and over and over...

In other words, I'll take a workaround over constant annoyance.

[Vicente Niente]

Hi everyone. I had the same problem with xmodmap. This improve a little bit the solution of Archlinux fellas:
1. You have your settings in ~/.Xmodmap file.
2. You write:" /usr/bin/xmodmap ~/.Xmodmap " in your Startup Application Preferences (in my case: xfce4-session-settings).
3. You go where your keyboard settings (in my case xfce4-keyboard-settings). Click on "Layout" tab, uncheck "Use system defaults" and close. That's all and work for me.