Tor

[Tor]

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.

[Tor]

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.

[Tor]

Hi Christian.
There may be something wrong, we’ll verify it. Thank you for the report. 🙂

[Tor]

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=true

[Tor]

Hi.
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.

[Tor]

You’re welcome Alex. 🙂

[Tor]

Yep, try to add the ‘–exit’ option and let me know if it does what you want.

[Tor]

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.

[Tor]

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”.

[Tor]

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.

[Tor]

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.

[Tor]

Hi Damian.
Your problem is very similar to the one described in this article:

The NoMachine file transfer tracking window becomes unusable on GNOME
https://www.nomachine.com/TR06M05637

A fix was released with version 5.1.54, so it would be great if you could upgrade your NoMachine client. Anyway you may try to work around the issue by unchecking the item “Show the transfer status” in the NoMachine tray menu.

[Tor]

Hi reesd.
Your remark is correct, even if the OS grabs the keystroke for its purposes we should be able to forward the Period key to remote desktop. There are some system shortcuts impossible to intercept, but Command-Period should not be among those because it generates a specific event delivered to the application. In order to track the issue we’ve opened this Trouble Report, you may sign up to be informed when we’ll release a fix:

The Command-Period shortcut is not correctly sent to the remote desktop
https://www.nomachine.com/TR01O07531

[Tor]

Hi efkan.
Thanks for your report. We correctly support the Indicator API (used on Freya with Ayatana, and on Loki through a plugin for Wingpanel), but we’ve verified the issue on Elementary and already implemented a fix. We’ll include it in the next release.
If you want to be informed when we’ll release it, you can subscribe to the following trouble report:

https://www.nomachine.com/TR01O07501

[Tor]

The list of resolutions looks to be correct. Did I understand correctly that your remote desktop now resizes to the correct resolution, so the xrandr configuration somehow got fixed? 🙂

[Author]

Posts