Re: Workaround for foreign keyboard problem to be entered in FAQ section 4.1.6

erspective) symbolic links named e.g. "xkb" are changed into Windows shortcuts and renamed "xkb.lnk" during this process. Subsequently, X doesn't start properly and you can e.g. not use the setxkbmap command. -- View this message in context: http://www.nabble.co

Re: Workaround for foreign keyboard problem to be entered in FAQ section 4.1.6

[EMAIL PROTECTED] wrote: Hi all: I recently hit the foreign keyboard problem described in section 4.1.6 of the Cygwin/X FAQ. That is, I started with: $ setxkbmap.exe de -model pc105 Couldn't interpret _XKB_RULES_NAMES property [...] and then I tried what the FAQ said, but I got the f

Workaround for foreign keyboard problem to be entered in FAQ section 4.1.6

Hi all: I recently hit the foreign keyboard problem described in section 4.1.6 of the Cygwin/X FAQ. That is, I started with: $ setxkbmap.exe de -model pc105 Couldn't interpret _XKB_RULES_NAMES property [...] and then I tried what the FAQ said, but I got the following error: $ xkbcomp