Forum Replies Created
-
AuthorPosts
-
BritgirlKeymaster
Since we haven’t received logs, I suggest you update to 5.3.9 and let us know if the problem persists. If it does, we’ll need logs to be able to investigate further.
BritgirlKeymaster🙂 Our pleasure.
BritgirlKeymasterThe TR mentioned in this forum post has been fixed in 5.3.9. Please update and let us know if you continue to have problems.
BritgirlKeymasterThe Trouble Report mentioned in this topic has been fixed in version 5.3.9. Please update.
BritgirlKeymasterThe Feature Request mentioned in this topic has been implemented in 5.3.9.
BritgirlKeymasterSo you should now be showing ‘Info: H264 support is available’ in the session logs, and in the menu’s Display Settings, you should not see VP8 as the codec, but H.264.
Let us know how you get on with the games 😉
BritgirlKeymasterwe did get your email 😉
as for the message, something went wrong when you set it up. Instead of copying, just do symlinks
cd /usr/lib/x86_64-linux-gnu/
ln -s libavcodec-ffmpeg.so.56.60.100 libavcodec.so
ln -s libavutil-ffmpeg.so.54.31.100 libavutil.soIf that doesn’t change anything, remove symlink: rm /usr/NX/lib/libstdc++.so.6
and try again.
BritgirlKeymaster@mikeev, we’ll need logs again as per Zaq’s instructions for the last time.
We have no issues setting up a headless system with NoMachine on Ubuntu, that’s why we ask for logs 😉
BritgirlKeymasterTo check if it’s a decoding issue you can look in your Linux client session log (.nx/R-*) and see if either the following is printed:
Info: H264 support is available.
or
Info: H264 support is not available.
BritgirlKeymasterYes, we did receive it. But that time you didn’t attach the .nx directory, your second email had it attached. Anyway, they don’t show anything that would tell us what is happening other than we can see that something is crashing when libraries are being loaded. We can pass you a debug version (for 5.2.21, not for an earlier version) if you are interested in installing it and extracting the logs – they’ll give us additional details.
BritgirlKeymasterDarksurf, your issue is a separate issue. Can you open a new topic (rather than a reply to an existing topic) with all the information requested (see ‘What to include’ )
BritgirlKeymasterThe client logs were missing it seems. Please send those from the 5.2.21 version. The .nx directory, and to be exact the R-* directories from there is what we will be looking for.
May 24, 2017 at 13:22 in reply to: Single user with black screen accessing NoMachine Terminal Server on Xenial #14894BritgirlKeymasterYes, we did thank you. One of the team will get back to you soon.
BritgirlKeymasterAre you sure you have installed Enterprise Desktop? From the image it appears you have installed a product which offers the virtual Linux desktop functionality (any of the products from the Terminal Server range, plus Enterprise Server).
BritgirlKeymasterIndeed, disabling the antivirus shouldn’t be necessary, but in this particular case there is a bug specifically with AVAST which is conflict with NoMachine, and disabling isn’t enough. You can see the details here: https://www.nomachine.com/TR03O07676.
Please use the notify me tool to know when a fix is available.
-
AuthorPosts