Forum Replies Created
-
Posts
-
Sorry, maybe I wasn’t clear. What is the macOS version where you have installed the NoMachine software?
Explaining why a session was suddenly closed requires a proper investigation based on logs and a backtrace.
You haven’t said what distro and version it is (I’m assuming Linux on the server), what the user was doing when the session suddenly closed, what the user was connecting from and so on. Is this connecting to a free NoMachine installation or a Terminal Server?
Logs can be found by following these instructions.
https://www.nomachine.com/AR10K00697This is not our login – it’s a system login. So for example you need to look at the Xubuntu manual on how to set auto-login.
Did you follow these instructions?
NoMachine’s own default settings should be suitable for the majority of environments in order to obtain optimal performance. Forcing specific settings for fine-tuning of the performance and display quality usually requires a proper investigation first. Changing node.cfg and server.cfg settings risks introducing unexpected behaviour and I think the NoMachine Support Team is able to suggest the most suitable configuration for these special cases if you are trying to set up your own commercial environment.
Associated reading:
The ProxyExtraOptions and DisplayServerExtraOptions keys in the node configuration file
https://www.nomachine.com/AR02N00877The server.cfg and node.cfg files explained
https://www.nomachine.com/AR02N00877You can also search these forums to see in what specific cases these keys have been modified.
It’s slightly more complicated 🙂
There are a number of issues with NoMachine on Arch-based distros which we have currently queued up for investigation. We will update this topic soon.
NoMachine work perfectly on all of them when on any other based distro (Debian, redhat,etc..) or Windows.
Debian, Red Hat, Fedora, Ubuntu, Suse are those distros we officially support so NoMachine must work out-of-the box 🙂 To be honest, Arch is not in the list of officially supported distros. There are so many Linux distributions and desktop variations for any possible Linux distribution that, even if we were willing to support them all, it would be an impossible task.
At the moment drag and drop is to the desktop only. We are, however, evaluating the possibility of dropping to the folder where it is being dragged to, but it hasn’t been confirmed as part of the development roadmap yet.
Can you confirm which Windows version(s) and is this Windows to Windows?
Can you show me a screenshot of what you have set on the remote laptop is Transfer preferences in both Player and Server?
https://www.nomachine.com/DT10O00154#2.3 e https://www.nomachine.com/DT10O00154#3.4
By window server I think you mean display server 🙂
It’s not clear what’s slow exactly. Is typing only slow with NoMachine’s only display server? What version of Kubuntu are you using?
Inotamira, provided you are using Arch on Xorg and not Wayland, you could submit logs as Mth wrote just above. This topic is specifically related to Arch on Xorg. If you’re using Wayland or another distro, you should open a new topic.
loulou921222, please submit the logs as requested.
I’d like to add at this point that Arch is not one of the officially supported distros which are Ubuntu, Fedora, Red Hat (and CentOS), Debian, Suse (and OpenSuse). The official list is here: https://www.nomachine.com/AR07H00568. Having an “officially supported list” doesn’t mean we won’t investigate and fix NoMachine-related problems are sometimes brought to our attention on other Linux flavours, such as this one with Arch on Xorg 🙂
As this article states: https://www.nomachine.com/AR11K00740
“Troubleshooting X problems can be complex. Troubleshooting desktop environments can be complex.”Maybe you should take a look at your other topic https://forums.nomachine.com/topic/collect-logs-automatically-and-plug-it-to-elastic-search
The problem is related to Wayland and GDM and it’s a known issue. You can see the Trouble Report which is in status ‘Open’:
Cannot connect to the physical desktop of Ubuntu 18.04 (Error 108)
https://www.nomachine.com/TR10P08935Using LightDM as an alternative is possible or the workaround we included in the TR.