Bug 582123

Description of problem:

My bash_profile calls xmodmap to define some keyboard customisations. This works fine on startup + login. However if I suspend to ram, the customisations are reverted and I have to manually call xmodmap again. The exact same setup worked fine under F11.

Version-Release number of selected component (if applicable):
Fedora 13 beta with kernel 2.6.33.2-35.fc13.x86_64. Running KDE 4.4.2.


How reproducible:


Steps to Reproduce:
1.Create a file called .xmodmap containing customisations, for example:
 !
 ! Swap Caps_Lock and Control_L
 !
 remove Lock = Caps_Lock
 remove Control = Control_L
 keysym Control_L = Caps_Lock
 keysym Caps_Lock = Control_L
 add Lock = Caps_Lock
 add Control = Control_L

keycode 61 = exclam less
keycode 51 = asterisk greater

2.place a line "xmodmap ~/.xmodmap" in .bash_profile
3.Log out and back in or restart. Note that the customisations have taken effect.
4.Suspend to ram (in KDE use the kickoff menu) to "sleep".
5. Wake up the computer. Note that the keyboard customisations have been reverted.
  
Actual results:

Keyboard customisations do not persist across a suspend - resume cycle.
 
Expected results:

Customisations should persist across a suspend-resume cycle. They did in F11 with exact same xmodmap and .bash_profile

Additional info:

I use an FR (AZERTY) keyboard layout on a QWERTY keyboard, set using the KDE System Settings. This is preserved across a suspend.

Reporting this against the kernel since that handles the suspend/resume.