Op vrijdag 2 januari 2004 21:13, schreef Jan Elders:
--- exec 2>/tmp/debug set -x ---
Now check the file /tmp/debug after execution of X
All right, did that (put just in front of xmodmap statement). The following is shown in /tmp/debug : + xmodmap -e 'keycode 96 = EuroSign' + logger '.xinitrc called for user me' + exec /usr/X11R6/bin/kde xset: bad font path element (#113), possible causes are: Directory does not exist or has wrong permissions Directory missing fonts.dir Incorrect font server address or syntax xset: bad font path element (#113), possible causes are: Directory does not exist or has wrong permissions Directory missing fonts.dir Incorrect font server address or syntax kbuildsycoca running... ....... and some more stuff ........
What does this tell us ??? I believe the xset errormessage relates to the exec /usr/X11R6/bin/kde command, and has nothing to do with the xmodmap command. Right ? Anyway, I have no clue what to do next.
Me neither ..., but some hints for the above error: You can put the same debugging trick in /usr/X11R6/bin/kde. It will give you the location that goes wrong in /usr/X11R6/bin/kde which is btw a link to /opt/kde3/bin/startkde. I don't remember what you already did; Did you try to use the .Xmodmap file already, the one in your $HOME and the system one. Does something change grep xmodmap .* .xinitrc.template: test -r $XLIBDIR/Xmodmap && xmodmap $XLIBDIR/Xmodmap .xinitrc.template: test -r $HOME/.Xmodmap && xmodmap $HOME/.Xmodmap XLIBDIR=/usr/X11R6/lib/X11/Xmodmap I tried the following, from a xterm, konsole, etc. - run kword - press F12 => result nothing - xmodmap -e 'keycode 96 = EuroSign' - run kword - press F12 => there she is. Next thing try the debugging thing in /usr/bin/X11/startx and see what files are executed.... -- Richard Bos Without a home the journey is endless