Tor

[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!

[Tor]

Hi. NoMachine selects the icon color depending from current theme. Please send here the output of the following command executed in a terminal window:

gsettings get org.mate.interface icon-theme

 

[Tor]

Hi. We’re not aware of such an issue, but it would be nice if you could contact us on forum[at]nomachine[dot]com to receive a client debug version. It would be helpful to collect some data in order to understand why the client cannot match the server stored settings.

[Tor]

Hi there, I am having this same problem. Please see attached image.

Hi. Could you kindly execute this command in Terminal (located in Applications => Utilities) on the machine where you don’t see the icon?

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

Send to forum[at]nomachine[dot]com the TAR.GZ archive. We’d like to check if you’ve problems with the image file. Thanks.

[Tor]

Hi.

Would it be possible in future to develop a NoMachine Android app that utilizes all available screen space?

Current version already implements immersive mode (the way to use the full screen area), but we had to disable it because it was causing issues with positioning the extended keyboard. Unluckily Android doesn’t offer a programming interface to know the geometry of the virtual keyboard, so we had to find solutions based on application layouts which clash with immersive mode. We’ll release a version addressing the issue very soon, so immersive mode will be available again.

[Tor]

Hi Larry. Thank you for sharing more details about your environment. The smaller window size is caused by the scaling of 125% you’re using on that monitor. You could verify this workaround:

• Right-click the NoMachine User Interface shortcut and select Properties
• Select the Compatibility tab
• Check the box “Override high DPI scaling behavior”
• Select “Application” from the combo under “Scaling performed by”

 

[Tor]

Hey Larry! Could you please check if your display is configured to use 100% of available physical area? You’ll find it in Windows Settings => System => Display.

[Tor]

Hi. We’re working on a version allowing to configure the authentication through SSH agent and better handling multiple factors. There are still some doubts about what to show to users and how to retrieve correct information, I’ll try to pack a testing version as soon as all changes will be completed.

[Tor]

Hi. We’re happy to know your experience on Chromebook! We’ve done many fixes and specific changes to support correctly Chrome OS and will keep doing it because, as you said, it’s a great opportunity for remote working.

We’re currently working on improving window initial size and resizes, and we’d like to do something for cursor images, but unluckily Android doesn’t offer easy and reliable ways to do it. As workaround you may enable showing the remote cursor.

About the mouse wheel, did you maybe notice if the experience is the same with multiple mouse models?

[Tor]

I’m surprised your authentication works! 😀 We don’t officially support a three-factor authentication, so I’m sure there is a lot of space for improvements. We’re doing tests in our labs to identify problems and required changes, I’ll send you an update as soon as we complete the investigation. Thank you for sharing your configuration. 🙂

[Tor]

Hi. What are connection details not correctly saved? Do you configure those connections with the wizard, or do you use the servers automatically discovered in LAN?

[Author]

Posts