Forum Replies Created
-
Posts
-
Hi vstubbs.
Have you downloaded the libx264 sources from our web site and followed the instructions in https://www.nomachine.com/AR10K00695? As exaplained in the article, the libx264 library with our modification is required.
Have you enabled the codec also on client side as explained in https://www.nomachine.com/AR10K00696?
If you followed all the steps and H.264 is still not used, please send us the logs for further investigation. You can find instructions in https://www.nomachine.com/AR07K00677. You can attach them here or email to forum[at]nomachine[dot]com.
Hi Steve,
here are a couple of examples of graphics card models that have been widely tested in our labs: NVIDIA Quadro K600, AMD Radeon HD6570.
Anyway, it would be useful to know what kind of problems you are experiencing, as we can’t be sure they are due to the graphics card.
We’ve been trying to get NoMachine 4.3.30 working with Gnome 3, but no luck. A physical server connection works somewhat, except that there’s a blue flashing sort of artifact that completely destroys usability. As the mouse is moved around on the screen and different UI elements gain focus, large parts of the screen will turn blue or black. Seems to be some sort of colormap or layering issue?
Is that a virtual machine? If so, what virtualization software are you using?
If it is not a virtual machine, what is your graphics card? Did you install proprietary drivers?A virtual server connection does not have this problem, but it’s very slow. If one right clicks on the desktop background, it takes many seconds before the background menu is displayed. Completely unusable. As a wild guess, maybe Gnome 3′s GPU operations are being emulated slowly in software instead?
Please find the relevant info here: https://www.nomachine.com/AR12L00831.
Can you tell us more about the versions of your operating systems and of the NoMachine software installed on client and server side?
If you are running the last NoMachine version and still reproduce the issue, please gather a complete set of logs as explained in https://www.nomachine.com/AR07K00677. If you prefer, you can send logs to forum[at]nomachine[dot]co.
Hi tommas,
so the relevant logs were probably cleaned up. At this point we would need a new set of logs after setting the ‘SessionLogClean 0’ key to the node.cfg file. Detailed instructions on how to gather a complete set of logs can be found here: https://www.nomachine.com/AR07K00677.
Anyway, before proceeding with new logs, I would recommend to upgrade to the new 4.4.1 version, that contains fixes to several problems, also affecting the Windows server.
Hi tommas,
thanks for the logs. The issue seems due to a failure in creating a session directory in the user’s home on server side (specifically C:\Users\Tommas\.nx\M-Tommas-13001-E98BCB8378573FEFB167B44F544BCD44). To investigate further, we would also need the content of the ‘C:\Users\Tommas\.nx’ directory from the Windows server.
Hi.
There is a issue affecting mac servers tracked in https://www.nomachine.com/TR11L04663. This should be the problem reported by the original poster. A fix will be made available in the upcoming software update.
The problem on the linux server could be different. Does it occur only with Chrome or with any application?
Hi.
As for the the problem with autorepeat, it looks like the issue in https://www.nomachine.com/TR10L04603. It should be already fixed in the last version.
Regarding the first problem, what is the resolution on your client machine? Logs could be useful to understand what’s going on. You can find instructions for gathering a complete set of logs in https://www.nomachine.com/AR07K00677 (you can send them to forum[at]nomachine[dot]com, if you prefer), but for a start client side logs could be enough. Please also check if you have a .config/monitors.xml file in the user’s home on the server, and what resolution is specified there.
Hi andrea,
the original problem looks like a problem with video drivers.
May I assume you are using NoMachine free on server side and you are connecting to the physical desktop of that machine?
Can you check the CPU usage on server side and tell us what processes, if any, consume most of it?
Logs could also be useful. You can find instructions for retrieving them in https://www.nomachine.com/AR07K00677. You can attach logs here or send to forum[at]nomachine[dot]com.
Another possibility could be bad network conditions. You could try to lower the Display quality using the slider in the Display settings tab and check if this alleviates the problem in any way.
Unfortunately logs from client side are not enough to clarify the issue. Please gather a complete set of logs as explained in https://www.nomachine.com/AR07K00677. If you prefer, you can send logs to forum[at]nomachine[dot]com. You can also check if there are any core files in the user’s home on server side.
Hi heartbreak,
your problem seems similar to the one described in https://www.nomachine.com/TR10L04587, though we could not reproduce it in our labs.
A complete set of logs could be useful. You can gather them by following the instructions in https://www.nomachine.com/AR07K00677. If you prefer, you can send logs to forum[at]nomachine[dot]com.
Hi Steve,
in the current version NoMachine for linux is not taking advantage of the graphics card (though work is in progress on this matter).
Could you explain further why you say that NoMachine doesn’t seem to like your graphics card?
Hi Bart,
thanks for your answers. As for your old problems with Ubuntu, as far as we know all problems related to the synchronization of toggle keys should be fixed in the last version (BTW, I see you are using a quite old version on client side, various bugs have been fixed since then).
Regarding the issue with NumLock, here are a couple more links that confirm this has to be considered a bug in Mate:
https://bugs.launchpad.net/ubuntu-mate/+bug/1364111
https://github.com/mate-desktop/mate-settings-daemon/issues/57
Hi Justin.
1) When interacting with the remote desktop, I get a lot of OS ding sounds (like each time an app is started, new window is created) – known issue, way to resolve?
This has been reproduced in our labs and it is currently being investigated.
2) When you logout of the remote desktop (logout of Windows), the image does not update to the login screen, you are stuck at the image just before logout. Is this by design? Seems like a bug to me.
This should be fixed with the next software update.
3) Do the graphics options in preferences apply only for serving? In other words, if I make a change on my client !M, will that affect how the server streams the graphics? (The UI is not clear on this matter.)
Those settings only apply when the machine where you are doing the changes on acts as a server. If you change preferences (from the NoMachine tray icon) on the client machine, those changes won’t be exported to the server.
Anyway, there is a different set of settings that affects the way the server streams the display. Those are the ones that can be tweaked from the NoMachine Player toolbar during the session.4) In Performance preferences, there are options for framerate and display encoding, and both are unchecked by default. If these are unchecked (i.e., no specification made), what values are they using?
Default value for framerate is 25 fps. The encoding method depends also on the decoding capabilities of the client. If the client supports H.264 decoding (by means of the hardware or by codec libraries), then H.264 will be chosen. Otherwise VP8 encoding is always used. MJPEG won’t be used unless it is explicitly requested.
Hi Justin,
the logs seems to point to a problem related to the video drivers. Can you specify the version of your graphics card so we can try to replicate this issue in our labs?
Please try to disable the hardware acceleration from the NoMachine tray icon on the server machine:
Show the server status -> Server preferences -> Performance
then uncheck “Use acceleration for display processing”.