[X2Go-Dev] Fwd: [Bug 1033876] New: x2go session does not set correct keyboard type

Orion Poplawski orion at cora.nwra.com
Sun Nov 24 03:56:53 CET 2013


Could anyone see what it going wrong here?  Thanks.


-------- Original Message --------
Subject: [Bug 1033876] New: x2go session does not set correct keyboard type
Date: Sat, 23 Nov 2013 23:20:58 +0000
From: bugzilla at redhat.com
To: orion at cora.nwra.com

https://bugzilla.redhat.com/show_bug.cgi?id=1033876

             Bug ID: 1033876
            Summary: x2go session does not set correct keyboard type
            Product: Fedora
            Version: 20
          Component: x2goserver
           Severity: medium
           Assignee: orion at cora.nwra.com
           Reporter: rmj at ast.cam.ac.uk
         QA Contact: extras-qa at fedoraproject.org
                 CC: orion at cora.nwra.com



Description of problem:
x2go KDE session does not have correct keyboard type

Version-Release number of selected component (if applicable):
This is seen on Fedora 20 beta
x2goserver-4.0.1.6-5.fc20.x86_64

x2goclient 4.0.0.3 on Windows XP

How reproducible:
Every time.

Steps to Reproduce:
1. From a Windows XP laptop with UK keyboard, configure an x2go session with
Session preferences / settings /
keyboard layout: gb
keyboard model: pc105/gb
2. Start x2go session to Fedora 20 beta
3. Type on the keyboard

Actual results:
Keyboard is incorrectly mapped.
eg Shift 3 gives # instead of £.
| key gives >
~ key gives |
# key gives \
" key gives @
@ key gives "
etc

Seen in konsole, firefox, gedit etc.

Expected results:
Keys give the symbols printed on them

Additional info:
Correct keyboard mapping can be recovered by giving the command:
setxkbmap gb

The file: 
/tmp/.x2go-testuser/session-C-testuser-51-1385245333_stDKDE_dp32.log

contains the message:
nxagentXkbGetRules: WARNING! Failed to stat file
[/usr/lib64/nx/X11/xkb/rules/xorg]: Unknown error -1.
keyboard file created

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.





More information about the x2go-dev mailing list