On 09/08/2017 10:31 PM, Robert Kudyba wrote:

See attached screen shot and suggested commands to run. This is Fedora 26. Any ideas?

Name : x2goserver Version : 4.0.1.20 Release : 2.fc26 Arch : x86_64 Size : 309 k Source : x2goserver-4.0.1.20-2.fc26.src.rpm Repo : @System From repo : @commandline Summary : X2Go Server URL : http://www.x2go.org License : GPLv2+

xprop -root | grep XKB _XKB_RULES_NAMES_BACKUP(STRING) = "xorg", "pc105", "us", "", "grab:break_actions" _XKB_RULES_NAMES(STRING) = "xorg", "pc105", "us", "", "grab:break_actions"

This is more or less the intended behavior. You cannot and shouldn't be allowed to change the xkb settings in the remote session when connected from an OS X client. The XKB settings here are weird though - while they look better in the forwarded message.

OS X is very special in this regard and seems to set "fake" values, which are mapped differently internally (most likely via Quartz integration.)

If you change the keyboard layout in the remote session, you will only get a very garbled layout - even though the same settings would be working fine from Linux or Windows clients.

AFAIK the functionality to disallow XKB changes is broken though, so I wonder why it's working in this instance.

Also, given that the session did start up, what do you mean by "fail to login"? Getting a screenshot of a working session from a failed login would be rather difficult...

Mihai