[X2Go-User] Keyboard doesn't work from Mac OSX to Scientific Linux 7 x2go server

Discussion:

James M. Pulver

2018-06-28 17:56:08 UTC

The keyboard is unusable when launching XFCE on SL7.4 via X2Go from OS
X. icewm-session works fine on SL7, and XFCE works fine on SL6.

We've tried different versions of the Agent with no change...

--
James Pulver
CLASSE Computer Group
Cornell University

Stefan Baur

2018-06-28 18:24:25 UTC

Permalink

Post by James M. Pulver
The keyboard is unusable when launching XFCE on SL7.4 via X2Go from OS
X. icewm-session works fine on SL7, and XFCE works fine on SL6.
We've tried different versions of the Agent with no change...

Please share which X2GoClient version you are using, and what exactly
happens that makes it unusable. I.e. are no keystrokes coming through,
or additional ones, or wrong ones, ...

Kind Regards,
Stefan Baur

--
BAUR-ITCS UG (haftungsbeschränkt)
Geschäftsführer: Stefan Baur
Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364
Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243

James M. Pulver

2018-06-29 13:05:54 UTC

Permalink

I apologize for being a little vague and using the wrong terms. (For
reasons I can't explain, I'm the intermediary for this report - I don't
personally use MacOSX)

We have tested with client versions from 4.0.0 to 4.1.1 with the same
issue, and it's that the keyboard types in "random" keys when users try
and type anything. The clipboard seems to work properly though. Per an
offline e-mail, we were also asked to run setxkbmap -query -v 7

results:
[***@lnx100 ~]$ setxkbmap -query -v 7
Applied rules from xorg:
rules: xorg
model: null
layout: us
Trying to build keymap using the following components:
keycodes: xfree86+aliases(qwerty)
types: complete
compat: complete
symbols: pc+us
geometry: pc(pc104)
rules: xorg
model: null
layout: us

