On Saturday 28 February 2004 11:47, David Decotigny wrote:
> Since I don't know who "[EMAIL PROTECTED]" will reach, I
> repost a preliminary workaround to the right (?) addresses.

I didn't get it per E-Mail, thanks for the resend.


> See the attachment. By doing an strace on X, I noticed that X looks for
> my symbol map in symbols/pc/fr_new instead of
> symbols/macintosh/fr_new... Since I have a lot of problems with my dsl
> connection, I cannot check the XF86 docs to see any changes in the
> configuration statements, but it seems to be something as stupid as this.
>
> BTW, I found a working workaround for my keyboard configuration : Once X
> is launched, in a terminal, simply issue "setxkbmap fr_new".

*dancing* That was the solution, at least it leads me to the solution / 
workaround:

[EMAIL PROTECTED]:~$ setxkbmap fr_new
Error loading new keyboard description
[EMAIL PROTECTED]:~$ setxkbmap de_new
Error loading new keyboard description
[EMAIL PROTECTED]:~$ man setxkbmap
[EMAIL PROTECTED]:~$ setxkbmap -print
xkb_keymap {
        xkb_keycodes  { include "xfree86+aliases(qwertz)"       };
        xkb_types     { include "complete"      };
        xkb_compat    { include "complete"      };
        xkb_symbols   { include 
"pc/pc(pc105)+pc/de(nodeadkeys)+ctrl(nocaps)"   };
        xkb_geometry  { include "pc(pc105)"     };
};
[EMAIL PROTECTED]:~$ setxkbmap de
[EMAIL PROTECTED]:~$ ~ (with space after)
[EMAIL PROTECTED]:~$ setxkbmap "de(nodeadkeys)"
[EMAIL PROTECTED]:~$ ~ *g*

Many thanks to all who have helped me, this workaround is much better than 
"copy&paste" or writing out the path! Now I hope that the real bug will be 
found, if I can do anything for it just ask!

-- 
Beste Gruesse / Best regards Markus Meissner


Reply via email to