fra81

[fra81]

Work is in progress, but it is a major change and it will require quite a long period of testing, given the number of different Linux platforms.

So I can’t say exactly. Should be in terms of weeks.

[fra81]

Please send the whole ‘/Library/Application Support/NoMachine/var/log/’. That will be useful also for the first problem.

[fra81]

Are you attaching to the physical display of your home machine? Or are you creating a new virtual desktop?

Please gather client and server side logs as explained here: https://www.nomachine.com/AR07K00677.

Send to: forum[at]nomachine[dot]com.

[fra81]

Sorry for the delay, it looks like I missed your post.

There is no option for decreasing memory usage and those are expected values. Consider anyway that the nxnode.bin process in the new version includes the functionalities of both nxnode and nxagent processes of the old version.

[fra81]

Can you please provide more info:

– What is the nx process with high CPU usage?
– Does the CPU usage remain high when there are no visible updates in the session?
– NoMachine product and version on local and remote machine (free version, Workstation, etc).
– Whether the problem arises connecting to a physical or a virtual display.

[fra81]

Please try:

ln -s /usr/lib/i386-linux-gnu/libavcodec.so.54 /usr/lib/i386-linux-gnu/libavcodec.so
ln -s /usr/lib/i386-linux-gnu/libavutil.so.51 /usr/lib/i386-linux-gnu/libavutil.so

[fra81]

Are you using the free NoMachine version? If so, how did you enable x264 before the upgrade, did you buy the AVC packed or you had ffmpeg installed?

Can you please copy the output of  the ‘locate libavcodec.so’ command?

[fra81]

This appears to be a problem of this Evolution version when running with older X.org versions. Tests showed that the crash is reproducible also without using NoMachine, in a physical display running the same X.org version as NoMachine’s.

That said, this problem will be automatically solved when the transition to the new X.org will be completed in NoMachine.

[fra81]

Hi all,

we are working on those glitches. They should be fixed in the upcoming update.

[fra81]

Can you specify the NoMachine version you are using?

Are you able to connect from a client running in the same machine where you were trying to connect to, by creating a connection to localhost?

[fra81]

We are working at the problem. It seems to have to do with some Pixmaps or RENDER Pictures not recreated correctly at session reconnect.

Everything was working perfectly with 4.1.29

This appears to be a randomness. We didn’t change anything which may have remotely to do with this bug, so also the 4.1.29 is probably affected.

[fra81]

Possibility to choose the monitor is under development.

This is the related Feature Request:

https://www.nomachine.com/FR11K02797

[fra81]

There is no bug if you are attaching to the physical display and those are the only resolutions supported by your video card drivers.

I assume the difference is that you are running virtual sessions when using xrdp. This is available in NoMachine in the Workstation product.

[fra81]

“I tried the differents display option using the page peel menu, but it’s not working, when i put fullscreen it’s only stretching the screen and it’s not confortable at all. I d like to have a true resolution on it.”

Be sure the “Fit to screen” button is unchecked on the bottom of the screen. It’s the first button of the row.

[fra81]

To do that go in the control panel on the server and change the resolution to whatever is listed. The client should resize accordingly.

On Linux we use the randr X extension to resize the display.

Try the following commands and include the output:

xrandr -q

xrandr -s 1920×1080

[Author]

Posts