Forum Replies Created
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.November 6, 2020 at 08:44 in reply to: 5 seconds lag when running Kubuntu with built in window server #30244
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?November 5, 2020 at 18:56 in reply to: NoMachine nxplayer will not launch for Win 10 install #30239
Please send any attachments to forum[at]nomachine[dot]com. Thanks!
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)
Using LightDM as an alternative is possible or the workaround we included in the TR.
NoMachine supports syslog timestamp format. You can define syslog timestamp format according to your own preference 😉
How does NX support multiple monitors? I discovered the client can switch between two different monitors or display a concatenation of the two screens on the remote machine. Does NX support mapping each remote monitor to local monitors at the same time?
This capability is planned for the future.
Making it possible to treat multiple monitors connected on the server as separate windows on client side
I am seriously tempted to deploy a bunch of rpi4 systems for the work-from-home crowd with preconfigured NX and VPNs, it may not fly non-technical users.
We have packages available for RP 🙂 Please make sure you read the article here to see which models we have tested and with which distributions: https://www.nomachine.com/AR07N00896
An alternative would be some form of application gateway that the user could connect to and have their NX connection relayed to the remote machine.
Our gateway option, Cloud Server, is geared towards organizations with large numbers of users, so is probably overkill for what you need. We don’t currently have an option to cater for smaller groups or private users which want to centralize access for a small number of users.
If you’re looking for a remote desktop solution to get your users carry out business-related activities, you should look at Enterprise Desktop which is installed on the remote computers you want to access. Users can just install the free NoMachine version or the Enterprise Client package on their connecting devices. If you need a quote and pricing based on volume, please contact our sales team by submitting a Contact Request via the footer of our website.
We received link to logs, thanks.
You didn’t get back to us on whether you were still encountering the issue with the server still running despite having turned it off via the GUI. If you are still encountering the problem with the latest version 6.12, please open a new topic.October 29, 2020 at 17:53 in reply to: White screen when logging into Catalina client prior to client login #30133
We didn’t receive any further information from you so I have closed this topic. I advise you to update to the latest version and open a new topic if you encounter the issue again.
What distribution are you using?
The term “virtual desktop” in NoMachine refers to the Terminal Server products. Maybe you are referring to virtual desktops as the VMs where you have installed Enterprise Desktop?
Enterprise Desktop (version 6) is for access to the physical display, and when the host is headless (no local X server found) NoMachine creates a “virtual” one using its own embedded X server.
I think you know about these already, but I’ll paste them here for other readers. The following keys in the server configuration file allow for managing the behavior of the server when it needs to create the X11 display:
# Enable or disable the automatic creation of an X11 display when no
# X servers are running on this host (e.g. headless machine) to let
# users connect to the desktop. This setting applies to NoMachine
# servers not supporting virtual desktops and permits to have one
# single display.
# 1: Enabled. NoMachine will create automatically the new display at
# server startup. This setting has to be used in conjunction with
# ‘DisplayOwner’ and ‘DisplayGeometry’.
# 0: Disabled. NoMachine will prompt the user for creating the new
# display. This is the default.
# When ‘CreateDisplay’ is enabled, specify the display owner and let
# NoMachine create the new display without querying the user. If the
# server supports only one concurrent connection, the connecting user
# must be the display owner set in this key.
How do I fix this?
Questions about how you should configure your Ubuntu system and SSHD would be better off in the Ubuntu forums 😉
And shouldn’t the NoMachine installer fix this on installation?
How would NoMachine be able to do that if it doesn’t know a priori exactly what you did to your system and how you did it? Besides the fact that altering a systems configuration during installation would be unacceptable to most users. NoMachine adapts to what the system’s configuration is set to do when it is installed.
BTW, just a note on SSH support in the free version should you wish to connect using SSH once you’ve fixed your system’s configuration; the free version supports connections via NX. If you want to connect using SSH, you should try the Enterprise Desktop product.