[***@lnx100 ~]$ xprop -root
_XROOTPMAP_ID(PIXMAP): pixmap id # 0xc0001c
XFDESKTOP_IMAGE_FILE_0(STRING) = "/usr/share/backgrounds/images/default.png"
_NET_DESKTOP_NAMES(UTF8_STRING) = "Workspace 1", ""
_NET_CLIENT_LIST_STACKING(WINDOW): window id # 0xc00003, 0x2400003,
0xa00003, 0xa0001f
_NET_CLIENT_LIST(WINDOW): window id # 0xa00003, 0xa0001f, 0x2400003,
0xc00003
_NET_DESKTOP_LAYOUT(CARDINAL) = 0, 0, 1, 0
_NET_ACTIVE_WINDOW(WINDOW): window id # 0x2400003, 0x0
_NET_CURRENT_DESKTOP(CARDINAL) = 0
_NET_DESKTOP_VIEWPORT(CARDINAL) = 0, 0
_NET_DESKTOP_GEOMETRY(CARDINAL) = 1440, 900
_NET_SUPPORTING_WM_CHECK(WINDOW): window id # 0x800122
_NET_SUPPORTED(ATOM) = _NET_ACTIVE_WINDOW, _NET_CLIENT_LIST,
_NET_CLIENT_LIST_STACKING, _NET_CLOSE_WINDOW, _NET_CURRENT_DESKTOP,
_NET_DESKTOP_GEOMETRY, _NET_DESKTOP_LAYOUT, _NET_DESKTOP_NAMES,
_NET_DESKTOP_VIEWPORT, _NET_FRAME_EXTENTS, _NET_MOVERESIZE_WINDOW,
_NET_NUMBER_OF_DESKTOPS, _NET_REQUEST_FRAME_EXTENTS,
_NET_SHOWING_DESKTOP, _NET_SUPPORTED, _NET_SUPPORTING_WM_CHECK,
_NET_SYSTEM_TRAY_OPCODE, _NET_WM_ACTION_ABOVE, _NET_WM_ACTION_BELOW,
_NET_WM_ACTION_CHANGE_DESKTOP, _NET_WM_ACTION_CLOSE,
_NET_WM_ACTION_FULLSCREEN, _NET_WM_ACTION_MAXIMIZE_HORZ,
_NET_WM_ACTION_MAXIMIZE_VERT, _NET_WM_ACTION_MINIMIZE,
_NET_WM_ACTION_MOVE, _NET_WM_ACTION_RESIZE, _NET_WM_ACTION_SHADE,
_NET_WM_ACTION_STICK, _NET_WM_ALLOWED_ACTIONS, _NET_WM_CONTEXT_HELP,
_NET_WM_DESKTOP, _NET_WM_FULLSCREEN_MONITORS, _NET_WM_ICON,
_NET_WM_ICON_GEOMETRY, _NET_WM_ICON_NAME, _NET_WM_MOVERESIZE,
_NET_WM_NAME, _NET_WM_PID, _NET_WM_PING, _NET_WM_STATE,
_NET_WM_STATE_ABOVE, _NET_WM_STATE_BELOW, _NET_WM_STATE_DEMANDS_A!
TTENTION,
_NET_WM_STATE_FOCUSED, _NET_WM_STATE_FULLSCREEN,
_NET_WM_STATE_HIDDEN, _NET_WM_STATE_MAXIMIZED_HORZ,
_NET_WM_STATE_MAXIMIZED_VERT, _NET_WM_STATE_MODAL, _NET_WM_STATE_SHADED,
_NET_WM_STATE_SKIP_PAGER, _NET_WM_STATE_SKIP_TASKBAR,
_NET_WM_STATE_STICKY, _NET_WM_STRUT, _NET_WM_STRUT_PARTIAL,
_NET_WM_SYNC_REQUEST, _NET_WM_SYNC_REQUEST_COUNTER, _NET_WM_USER_TIME,
_NET_WM_USER_TIME_WINDOW, _NET_WM_WINDOW_OPACITY,
_NET_WM_WINDOW_OPACITY_LOCKED, _NET_WM_WINDOW_TYPE,
_NET_WM_WINDOW_TYPE_DESKTOP, _NET_WM_WINDOW_TYPE_DIALOG,
_NET_WM_WINDOW_TYPE_DOCK, _NET_WM_WINDOW_TYPE_MENU,
_NET_WM_WINDOW_TYPE_NORMAL, _NET_WM_WINDOW_TYPE_SPLASH,
_NET_WM_WINDOW_TYPE_TOOLBAR, _NET_WM_WINDOW_TYPE_UTILITY, _NET_WORKAREA,
_GTK_FRAME_EXTENTS, _GTK_HIDE_TITLEBAR_WHEN_MAXIMIZED,
_GTK_SHOW_WINDOW_MENU, _NET_STARTUP_ID
_NET_WORKAREA(CARDINAL) = 0, 49, 1440, 810
_NET_NUMBER_OF_DESKTOPS(CARDINAL) = 1
XKLAVIER_ALLOW_SECONDARY(INTEGER) = 0
XIM_SERVERS(ATOM) = @server=ibus
RESOURCE_MANAGER(STRING) =
"\nXft.antialias:\t1\nXft.hintstyle:\thintfull\nXft.rgba:\tnone\nXcursor.theme:\t\nXcursor.size:\t0\nXcursor.theme_core:\t1\n"
NAUTILUS_DESKTOP_WINDOW_ID(WINDOW): window id # 0xc00003
XFCE_DESKTOP_WINDOW(WINDOW): window id # 0xc00003
AT_SPI_BUS(STRING) =
"unix:abstract=/tmp/dbus-6f0efR26cY,guid=542107f375b4063230b0f8a05b355aa5"
GDK_VISUALS(INTEGER) = 157, 0
PULSE_COOKIE(STRING) =
"84a7e31efb12bae06510446fcf2ca3ab626b59dac0c991cec4b690433ee2504223e2319bd68f1d064e540c1fe1f9cfc7cb9815257b31d6b37b936e7e81cbbab11b1c16f2899fff4c09d5fdf77e8158ef4a9ef0ed75595c3dfb9e43a47e6b0669fba9576dab98b6f51e8133c11916942e2f07d025a93a4d0987967bb928ecc0848e4c13eaf767840fa9e22646c8f1f948b9eaaa0ee6d80e526ae54ef4a3ab10e34c05fb4b7c818f9fd74bf95c105c0f56caf74f88e169709e6d6508908653e9642b5c433cd1b9dfeb063f844514d2396ef69201c4db3ba60955ba605b1c8ae6428129f965579f2bb153f237f436e4afed36fabe9b53ad9cf4a9e320eac363ed5a"
PULSE_SERVER(STRING) =
"{aba847eca9d743bcae07dc72d78c8ac7}unix:/run/user/2417/pulse/native"
PULSE_SESSION_ID(STRING) = "9476"
PULSE_ID(STRING) = "***@aba847eca9d743bcae07dc72d78c8ac7/11117"
_DT_RESTORE_MODE(STRING) = "xfce4"
_DT_SAVE_MODE(STRING) = "xfce4"
_XKB_RULES_NAMES(STRING) = "xorg", "null", "us", "", ""

