Forum Replies Created
-
Posts
-
We were able to reproduce similar behaviour and have since opened a Trouble Report. The fix for this issue can be tracked using this link: https://www.nomachine.com/TR03V11111
It will be in the next maintenance release.
This is the Trouble Report. Please use the link to monitor its status https://kb.nomachine.com/TR05V11159.
It could be. You can verify this by checking whether it happens when activating another window, then going back to the NoMachine client window. In that case you can keep the keyboard grab working correctly when the NoMachine client is selected by clicking the Dock icon, by using Command + Tab and by selecting the window in Mission Control.
Hi, are you able to send us the full server-side logs so we can check what’s happening? 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!
Additionally, any journalctl output (
sudo journalctl -x |grep -i gdm) and the output ofps -ef.I forgot to post the link to the Trouble Report https://kb.nomachine.com/TR05V11159. You can use that to track when a fix has been released.
We checked the logs and confirm that the problem is the same as the one reported here: https://forum.nomachine.com/topic/nomachine-not-using-gpu-for-encoding#post-47274 related to specific nvidia driver versions. We are currently investigating workarounds, but for the time-being you should try downgrading to an earlier driver version (535.129.03 appears to be ok) or continue to use software encoding.
We don’t have an official date for the release yet, but we are working hard to make it available by this summer.
Some clarifications to your comments…
… won’t allow NoMachine to become visible to the distant computer.
NoMachine hosts are visible to other NoMachine clients when they are all on the same LAN (i.e in Machines computers on the same LAN show with a pipe icon).
Distant computer user entered the host’s local LAN IP ’cause presumably that’s the way NoMachine works
When the user is on the same LAN as the computer you want to connect to, the local LAN IP is used. When connecting over the Internet, you use the public IP address of computer. For most users, this is the IP address of the router that sits in front of the computer you want to access.
Did you already see https://docs.netgate.com/pfsense/en/latest/nat/port-forwards.html#figure-port-forward-example (for the Pfsense port forwarding configuration)?
Hi, we checked the logs and we see that encoding fails at a very early stage, at a point where it seems unlikely that it can be a NoMachine issue. Can you confirm in any way that the other apps you mention are using HW encoding and not a SW fallback? How have you checked that they are using HW encoding?
Hi, can you send us the logs from the OS you are connecting to (i.e the NoMachine Windows server). Please use the following instructions:
https://kb.nomachine.com/DT07S00243
To enable debug on Windows, open a CMD console as administrator:> %ALLUSERSPROFILE%\NoMachine\nxserver\nxserver.exe --debug --enable allStart a session as usual and then gather the logs:
> %ALLUSERSPROFILE%\NoMachine\nxserver\nxserver.exe --debug --collectThe log archive is named as: NoMachine-log-
.zip (e.g. NoMachine-log-2018.09.27-11.44.01.zip) and stored in: %PROGRAMDATA%/NoMachine/var/log/archives on Windows 10/11. Send them to forum[at]nomachine[dot]com. Thanks! Strange. This sounds more like a network problem. When you see that error, can you ping or ssh in to the Pi?
Did you install FF via snap? Make a test of audio in the virtual desktop, with any app not installed by snap, e.g vlc player. Does sound work?
Install FF this way: https://www.omgubuntu.co.uk/2022/04/how-to-install-firefox-deb-apt-ubuntu-22-04
Then connect to the virtual desktop.