Tor

[Tor]

Hi Werner.
You can track this Trouble Report to know when we’ll release the fix:

https://www.nomachine.com/TR11P08966

Thank you for the kind help in identifying it.

[Tor]

Hi Angela.
What is the complete command you’re using to launch the nxplayer?

[Tor]

Hi. Thank you for sharing further information.
The option you’re mentioning is useful if you want to work with fullscreen window. If you plan instead to just use windowed mode and since you’re creating a virtual desktop, I’d suggest to enable the option “Resize remote screen” in the Display menu and to check the box “Remember current window size and position” in the Disconnection panel.

[Tor]

Hi Werner.
There is a known problem with drag&drop on Wayland:

https://www.nomachine.com/TR02P08427

While checking your report we’ve also found a similar issue occurring when running a custom command in a virtual desktop (we’re still investigating it).

Could you please confirm if you’re using Wayland or a custom session running in a virtual desktop?

[Tor]

Please let me know if I’m clear with the example.

Yes, thanks. Just two more questions:

1. Did you evaluate using guest users? They would allow to automatically create a new user for each client connections, environment would not be shared among them (different home directories) and your script would be easier.

2. Do users need to suspend and restore sessions, or when a user disconnects the session should rather be terminated?

[Tor]

Hi.
Could you describe those scenarios with more details please? By having more information we could better understand your needs and evaluate if available NoMachine server configurations could help, or plan features offering new possibilities.

[Tor]

Hi.
Can you verify if your Windows server supports the resolution 1378×764? You can find the list of available geometries in Windows display settings. It would be great if you take a screenshot of the combo popup listing them.

[Tor]

Hi Mick.
You can prepare a configuration file template, customize it through AppleScript and open it to execute NoMachine client.
Start the connection wizard by pressing the ‘New’ button and create the default configuration. You’ll find it in the Documents/NoMachine folder.

These are the fields you’ll need to customize:

<option key="Server host" value="%IP%" />
<option key="Session" value="unix" />
<option key="Desktop" value="console" />
<option key="Custom Unix Desktop" value="application" />
<option key="Command line" value="%SCRIPT%" />

%IP% is the IP or hostname of the server, while %SCRIPT% is the command or sequence of commands to execute on the server.
After you create the temporary connection file with such configuration, use it with this command:

open <path to the NXS file>

Is that enough or you would like to customize more options?

[Tor]

Hi. Thank you for sending logs, we’ve identified a possible problem and we’ll follow up soon with a testing version.

[Tor]

Hi. Keep Control and Alt keys pressed while resizing the window, you’ll notice the new size strictly follow the server’s geometry ratio. Is that helpful?

[Tor]

Thanks. If you didn’t change the connection policy on the server, the client will already select automatically the running virtual desktop assuming that (a) the connecting user is the owner of the session, (b) the name of the current session (the one you see in the main client interface) is the same of the one running on the server (the one you see in the list of running desktops) and (c) there is only one session with that name running on the server.
Can you confirm if all those conditions are met?

[Tor]

Hi.
Is the ‘active’ session a physical or a virtual desktop? What is the NoMachine product running on the server? Are you using latest NoMachine version?

[Tor]

NoMachine can’t possibly know all the GTK theme names someone may use and then guess if light/dark would look better?

What you suggest is what NoMachine does, but there is a problem causing the theme to be incorrectly parsed in your environment. We’ll fix it soon.
In the meanwhile you can work around the issue by replacing the red icon with the dark version:

sudo cp -a /usr/NX/share/images/tray-ubuntu.png /usr/NX/share/images/tray-linux.png
sudo cp -a /usr/NX/share/images/tray-ubuntu-faded.png /usr/NX/share/images/tray-linux-faded.png

[Tor]

Disabling client side post processing is a side-effect. Doing it always improves the performance a bit. In fact, among the other things, we are working on a better deblock filter. Despite this, the issue you are facing is a specific macOS problem occurring on monitors supporting wide color gamut. We’ve identified the operation wasting the CPU time and we will shortly release a fix for it.

[Tor]

I have the same problem on macOS 10.14. Not so bad because I can just start NX manually, but still.

Hi. Your problem may be a little bit different, so we’d like to check also current server/node logs. Please run the following commands in a Terminal window:

cd /Library/Application\ Support/NoMachine/var
sudo tar -czf NoMachine-log.tar.gz log

Compress as well the log of the failed process I see in your home directory:

tar -czf nxclient-logs.tar.gz ~/.nx/F-M-*

Thanks!

[Author]

Posts