--
James Pulver
CLASSE Computer Group
Cornell University

Post by Stefan Baur

Stefan Baur

2018-06-29 13:32:16 UTC

Permalink

Hi James,

there has been an issue/regression regarding macOS keyboard support in
X2GoClient, which wasn't fixed before 4.1.1.* series.

Looking at the changelog for 4.1.2.0, I am not sure if the fix made it
into the release.

Please, *first* try the official 4.1.2.0 release which you can find at:

<https://code.x2go.org/releases/X2GoClient_latest_macosx_10_13.dmg> (for
10.13 and up)

<https://code.x2go.org/releases/X2GoClient_latest_macosx_10_11.dmg> (for
10.11 and 10.12)

<https://code.x2go.org/releases/X2GoClient_latest_macosx_10_9.dmg> (for
10.9 and 10.10 - note that this link is currently broken, but should be
available again later on tonight - try around 23:00 UTC or later, I'd say)

If the latest official release does not work for you, and ONLY then,
please try out this nightly build from May 2018, and report back if it
fixes your issue.

<https://code.x2go.org/releases/binary-macosx/x2goclient/nightly/4.1.2.0/x2goclient-4.1.2.0.git20180524.1776.heuler.OSX_10_13.dmg>
(for 10.13 and up)

<https://code.x2go.org/releases/binary-macosx/x2goclient/nightly/4.1.2.0/x2goclient-4.1.2.0.git20180524.1776.heuler.OSX_10_11.dmg>
(for 10.11 and 10.12)

As with all nightly builds, these should not be used for mass
deployment. The reason is that nightly builds may carry a version
number that matches a release, yet differ from the release version, so
telling nightly and release versions apart can become a hairy mess in
large roll-outs, especially when your only way of determining the
version is to check the "About" menu of X2GoClient.

Kind Regards,
Stefan Baur

