The problem appeared when xorg started to use evdev rules (used by evdev<div>driver) by default.<div>But evdev and xf86 rules (used by kbd driver) aren't compatible. So the client</div><div>sends an evdev keycode but the xfree86 server don't understand.</div>
<div>On nxagent 3.3.0-X (not sure about the version) they created a workaround that</div><div>converts the evdev keycode into a xfree86 keycode. But this workaround is used</div><div>when the parameter "client=linux" is passed to the nxagent and the xorg on the </div>
<div>client is using evdev rule or using xfree86 rule and evdev layout.</div><div><br></div><div>FreeNX from svn doesn't passes the client parameter to nxagent so the workaround is</div><div>never used. Take a look the patch Mario Becroft sent, I am pretty sure I made it.</div>
<div>If remember correctly the workaround for this problem on the freenx side is the</div><div>"${client:+client=$client,}" part.</div><div><br></div><div>For my abnt2 keyboard this workaround don't work for every key. But the not</div>
<div>working ones are not essential.</div><div><br></div><div>I hope this helps</div><div>Regars</div><div>Shima</div><div><br><div class="gmail_quote">On Tue, Jun 16, 2009 at 4:35 AM, Aidan Marks <span dir="ltr"><<a href="mailto:aidan@cisco.com">aidan@cisco.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">It's been broken for some time on gentoo.<br>
<br>
server -<br>
<br>
net-misc/nxserver-freenx-0.7.3_p104-r1<br>
net-misc/nx-3.3.0-r4<br>
x11-base/xorg-server-1.5.3-r6<br>
<br>
client -<br>
<br>
net-misc/nxclient-3.3.0.6<br>
<br>
setxkbdmap doesn't help.<br>
<br>
sigh.<br>
<br>
I'd been hoping it would just get fixed - it is a regression as it<br>
worked for a long time. can't remember which update broke it. :(<br>
<br>
Il 16/06/09 17:22, Florian Schmidt ha scritto:<br>
<div><div></div><div class="h5">> Hi,<br>
><br>
> If I imagine right also nx-3.3.0-something was needed to fix the keymaps for<br>
> Client Systems with Xorg >1.5<br>
> At least this was necessary at our installations.<br>
><br>
> Cheers,<br>
> Florian<br>
><br>
> 2009/6/16, Mario Becroft <<a href="mailto:mb@gem.win.co.nz">mb@gem.win.co.nz</a>>:<br>
>> Neal Becker <<a href="mailto:ndbecker2@gmail.com">ndbecker2@gmail.com</a>> writes:<br>
>><br>
>>> I'm using<br>
>>> nxclient-3.3.0-6.x86_64<br>
>>> freenx-server-0.7.3-11.fc10.x86_64<br>
>>><br>
>>> Keyboard mapping is not working. The keys <up>, <down>, <right>, <left><br>
>> are<br>
>>> mapped to I-don't-know-what. The keys <kp-up>, etc work OK. Really<br>
>>> annoying in emacs. Any ideas? (Client side is kde, if that matters).<br>
>><br>
>> Sounds slightly similar to something that was reported and patched a<br>
>> while ago; does your freenx installation include the following patch?<br>
>><br>
>><br>
>><br>
>> --<br>
>> Mario Becroft <<a href="mailto:mb@gem.win.co.nz">mb@gem.win.co.nz</a>><br>
>><br>
>> ________________________________________________________________<br>
>> Were you helped on this list with your FreeNX problem?<br>
>> Then please write up the solution in the FreeNX Wiki/FAQ:<br>
>><br>
>> <a href="http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ" target="_blank">http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ</a><br>
>><br>
>> Don't forget to check the NX Knowledge Base:<br>
>> <a href="http://www.nomachine.com/kb/" target="_blank">http://www.nomachine.com/kb/</a><br>
>><br>
>> ________________________________________________________________<br>
>> FreeNX-kNX mailing list --- <a href="mailto:FreeNX-kNX@kde.org">FreeNX-kNX@kde.org</a><br>
>> <a href="https://mail.kde.org/mailman/listinfo/freenx-knx" target="_blank">https://mail.kde.org/mailman/listinfo/freenx-knx</a><br>
>> ________________________________________________________________<br>
>><br>
>><br>
><br>
><br>
</div></div>> ------------------------------------------------------------------------<br>
<div><div></div><div class="h5">><br>
> ________________________________________________________________<br>
> Were you helped on this list with your FreeNX problem?<br>
> Then please write up the solution in the FreeNX Wiki/FAQ:<br>
><br>
> <a href="http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ" target="_blank">http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ</a><br>
><br>
> Don't forget to check the NX Knowledge Base:<br>
> <a href="http://www.nomachine.com/kb/" target="_blank">http://www.nomachine.com/kb/</a><br>
><br>
> ________________________________________________________________<br>
> FreeNX-kNX mailing list --- <a href="mailto:FreeNX-kNX@kde.org">FreeNX-kNX@kde.org</a><br>
> <a href="https://mail.kde.org/mailman/listinfo/freenx-knx" target="_blank">https://mail.kde.org/mailman/listinfo/freenx-knx</a><br>
> ________________________________________________________________<br>
________________________________________________________________<br>
Were you helped on this list with your FreeNX problem?<br>
Then please write up the solution in the FreeNX Wiki/FAQ:<br>
<br>
<a href="http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ" target="_blank">http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ</a><br>
<br>
Don't forget to check the NX Knowledge Base:<br>
<a href="http://www.nomachine.com/kb/" target="_blank">http://www.nomachine.com/kb/</a><br>
<br>
________________________________________________________________<br>
FreeNX-kNX mailing list --- <a href="mailto:FreeNX-kNX@kde.org">FreeNX-kNX@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/freenx-knx" target="_blank">https://mail.kde.org/mailman/listinfo/freenx-knx</a><br>
________________________________________________________________<br>
</div></div></blockquote></div><br></div></div>