[prev in list] [next in list] [prev in thread] [next in thread] 

List:       freenx-knx
Subject:    [FreeNX-kNX] Keyboard mapping problem
From:       FabianFranz () gmx ! de (Fabian Franz)
Date:       2005-03-02 0:19:10
Message-ID: 200503020119.12671.FabianFranz () gmx ! de
[Download RAW message or body]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Am Dienstag, 1. M?rz 2005 11:09 schrieb Roderick Johnstone:
> Hi

Hi Roderick,

>> I can fix the keyboard mapping problems by hand if I do the following in
> a terminal window in the NX session:
>
> linux> setxkbmap -model pc105 -layout gb
> Couldn't interpret _XKB_RULES_NAMES property
> Use defaults: rules - 'xorg' model - 'pc101' layout - 'us'
> free(): invalid pointer 0xbfe4f2e8!

Thats interesting. thank you.

>
> Note, this produces an error, but does actually fix the mapping so my
> pipe and hash keys etc are appropriate for the GB layout.
>
> If I re-issue this command the error is not reported again.
>
> Can anyone with a non-us keyboard confirm this behaviour?

Yes, but I still have my preferred keyboard from KDE.

>
> Could someone suggest how I can trace the problem - I'm not even sure if
> this is a client-side or server-side issue, or something peculiar to my
> own setup here.

Its a server-side issue, but I think this is fixed in CVS as we are now 
setting kbtype correctly.

cu

Fabian
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFCJQaAI0lSH7CXz7MRArThAJ9QG6ERa05hbCVGAo/Ua7YW+0zaTwCeN0eK
VJncPstdB969IiCw/GOn7Dk=
=Fjf8
-----END PGP SIGNATURE-----



[prev in list] [next in list] [prev in thread] [next in thread]