graywolf

[graywolf]

Hello.

NoMachine 5.0.53 introduced many changes. Is it possible for you trying the latest NoMachine client?

[graywolf]

Hello macphi.

Could you tell me version of OS X and NoMachine are you using?

[graywolf]

Hello.

It’s likely that the Win key state is stuck to “pressed”, so that the resulting combo are Win+plus and Win+minus: these are the shortcuts for the Magnifier app in Windows 10. When you are remotely connected to wht Windows 10 box, press right and left Win key once, in order to restore the “released” state.

 

[graywolf]

Hello. One of the following actions will help:

1. Try also “Fit to window”.
2. Try to switch on/off the checkbox “Change the server resolution to match the client when I connect” in the dialog you see just after the session is connected (see image).
3. In the remote desktop, use Display Settings to change resolution
4. or open a terminal and use command “xrandr” to see the available resolution and set the preferred one.

Attachments:

1. 

   resolution.png
   

[graywolf]

Hello indy2005.

If you are asked only for password, is very likely your user belongs to the administrators’s group. So just typing your password should work.

If it didn’t, check the “sudoer” abilities of your user by the command “sudo -l”.

RPM installation doesn’t set any default password.

 

[graywolf]

Hello vnaipaul.

and after adjusting paths in the NX files

The installation doesn’t require any manual tweak that conversely could break something.

So my advice is: uninstall NoMachine completely, remove any NX directory left around, install again with rpm –prefix /opt/nomachine.

[graywolf]

Hello.

I guess the Windows box has a keyboard with numpad embedded in the alphabetical keypad and that NumLock was activated. In such situations some letters are mapped onto numbers, typically:

• M -> 0
• J,K,L -> 1,2,3
• U,I,O -> 4,5,6

Turning off NumLock should help.

 

[graywolf]

Hello.

Please send the whole /usr/NX/var/log directory to the email address forum (at) nomachine (dot) com along with the output of commands:
sudo -l
sudo getent group | grep your_user_name
sudo getent passwd your_user_name

[graywolf]

Thanks, I’ll try this.

You’ll receive instructions by mail.

[graywolf]

Hello. Do you mind trying an experimental version? It would help to gather information useful to solve this issue.

Please email to forum (at) nomachine (dot) com to receive the package.

[graywolf]

Hello Gregory,

it is possible that a modifier key got stuck. If that issue occurs again try to press and release all modifiers (right and left Ctrl, right and left Shift, right and left Alt, AltGr if exists) one by one and see if mouse comes back to normal.

[graywolf]

Could you attach folder /usr/NX/var/log from the Raspberry server?

[graywolf]

It seems the right way for settng keyboard on that distro is the command

dpkg-reconfigure keyboard-configuration

Let me know if it helps.

[graywolf]

Could you confirm that you are running NoMachine version 4 or 5 as a server?

Did the problem arise connecting to a physical display?

I think you have to set the keyboard layout in the remote desktop environment. In Gnome the configuration is somewhere under “System”, “Preferences”, “Keyboard”, tab: “Layout”, precise location depending on version.

 

Attachments:

1. 

   Layouts.png
   

[graywolf]

Client simply gets the keyboard currently set in the local system. It is possible you need to change keyboard layout in the desktop you are reaching from remote. Could you describe the actions that made you notice keyboard wasn’t correct?

[Author]

Posts