Forum Replies Created
-
Posts
-
We aren’t aware of issues with taking an excessive amount of time to log out. We had one occurrence of a session taking 10 secs to log out but there were many applications open at the time. How many applications do you have open at the time of log out and what are they?
See here:
Drag and drop is not supported with Wayland desktops
https://www.nomachine.com/TR02P08427It’s not clear to me what the problem was that you were encountering in the first place, but if you considered the “issue” resolved, that’s fine. I requested logs because I was under the impression that you were seeing a “waiting for desktop to authorise” message despite 1) logging in with the same username and 2) you had followed the advice of Mth in the topic you mentioned.
I mentioned “security risk” which is taken from Mth’s original answer to the topic that you were quoted at the start of this thread: having an unwanted user attach to your desktop without your permission is not what most people want. So the desktop owner has a choice to accept or refuse. Of course, if you trust the user with your username and password (you are the owner), then that’s entirely your choice and not under discussion here.
Maybe you should have a look at the Security section of the Server Guide document in our Knowledge Base.
If you continue to see behaviour which doesn’t match what you’ve set on each server, please open a new topic: https://www.nomachine.com/DT10O00155#2.2.At NoMachine we want our users to be able to connect to and use any desktop environment they want, we don’t like to discourage 😉
Gnome and KDE are the most commonly used Linux desktop environments amongst our users. Then there are “lighter” choices which we also support, browsing the knowledge base is testament to that, and are becoming increasingly popular. See these for example:
Desktops environments supported by NoMachine
https://www.nomachine.com/AR10K00725Setting a lightweight desktop environment on Ubuntu 11.04 or later (there is also an article for Fedora)
https://www.nomachine.com/AR07K00676We prefer to let our users choose their own DE based on their own tests and general preferences. We publish benchmarks in or knowledge base (not for all DE, but the most common ones). For example,
Guidelines for sizing a NoMachine infrastructure and benchmark tests for v. 6
https://www.nomachine.com/AR02P00966Performance all comes down to what you are using on the physical machine. For example, 3D graphical effects (e.g. shadows, animations, fading menu etc..) perform better on hosts with a capable GPU (Graphics Processing Unit) but are made available also on those machines without a GPU. In this case software rendering is done on CPU instead on GPU. This process is CPU-intensive and does require sufficient CPU power for a good experience. A lightweight desktop like Xfce or Mate is less resource intensive and will help to reduce the CPU load. You can find some examples for installing and running an alternative desktop here: https://www.nomachine.com/AR04K00667
It seems strange that all those NoMachine servers are presenting the same problem. As Mth wrote in the topic that you mentioned, the default behaviour (and provided the configuration files have been messed with):
1. When there is Login Window, you can connect with any user without prompt.
2. When there is a user desktop logged (User A), you can attach as the same user without prompt. (To UserA’s desktop)
If you enter different credentials in NoMachine player (UserB), you are not desktop owner, there could be a potential security risk involved, so UserA will see the prompt and consequently decide whether to authorise or not.
Since we are not able to reproduce the problem, I suggest you increase the debug level in the logs of one of the affected host machines (let’s say from one of the x.org hosts) and send them to us and we will take a look. For now you can continue to run the earlier version of NoMachine. Instructions are here:
https://www.nomachine.com/DT10O00163
Enable debug on the server machine and then do:
sudo /etc/NX/nxserver --restartThen please gather logs either manually or by executing:
sudo /etc/NX/nxserver --debug --collectPlease send the logs to forum[at]nomachine[dot]com using the title of this forum’s thread as the mail’s subject.
There are two known issues with audio on Mac. You can also find a number of topics specifically related to audio on macOS in this forum.
Two trouble reports are these:
https://www.nomachine.com/TR05R09720
https://www.nomachine.com/TR06R09774There are workarounds so I advise you to try them.
In terms of what you get in the free version vs Enterprise Desktop (its pay-for equivalent) multi-media is available in both. What you don’t get in the free version is browser-based access and SSH support. You can compare them here: https://www.nomachine.com/remote-access-for-everyone
Purchasing subscriptions rather than use the free edition means you get technical assistance plus any hot fixes which are available but haven’t been released yet. I’m not sure what you mean by mixing OSes. A license for Windows cannot be used on a Mac host if this is what you mean. If you have two computers that you want to remote in to, and one is Mac and one is Window, you need two licenses.
The file you tried to attach may have been too big, please submit to forum[at]nomachine[dot]com making sure to use the title of your topic as the subject.
We are still not able to reproduce this problem and the logs you submitted were not complete. Either you didn’t enable debug or they are not from the Xubuntu server host. (the quickest way to enable logs: https://www.nomachine.com/DT10O00162)
Additional details which are also asked in the other topic are require as well:
Which desktop environment and desktop manager are being used?
Is it a physical machine or a virtual?
Is Wayland being used for login window or/and desktop on the Xubuntu host?And you confirm that uncommenting ‘WaylandEnable=false’ on /etc/gdm3/custom.conf didn’t work?
Which topic is marked as solved? I thought maybe a topic that you submitted previously but you haven’t submitted any topics prior to this one. Please provide a link so we can understand what issue you are referring to.
What Linux distro are you connecting to, what version? Is Wayland running there or Xorg? You say that on NoMachine version 6.11 you didn’t have this issue, have I understood correctly?
We haven’t been able to reproduce this at all. Please send us a screenshot from the Advanced Power Settings plus logs from the affected Windows server host. Please see here for instructions on where to find logs.
https://www.nomachine.com/AR10K00697
Submit everything to forum[at]nomachine[dot]com making sure to use the title of this topic as the subject of your email. Thanks!
Thanks for taking the time to report this. Support for macOS on ARM isn’t available yet, although we are currently working on NoMachine compatibility with this architecture 😉
Sway desktop is not detected and as a result NoMachine can’t attach to it to display it (hence you see nothing).
A better workaround would be to put the command you are using in the node.cfg file instead. That way it would be automatic and you wouldn’t have to launch ‘vncviewer -fullscreen localhost:0’ every time you connect.
Try defining it in DefaultDesktopCommand in the NoMachine’s node configuration file.