Forum Replies Created
-
Posts
-
What with the great variety of desktop environments available for Linux hosts, a certain desktop may not run out-of-the-box. Moksha is not a common DE amongst our users which favour predominantly Gnome, KDE, XFCE, LXDE, Cinnamon. It’s impossible for us to test all distros with all possible DE flavours available.
With regards to the comment about updating – our choice by design was to use our own upgrade servers and protocol, or for those who don’t want to update from our own servers, there is the possibility to download the package from our website and launch the usual procedure for updating Linux packages.
We tested that installing the package from our website installs correctly. We’ll investigate further with the software updates method.
Mac El Capitan 10.10.5
NoMachine 5.2.1 (did not yet upgrade to latest)
This is on the server side I take it. What OS are you connecting from? Knowing your complete set-up will allow us to investigate, following the exact same steps. It is advisable to update your software in any case.
I get mostly “No available sessions on this server” just like per https://nomachine.com/TR11K04044
This TR is from 2014 and on version 4. It’s very unlikely that the issue you are encountering is caused by a bug from a much earlier version.
What I suggest is you enable debug, reproduce the problem and then send us the logs (to forum[at]nomachine[dot]com. Both server and client side. Please follow the instructions here: https://www.nomachine.com/DT07M00098
Update: we haven’t been able to reproduce the problem, so logs would be useful.
We are not able to reproduce this issue. Since we’ve released 5.3.9, updating is advised just to make sure whether the problem persists. We will then send you a debug package for your 5.3.9 installation.
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.
The 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.
So 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 😉
we 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.
@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 😉
To 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.
Yes, 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.
Darksurf, 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’ )
The 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.