Forum Replies Created
-
Posts
-
This is related to Fedora’s use of Wayland.
Please see the following Feature Request which documents adding support for Wayland: https://www.nomachine.com/FR10N03221.
Until we add support for Wayland protocol you should disable Wayland in the gdm configuration by adding the following key in /etc/gdm/custom.conf:
WaylandEnable=false
I don’t know what version you have installed. You say 2016 – does this mean it’s v5?
From version 4 onwards the free version of the NoMachine software allows access to the physical desktop of the remote host (1 connection).
If you want to run 2 instances of the Linux environment on the same host you need the Workstation installed. You can download this from the website as an evaluation here: https://www.nomachine.com/download-enterprise#NoMachine-Workstation.
We use Microsoft’s DXVA and DirectX 9 APIs for hardware decoding acceleration on Windows platforms. The problem you’re having is that this function from DX9 returns to us invalid values of frame stride. Without the correct value we can’t process frame and therefore this crash happens. You can switch to software decoding by setting key “Enable hardware accelerated decoding” in player.cfg to “disabled” – in this case by default you’ll be using VP8 decoding, unless you follow steps in article https://www.nomachine.com/AR10K00696 or buy AVC Pack to enable H264 software decoding. Other possibility would be to update graphics drivers and DirectX. Also make sure you don’t have any custom DirectX libraries in your system in default paths that could be loaded instead of original ones.
The logs were probably too big to be accepted. Submit them to forum[at]nomachine[dot]com. Make sure you include the link to the topic.
Please also provide some further information about the client OS you are using and what is on the remote host you are connecting to (distribution, version, NoMachine product, see ‘What to include’ below).
Thanks
If the lssas.exe process is working in protected mode one, possible workaround is to configure antivirus software, so that it doesn’t enable additional security settings in Windows. In AVG it’s possible to check ‘Disable antivirus self protection’ option.
Other anti-viruses can have a different name for this setting. In the worst case scenario, the user needs to completely disable/uninstall antivirus software.
There is a new TR related to the recent findings above. Please sign up to know when a fix has been released using ‘notify me’.
There is a Trouble Report which we have open on this issue: https://www.nomachine.com/TR03O07676. Please sign up to know when a fix is available with the ‘notify me’ option.
‘BaseDirectory’ represents the folder where the application gets installed. On Mac, this is usually Applications.
Please consult the following article for instructions on how to enable logs.
https://www.nomachine.com/DT07M00098
Reproduce the issue and send us <home_directory>/.nx, /usr/NX/var/log and /etc/sssd/sssd.conf.
You can also check the content of /var/log/secure or /var/log/auth.log (depending on distro) for entries suggesting authentication failure.
Hello, we’ve not been able to reproduce on Gentoo, using SSH port set to 222 and by setting the same rules in iptables. What I suggest is you update to 5.3.9 and see if the problem persists and let us know.
Fixed in version 5.3.9. See:
Black screen occurs when connecting via web with WebRTC enabled
https://www.nomachine.com/TR05O07747Please update.
Thanks for the feedback 🙂
NoMachine is compatible with Nougat tablets. The app you find in the Play store is for Android tablets but not optimized for phones which is the reason why you see the desktop cut off on the sides. If you install it on a tablet, you’ll see that the sides aren’t cut off at all. We’ll update the app’s page to make it clearer that phone users should come to our website to download the app.
An app for smartphones is planned and will be released as part of the NoMachine 6 branch, so look out for that. It’s coming soon!
https://www.nomachine.com/FR12M02991, on the other hand, is still under evaluation and hasn’t been inserted in to the roadmap yet – let’s get version 6 out first 😉
What with the great variety of desktop environments available for Linux hosts, a certain desktop may not run out-of-the-box. Moksha is not a common DE amongst our users which favour predominantly Gnome, KDE, XFCE, LXDE, Cinnamon. It’s impossible for us to test all distros with all possible DE flavours available.
With regards to the comment about updating – our choice by design was to use our own upgrade servers and protocol, or for those who don’t want to update from our own servers, there is the possibility to download the package from our website and launch the usual procedure for updating Linux packages.
We tested that installing the package from our website installs correctly. We’ll investigate further with the software updates method.