Forum Replies Created
-
Posts
-
This is a bug in Chrome, not NoMachine. We have seen that problem is the same when Chrome is used on the physical screen (so take away NoMachine from the scenario) with the new Flash plugin 11.2.202.616. It is not reproduced using Chrome with flash plugin version 11.2.202.548.
There is a Trouble Report for this bug. Please use the ‘notify me’ box to know when a fix has been released.
https://www.nomachine.com/TR04N06814this only happens when there is no X server running
The issue is specifically correlated to the fact that it’s headless. Please see the Trouble Report we opened: https://www.nomachine.com/TR04N06814 and sign up to the ‘notify me’ to know when a fix has been released.
@redmumba what distribution is the Amazon image? Slackware?
The hardware decoder facilities are not available on the client, but you can still use H.264 software encoding. You have five options:
a) install our our ffmpeg libs, download and build from http://www.nomachine.com/downloads/5.1/sources/ffmpeg-5.1.24.tar.gz
b) install the original ffmpeg libs, download and build from https://ffmpeg.org/releases/ffmpeg-3.0.2.tar.xz
c) use the prebuilt ffmpeg Zeranoe packages, which you need to extract to the directory nxdir/bin (windows):
https://ffmpeg.zeranoe.com/builds/win32/shared/ffmpeg-20160425-git-9ac154d-win32-shared.7zd) use the AVC pack (available for a small fee – you only need it on the client side)
e) change your resolution 🙂
@samikbaqchi we’ll need the installation logs. They are placed in the AppData folder under the user’s home, e.g.:
C:\Users\USER_NAME\AppData\Local\Temp\Setup Log 2016-04-2…..
Send them to forum[at]nomachine [dot] com
If you are connecting to virtual Linux desktop sessions, configuration wise there should be nothing to do other than disabling X11 vector graphics mode (previously known as “lightweight” mode) on the server. For more info see here https://www.nomachine.com/AR02L00779. We will detect what’s in place on the server side and tell the client to do the appropriate decoding.
On the client side if you have Win or Mac, then the system’s H.264 decoding will be used. If you’re using Linux, you’re going to need the FFMPEG libraries installed. See the article here for more details: https://www.nomachine.com/AR10K00696.
To check what’s being used in your session, you can look in the C-*/session logs. There should be a line: Info: Using H.264 software encoder.
You can also check when connected by going in to the menu CtrlAlt0 ->Display -> Display settings and seeing what appears at the bottom.
If you followed the procedure correctly on the Workstation and client-side hosts, then you shouldn’t have any problem, but there are 2 possibilities when decoding doesn’t work: a) when session resolution is higher than 1920×1080 (we explicitly disabled higher resolutions due to problems with some of the old graphic cards), b) your Windows is in a virtual machine, so it lacks hardware capabilities.
Hi, at the moment remote access via the browser is available in Cloud Server, but we are evaluating whether to add this functionality also to our other products in the NoMachine for the Enterprise range.
@Spart, thanks for sending in the logs. We can confirm that the bug reported in 5.1.9 is fixed in the latest version, so everyone please update their software to 5.1.2x.
Yes. But I will send it again. Write to forum[at]nomachine[dot]com and we can also send it to you that way.