Post by James M. Pulver
I apologize for being a little vague and using the wrong terms. (For
reasons I can't explain, I'm the intermediary for this report - I don't
personally use MacOSX)
We have tested with client versions from 4.0.0 to 4.1.1 with the same
issue, and it's that the keyboard types in "random" keys when users try
and type anything. The clipboard seems to work properly though. Per an
offline e-mail, we were also asked to run setxkbmap -query -v 7
rules:      xorg
model:      null
layout:     us
keycodes:   xfree86+aliases(qwerty)
types:      complete
compat:     complete
symbols:    pc+us
geometry:   pc(pc104)
rules:      xorg
model:      null
layout:     us
_XROOTPMAP_ID(PIXMAP): pixmap id # 0xc0001c
XFDESKTOP_IMAGE_FILE_0(STRING) =
"/usr/share/backgrounds/images/default.png"
_NET_DESKTOP_NAMES(UTF8_STRING) = "Workspace 1", ""
_NET_CLIENT_LIST_STACKING(WINDOW): window id # 0xc00003, 0x2400003,
0xa00003, 0xa0001f
_NET_CLIENT_LIST(WINDOW): window id # 0xa00003, 0xa0001f, 0x2400003,
0xc00003
_NET_DESKTOP_LAYOUT(CARDINAL) = 0, 0, 1, 0
_NET_ACTIVE_WINDOW(WINDOW): window id # 0x2400003, 0x0
_NET_CURRENT_DESKTOP(CARDINAL) = 0
_NET_DESKTOP_VIEWPORT(CARDINAL) = 0, 0
_NET_DESKTOP_GEOMETRY(CARDINAL) = 1440, 900
_NET_SUPPORTING_WM_CHECK(WINDOW): window id # 0x800122
_NET_SUPPORTED(ATOM) = _NET_ACTIVE_WINDOW, _NET_CLIENT_LIST,
_NET_CLIENT_LIST_STACKING, _NET_CLOSE_WINDOW, _NET_CURRENT_DESKTOP,
_NET_DESKTOP_GEOMETRY, _NET_DESKTOP_LAYOUT, _NET_DESKTOP_NAMES,
_NET_DESKTOP_VIEWPORT, _NET_FRAME_EXTENTS, _NET_MOVERESIZE_WINDOW,
_NET_NUMBER_OF_DESKTOPS, _NET_REQUEST_FRAME_EXTENTS,
_NET_SHOWING_DESKTOP, _NET_SUPPORTED, _NET_SUPPORTING_WM_CHECK,
_NET_SYSTEM_TRAY_OPCODE, _NET_WM_ACTION_ABOVE, _NET_WM_ACTION_BELOW,
_NET_WM_ACTION_CHANGE_DESKTOP, _NET_WM_ACTION_CLOSE,
_NET_WM_ACTION_FULLSCREEN, _NET_WM_ACTION_MAXIMIZE_HORZ,
_NET_WM_ACTION_MAXIMIZE_VERT, _NET_WM_ACTION_MINIMIZE,
_NET_WM_ACTION_MOVE, _NET_WM_ACTION_RESIZE, _NET_WM_ACTION_SHADE,
_NET_WM_ACTION_STICK, _NET_WM_ALLOWED_ACTIONS, _NET_WM_CONTEXT_HELP,
_NET_WM_DESKTOP, _NET_WM_FULLSCREEN_MONITORS, _NET_WM_ICON,
_NET_WM_ICON_GEOMETRY, _NET_WM_ICON_NAME, _NET_WM_MOVERESIZE,
_NET_WM_NAME, _NET_WM_PID, _NET_WM_PING, _NET_WM_STATE,
_NET_WM_STATE_ABOVE, _NET_WM_STATE_BELOW, _NET_WM_STATE_DEMANDS_A!
TTENTION,
_NET_WM_STATE_FOCUSED, _NET_WM_STATE_FULLSCREEN, _NET_WM_STATE_HIDDEN,
_NET_WM_STATE_MAXIMIZED_HORZ, _NET_WM_STATE_MAXIMIZED_VERT,
_NET_WM_STATE_MODAL, _NET_WM_STATE_SHADED, _NET_WM_STATE_SKIP_PAGER,
_NET_WM_STATE_SKIP_TASKBAR, _NET_WM_STATE_STICKY, _NET_WM_STRUT,
_NET_WM_STRUT_PARTIAL, _NET_WM_SYNC_REQUEST,
_NET_WM_SYNC_REQUEST_COUNTER, _NET_WM_USER_TIME,
_NET_WM_USER_TIME_WINDOW, _NET_WM_WINDOW_OPACITY,
_NET_WM_WINDOW_OPACITY_LOCKED, _NET_WM_WINDOW_TYPE,
_NET_WM_WINDOW_TYPE_DESKTOP, _NET_WM_WINDOW_TYPE_DIALOG,
_NET_WM_WINDOW_TYPE_DOCK, _NET_WM_WINDOW_TYPE_MENU,
_NET_WM_WINDOW_TYPE_NORMAL, _NET_WM_WINDOW_TYPE_SPLASH,
_NET_WM_WINDOW_TYPE_TOOLBAR, _NET_WM_WINDOW_TYPE_UTILITY, _NET_WORKAREA,
_GTK_FRAME_EXTENTS, _GTK_HIDE_TITLEBAR_WHEN_MAXIMIZED,
_GTK_SHOW_WINDOW_MENU, _NET_STARTUP_ID
_NET_WORKAREA(CARDINAL) = 0, 49, 1440, 810
_NET_NUMBER_OF_DESKTOPS(CARDINAL) = 1
XKLAVIER_ALLOW_SECONDARY(INTEGER) = 0
RESOURCE_MANAGER(STRING) =
"\nXft.antialias:\t1\nXft.hintstyle:\thintfull\nXft.rgba:\tnone\nXcursor.theme:\t\nXcursor.size:\t0\nXcursor.theme_core:\t1\n"
NAUTILUS_DESKTOP_WINDOW_ID(WINDOW): window id # 0xc00003
XFCE_DESKTOP_WINDOW(WINDOW): window id # 0xc00003
AT_SPI_BUS(STRING) =
"unix:abstract=/tmp/dbus-6f0efR26cY,guid=542107f375b4063230b0f8a05b355aa5"
GDK_VISUALS(INTEGER) = 157, 0
PULSE_COOKIE(STRING) =
"84a7e31efb12bae06510446fcf2ca3ab626b59dac0c991cec4b690433ee2504223e2319bd68f1d064e540c1fe1f9cfc7cb9815257b31d6b37b936e7e81cbbab11b1c16f2899fff4c09d5fdf77e8158ef4a9ef0ed75595c3dfb9e43a47e6b0669fba9576dab98b6f51e8133c11916942e2f07d025a93a4d0987967bb928ecc0848e4c13eaf767840fa9e22646c8f1f948b9eaaa0ee6d80e526ae54ef4a3ab10e34c05fb4b7c818f9fd74bf95c105c0f56caf74f88e169709e6d6508908653e9642b5c433cd1b9dfeb063f844514d2396ef69201c4db3ba60955ba605b1c8ae6428129f965579f2bb153f237f436e4afed36fabe9b53ad9cf4a9e320eac363ed5a"
PULSE_SERVER(STRING) =
"{aba847eca9d743bcae07dc72d78c8ac7}unix:/run/user/2417/pulse/native"
PULSE_SESSION_ID(STRING) = "9476"
_DT_RESTORE_MODE(STRING) = "xfce4"
_DT_SAVE_MODE(STRING) = "xfce4"
_XKB_RULES_NAMES(STRING) = "xorg", "null", "us", "", ""
--
James Pulver
CLASSE Computer Group
Cornell University

