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@redhat.com To: orion@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@cora.nwra.com
Reporter: rmj@ast.cam.ac.uk
QA Contact: extras-qa@fedoraproject.org
CC: orion@cora.nwra.comDescription 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:
- From a Windows XP laptop with UK keyboard, configure an x2go session with Session preferences / settings / keyboard layout: gb keyboard model: pc105/gb
- Start x2go session to Fedora 20 beta
- 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.
Hi Orion,
On So 24 Nov 2013 03:56:53 CET, Orion Poplawski wrote:
The file:
/tmp/.x2go-testuser/session-C-testuser-51-1385245333_stDKDE_dp32.logcontains the message: nxagentXkbGetRules: WARNING! Failed to stat file [/usr/lib64/nx/X11/xkb/rules/xorg]: Unknown error -1. keyboard file created
maybe we should link /usr/lib64/nx/X11/xkb/rules/xfree86 to
/usr/lib64/nx/X11/xkb/rules/xorg?
???
Mike
--
DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148
GnuPG Key ID 0x25771B31 mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
On 11/25/2013 10:18 AM, Mike Gabriel wrote:
Hi Orion,
On So 24 Nov 2013 03:56:53 CET, Orion Poplawski wrote:
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
maybe we should link /usr/lib64/nx/X11/xkb/rules/xfree86 to /usr/lib64/nx/X11/xkb/rules/xorg?
???
Mike
Hmm, I don't have a /usr/lib64/nx/X11/xkb directory in the Fedora package. Any reason we couldn't point to /usr/share/X11/xkb?
-- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA/CoRA Division FAX: 303-415-9702 3380 Mitchell Lane orion@cora.nwra.com Boulder, CO 80301 http://www.cora.nwra.com
I have a similar problem with the new versions of X2Go and the OSX client. Ubuntu 12.04 servers with X2Goserver 4.0.1.8 and XFCE 4.10. With x2goclient 4.0.1.1 on Ubuntu 12.04 it works fine, but with x2goclient on OSX (tested 4.0.0.4, 4.0.1.1 and latest git) the keyboard is completely screwed up. It does not matter if I set it to use current keyboard setup or if I explicitely set a keyboard layout. This problem started appearing when the latest x2goserver update rolled out and seems to be independent from the client, except it only seems to materialize on OSX...
2013/11/26 Orion Poplawski <orion@cora.nwra.com>
On 11/25/2013 10:18 AM, Mike Gabriel wrote:
Hi Orion,
On So 24 Nov 2013 03:56:53 CET, Orion Poplawski wrote:
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
maybe we should link /usr/lib64/nx/X11/xkb/rules/xfree86 to /usr/lib64/nx/X11/xkb/rules/xorg?
???
Mike
Hmm, I don't have a /usr/lib64/nx/X11/xkb directory in the Fedora package. Any reason we couldn't point to /usr/share/X11/xkb?
-- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA/CoRA Division FAX: 303-415-9702 3380 Mitchell Lane orion@cora.nwra.com Boulder, CO 80301 http://www.cora.nwra.com
X2Go-Dev mailing list X2Go-Dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/x2go-dev
-- Anders Bruun Olsen It-ansvarlig Det Danske Sprog- og Litteraturselskab (Society for Danish Language and Literature)
This in x2gostartagent seems wrong:
if [ "$X2GO_SET_KBD" == "0" ] || [ "$X2GO_KBD_TYPE" != "auto" ]; then $X2GO_LIB_PATH/x2gosyslog "$0" "info" "blocking creation of agent's keyboard file ${SESSION_DIR}/keyboard as requested by session startup command" mkdir -p ${SESSION_DIR}/keyboard fi
In the normal case, X2GO_SET_KBD is 1 and the type is specified as pc105/us or pc105/gb, etc. Since X2GO_KBD_TYPE != auto it does not set the keyboard setttings.
I'm not sure what is trying to be done here. An earlier comparison is:
if [ "$X2GO_SET_KBD" == "0" ] || [ "$X2GO_KBD_TYPE" == "auto" ];then
X2GO_HOST="nx/nx,link=${X2GO_LINK},pack=${X2GO_PACK},limit=0,root=${SESSION_DIR},cache=8M,images=32M,type=${X2GO_TYPE},id=${SESSION_NAME},cookie=$X2GO_COOKIE,errors=${SESSION_LOG},kbtype=null/null,${option_geometry}resize=${X2GO_RESIZE},fullscreen=${X2GO_FULLSCREEN},accept=${REMOTE},listen=${GR_PORT},client=linux,menu=0" else
X2GO_HOST="nx/nx,link=${X2GO_LINK},pack=${X2GO_PACK},limit=0,root=${SESSION_DIR},cache=8M,images=32M,type=${X2GO_TYPE},id=${SESSION_NAME},cookie=$X2GO_COOKIE,errors=${SESSION_LOG},kbtype=${X2GO_KBD_TYPE},${option_geometry}resize=${X2GO_RESIZE},fullscreen=${X2GO_FULLSCREEN},accept=${REMOTE},listen=${GR_PORT},client=linux,menu=0" fi
So you probably want a == auto.
On 11/23/2013 07:56 PM, Orion Poplawski wrote:
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@redhat.com To: orion@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@cora.nwra.com Reporter: rmj@ast.cam.ac.uk QA Contact: extras-qa@fedoraproject.org CC: orion@cora.nwra.comDescription 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:
- From a Windows XP laptop with UK keyboard, configure an x2go session with Session preferences / settings / keyboard layout: gb keyboard model: pc105/gb
- Start x2go session to Fedora 20 beta
- 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 " etcSeen 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
-- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA/CoRA Division FAX: 303-415-9702 3380 Mitchell Lane orion@cora.nwra.com Boulder, CO 80301 http://www.cora.nwra.com
Hi Orion,
On Do 28 Nov 2013 01:12:18 CET, Orion Poplawski wrote:
This in x2gostartagent seems wrong:
if [ "$X2GO_SET_KBD" == "0" ] || [ "$X2GO_KBD_TYPE" != "auto" ]; then $X2GO_LIB_PATH/x2gosyslog "$0" "info" "blocking creation of
agent's keyboard file ${SESSION_DIR}/keyboard as requested by
session startup command" mkdir -p ${SESSION_DIR}/keyboard fiIn the normal case, X2GO_SET_KBD is 1 and the type is specified as
pc105/us or pc105/gb, etc. Since X2GO_KBD_TYPE != auto it does not
set the keyboard setttings.
This is a bit hacky, I agree. Let me start from the beginning...
The ~/.x2go/<session>/keyboard file gets created by x2goagent. Always.
It is a file containing settings for the client-side keyboard. This
parameter in this file can be used to configure the session keyboard
automagically.
Now, we have three different keyboard setup types (actually four):
do not do anything about keyboard setup
-> X2GO_SET_KBD = 0 -> X2GO_KBD_TYPE = null/null (or so)
set a keyboard specified in X2Go Client
-> X2GO_SET_KBD = 1 -> X2GO_KBD_TYPE = pc105/de (or so)
auto-detect client-side keyboard
-> X2GO_SET_KBD = 1 -> X2GO_KBD_TYPE = auto
Only with this third parameter combination we want the
~/.x2go/<session>/keyboard to be created by x2goagent. Best (only?)
way for this is blocking the file name with a directory. x2goagent
will silently stumble over this blocked directory/file name and it
will not create the keyboard file.
(4. from Mac OS X you can theoretically use X2GO_KBD_TYPE = query. In
X2Go Client, however, there is code that sets X2GO_KBD_TYPE=query and
X2GO_SET_KBD=0, this basically disables the X2GO_KBD_TYPE=query. I
tested with a Mac User on IRC lately how the effect would be if we
switched this combination to X2GO_KBD_TYPE=query and X2GO_SET_KBD=1.
On his setup that change worked, so I added that to the latest X2Go
Server release. However, Anders has just reported a f****-up keyboard
layout since the latest X2Go Server release and I suspect that that
code is effecting that).
Next fact that comes into play here now is: the script
x2gosetkeyboard. This script is responsible for reading the
~/.x2go/<session>/keyboard, extracting its information and running
setxkbmap on the X2Go session's $DISPLAY. This, I found, is only good
working well, if that x2gosetkeyboard call is evoked from
x2goruncommand. However, x2goruncommand does not know about
X2GO_SET_KBD and X2GO_KBD_TYPE.
Thus, I have to leave a message for x2gosetkeyboard via the
x2gostartagent script. The information required is: is x2gosetkeyboard
supposed to run or not. This I do with creating
~/.x2go/<session>/keyboard as a directory prior to launching x2goagent.
So, IMHO the if clause above is just selecting the described case.
I'm not sure what is trying to be done here. An earlier comparison is:
if [ "$X2GO_SET_KBD" == "0" ] || [ "$X2GO_KBD_TYPE" == "auto" ];then
X2GO_HOST="nx/nx,link=${X2GO_LINK},pack=${X2GO_PACK},limit=0,root=${SESSION_DIR},cache=8M,images=32M,type=${X2GO_TYPE},id=${SESSION_NAME},cookie=$X2GO_COOKIE,errors=${SESSION_LOG},kbtype=null/null,${option_geometry}resize=${X2GO_RESIZE},fullscreen=${X2GO_FULLSCREEN},accept=${REMOTE},listen=${GR_PORT},client=linux,menu=0" else
X2GO_HOST="nx/nx,link=${X2GO_LINK},pack=${X2GO_PACK},limit=0,root=${SESSION_DIR},cache=8M,images=32M,type=${X2GO_TYPE},id=${SESSION_NAME},cookie=$X2GO_COOKIE,errors=${SESSION_LOG},kbtype=${X2GO_KBD_TYPE},${option_geometry}resize=${X2GO_RESIZE},fullscreen=${X2GO_FULLSCREEN},accept=${REMOTE},listen=${GR_PORT},client=linux,menu=0" fi
This one is also correct... In this if clause we set the NX option
kbtype=null/null or kbtype=${X2GO_KBD_TYPE}. We only want to set
kbtype=${X2GO_KBD_TYPE}, if it is not auto and X2GO_SET_KBD is
enabled. This is handled by the above quoted if-clause IMHO.
So you probably want a == auto.
Don't think so...
Mike
DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148
GnuPG Key ID 0x25771B31 mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
On 11/28/2013 01:46 AM, Mike Gabriel wrote:
Hi Orion,
On Do 28 Nov 2013 01:12:18 CET, Orion Poplawski wrote:
This in x2gostartagent seems wrong:
if [ "$X2GO_SET_KBD" == "0" ] || [ "$X2GO_KBD_TYPE" != "auto" ]; then $X2GO_LIB_PATH/x2gosyslog "$0" "info" "blocking creation of agent's keyboard file ${SESSION_DIR}/keyboard as requested by session startup command" mkdir -p ${SESSION_DIR}/keyboard fi
In the normal case, X2GO_SET_KBD is 1 and the type is specified as pc105/us or pc105/gb, etc. Since X2GO_KBD_TYPE != auto it does not set the keyboard setttings.
This is a bit hacky, I agree. Let me start from the beginning...
The ~/.x2go/<session>/keyboard file gets created by x2goagent. Always. It is a file containing settings for the client-side keyboard. This parameter in this file can be used to configure the session keyboard automagically.
Now, we have three different keyboard setup types (actually four):
do not do anything about keyboard setup
-> X2GO_SET_KBD = 0 -> X2GO_KBD_TYPE = null/null (or so)
set a keyboard specified in X2Go Client
-> X2GO_SET_KBD = 1 -> X2GO_KBD_TYPE = pc105/de (or so)
So, in this case, how are the keyboard settings supposed to be applied?
auto-detect client-side keyboard
-> X2GO_SET_KBD = 1 -> X2GO_KBD_TYPE = auto
Only with this third parameter combination we want the ~/.x2go/<session>/keyboard to be created by x2goagent. Best (only?) way for this is blocking the file name with a directory. x2goagent will silently stumble over this blocked directory/file name and it will not create the keyboard file.
(4. from Mac OS X you can theoretically use X2GO_KBD_TYPE = query. In X2Go Client, however, there is code that sets X2GO_KBD_TYPE=query and X2GO_SET_KBD=0, this basically disables the X2GO_KBD_TYPE=query. I tested with a Mac User on IRC lately how the effect would be if we switched this combination to X2GO_KBD_TYPE=query and X2GO_SET_KBD=1. On his setup that change worked, so I added that to the latest X2Go Server release. However, Anders has just reported a f****-up keyboard layout since the latest X2Go Server release and I suspect that that code is effecting that).
Next fact that comes into play here now is: the script x2gosetkeyboard. This script is responsible for reading the ~/.x2go/<session>/keyboard, extracting its information and running setxkbmap on the X2Go session's $DISPLAY. This, I found, is only good working well, if that x2gosetkeyboard call is evoked from x2goruncommand. However, x2goruncommand does not know about X2GO_SET_KBD and X2GO_KBD_TYPE.
Thus, I have to leave a message for x2gosetkeyboard via the x2gostartagent script. The information required is: is x2gosetkeyboard supposed to run or not. This I do with creating ~/.x2go/<session>/keyboard as a directory prior to launching x2goagent.
So, IMHO the if clause above is just selecting the described case.
I'm not sure what is trying to be done here. An earlier comparison is:
if [ "$X2GO_SET_KBD" == "0" ] || [ "$X2GO_KBD_TYPE" == "auto" ];then
X2GO_HOST="nx/nx,link=${X2GO_LINK},pack=${X2GO_PACK},limit=0,root=${SESSION_DIR},cache=8M,images=32M,type=${X2GO_TYPE},id=${SESSION_NAME},cookie=$X2GO_COOKIE,errors=${SESSION_LOG},kbtype=null/null,${option_geometry}resize=${X2GO_RESIZE},fullscreen=${X2GO_FULLSCREEN},accept=${REMOTE},listen=${GR_PORT},client=linux,menu=0"
else
X2GO_HOST="nx/nx,link=${X2GO_LINK},pack=${X2GO_PACK},limit=0,root=${SESSION_DIR},cache=8M,images=32M,type=${X2GO_TYPE},id=${SESSION_NAME},cookie=$X2GO_COOKIE,errors=${SESSION_LOG},kbtype=${X2GO_KBD_TYPE},${option_geometry}resize=${X2GO_RESIZE},fullscreen=${X2GO_FULLSCREEN},accept=${REMOTE},listen=${GR_PORT},client=linux,menu=0"
fi
This one is also correct... In this if clause we set the NX option kbtype=null/null or kbtype=${X2GO_KBD_TYPE}. We only want to set kbtype=${X2GO_KBD_TYPE}, if it is not auto and X2GO_SET_KBD is enabled. This is handled by the above quoted if-clause IMHO.
So you probably want a == auto.
Don't think so...
You may be right - we tried this and apparently it doesn't help (with both KDE and XFCE). I wonder if something in the desktop environment settings is overriding the settings.
-- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA/CoRA Division FAX: 303-415-9702 3380 Mitchell Lane orion@cora.nwra.com Boulder, CO 80301 http://www.cora.nwra.com
Hi Orion
On Fr 29 Nov 2013 16:15:53 CET, Orion Poplawski wrote:
You may be right - we tried this and apparently it doesn't help
(with both KDE and XFCE). I wonder if something in the desktop
environment settings is overriding the settings.
I had that with a GNOMEv2 session and a user profile once. Make sure
the desktop shell does not want to play with the keyboard settings at
all!!!
Mike
--
DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148
GnuPG Key ID 0x25771B31 mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
On 11/29/2013 08:32 AM, Mike Gabriel wrote:
Hi Orion
On Fr 29 Nov 2013 16:15:53 CET, Orion Poplawski wrote:
You may be right - we tried this and apparently it doesn't help (with both KDE and XFCE). I wonder if something in the desktop environment settings is overriding the settings.
I had that with a GNOMEv2 session and a user profile once. Make sure the desktop shell does not want to play with the keyboard settings at all!!!
Mike
I still can't figure this out, but can reproduce some problems. This is with x2goserver-4.0.1.9-2.el6.x86_64 on the server, and x2goclient-4.0.1.1-1.fc19.x86_64 on the client. Starting an XFCE session and launching a terminal. At this point arrow keys do not work in the shell. So I do:
[orion@vulcan ~]$ setxkbmap -print Couldn't interpret _XKB_RULES_NAMES property Use defaults: rules - 'base' model - 'pc105' layout - 'us' xkb_keymap { xkb_keycodes { include "xfree86+aliases(qwerty)" }; xkb_types { include "complete" }; xkb_compat { include "complete" }; xkb_symbols { include "pc+us+inet(pc105)" }; xkb_geometry { include "pc(pc105)" }; }; [orion@vulcan ~]$ setxkbmap Couldn't interpret _XKB_RULES_NAMES property Use defaults: rules - 'base' model - 'pc105' layout - 'us' [orion@vulcan ~]$ setxkbmap -print xkb_keymap { xkb_keycodes { include "xfree86+aliases(qwerty)" }; xkb_types { include "complete" }; xkb_compat { include "complete" }; xkb_symbols { include "pc+us+inet(pc105)" }; xkb_geometry { include "pc(pc105)" }; };
After I run "setxkbmap", the arrow keys work fine.
I still can't find where setxkbmap is supposed to be executed in this case.
-- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane orion@nwra.com Boulder, CO 80301 http://www.nwra.com
Hi Orion,
----- Original message -----
On 11/28/2013 01:46 AM, Mike Gabriel wrote:
Hi Orion,
On Do 28 Nov 2013 01:12:18 CET, Orion Poplawski wrote:
This in x2gostartagent seems wrong:
if [ "$X2GO_SET_KBD" == "0" ] || [ "$X2GO_KBD_TYPE" != "auto" ]; then $X2GO_LIB_PATH/x2gosyslog "$0" "info" "blocking creation of agent's keyboard file ${SESSION_DIR}/keyboard as requested by session startup command" mkdir -p ${SESSION_DIR}/keyboard fi
In the normal case, X2GO_SET_KBD is 1 and the type is specified as pc105/us or pc105/gb, etc. Since X2GO_KBD_TYPE != auto it does not set the keyboard setttings.
This is a bit hacky, I agree. Let me start from the beginning...
The ~/.x2go/<session>/keyboard file gets created by x2goagent. Always. It is a file containing settings for the client-side keyboard. This parameter in this file can be used to configure the session keyboard automagically.
Now, we have three different keyboard setup types (actually four):
- do not do anything about keyboard setup
-> X2GO_SET_KBD = 0 -> X2GO_KBD_TYPE = null/null (or so)
- set a keyboard specified in X2Go Client
-> X2GO_SET_KBD = 1 -> X2GO_KBD_TYPE = pc105/de (or so)
So, in this case, how are the keyboard settings supposed to be applied?
I still owe you an answer to this...
The keyboard layout and the variant (Python X2Go only) in this case will get set via the client. Scan for setxkbmap in onmainwindow.cpp of X2Go Client for details.
The X2GO_KBD_TYPE will be passed to nxagent, directly.
Mike
--
DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976148
GnuPG Key ID 0x25771B13 mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
On 11/30/2013 01:44 AM, Mike Gabriel wrote:
Hi Orion,
----- Original message -----
On 11/28/2013 01:46 AM, Mike Gabriel wrote:
Hi Orion,
On Do 28 Nov 2013 01:12:18 CET, Orion Poplawski wrote: 2. set a keyboard specified in X2Go Client
-> X2GO_SET_KBD = 1 -> X2GO_KBD_TYPE = pc105/de (or so)
So, in this case, how are the keyboard settings supposed to be applied?
I still owe you an answer to this...
The keyboard layout and the variant (Python X2Go only) in this case will get set via the client. Scan for setxkbmap in onmainwindow.cpp of X2Go Client for details.
The X2GO_KBD_TYPE will be passed to nxagent, directly.
Mike
I see:
void ONMainWindow::slotChangeKbdLayout(const QString& layout) { #ifdef Q_OS_LINUX QStringList args; args<<"-layout"<<layout;
x2goDebug<<"Running setxkbmap with params: "<<args.join(" ");
QProcess::startDetached("setxkbmap",args);#endif }
The bug report (https://bugzilla.redhat.com/show_bug.cgi?id=1033876) is with a Windows XP client. Is that the issue, that this code is only run on Linux? Why?
-- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane orion@nwra.com Boulder, CO 80301 http://www.nwra.com
-
Anders Bruun Olsen -
Mike Gabriel -
Orion Poplawski