Tor

[Tor]

Hi Martin.
You can open the Display menu by pressing Control + Alt + 0 and by clicking the Display item.
In order to know if your window manager can be configured to show thick window borders we’d need to know the operating system version running on the server, as this is a system configuration.

[Tor]

Hi. We have a similar issue documented here:

https://www.nomachine.com/TR10Q09439

During our tests we’ve found this issue occurs when Sticky Keys are enabled on Windows, could you please verify if that is your case? The configuration can be checked in Settings, Ease of Access, Keyboard, Use Sticky Keys.

[Tor]

Hi. Is the ‘Scale to window’ option enabled in the Display menu? If the remote desktop is being shrinked in the window, grabbing a window edge could be difficult if the remote window manager has a tiny sensitive area since it’ll be reduced even more by the scaling down effect. If this is the case you could disable the scaling mode, or configure the window manager to show bigger window frames.

[Tor]

Nothing changed between my initial report and now.

So far we could not reproduce the issue you’re describing, with the Gnome configuration I’ve suggested above. Could you contact us at forum[at]nomachine[dot]com, so we could send you a client automatically dealing with the compositor requests in order to exclude some trivial problems?

[Tor]

Thank you for your feedback. Would you like to tell us the name of the Antivirus and the version, so we can contact them to discuss the issue? If you can’t publish the name here feel free to contact us to forum[at]nomachine[dot]com.

[Tor]

Hi. Open the Display menu bar and verify that “Scale to window” is NOT selected, because that is generally the reason why you see some stretching. You should select “Enable viewport mode” and choose in Display settings the same resolution of your client display, so when going fullscreen you’ll have a perfect 1:1 ratio. Let us know if this helps.

[Tor]

Hi. Please open the Console application from Utilities menu, select “User Reports” on the left column and click on the most recent file in the list on the right that has prefix “nxplayer_”. Right click the selected file, choose “Reveal in Finder” in the context menu, then send that file to forum[at]nomachine[dot]com.
Confirm here if there are no files with that prefix, so we’ll discuss another way to debug your issue.

[Tor]

Hi. Could you send here the output of the command xrandr -q executed in a terminal on the virtual desktop?

[Tor]

The client is not swapping keys between Linux and macOS, so if you want to send Command + C you’ll have to press the keyboard button corresponding to “Command” on Mac (for example on a Windows keyboard it would be the Windows button). Can you confirm you’ve used shortcuts in this way?

[Tor]

I tried it in fullscreen, windowed, another monitor, virtual desktop, with grab and without grab.

You NEED keyboard grabbing if those shortcuts are being used by the local system. 🙂
You’re probably using Wayland, this is the reason why it is not working. The problem is documented here:

https://www.nomachine.com/TR10P08952

Since you’re using GNOME you can try the following workaround:

1. Enable input grabbing in Wayland

gsettings set org.gnome.mutter.wayland xwayland-allow-grabs true

2. Print the whitelisted applications

gsettings get org.gnome.mutter.wayland xwayland-grab-access-rules

3. Append ‘nxplayer.bin’ to the existing application classes. “App A” is an example, your whitelist could be empty so you just need to add the player

gsettings set org.gnome.mutter.wayland xwayland-grab-access-rules "['App A', 'nxplayer.bin']"

4. Launch the player by enabling the active window grabbing

/usr/NX/bin/nxplayer --activegrab

[Tor]

Hi. Can you please verify if shortcuts are correctly forwarded when NoMachine client window is fullscreen? Don’t forget to enable keyboard grab option, it is required to catch also shortcuts used by your Linux system.

[Tor]

Hi.

NX 7.4.1 as many other 7.x release binaries shows problematic reliability on Linux.

We’re not aware of reliability issues on Linux, so it would be great if you can share your experience.

On this machine [ ubuntu 20.04 LTS ] there is a consistent high CPU load for /usr/NX/nxclient.bin –monitor –tray

Ubuntu 20 is one of our most common Linux testing environments, we would have noticed an obvious problem. Do you mind collecting the following information and sending it to forum[at]nomachine[dot]com :
– Directories with prefix “M-” in $HOME/.nx directory of the machine where nxclient.bin takes too much CPU
– File top.txt created with the command top -b -n 5 -H -p $(pgrep nxclient.bin) > top.txt (it’ll require a few seconds to dump the data)
– File strace.txt created with the command sudo strace -o strace.txt -tt -p $(pgrep nxclient.bin)

If you’ve multiple nxclient.bin instances but only some of them have high CPU load, replace the “pgrep nxclient.bin” command with the PID of one of those instances.

Looking at the binary there may be issues with dependencies for yet unclear reasons.

The NoMachine libraries path is not in the default search path for dynamic linker, so if you want to print all dependencies you need to run LD_LIBRARY_PATH=/usr/NX/lib ldd /usr/NX/bin/nxclient.bin.

[Tor]

Hi. The crash you reported is pretty weird and occurs in an unexpected call, so since you can easily reproduce it could you verify if there are other crash reports under /var/crash and extract also those stacks?
Reading logs would be very helpful as well, you can compress your $HOME/.nx folder and send everything (logs and stacks) to forum[at]nomachine[dot]com.
Thanks.

[Tor]

Hi. You could be using a NoMachine server discovered in LAN. In such a case connection settings are stored in a cache and there is not a connection file in the Documents/NoMachine folder.
You could Edit such server entry, copy the IP and the Port, then go back and click the Add menu button to create a new connection with those same IP and Port. After you create this new connection file you can either use the Machines context menu to create a copy in another location, or create a shortcut to that file with Finder (right click, Make Alias).

[Tor]

Hi. Version 7 introduced a big overhaul of the graphical user interfaces, and among those changes the proxy settings were moved from connection to client configuration. We understand your need, however adding also the configuration of the proxy in connection settings would be slightly confusing and impact the usability improvements we did to cover the most generic user needs.
You could try a different solution not requiring to edit connection files, by using the client command line option --config to select a custom configuration file. Configure the proxy and rename the file %USERPROFILE%\.nx\config\player.cfg (Windows path) for every configuration you need. Create a shortcut by copy-pasting the one created by default on desktop, edit properties of the new shortcut and add the option --config C:\Users\<username>\.nx\config\<config filename>.cfg to the Target field. You can name the shortcut to identify the proxy configuration and use it. This is the procedure for Windows, but on Linux and Mac it’s very similar.

[Author]

Posts