Arch Linux

broch

Banned

From: L.A. California

Registered: 2006-11-13

Posts: 975

xmodmap broken? [resolved]

/usr/bin/xmodmap $HOME/.Xmodmap
does not work anymore irrelevant of a way executed (command line, bashrc, $HOME/.kde/Autostart)

when issuing xev to trace keystrokes I see
KeyPress event, serial 31, synthetic NO, window 0x2c00001,
    root 0x1a5, subw 0x0, time 1878106, (234,1), root:(238,25),
    state 0x0, keycode 160 (keysym 0x1008ff12, XF86AudioMute), same_screen YES,
   XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False

I assume that it should be

XLookupString gives 1 bytes:
XmbLookupString gives 1 bytes:

this (xmodmap) worked well.

Is there any resolution to this problem?
thanks

Last edited by broch (2007-07-01 02:38:18)

emmybear

Member

Registered: 2007-04-20

Posts: 38

Re: xmodmap broken? [resolved]

It says 0 for both of those for me as well, and works just fine. Are the keybinds associated with the keys not working or something?

broch

Banned

From: L.A. California

Registered: 2006-11-13

Posts: 975

Re: xmodmap broken? [resolved]

keybindings for lower volume, mute and raise volume do not work anymore (worked)
these are mapped through xmodmap and stopped to work recently

keys mapped through xbindkeys still work

broch

Banned

From: L.A. California

Registered: 2006-11-13

Posts: 975

Re: xmodmap broken? [resolved]

it seems to be even worse:
starting xbindkeys makes my keyboard non-responsive

not sure about the cause, as this worked pretty well

broch

Banned

From: L.A. California

Registered: 2006-11-13

Posts: 975

Re: xmodmap broken? [resolved]

1) seems that xmodmap does not work anymore irrelevant of the way it was invoked
2) seems that adding for example
"amarok --play"
XF86AudioPlay
to .xbindkeysrc
kills keyboard in general

this must be replaced by
"amarok --play"
m:0x0 + c:162

this works

finally adding XF86AudioRaiseVolume, XF86AudioLowerVolume, XF86AudioMute directly to the KMix global shortcuts allow to set volume on kmix. This is not optimal as kMix must run first but at least it works.

so whatever changes were made it affected at least keyboard on HP dv500z. It may not affect different keyboard types though. I have seen similar problems on ubuntu forums. It looks like issues with kde.