Forum Replies Created
-
Posts
-
Hi everyone, the patch hasn’t been released yet. When a new version of a major Linux distribution comes out, it needs to go through our quality assurance procedures to check compatibility and potential usability issues, such as the one described in this thread. We generally need at least a month in order to officially add it to our list of supported list. This gives us the time to test thoroughly and eliminate problems.
Until then, the best alternative is either to use virtual desktop sessions (if you are using Workstation), or use another GUI such as KDE, Unity, XFCE, LXDE or another if that’s possible.
The Trouble Report is here https://www.nomachine.com/TR11M06188.
When the fix has been officially released you will receive a notification. Just check the ‘notify me’ box and leave your email address.
If you haven’t already done so, please update to the latest version. A fix was released in NoMachine 5.
This looks similar to a bug we found in our internal tests and for which we have implemented a patch (not released yet). But to make sure, can you tell us who the owner of the session is? You can see this info in the session list once you’ve authenticated e.g User ‘nomachine’.
Attachments:
I think Fra81 meant to point to this: https://www.nomachine.com/getting-started-with-nomachine and https://www.nomachine.com/getting-started-with-nomachine#internet
I just made a quick test from Android client to the latest NoMachine 5 installed on Ubuntu 14 and don’t have any problem. I see the system’s login screen. Have you tried the latest version? It might be a good idea to send us logs. Follow the instructions here: https://www.nomachine.com/DT04M00076 send to forum[at]nomachine[dot]com making sure to reference your topic.
Please make sure you are using the latest version. If you are still having problems, you can check the logs by following the instructions in the article here https://www.nomachine.com/AR10K00697
Please make sure you download the latest version which we released last week. It contains the fix for the above TR.
The following information would be useful:
– NoMachine product on local and remote machine (free version, Workstation, etc).
– Whether the problem arises connecting to a physical or a virtual display.
– Remote and local Windows/Mac/Linux version (Windows XP/7/8, OS X 10.x, Ubuntu xyz, Mint x.y, etc.).
– If on Linux, desktop version (GNOME. KDE, whatever) on client and on server.Hi Sean,
there is a Trouble Report open on that: https://www.nomachine.com/TR10M06171
You can sign up to receive notification of its fix if you want. Just follow the link.
If you have a subscription with us then you should open a ticket in your customer area. If you are using the NX Free Edition from our legacy software, you can use the Contact Us link in the footer of the website below. Select General Enquiries.
I passed you a link to a document which describes the most common settings that administrators might want to pre-configure for their users.
https://www.nomachine.com/DT07M00094
This document goes into detail about .nxs and .cfg file options.Not all the entries of the cfg are mentioned because they are not meant to be interfered with because editing them can cause problems. That said, we understand that admins need to understand what options have changed and/or where to find them. For your custom configuration within your set-up, I would suggest you post your specific question to the support teams giving details about what you were setting in the legacy version and what you would like to achieve with the new version.
This TR has been opened and will be solved in a successive update of version 5.
I suggest you try version 5. Improvements for headless server users were introduced.
