Forum Replies Created
-
Posts
-
Hi smartin,
the upgrade to the latest X.org version is indeed present in version 4.3. If upgrading to version 4.3 was not enough to solve the Evolution crashes, they are likely to be the same issue described in https://www.nomachine.com/TR10L04590. The fix will be included in the upcoming update.
If you are willing to test a patch for that problem, please contact us at forum[at]nomachine[dot]com.
Hi,
yes, installing the AVC Pack is the easy way. Alternatives exist and they are explained in details in the two links at the bottom of the article I pasted in my previous post. I report them here for convenience:
http://www.nomachine.com/AR10K00696
http://www.nomachine.com/AR10K00695They are step-by-step guides on how to enable H.264 on server and client side.
As for the two issue you are reporting:
1) special mouse button are not supported yet;
2) that is a bug and we will certainly check it out;
Regards.
Hi Yeris,
can you please:1) try disabling “Use acceleration for display processing” (Server preferences -> Performance tab), should it make any difference;
2) collect logs as explained in https://www.nomachine.com/AR07K00677 and send them to forum[at]nomachine[dot]com for investigation.
Thanks.
Hi byrne.
Okay thanks for the feedback. The knowledge base entry “https://www.nomachine.com/AR02L00782″ is not very clear about server side graphics hardware utilisation. I’m not sure what it means by server side hardware acceleration?
On server side hardware acceleration refers to the possibility of capturing the screen content from the GPU memory directly, without having to use the OS APIs. This is the deafault method on Windows servers. On client side it enables the hardware decoding.
I see that when we specify “lightweight” mode the rootless window seems to draw correctly. Can you select between vp8/h264/lightweight sessions as a client option? We require reasonable video playback across the LAN to clients machines so I suspect that NX compression is not going to as good as h264 for our purposes.
That is not available as a client option.
Hi esamo,
you could try to enable the H.264 encoding. It could be beneficial for both your first two questions, as it will provide higher quality and reduced encoding time, thus improving latency. You may consider the AVC Pack or installing the required codecs by hand. More info here:
https://www.nomachine.com/AR10K00706
As for your third question, virtual sessions on Windows are not possible at the moment, but such feature is certainly in our plans.
Hi Chris,
that doesn’t seem the same problem of the Trouble Report you mention, since that only occurs when the screensaver steps in.
We just tested with your same environment and we found no problem, so I would like some more info from you:
1) What is your desktop (Gnome, KDE, …)?
2) What is your desktop manager (gdm, kdm, lightdm, …)?
3) Please send us log files as explained in https://www.nomachine.com/AR07K00677 and send them toforum[at]nomachine[dot]com.
Hi Zsolt,
we are testing again the solution to that Trouble Report in our labs, but we are unable to reproduce any problem so far, so it has to be some corner case. The user who originally reported the problem never got back to us.
We are preparing a test build for you to test. In the meanwhile, can you try to disable the autorepeat completely by the “xset r off” command on the Ubuntu remote server? Just to exclude the possibility we are looking in the wrong direction… 🙂
Are you connecting to a physical display or are you running a virtual KDE session? Or maybe are you starting a single application in a custom session and the taskbar you are talking about is the one on your local machine?
Can you specify the local and the remote OS versions?
We are not aware of any similar problem. We are now checking what can be the possible causes.
Thanks for reporting.
Hi,
xrestop output was just intended to rule out an abnormal allocation of resources, but I have nothing specific in mind (pixmaps would be best candidate to look at though).
While waiting for you to upgrade we will run more tests on that platform.
Hello,
this seems different from original reports (where CPU usage was high for both Xorg and nxnode processes).
Is it Xorg’s CPU usage always high? Or only when you are connected through NoMachine to that machine? Or when you disconnect the session?
Hi dhy,
first of all I would suggest to upgrade to the most recent version (4.2.27).
If you will still experience the same, can you please specify the version of the remote OS and the desktop manager (Gnome, KDE…)?
Also the output from the ‘xrestop’ command run inside the session could be useful.
Hi,
sorry for the delay in getting back to you.
Logs were examined and we couldn’t find anything wrong. In the meanwhile version 4.2.27 has been released. Can you check the new one?
Many more tests have been run in the time being on that platform without any problem and honestly I can’t imagine how NoMachine could disrupt the system keyboard and mouse. Are you sure this issue is triggered by NoMachine and it is not reproducible when working on the physical machine? Can it be originated maybe by a system update?
Hi,
that is not supported in the current version, but it is in our plans.
Related Feature Request is: https://www.nomachine.com/FR12K02799.