Forum Replies Created
-
Posts
-
Are you still able to connect to the machines that aren’t discovered using their IP address?
What macOS versions are installed on all the M1 hosts which aren’t discovering the other machines? And on the M3 host?
Can you also send us the output of this command on the player side?
for DEVNAME in /dev/dri/* ; do LIBVA_DRIVER_NAME=nvidia vainfo --display drm --device $DEVNAME ; doneSorry, forgot to ask you to execute this command in a terminal
sudo /usr/NX/bin/nxserver --eglcapture noand reboot (or logout and then login). Does that change anything?Can you send us the node.cfg file of the NoMachine server, and also the output of this command:
/usr/NX/scripts/vgl/vglrun glxinfo | grep -i “renderer\|vendor”
In the logs we can see that the server sets the LD_PRELOAD library. Maybe is not set in your user profile?
The attachments were not working for some reason and so they have been removed. Can you send them directly to forum[at]nomachine[dot]com, please?
I assume you’ve got 8.14 on the Windows computer as well.
When you say “after rest” in the title, do you mean you start the session to the Mac and leave the session open/running, and then go back to it after some time?
UDP traffic goes through port 4000, this has been the case since the first release of version 8. Using ports 4011-4999 would not improve performance.
Is the display server X11 or Wayland? On Kubuntu it’s x11 by default, maybe you installed Wayland and are you using that?
Logs would be useful from both sides. 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!
Thanks for your input. We will evaluate whether offering a shortcut for activating/releasing keyboard grab is feasible.
Our Multi Monitor fullscreen spans a window across multiple displays. On macOS this is not possible in the default configuration, where every display has its own “Space”. A workaround consists in disabling such option (“Displays have separated Spaces”).
Hi, we would still like to send you a debug package if that’s ok with you, it would allow us to debug EGL capture. Please check your inbox for emails from us, there will be a link to a package for you to download along with further instructions.
The problem with right-click was actually fixed in an older version of NoMachine for Mobile.
Here is the original Trouble Report: https://kb.nomachine.com/TR07P08723.
Successive Android system updates, namely 12 and later versions, introduced changes to properties of some events, and the problem has unfortunately re-appeared, but it does not occur on all models of devices. We opened a new Trouble Report, https://kb.nomachine.com/TR08V11198. The next NoMachine update for mobile will include the fix.
emilianoheyns, can you confirm that you are still experiencing this issue on Sequoia after updating to NoMachine 8.14 and after following the instructions in the article I linked earlier?
All NoMachine Linux Terminal Server products support VirtualGL, including the evaluation version. You need to enable VirtualGL first, so this is the first thing you should check. How to do that is explained in the following article:
How to enable VirtualGL support on Linux in NoMachine
https://kb.nomachine.com/AR05P00982In short, the commands to use are
sudo /etc/NX/nxserver --virtualglinstallandsudo /etc/NX/nxserver --virtualgl yes. But please consult the article for full steps.Let us know if following those steps helps.
In your output of the client, we can see that HW encoding is working correctly. On the client side the session is using software decoding, and not hardware decoding. If this is not what you expected on the client side (we are not sure from what you wrote), you should send us logs from the device you are connecting from and we will check them. See this article (step 4) https://kb.nomachine.com/DT07S00243.