Forum / General Discussions / Problems of resolution and keyboard
- This topic has 2 replies, 2 voices, and was last updated 12 years ago by
graywolf.
-
AuthorPosts
-
April 10, 2014 at 08:49 #3006
RomnParticipantHi, I am used to NoMachine 3.5 to connect from my Macbook (with one screen and an azerty keyboard) to an Ubuntu host (which as two screens and a qwerty keyboard). That works well until I had to update my Macbook to MacOs 10.9 (Maverick) and thus upgrade NoMachine to the version 4.2.
Now, when I connect to my host, I have a small windows inside which there are two windows in the resolution of the host, it is totally unusable. And the keyboard stays in qwerty and don’t adapt to the azerty layout of the client.
I can’t find anything in the option to help (I have tried to check and uncheck the box “change the server resolution to match the client”, it has absolutely no effect).
How can I fix this ?
Thank you.
April 14, 2014 at 08:30 #3095
RomnParticipantHere are some additional details of the configuration :
Both the server and the client have NX 4.2.19 in its Free version.
The server run under Ubuntu 13.10 64bits with the default desktop environment and in the setting I let the default setting, I can’t remember anyone which may be related to the problem. I still don’t understand if what I encounter is a bug or a feature of the 4th version.Attached to this post is a screenshot of my client NoMachine windows.
Attachments:
April 14, 2014 at 09:36 #3123
graywolfParticipantHello Romn,
when more monitors are in use on the server, NoMachine captures the whole virtual screen extending on all monitors. As the client is set to scale the captured screen to fit in its window, you could find that the resulting image is too squeezed if the server screen is much larger than the client window.
In case like this it is better if you set the client not to fit in the window: run the NoMachine session, press Ctrl+Alt+0, click on “Display” and turn off the option “Fit to window”.
About the keyboard, please send log files to us in order to check for possible problems. By the way, what you described looks the expected behavior. The layout that matters is the one set on the server. You need to change the server setting in order to match the client keyboard.
You can find instructions to gather server side logs here: https://www.nomachine.com/AR07K00677
-
AuthorPosts
This topic was marked as solved, you can't post.

