fra81

[fra81]

Hi Bart,

this looks very similar to the problem reported here: http://forums.mate-desktop.org/viewtopic.php?f=5&t=2094.

Can you try the suggested workaround?

[fra81]

Hi elan,

unfortunately the logs you sent are not complete and not useful for the investigation. Please send a complete set of logs as explained in details here: https://www.nomachine.com/AR07K00677. If you wish, you can send them to forum[at]nomachine[dot]com by referencing this topic in the subject.

But before that, can you tell something more? I see you are connecting to a Xvfb display. Is this a headless machine and you followed instructions in https://www.nomachine.com/AR10K00710? Have you launched a desktop environment (or any X application) inside the Xvfb display?

[fra81]

Hi iceback,

I assume the session was left in disconnected state, and when you reconnected after 2 weeks you found it unresponsive?

Do you still have logs from that session? More info on how to gather logs here: https://www.nomachine.com/AR07K00677. They can be sent to forum[at]nomachine[dot]com.

Finally, if the session is still running, please do a test: try to reconnect that session by double-clicking on the icon representing the session but, while doing so, keep Ctrl+Alt pressed. This will make the session is reconnected in “shadowing” mode. Let’s see if user input works with the different protocol.

[fra81]

Hi claus,

by default NoMachine listens on port 4000. Can you tell us the output of the ‘netstat -an | grep LISTEN’ command on the server?

Also server side logs could be useful. You can find instructions on how to gather logs in https://www.nomachine.com/AR07K00677. You can send them to forum[at]nomachine[dot]com.

[fra81]

Hi,

from the logs it looks like the only running instance of Xserver is a Xvfb (virtual framebuffer). Can you confirm?

Is that a headless machine and you started Xvfb maybe for the purpose of allowing connections through NoMachine?

Are you sure a desktop environment is actually running inside the Xvfb?

[fra81]

Hi,

unfortunately the archive seems to be corrupted. Can you please send the logs again to forum[at]nomachine[dot]com?

[fra81]

Hi BitPerfectRichard,

we finally managed to reproduce the problem with Console Log and the fix will be included in the upcoming software update.

The issue was related to the “Resize remote screen” feature and disabling it would have worked as a workaround. The reason why you don’t reproduce it with the just released Yosemite is that remote resize is not yet fully supported there and we are working on it. This should also explain why you don’t get the expected resolution.

[fra81]

Hi 70tas,

available resolutions depends on the Hyper-V and video drivers. NoMachine can only choose among the resolutions supported by the hardware.

You can try the “Fit to window” option that will stretch the remote screen to match the resolution you have on client side.

[fra81]

Hi sivaraman.s,

what is your NoMachine version?

We would need the complete set of logs to investigate further. Please follow the instructions in https://www.nomachine.com/AR07K00677 (included section “How to gather node logs”) to gather all logs and send them to forum[at]nomachine[dot]com.

[fra81]

Could you please verify the version of your libavcodec and libavutil libraries?
You can do this by listing files in their install directory, e.g.:

$ ls -l /usr/lib/libav*

Currently NoMachine supports avcodec library up to major version 55. If you have the newest version (which is 56), you should downgrade your libraries to use it with NoMachine. Support for version 56 is being added.

[fra81]

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.

[fra81]

Can you please specify your OS and desktop versions?

[fra81]

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/AR10K00695

They 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.

[fra81]

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.

[fra81]

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.

[Author]

Posts