Post by Stefan Baur

_______________________________________________
x2go-user mailing list
https://lists.x2go.org/listinfo/x2go-user

--
BAUR-ITCS UG (haftungsbeschränkt)
Geschäftsführer: Stefan Baur
Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364
Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243

James M. Pulver

2018-06-29 15:31:53 UTC

Permalink

Hi, thanks for that suggestion. The very latest version did fix the
keyboard issue. (4.1.2.0)

--
James Pulver
CLASSE Computer Group
Cornell University

Post by Stefan Baur
Hi James,
there has been an issue/regression regarding macOS keyboard support in
X2GoClient, which wasn't fixed before 4.1.1.* series.
Looking at the changelog for 4.1.2.0, I am not sure if the fix made it
into the release.
<https://code.x2go.org/releases/X2GoClient_latest_macosx_10_13.dmg> (for
10.13 and up)
<https://code.x2go.org/releases/X2GoClient_latest_macosx_10_11.dmg> (for
10.11 and 10.12)
<https://code.x2go.org/releases/X2GoClient_latest_macosx_10_9.dmg> (for
10.9 and 10.10 - note that this link is currently broken, but should be
available again later on tonight - try around 23:00 UTC or later, I'd say)
If the latest official release does not work for you, and ONLY then,
please try out this nightly build from May 2018, and report back if it
fixes your issue.
<https://code.x2go.org/releases/binary-macosx/x2goclient/nightly/4.1.2.0/x2goclient-4.1.2.0.git20180524.1776.heuler.OSX_10_13.dmg>
(for 10.13 and up)
<https://code.x2go.org/releases/binary-macosx/x2goclient/nightly/4.1.2.0/x2goclient-4.1.2.0.git20180524.1776.heuler.OSX_10_11.dmg>
(for 10.11 and 10.12)
As with all nightly builds, these should not be used for mass
deployment. The reason is that nightly builds may carry a version
number that matches a release, yet differ from the release version, so
telling nightly and release versions apart can become a hairy mess in
large roll-outs, especially when your only way of determining the
version is to check the "About" menu of X2GoClient.
Kind Regards,
Stefan Baur

Post by Stefan Baur

_______________________________________________
x2go-user mailing list
https://lists.x2go.org/listinfo/x2go-user