Forum Replies Created
-
Posts
-
Thanks for submitting the logs. Player logs are showing HW decoding is not being used. Did you also disable also hardware decoding (on Linux) besides disabling hardware encoding on Windows?
Also useful for the investigation:
1) Run this command on the client machine and send us the file (‘xdpyinfo.out’).:
xdpyinfo -ext all > xdpyinfo.out
2) Does closing the player and reconnecting help?3) Does the problem appear after the screensaver starts up?
4) You say you reinstalled the server and it solved the crash which is good news. We would appreciate a new set of logs, including both server and client logs, just after having reproduced the issue. This will allow us to compare with the earlier ones you sent.
5) Is the monitor of the server attached and turned on all the time when the issue is reproduced? Or if it’s a laptop, is the lid open?
Hi, can you try disabling HW encoding on the Windows and see the freezing still occurs? On the Windows machine, open NoMachine settings > Server > Performance > Untick the box ‘Use hardware encoding’.
If it does, player logs from the Linux client this time would be useful. Please refer to the same document I pointed you to last time.
Hi, we aren’t aware of similar issues on Windows 11. Are you able to send us the server-side logs from the Windows machine, so we can check them? 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!
OneVPL is now the replacement to MediaSDK.
Indeed. In fact support for OneVPL will be added in the next update (coming soon).
Electrosaur, write to us using Contact Us in the footer, select General Enquiries, tell us what package type you need, and we’ll send you the link.
Gerard, you already opened the topic which is handling the audio issue, so we’ll continue with that in your other thread.
Can you tell us what configuration you have in order to get 30 bit per pixel? We can verify it first in our labs.
We’re checking the Quick Sync error. With regards to audio, can you tell us the distribution and version, display manager/desktop environment?
The logs show that the issue is actually a different one. This https://www.nomachine.com/TR03U10784. Support for 10 bits channels is planned, most likely in one of the minor releases of the v9 tree.
Hi, thanks for the submitting the logs. The agent logs were missing unfortunately (which we need), but in the server logs we can see the following errors:
7901 259 2024-03-23 04:06:03 608.263 Socket: ERROR! Can’t execute the sysctl request.
7901 259 2024-03-23 04:06:03 620.942 Socket: ERROR! Error is 12 ‘Cannot allocate memory’.What we don’t know if this is due to system memory being exhausted or whether you have a per-user limit, but it’s something you need to check. Then, please gather the logs (
--enableall as per the instructions) making sure not to remove the agent logs.Take a look at the article here “The password scrambling algorithm in NX Client”, https://kb.nomachine.com/AR01C00125
If it’s a headless Linux host you are connecting to, please follow the tips in the article here https://kb.nomachine.com/AR03P00973, specifically 1) Use a X virtual framebuffer.
Better would be to disable the display manager permanently, then the DM won’t start after reboot. This is the command
to disable and stop the DM:sudo systemctl disable --now[enter here display manager]
sudo /etc/NX/nxserver --restart(just once, after reboot all will be fine)Now when you connect, you should be able to start your session correctly.
If that doesn’t help, please submit the following information:
– NoMachine product and version on local and remote machine (free version, Workstation, etc).
– Whether the problem arises connecting to a physical or a virtual display.
– Remote and local Windows/Mac/Linux version (Windows XP/7/8, OS X 10.x, Ubuntu xyz, Mint x.y, etc.).
– Desktop version (GNOME. KDE, whatever) you are connecting to.
When you connect, are you seeing a black screen with a moving cursor, or are you seeing the desktop’s content which is frozen (except for the cursor). Is there a specific application running?