fra81

[fra81]

Hi,

can you check the CPU usage on server side? Maybe it is Gnome 3 that is having problems running headless  (provided you are using it). In that case, I would try to install a lightweight desktop environment like Mate and edit the DefaultDesktopCommand configuration key accordingly (as explained in https://www.nomachine.com/AR07K00676, even though specific instructions in this article are for Ubuntu). More possible solutions are in this article: https://www.nomachine.com/AR07K00676.

[fra81]

Hi,

please tell the output of:

ls -l /usr/lib/x86_64-linux-gnu/libva*.so*

[fra81]

Hi,

is the server a headless machine?

In case it is, you could try the solution at point 1) of https://www.nomachine.com/AR03P00973. Or you can try to attach a monitor to the server or to buy a HDMI Dummy Plug adapter.

[fra81]

Hello,

since you intend to send events bypassing the NoMachine connection, please make sure you check the ‘Disable frame buffering on decoding’ option in Display settings from the in-session toolbar.

Then please collect also session statistics (open settings from the in-session toolbar, click on Connection, then click on ‘Take the statistics’) and check the CPU usage on the server machine.

[fra81]

Hi,

thanks for the logs. I see that NoMachine can’t use the fastest capture method but also Windows itself seems to work without GPU acceleration (and Windows Aero is probably disabled). This could mean that drivers are missing or not working correctly. Or is this maybe a virtual machine? And in case, how many resources (mostly CPUs) are assigned to it?

[fra81]

Hi,

please gather logs as explained in https://www.nomachine.com/AR10K00697. Also session statistics could be useful: run the menu panel within the session by Ctrl+Alt+0 or click on the page peel, click on Connection, then click on ‘Take the statistics’ and save. You can send all files to forum[at]nomachine[dot]com.

[fra81]

Thank you for the backtrace. We are preparing a possible patch for you to test. Please write to forum[at]nomachine[dot]com so we can send it to you.

[fra81]

Hi,

it seems the nxnode process on the server keeps crashing, and this problem is unknown. Please check for core files (usually located in the user’s home directory) and follow instructions in https://www.nomachine.com/AR09L00810 to generate a backtrace.

[fra81]

Hi,

is the Linux server headless?

Please gather server side logs (possibly after disabling hardware encoding) as explained in https://www.nomachine.com/AR10K00697. You can send them to forum[at]nomachine[dot]com.

[fra81]

Hi,

you can disable the desktop manager permanently:

systemctl stop display-manager
systemctl disable display-manager

Alternatively you can use a HDMI Dummy Plug adapter.

[fra81]

Hi,

any chance to get NoMachine logs from the non-working case? To do that, you would have to restore the Radeon card, reproduce the issue and gather logs as explained in https://www.nomachine.com/AR10K00697. You can also send them to forum[at]nomachine[dot]com. If you do that, please also try to uncheck the ‘Use acceleration for display processing’ box in Server preferences -> Performance tab and see if it solves the problem.

[fra81]

when I login, the screen resets to 1920 x 1080

Probably I didn’t get it right before. I thought “login” as “connect to the server”. Do you mean that you log in the remote user into its desktop, i.e. you connect to the login screen on the physical display and then log in?

In that case, it is likely that the desktop environment stores the last resolution set and uses that when starting up. If you change the resolution via the system preferences inside the session, then the new resolution would be stored.

[fra81]

So it seems the official ones are affected. Thank you for the info 😉

[fra81]

Hi,

would you tell us what new drivers exactly?

[fra81]

Hi,

please check that the ‘Match the client resolution upon connecting’ box is unchecked in the NoMachine menu inside the session -> Display -> Change settings panel.

[Author]

Posts