Britgirl

[Britgirl]

Hi, this is a known issue and the fix will be in the next update.

Message “SELinux is preventing systemd from ioctl access on the file /usr/lib/systemd/system/nxserver.service” is issued on RHEL 9.3
https://kb.nomachine.com/TR02V11080

[Britgirl]

In version 8 it is configured on the server side using the EnableCredentialsStoring key in the server.cfg. Also present in the free version.

The key to not store the credentials is set in the server.cfg on the server, not the player.cfg. Remove the key from the player.cfg, if you’ve added it, which is not required. Then try again. Restart the nxserver. If you are still being requested for the credentials, tell us

Client OS and version
Server OS and version

Also submit the player.cfg and server/node cfg and we can check them. Send them to forum[at]nomachine[dot]com.

[Britgirl]

The output you pasted show that ihd is still being loaded from /opt/intel/mediasdk/lib64/iHD_drv_video.so. Try restarting nxserver again. Knowing its proxmox can make a difference yes. What’s the exact distro and display manager your replicating?

[Britgirl]

When you say client which machine are you referring to? The device you are connecting from or the device you are connecting to? Please tell us the version of NoMachine you are using on the client (where you start the connection) and the NoMachine server you are connecting to. I assumed you had installed v8 on both machines. If you are using a legacy version of NoMachine (prior to version 8), it’s better to submit your question to the team via the website. The forums are always dedicated to the latest version.

[Britgirl]

Right now the only way to have multiple monitors in a virtual desktop session is to connect from a client machine that has multiple monitors. It’s rather a unique use case, but we can evaluate whether to add the possibility to create virtual desktops with an arbitrary number of virtual monitors or not 🙂

[Britgirl]

There is a difference in what is printed in the earlier logs and what is printed in the example procedure (#post-47716).

Logs show:
libva info: VA-API version 1.19.0
libva info: Trying to open /opt/intel/mediasdk/lib64/iHD_drv_video.so

Your example:
libva info: VA-API version 1.20.0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so

It’s a different libva version and also a different filepath for the iHD driver.

You should check that you don’t have mixed libva libraries. For example, if you’re using Debian/Ubuntu, from a shell run dpkg -l libva*. What’s the output?

Next, make sure you’re using the iHD driver that is being used in your example, which is /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so. A quick way to do that is to rename iHD_drv_video.so which is in /opt/intel/mediasdk/lib64/to something else, for example:

cd /opt/intel/mediasdk/lib64/
mv iHD_drv_video.so iHD_drv_video.so.original

and restart NoMachine. Does that help?

[Britgirl]

In version 8 it is configured on the server side using the EnableCredentialsStoring key in the server.cfg. Also present in the free version. Find the key and set it to

EnableCredentialsStoring none

You can find more info about this key and the configuration files is available, for example, here: https://kb.nomachine.com/DT07S00246#3.3 and https://kb.nomachine.com/AR02N00877.

[Britgirl]

The next step is to understand if it’s a drivers problem or not. Can you try the package libmfx-tools and encode with its sample encoder? The procedure is here:

https://github.com/Intel-Media-SDK/MediaSDK/wiki/Intel-media-stack-on-Ubuntu

sudo apt-get install libmfx-tools

export LIBVA_DRIVER_NAME=iHD
wget https://github.com/lu-zero/fate-samples/raw/master/h264-conformance/AUD_MW_E.264

# Encode H.264 stream w/ Low Power encoder on gen9+ (skl+)
/usr/share/mfx/samples/sample_encode h264 \
-w 176 -h 144 -f 30 -cqp -qpi 30 -qpp 30 -qpb 30 -qsv-ff \
-i AUD_MW_E.yuv -o encoded_AUD_MW_E.264

[Britgirl]

Are you still able to send us the logs from player and server sides?

Seems that switching off the hardware decoding using NoMachine’s GUI does not work. For disabling hardware decoding one should edit player.cfg file

Do you mean that you tried disabling HW decoding in the connection menu and you still got the green screen? The menu enables/disables for the session, but does not stop the libraries from being loaded. You need to edit the file $HOME/.nx/config/player.cfg on the client side and set the configuration key “Enable hardware accelerated decoding” to “disabled” to stop the libraries from being loaded entirely.

The options are:
1) true: hw decoding enabled
2) false: hw decoding disabled (but libraries for hw decoding are loaded)
3) disabled: hw decoding disabled (libraries for hw decoding are never loaded and the checkbox is greyed out inside menu panel)

From the menu, you are able to toggle between options 1 and 2. So does setting the key to “disabled” in the player.cfg solve the issue?

[Britgirl]

Hi, is this computer you changed from nvidia to AMD the client or the server? Can you send us the complete set logs of the server-side computer you’re connecting to and logs of the client computer you’re connecting from? You can extract them using the instructions here: https://kb.nomachine.com/DT07S00243. Send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!

[Britgirl]

Hi,

there seems to be an issue with capture in the agent. A simple reboot could solve the issue. Did you already try that? If that didn’t help, you can also try changing the screen capture method in the ‘C:\Program Files\NoMachine\etc\node.cfg’ file.

DisplayServerExtraOptions "-nodxgigrab"

[Britgirl]

Take a look at the answer from Mth in an earlier topic

Unable to make the local display available or access to the local display is disabled

[Britgirl]

Hi, it’s not currently possible but we will be adding support for USB auto-sharing, so all you will need to do is plugin the device, before or during the NoMachine session, it won’t matter. Watch out for this in one of the successive v9 updates.

[Britgirl]

We investigated with the specific logitech keyboard and opened the Trouble Report here https://kb.nomachine.com/TR02V11091. It will be in the next maintenance release.

[Britgirl]

It’s hard to say why that is happening, it’s possible network related? Our tests show that over the Internet there are no pops in audio or microfreezes. When it happens, please submit:

logs from the server side (the machine you are connecting to) – see this document https://kb.nomachine.com/DT07S00243
logs from the player side (the machine you are connecting from) – see the same document as above
Session statistics – check the instructions in this article on how to get session statistics https://kb.nomachine.com/AR02N00875

Submit everything to forum[at]nomachine[dot]com.

[Author]

Posts