[FreeNX-kNX] Client reports keyboard dk instead of keyboard da to Windows...

Verner Kjærsgaard vk at os-academy.dk
Tue Feb 28 21:41:50 UTC 2006


Tirsdag den 28. februar 2006 10:27 skrev Alastair Johnson:
> This patch is so simple you may as well do it by hand. Find freenx  file
> nxnode (mine's in /usr/bin) and open it for editing. Go to line 224. The
> code will look very much like that in the patch, but missing the lines
> beginning with a +. Insert the missing lines (but without the '+') and save
> the file.
>
> The patch is generated by the diff command which finds the differences
> between 2 (groups of) files. This generates output like the patch below.
> The patch command can apply that output to existing files. This saves
> passing round a whole source file or tree when only a few lines have
> changed. Both commands have comprehensive man pages, and google is your
> friend if you want to find out more. Graphical tools like kdiff3 can be
> handy too.
>
> On Monday 27 February 2006 20:17, Verner Kjærsgaard wrote:
> > Mandag den 27. februar 2006 07:33 skrev Mads Jepsen:
> > > This problem has existed for all 1.5.0 Clients I have used. I started
> > > using NX in september last year.
> > >
> > > > > - from a feedback from NoMachine support, I know that the
> > > > > nx-win-client (version 138) sends keybd=dk to the MS2003 server
> > > > > instead of keybd=da as it should.
> > >
> > > I
> > > Herbert Graeber made a fix for a problem with the german keyboard Maybe
> > > you can use it:
> > >
> > > It's simple: replace the value of the varible kbtype by the correct
> > > value
> > > before it's first use. Here is the patch:
> > >
> > > --- nxnode.org  2005-12-22 23:18:49.000000000 +0100
> > > +++ nxnode      2005-12-22 11:51:30.000000000 +0100
> > > @@ -224,6 +224,9 @@
> > >         export XAUTHORITY="$USER_FAKE_HOME/.nx/C-$sess_id/authority"
> > >         export HOME="$USER_FAKE_HOME"
> > >
> > > +       # hack: fix for german keyboard layout
> > > +       [ "$kbtype" = "pc102/de" ] && kbtype="pc105/de"
> > > +
> > >         # backwards compatibility
> > >         K=""
> > >         [ -n "$keyboard" ] && K="-keyboard $keyboard"
> > >
> > >
> > > Cheers,
> > > Herbert
> >
> > Hi Herbert and list,
> >
> > - thank you for your help!
> >
> > Unfortunately, I don't know how to use the info provided. Although I'm a
> > skilled programmer for many years (assembler, C), I have no knowledge of
> > how to apply patches and so on, as I've not worked in this area.
> >
> > As I understand it I need the source for the server part (nxnode)? And
> > then I should be able to apply the patch to the source file in question -
> > by giving some commands? Then recompile and link...
> >
> > Can someone guide me to a short how-to or some?
> >
> >
> >
> >
> > ------------------------------

Hi list and all helpers!

I thought it would be in place to say thank you to the list and the helpers in 
this matter. That be done now :-)

Alas, it didn't work.

This is what I did:

In VMware, I installed 3 machines, one MS-Windows2000 to run the client from, 
one SuSE10 to act as the NX-server and proxy to one MS-2003 Terminal Server 
(the one onto which the client from the MS2000 machines wants to connect to).
I installed FreeNX version 0.4.4 on the SUSE box.

With this setup, I was able to replicate the incorrect keyboard behavior as 
well as the correct keyboard behavior when connecting using a linux client 
etc.

I then found the nxnode file (in /usr/bin/) and corrected it according to the 
instructions given. No result. I even tried to duplicate the german patch, no 
result. I still get the stupid [ signs when I expect danish nationals 
instead...

I'm about to give up now. Only, it's cost me a lot of credibility - and 
hopefully not an entire customer. 

One bitter remark, though. I've bought quite a number of enterprise licenses 
from NoMachine. I thought it was the proper thing to do. Also, I would get 30 
days or so of installation support. Well, all I got was a recognized TR 
(Trouble Report) and no more. That's not of much use to me or my customer.
What I wanted was a fix. Or a time for when it's ready.

I got neither.

Anyhow, thank you to the list and helpers.

Best regards,
Verner Kjærsgaard
Denmark.





More information about the FreeNX-kNX mailing list