Forum Replies Created
-
Posts
-
Hi, our developers are working on that issue right now. A solution will be released in one of the upcoming maintenance releases.
We checked on the fly and didn’t reproduce your issue.
NoMachine service 8.4.2 -> do you have the Free Edition installed or something else?
If I connect directly to the computer everything works just fine.
Do you mean if you connect with NoMachine to the physical desktop everything works fine? Please clarify this point.
When I access the computer through NoMachine from a Windows NoMachine client
Are you connecting to a virtual desktop? Can you submit screenshots or a recording from session start to the point where you reproduce the problem.
We prepared an article which also includes a section on trouble-shooting AMD drivers, please take a look:
How to use AMD HW encoder with NoMachine on Linux platforms
https://kb.nomachine.com/AR02U01190and follow the tips there. Do they help?
If you’ve updated to the latest version and cannot connect (since the original problem is solved), please open a new topic.
Also, the logs that you sent us, from Sophia which you say is the client, do not contain the logs I requested.
2) on the computer you are connecting from, tick the box ‘Don’t delete log files on exit’ option enabled in Settings -> Player -> Security. Otherwise the client logs will be missing or only partial.
Hi, thanks for taking the time to report this. It’s a known issue which can be tracked here:
Cannot login by NX protocol and private key when option ‘Import the private key to the connection file’ is checked
https://kb.nomachine.com/TR05S10271We have had a similar case with another user also using an AMD GPU (albeit a different model). We’ve not been able to reproduce this problem with any of the test set-ups we have (and we have many!). We cannot say if you are experiencing the same problem, but we can give some pointers to check.
The first thing you need to do is make sure that the resolution is not higher than 1920×1200. Higher resolutions are not supported yet because of problems with some AMD drivers
Then make sure you have the correct drivers and that they were installed correctly:
The drivers can be found here https://www.amd.com/en/support/linux-drivers and to install, run
sudo apt-get install ./amdgpu-install_5.4.50401-1_all.debAnd after that:
sudo amdgpu-install --usecase=amfDoes this change anything?
By the way, your attachment (was it the server log?) did not attach, so send it to forum[at]nomachine[dot]com.
Please follow the tips in this article:
How to use AMD HW encoder with NoMachine on Linux platforms
https://kb.nomachine.com/AR02U01190The other thread was
Can’t connect to the NoMachine server after moving to a new server
It might not be the same problem as the one listed there, so first let’s try to understand better what the steps are to reproduce your specific problem.
By “link” I assume you mean connection.
it indicated it was asking permission on kath to complete the link….The question didn’t appear on kath. It appeared on a different machine on my network, maggie (192.168.4.33).
Not sure what you mean here. Do you mean that you started a connection to machine kath, which needs to authorize the connection, but the question “do you want to authorize” appears on another machine? Maybe you just mixed up the connection files or used the wrong IP address/hostname to connect?
Anyway, this is what we need:
screenshots of the session to machine Kath being started right up until you see the spinning wheel and you are forced to interrupt it. Please remove any sensitive info from the images. Or you can submit a brief recording.
Then, logs from the server machine Kath and also logs from your Player machine (the computer you are connecting from).
To get logs please follow the instructions here:https://kb.nomachine.com/DT11R00182#2 for Linux. In short:
1) On the server from a terminal
sudo /etc/NX/nxserver --debug --enable all
2) on the computer you are connecting from, tick the box ‘Don’t delete log files on exit’ option enabled in Settings -> Player -> Security. Otherwise the client logs will be missing or only partial.
3) Start a connection to Kath and reproduce the problem
4) On the serversudo /etc/NX/nxserver --debug --collect(they are stored in /usr/NX/var/log/archive)
5) Zip up and send both sets of logs to forum[at]nomachine[dot]comIf you want add the images I requested earlier as attachments to the same email, please do.
Thanks
Do they all have the latest version of NoMachine installed on them?
What is the desktop environment on the problematic Ubuntu machine? Is Wayland or Xorg running as the display server?
Can you try connecting from the problematic machine to one of the others?
Can you paste the link to the topic where you found a potential solution but it didn’t work?
Hi,
the tutorial, or Welcome screen, is a generic one showing all the icons that are available across all the supported OSes. When multi-monitors are attached to the computer you are connecting from there will be two icons specifically for handling how to view the NoMachine window in relation to the monitors attached. The first one with numbers (so you can switch the view) and position 6 which makes the NoMachine window go full-screen across all monitors.
On macOS it’s a bit different mainly because Spaces does not allow for windows across more monitors. You could try disabling “Displays have separate spaces” on the Mac machine as a workaround.
You wrote you have “two screens on the server side and two screens on the client side”. To be able to treat multiple monitors connected on the server as separate windows on client side is actually something we are planning to do. This will allow the user which has connected and set up multiple monitors on the server side to display each remote monitor in a separate window and place that window in any desired location, including on the monitor of your choice. As yet, we can’t provide an ETA.