Forum Replies Created
-
Posts
-
Hi Alex. You can find options description here:
Command line options for the NoMachine client
https://www.nomachine.com/AR04O00923Hi. You can execute the NoMachine client with the command line option ‘–hide’, the main window will hide when the custom session starts and will show again when the session terminates. The option doesn’t affect other type of sessions, so you may consider to add it to your application’s shortcut.
Hi. At the moment a physical desktop cannot be automatically selected by storing it in the NXS file.
Hi Tobias.
We’re aware of this problem, it is documented here:https://www.nomachine.com/TR02L04268
The only workaround is disabling separate Spaces for displays. In order to avoid to scroll the window, you can enable the “Resize remote screen” option in the Display bar to tell the remote desktop to use the size of the window.
Hi.
Since the announce of Chrome OS supporting Android apps, we’re focused on improving our app to run flawlessly on Chromebooks. Check out this page to know if your model supports (or will support) Android apps so you can download NoMachine client from Play Store:https://sites.google.com/a/chromium.org/dev/chromium-os/chrome-os-systems-supporting-android-apps
We don’t have a native version for Chrome OS in our short-term roadmap, but if this will change in future we’ll announce it here and on our website.
Hi Gerhard.
There are multiple ways to have a shortcut pointing to your connection settings:– Click New in the client, and at the end of the wizard check the option “Create a link on the desktop”
or
– Copy on desktop the connection file, located by default in Documents\NoMachine
or
– Copy the connection file and paste it as shortcut on desktop
In all cases you can save the password in the connection file, if you don’t want to be asked again at connection time.
When you’re in the authentication panel the first time you connect, select the box “Save this password in the connection file” then click OK.
You may configure the client to automatically start when logging in the Ubuntu session. There should be an application like “Startup Applications Preferences” to configure autostarting applications, or you may configure it manually by creating the file ~/.config/autostart/nxplayer.desktop with the following content:
[Desktop Entry] Type=Application Name=NoMachine client Exec=/usr/NX/bin/nxplayer --session "path to the NXS file" --exit Icon=NoMachine Comment=NoMachine client automatic session X-GNOME-Autostart-enabled=trueHi.
The option “Grab the keyboard input” is the only way to send Cmd+W to the remote side. Please note the keyboard is grabbed only when the remote desktop is visible and active, so for example if you open the client menu and press Cmd+W, the window will close.Hi. I suppose you’re starting the NoMachine connection by double clicking on connection file. In such a case when the session terminates, the client goes back to the panel showing information about the connection you’ve just closed. If you want to get rid of it, you should select the button “Exit the player” instead of “Disconnect from the server” when you must close the player.
If this is not your case, can you please tell me how you start and close the connection? Thanks.Hi Brian.
If you’re running version 5.2, use the NoMachine tray menu to open the Server Status window. You’ll find the information you’re looking for.
If the version is older, you may need to use the button “Restore default settings” in the client settings window, because the welcome may have been hidden by checking the box “Don’t show this message again”.Hi. Connection configuration files are public and portable, you can use them from any devices. They’re stored by default in the Documents folder, there is a sub-folder called NoMachine. You can confirm the path (or change it) from Settings => Folders => Connections and Recordings.
Hi Christopher, thank you for the report. We agree, it’s not the right behaviour! 🙂 Could you kindly compress the most recent directory $HOME/.nx/R-* while the client is frozen, and send it to forum[at]nomachine[dot]com. We didn’t reproduce the issue in our labs, so your help would be great to speed up the investigation.