When I start a remote linux session from an OSX client, then disconnect and pick up the session from a windows client, the screen seems OK but the keyboard input is garbage. I thought I had that problem a long time ago and then it was fixed. Do the client versions have to stay in sync? And is there some way to reset the keyboard type to fix it and continue the session?
-- Les Mikesell lesmikesell@gmail.com
Hi Les,
On 07.04.2015 07:57 PM, Les Mikesell wrote:
When I start a remote linux session from an OSX client, then disconnect and pick up the session from a windows client, the screen seems OK but the keyboard input is garbage. I thought I had that problem a long time ago and then it was fixed. Do the client versions have to stay in sync? And is there some way to reset the keyboard type to fix it and continue the session?
The OS X client is synchronizing the keyboard layout by fetching the output of xmodmap on OS X and passing it to the remote session once every few seconds. If the Windows client is not overriding this on resuming by some means (I currently do not know the default behavior of the Windows-specific code), I'd expect the mappings to be wrong.
Aside from that, keeping the client versions close (or rather: using the newest version) is generally a good idea.
Maybe you just need to force a keyboard layout in the session settings on the Windows machine? Note that those options are not available in the OS X client due to the automatic synchronization via xmodmap anymore.
Mihai
On Tue, Apr 7, 2015 at 3:11 PM, Mihai Moldovan <ionic@ionic.de> wrote:
Hi Les,
On 07.04.2015 07:57 PM, Les Mikesell wrote:
When I start a remote linux session from an OSX client, then disconnect and pick up the session from a windows client, the screen seems OK but the keyboard input is garbage. I thought I had that problem a long time ago and then it was fixed. Do the client versions have to stay in sync? And is there some way to reset the keyboard type to fix it and continue the session?
The OS X client is synchronizing the keyboard layout by fetching the output of xmodmap on OS X and passing it to the remote session once every few seconds. If the Windows client is not overriding this on resuming by some means (I currently do not know the default behavior of the Windows-specific code), I'd expect the mappings to be wrong.
Aside from that, keeping the client versions close (or rather: using the newest version) is generally a good idea.
Maybe you just need to force a keyboard layout in the session settings on the Windows machine? Note that those options are not available in the OS X client due to the automatic synchronization via xmodmap anymore.
Thanks, but it doesn't seem to make a difference whether I have the windows client keyboard setting at automatic or configured as pc105/us. It still sends garbage to the session started by the OSX client.
On a positive note, though, the Windows 4.0.3.2 client no longer has a conflict with the 'synergy' keyboard/mouse sharing program I use. With earlier x2go client versions the mouse cursor would just disappear when it was supposed to move off the edge of the desktop monitor and take control of the adjacent computer.
-- Les Mikesell lesmikesell@gmail.com
-
Les Mikesell -
Mihai Moldovan