Forum Replies Created
-
Posts
-
Hi, we can reproduce and will be opening a Trouble Report. Thanks for reporting 🙂
The workaround in the meantime is to connect over ssh or change TTY (ctrl+alt+F2) – and remove the mentioned line greeter-setup-script=/usr/NX/scripts/vgl/vglgenkey or restore the orginal key:
sudo cp /etc/lightdm/lightdm.conf.orig.vgl /etc/lightdm/lightdm.confWe’re still investigating. In the meantime, can you take a look at the following link and try the steps there? This will at least check that everything is functional (without NoMachine in the mix).
export LIBVA_DRIVER_NAME=iHD wget https://github.com/lu-zero/fate-samples/raw/master/h264-conformance/AUD_MW_E.264 # Decode H.264 video stream w/ maximum speed /usr/share/mfx/samples/sample_decode h264 -i AUD_MW_E.264 # Decode H.264 video stream and dump output YUV /usr/share/mfx/samples/sample_decode h264 -i AUD_MW_E.264 -o AUD_MW_E.yuv -i420 # You can verify the result comparing with the following checksum: # sha1sum AUD_MW_E.yuv e17a3f8cfeeeb1cc46218c3c797d24dd84e82b59 AUD_MW_E.yuv # 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.264and tell us the outcome.
Thanks for letting us know. SSH tunnels aside, if you have any other questions about player and the server, or other components of NoMachine software, let us know here 🙂
With regards to the sound issue, check what is indicated in your Windows sound settings. Are you able to change to another audio output? With regards to the no access on Jetson issue, are you not even able to SSH into it? Have you tried rebooting? Rebooting with a monitor attached or HDMI dongle (if you don’t have a monitor)?
Hi,
please tell us:
1) if pointer/cursor grabbing is enabled in the Player.
2) if you’re sending Ctrl+Alt+Del through the shortcuts menu and you’re reaching the Windows security screen (lock, change user, task manager etc)
3) are those two players connected to the same desktop, each one showing a different monitor?To restore the GUI you just removed, you can run
sudo systemctl set-default graphical.target.You should still be able to connect with NoMachine 🙂 When you say “not able to get a screen”, what do you mean exactly? Did you install NoMachine on Windows, NoMachine on your Jetson and then tried connecting with NoMachine using the Jetson’s IP address? Can you tell us what happens exactly?
What desktop environment is running in Ubuntu? We have an article here with some tips about how to set up your Jetson. Take a look: https://kb.nomachine.com/AR02R01074 and follow the tips there and let us know how you get on.
Try installing using our official tar.gz packages from our website. Manjaro is a distribution we don’t support, but we tested on the fly and can’t reproduce your issue even with Yay What package did you use? There seems to be quite a lot of NX derivatives (which we can’t handle in these forums). We used “1 aur/nomachine 8.11.3-1 (+90 0.40)”
Please also tell us the Desktop Environment. Is it GNOME? XFCE?
https://forum.manjaro.org/t/howto-resolve-an-unbootable-manjaro-black-screen-login-failed-cant-boot-etc/3957
Some tips are available at the above link.It seems the local system is crashing (not nxplayer). Can you send us the system logs (journalctl) and player logs? Please refer to the following document for instructions 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!
You could also try disabling hardware decoding in the meanwhile (setting it to “disabled”, as explained in https://kb.nomachine.com/AR07U01202), just to exclude a possible problem with drivers.
I just noticed a typo in the previous command I wrote, apologies for that. It should have been
sudo sed -i '' -e 's/^AcceptedAuthenticationMethods.*/AcceptedAuthenticationMethods NX-private-key/' "/Applications/NoMachine.app/Contents/Frameworks/etc/server.cfg"Please check that you actually have sudo privileges.
Open a terminal and from CLI try to edit the file, for example with vim:
sudo vim /Applications/NoMachine.app/Contents/Frameworks/etc/server.cfgor just use command:
sudo sed -i '' -e 's/^AcceptedAuthenticationMethods.*/AcceptedAuthenticationMethods NX-private-keytest/' "/Applications/NoMachine.app/Contents/Frameworks/etc/server.cfg"This will change the key to:
AcceptedAuthenticationMethods NX-private-keyIt’s still not clear to us what problem with the NoMachine software you are experiencing. The screenshot you attached indicates that the web server doesn’t exist, not that NoMachine is unavailable/not running. You say that this NoMachine server is installed on a dedicated machine via your cloud provider, are you able to SSH into your VM?
Hi, it sounds like a permissions issue with screen recording in macOS. Can you try re-enabling screen recording in the MacBook settings? See the following article for the steps to take: https://kb.nomachine.com/AR11Q01061
If NoMachine has already been added, please remove it and add again.
Hi, if the issue happens again, we would like to see the nxtrace. The nxtrace.log file is generated only in case of a sudden termination of any of the NoMachine programs. It’s stored in: %PROGRAMDATA%/NoMachine/var/log on Windows Vista, 7, 8, 8.1, 10. I’ve passed your suggestion on to the developers 🙂
Hi, thanks for letting us know know. If you also tried ‘Scale to window’ mode instead of ‘viewport’ and that didn’t help, it could be related to the GPU on your Linux host that makes available only one resolution when the monitor is not present. A dongle “tricks” the system into thinking the monitor is attached.
It’s one of the workarounds for connecting to headless hosts. See our article in the KB for reference:
https://kb.nomachine.com/AR03P00973