Gnome3: Default keymapping incorrect

Question

I've been using arch with Awesome and everything was working fine. I installed gnome3 and started using that.
after Gnome 3 boots up this is the output of
xmodmap -pke
http://pastebin.com/VChFQXVT
keycode 110 = Home NoSymbol Home
keycode 111 = Up NoSymbol Up
keycode 112 = Prior NoSymbol Prior
keycode 113 = XF86AudioMute NoSymbol XF86AudioMute
keycode 114 = XF86AudioLowerVolume NoSymbol XF86AudioLowerVolume
keycode 115 = XF86AudioRaiseVolume NoSymbol XF86AudioRaiseVolume
keycode 116 = Down NoSymbol Down
keycode 117 = Next NoSymbol Next
keycode 118 = Insert NoSymbol Insert
keycode 119 = Delete NoSymbol Delete
keycode 120 =
keycode 121 = XF86AudioMute NoSymbol XF86AudioMute
keycode 122 = XF86AudioLowerVolume NoSymbol XF86AudioLowerVolume
keycode 123 = XF86AudioRaiseVolume NoSymbol XF86AudioRaiseVolume
keycode 124 = XF86PowerOff NoSymbol XF86PowerOff
keycode 125 = KP_Equal NoSymbol KP_Equal
as you can see keycode 113,114,115 are the same as 121,122 and 123
113-115 are suppose to be the right and left arrow keys and the end key on my laptop.
i can change this by running xmodmap but i found that after I resume my computer the change has reverted.
I would like to fix this at the root of the problem, where these values are being setup initially, but if you know a way i can put in xmodmap with the new key mappings so even after a resume that would be ok as well.
Any ideas what is causing this?
EDIT::
before running xmodmap to change the keymaps, I ran xev to try and figure out what the heck is going on.
this is the output of xev for a down keypress and a right keypress
KeyPress event, serial 29, synthetic NO, window 0x2400001,
root 0x15a, subw 0x2400002, time 12632041, (20,39), root:(764,369),
state 0x0, keycode 116 (keysym 0xff54, Down), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
KeyRelease event, serial 32, synthetic NO, window 0x2400001,
root 0x15a, subw 0x2400002, time 12632163, (20,39), root:(764,369),
state 0x0, keycode 116 (keysym 0xff54, Down), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
FocusOut event, serial 32, synthetic NO, window 0x2400001,
mode NotifyGrab, detail NotifyAncestor
FocusIn event, serial 32, synthetic NO, window 0x2400001,
mode NotifyUngrab, detail NotifyAncestor
KeymapNotify event, serial 32, synthetic NO, window 0x0,
keys: 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
maybe someone understands this a bit better than i do.
thanks.
Last edited by ButterQuark (2011-08-29 23:28:29)

Answer 1

Hi Jonas,
The edit  Key mapping information gets updated based on the mapping of the Remote key in Import manager.
Based upon which key for a given remote system you are mapping for a record the default key gets set in the Data manager.
The mapping can be done in the import manger but setting of the default key is limited only in the mdm Data manager.
You can only perform teh appropiate mapping of the required keys from your remote system as the Remote key for your records and view the same in Edit key mapping.
As this requires business intervention as mentioned in the above post i do not think this is allowed at the import stage.
Hope It Helped
Thanks & Regards
Simona Pinto