Forum Replies Created
-
Posts
-
Hey there!
Please try this: when you want to disconnect from the server press Control + Alt + T (or click the small shutdown icon in the menu) and check the box “Remember current window size and position” before selecting the Disconnect or Exit action. When you will use the same connection file, the client will restore the window geometry.Could you try the option ‘-geometry’ (single dash) with the same format? As X client, the nxplayer also supports X11 command line options.
in particular nxplayer window starts in the right position but it moves to another.
What is the position of the second window move? Is it always the same? I’m wondering if the Window Manager could move the window for some reasons.
– If player is started in the full screen (use full screen resolution to set)
– if player is started in window mode disable that function/ or use window resolution to send.What you are proposing is exactly what the option “Resize remote screen” does.
If you want to pre-configure your clients in order to disable “Match resolution” option and enable the “Resize screen” option, you could create a template connection file (NXS) and distribute it to your users.
Identify these keys in the connection file and change their values accordingly:<option key="Resize the remote screen to the local geometry" value="false" /> <option key="Enable session auto-resize" value="true" />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.
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.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?
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?
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.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.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?
Hi. Thank you for sending logs, we’ve identified a possible problem and we’ll follow up soon with a testing version.
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?
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?