Tor

[Tor]

Hi. We didn’t find conditions causing such an issue, global shortcuts are totally catched by the client when it has the focus, so we need more information to try understand what is happening.

• Let’s assume we define “client” the machine where NoMachine client is running, and “server” the machine where you connect with NoMachine, can you please explain the following sentence: “NoMachine switches the program on the server instead doing so on the client”. That sentence is the normal behaviour when grabbing keyboard is enabled, so there is something I’m still missing in your description.
• Do you work physically on the iMac where NoMachine client runs, or do you connect remotely to it?
• Did you notice if the problem occurs immediately after you switch locally to NoMachine client? e.g. you’re working on application A, then you switch to NoMachine client with Cmd + Tab and start doing Cmd + Tab to switch apps in the remote desktop.

Thanks.

[Tor]

This message is just to tell you that we’re still investigating the issue, we didn’t reproduce it so far so we’re analyzing possible problems. We may need to send you a debugging version, would you like to help us by running it?

[Tor]

Hi. It is not currently possible, but we’ll add it in future. Please subscribe the following Feature Request to be notified when we’ll release it:

Adding a new key in player.cfg to toggle ‘activegrab’ option
https://www.nomachine.com/FR05O03411

[Tor]

If you answer to my questions with questions we’ll not go far. 🙂 I’ve asked to check the “cache” subfolder, not only “.nx”. Also logs I’ve asked here can be helpful to understand what is happening, assuming there are no interferences (like something deleting the NoMachine cache, just to say).

[Tor]

I’m saying, that it is only randomly going to the remote desktop! In 80 percent it is still controlling the server side OS and does not get to the remote desktop!

Server side OS and remote desktop are the same thing. This is probably the reason why I don’t get what you mean. Are you maybe running NoMachine client remotely in another remote desktop solution?

By the way, so far attempts to reproduce issues with keyboard grabbing in our labs were unsuccessful. Maybe there is a 3rd party software interfering with NoMachine client, or there is a particular condition causing the misbehaviour.
We’ll need more information to run a deeper investigation, so please answer to the following questions:

• Is the issue occurring when switching any application, or only some particular applications?
• Do you’ve a single NoMachine client running, or multiple instances?
• Do you’ve 3rd party tools that may affect user input?
• Are you switching applications on different Spaces or Monitors?

Additionally it would be great if you could show the keyboard viewer (from Language OS X settings) and reproduce the issue while recording a video (for example with Quicktime Player).

[Tor]

From your client configuration file I see you’re probably using MDNS discovered servers, which confirms the reason why you don’t find files in Documents/NoMachine where only static connections are saved (connections that you’ve created with the wizard).
Settings for MDNS servers are stored in a cache, and they’re valid until the server doesn’t change its identity, like for example when NoMachine is uninstalled and installed again. You may pay attention to that to confirm if it occurs in that condition.
The other possibility is that the cache folder has bad permissions. Open Terminal and use the following command:

ls -ld $HOME/.nx/cache

[Tor]

Can you please send by e-mail also a screenshot of Folders tab from NoMachine Preferences?

[Tor]

Could you please send your client logs to verify if there is something wrong? Connect to your remote desktop and while the client is running open Finder, press Shift + Command + G, write “.nx” in the appearing dialog. Select the folder “config” and all folders with prefix “R-“, right click and select “Compress items”, then send the created archive to forum[at]nomachine[dot]com.

[Tor]

Open Finder, press Shift + Command + H to enter your home directory, press Shift + Command + G and in the dialog write “.nx” (without quotes).

[Tor]

Hi. You’re saying that when the grabbing keyboard option is enabled, the Cmd + Tab option goes to the remote desktop. This is exactly what the option is supposed to do. Can you please confirm the problem to be sure we’re talking about the same thing? 🙂
Also, for the investigation it is extremely important to know name and version of operating systems of client and server. Thanks.

[Tor]

Hi. You may have a problem with permissions of the folder where connection files are stored, by default in $HOME/Documents/NoMachine.

[Tor]

Hi. In order to disable the automatic viewport scrolling, edit the file $HOME/.nx/config/player.cfg and set to 0 the following key:

<option key=”Automatic viewport scrolling sensitive area size” value=”40″ />

There are currently no ways to move the viewport with shortcuts.

[Tor]

Hi. The option “Match the client resolution upon connecting” is stored in the connection file, so each time you create a new one it is set to default. You may distribute preconfigured connection files to your clients to disable the screen resolution change, or if you want to completely disable resize of physical desktops on a server, you may change the following key in the file server.cfg:

#
# Set the interaction level for the session connected to the physical
# desktop:
#
# 0: View-only. The session is connected to the desktop in
# view-only mode, i.e. the user can't interact with the
# physical desktop.
#
# 1: Restricted. User connected to the physical desktop can
# interact with the desktop except for resize operations.
#
# 2: Interactive. User connected to the physical desktop has
# full interaction with the desktop.
#
PhysicalDesktopMode 1

[Tor]

Hi. The client has no such possibility currently, but it may be an interesting feature. Would you like to share with us the reason why you need a borderless window? Thanks.

[Tor]

Hello. What you’ve discovered is correct, although you can make NoMachine client and locate pointer feature cohexist.
The setting helping us is “Grab the keyboard input”, but to catch this particular keystroke we need an additional command line option described in nxplayer --help:

--activegrab

When the setting ‘Grab the keyboard input’ doesn’t catch all keys, use this
option to force a different grabbing mode. The client will catch keys only
when the cursor is inside the window.

With this configuration you’ll be able to send the Ctrl key to the remote desktop, but of course the local cursor will not be highlighted when it is on the NoMachine client window.

[Author]

Posts