[FreeNX-kNX] problems with keybinding arrows to print screen on fedora 10

[Marcelo Boveto Shima]

Did you tried this 2 steps from comment 12?
    * Change the keyboard model to evdev:
       - GNOME: System -> Preferences -> Keyboard -> Keyboard model ->
Generic -> "Evdev-managed keyboard"
    * Restart the window manager that keeps the keyboard hotkeys:
       - GNOME: Go to a terminal and execute $ killall metacity.

On Tue, Jan 13, 2009 at 1:53 AM, Ted T. Logan <tedtheologian at gmail.com>wrote:

>  None of the solutions there work.  There are no keycodes that are
> generated for those keys when using xev.  What can I do?
>
>
>
> Marcelo Boveto Shima wrote:
>
> There is a discussion about this bug on
> https://bugs.launchpad.net/bugs/289918
>
> On Tue, Dec 30, 2008 at 10:53 PM, jhonyl <jhonyl at netscape.net> wrote:
>
>> you could use xev to find the keycodes of that keys and then use
>> xmodmap to map them. 'xmodmap -pke' will print your current mapping,
>> and also if you have a .xmodmaprc file in your home dir might be auto
>> run, and if not , then you could probably add a line that will run it
>> in one of the other rc files.
>>
>> There are more options, like xkeycaps program, and setting the xkb
>> mapping files.
>>
>>
>> -----Original Message-----
>> From: Ted T. Logan <tedtheologian at gmail.com>
>> To: freenx-knx at kde.org
>> Sent: Tue, 30 Dec 2008 3:15 am
>> Subject: [FreeNX-kNX] problems with keybinding arrows to print screen
>> on fedora 10
>>
>> I am having pretty much this problem:
>> http://www.nomachine.com/tr/view.php?id=TR11F02131
>>
>>
>> Two f10 machines.  Arrow up does print screen, and the other arrows
>> seem
>> to do nothing.
>>
>> I tried the xorg.conf solution mentioned on there to no avail.
>>
>> What can I do?  I have the latest client, 3.3.0 and freenx.
>>
>>
>>
>> nx-3.2.0-31.fc10.i386
>> freenx-server-0.7.3-11.fc10.i386
>> nxclient-3.3.0-3.i386
>>
>> ________________________________________________________________
>>     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
>> ________________________________________________________________
>>
>>
>> ________________________________________________________________
>>     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
>> ________________________________________________________________
>>
>
> ------------------------------
>
> ________________________________________________________________
>      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
> ________________________________________________________________
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/freenx-knx/attachments/20090113/53ddbe10/attachment.html>