Forum Replies Created
-
Posts
-
Well, Wayland is still very much in development, especially for KDE, and practically every release of every distribution changes things and NoMachine then has to adapt. So it’s not that there is no lack of support in NoMachine š
As for this specific issue, the fix will be in the next available maintenance. It did not make the 8.6 release last week.
We have not been able to reproduce this problem when connecting from either client v7 nor 8.6.
Please confirm the nginx version and which specific macOS ?Hi, the server settings path cannot be changed. It’s a global setting, one place for whole server host. The Player settings are per user, and that’s why you can change the path. What you can do is install the NoMachine server software to a different location.
Everybody, there is a workaround, and it’s the same as the one we reported for the topic here: https://forum.nomachine.com/topic/session-terminated-unexpectedly#post-41758
Quoting what I wrote there: We recently discovered a similar issue but only when using Linux Mint in a VM. Please edit /usr/NX/etc/node.cfg and set following key:
DisplayServerExtraOptions "-eventdelay 0"and restart nxserver:
sudo /etc/NX/nxserver --restartHi, just so that we have a clear picture of your set-up. Can you tell us the NoMachine product that you have on the Red Hat server?
Hi, can you tell us what operating system you are connecting from and connecting to? Are you running the latest NoMachine 8.6 on both sides?
Have you seen the article in our knowledge base that explains how to set up port-forwarding? (section 3. Troubleshooting for most common cases requiring manual configuration of the router)
https://kb.nomachine.com/AR04S01122
It could be that you have a double NAT and in that case port forwarding must be configured manually on both routers (your home router and your work’s computer)
Ilgaz, did you mean to write for this topic, or the other topic here:
https://forum.nomachine.com/topic/no-hardware-decode-on-kubuntu-22-04-gtx-1060-6gb/page/2 ?Please see my response from June 27th in this thread (#post-44716).
This is not a NoMachine issue. However, a workaround is to disable hardware decoding in the player. This is done in the following way:
ā close all nxplayer processes
ā open the $HOME/.nx/config/player.cfg file
ā find the āEnable hardware accelerated decodingā key and change it to look like this:
<option key=āEnable hardware accelerated decodingā value=ādisabledā />
We’ve not been able to reproduce the problem and so we will need the logs from the server. This was not made clear earlier.
To enable and extract the logs from the server side follow the document here:
https://kb.nomachine.com/DT07S00243
Once debug is enabled, you should connect server andĀ then disconnect. You can also click the mute button a few times to check what happens to unmuting during the session.
Send logs file to forum[at]nomachine[dot]com.
Everyone,
here is the Trouble Report:
Audio is not available in the session with NoMachine server v.8.5.3 on Manjaro Linux and other distros
https://kb.nomachine.com/TR05U10867its fix will be in the upcoming 8.6.
The vainfo output confirms that this is not a NoMachine issue, but a drivers issue. You can gather some more info on the driver problem by trying to run the vainfo command again modified in this way:
LIBVA_DRIVER_NAME=nvidia vainfo --display drmYou can also check the suggestions in these posts:
As a workaround an option is to disable hardware decoding in the player. This is done in the following way:
– close all nxplayer processes
– open the $HOME/.nx/config/player.cfg file
– find the “Enable hardware accelerated decoding” key and change it to look like this:
<option key=”Enable hardware accelerated decoding” value=”disabled” />
Hardware encoding won’t work if you uninstall the drivers.
Follow the instructions here:
How to use AMD HW encoder with NoMachine on Linux platforms
https://kb.nomachine.com/AR02U01190Keep the drivers installed and send us the logs so that we can investigate the black screen issue.
From the server side, please gather the logs following the instructions here and send to forum[at]nomachine[dot]com: