Re: Fw: incorrect keyboard mapping on MacOS Lion

[Chris <ch...@cc...>]

> From: Sergey Stepanov <sst...@an...>
> To: ope...@li...; ch...@cc... 
> Cc: "Pothineni, Sudhirbabu" <spo...@an...> 
> Sent: Friday, 16 August 2013, 0:12
> Subject: Re: incorrect keyboard mapping on MacOS Lion
> 
> Hi Chris,
> thanks for your response.

[SNIP]

> Perhaps it depends on multiple parameters, but in our case
> (CentOS-6.4 and NX-3.5 on the server side and OpenNX-0.16.0.725.dmg
> on the MacOS side) the keyboard was consistently OK in KDE, but
> we have many complains with Gnome. Unfortunately, our link to
> users is weak: they come and go all the time. Therefore I cannot
> state whether the keyboard in Gnome sessions was messed for all
> users on only for some. All of our clients are in US; so we expect
> that they have the US keyboard layout.

It could also be due to differences between FreeNX and Nomachine's
NX


[SNIP]
 
> The recipe was from the lead NOMACHINE developer. I believe he
> also communicated it to Fritz. Also, he suggested to set the
> keyboard to "query" on Mac only. I cannot verify it by myself
> because I do not even have a Mac. Here are the strings they were
> using:

It might just set the default, hence I get "us" not "gb"

it doesn't "query" else I would get  "evdev" also . . 


[SNIP]

 
> According to their explanations "keyboard=pc105/us" messed the
> keys while keyboard=query did not.
> 
> Could you please explain how to use nxacl? We would like to try it.


nxacl is only FreeNX.

Nomachine's NX has a large number of script options
eg

        UserScriptBeforeSessionStart = ""
set in
         /usr/NX/etc/server.cfg

but I don't know if you can modify parameters.

 
> We have to use commercial NX over FreeNX because it is easier for our
> users: most of them would have problems with importing the shared keys.

[SNIP]
 
> I did, but my understanding is that there is no full solution yet.
> I think the fact that the NX developers agreed to plugin and discuss
> the issue gives a great chance it may be finally resolved.
> 
> Thanks,
> 
> Sergey

Lets see if Anne can get the parameter change working  . . .