[FreeNX-kNX] keymap broken again

[jhonyl]

Hi,

I don't know specific for ArchLinux what has happened , but in general 
it can all be fixed. I have fixed it for Mac OSX that had problems with 
some keys, search my posts. In general you can run a script with 
xmodmap to change a few or all keys of the layout on startup. If your 
client give wrong options you can fix it with the nxacl script. You 
could also edit the xkb layout files (but back them up, since they are 
not as innocent as they may look) instead of xmodmap.



-----Original Message-----
From: Andreas Radke <a.radke at arcor.de>
To: FreeNX-kNX at kde.org
Sent: Fri, 24 Apr 2009 9:08 pm
Subject: [FreeNX-kNX] keymap broken again

After recent Xorg updates and NoMachine updates on ArchLinux the
keyboard layout is broken again: no | symbol, no {} and cursor up/down
and all that we had some months back.

So far I could solve this in my gnome session with opening the
appearance dialog twice and then the gtk theme and fonts got applied
properly and also the evdev keyboard magically worked then. Now this
twice dialog opening makes the NX session crash and close completely.
Running the dialog from command line and a Xfce session where the
keyboard layout also is broken I get this:

[andyrtr at workstation64 ~]$ xfce4-keyboard-settings
Xlib:  extension "Generic Event Extension" missing on display ":1001.0".
Xlib:  extension "Generic Event Extension" missing on display ":1001.0".
Xlib:  extension "Generic Event Extension" missing on display ":1001.0".
Xlib:  extension "Generic Event Extension" missing on display ":1001.0".
Xlib:  extension "Generic Event Extension" missing on display ":1001.0".
The program 'xfce4-keyboard-settings' received an X Window System error.
This probably reflects a bug in the program.
The error was 'XI_BadClass (invalid Class parameter)'.
  (Details: serial 169 error_code 133 request_code 131 minor_code 6)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error()
function.) [andyrtr at workstation64 ~]$



Ad you may know ArchLinux is running a rolling release and has allmost
every pkg in its most recent upstream version.

Any idea what made it break again? Any fix known? Do you need more
informations?

-AndyRTR
________________________________________________________________
     Were you helped on this list with your FreeNX problem?
    Then please write up the solution in the FreeNX Wiki/FAQ:

http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ

         Don't forget to check the NX Knowledge Base:
                 http://www.nomachine.com/kb/

________________________________________________________________
       FreeNX-kNX mailing list --- FreeNX-kNX at kde.org
      https://mail.kde.org/mailman/listinfo/freenx-knx
________________________________________________________________