Cannot detect any display running

[Kalabagh]

Sorry, I thought this message had been sent:

“Dear Mr. Kroy,

This is what I get:

/usr/share/xsessions/icewm.desktop:Exec=icewm-session
/usr/share/xsessions/mwm.desktop:Exec=mwm
/usr/share/xsessions/twm.desktop:Exec=twm
/usr/share/xsessions/xfce.desktop:Exec=startxfce4

So I think it has already installed xfce environment. What do you think?”

[kroy]

Like I suggested before (maybe you didn’t see it) you need to check the DefaultDesktopCommand in the /usr/NX/etc/node.cfg (on server side). It should be set:

DefaultDesktopCommand /usr/bin/startxfce4

If there is other value please modify it. Then it should start to work.

[Kalabagh]

Sorry, I thought this message had been sent:

“Dear Mr. Kroy,

This is what I get:

/usr/share/xsessions/icewm.desktop:Exec=icewm-session
/usr/share/xsessions/mwm.desktop:Exec=mwm
/usr/share/xsessions/twm.desktop:Exec=twm
/usr/share/xsessions/xfce.desktop:Exec=startxfce4

So I think it has already installed xfce environment. What do you think?”

[kroy]

This shows that you could be using XFCE but I asked you to check what is actually set in the DefaultDesktopCommand key in the /usr/NX/etc/node.cfg on the server side.

What is written there?

For example, it should be:
DefaultDesktopCommand /usr/bin/startxfce4

that you could create a XFCE session.

[Kalabagh]

Hi there kroy,

I have tried writing “/usr/bin/startxfce4” but nothing.

What is written by default is “/etc/X11/xdm/Xsession default”.

 

Thanks.

[kroy]

We don’t seem to be any closer to helping you resolve your issue. Our test environment on AWS shows that there are no issues with connecting to OpenSuse (this is what you said you are connecting to). Setting the DefaultDesktopCommand key to  “startxfce4” works as expected.

What we suggest is that you uninstall NoMachine (and remove config files sudo rm -rf /usr/NX) on the remote Amazon instance and reinstall NoMachine to reverse any changes. Then check the DefaultDesktopCommand again and reset it to “startxfce4”, if it’s different. Then restart NoMachine server to make sure that changes are implemented (sudo /usr/NX/bin/nxserver --restart).

Also, the logs from the server side, not  the connecting client, would be useful at this stage if, after the reinstall, you continue to have problems.

To get the logs from the server host, follow the instructions here: https://www.nomachine.com/DT10O00162

[Kalabagh]

Hi Mr. Kroy,

I have created a new instance with the same configuration. It works perfect and with the same AMI.

I also have no access to the AMI’s root user, because it’s not created by me, so let’s forget this issue.

So many thanks for all your help and concerned about having been unable to give a public solution.

[Britgirl]

Sudo would have worked. Anyway, I would rather say that Kroy gave you a reasonable proposal by suggesting you to uninstall and then reinstall given that previous attempts to provide a solution hadn’t worked, and that you didn’t submit the logs (twice we asked over these past weeks). NoMachine installs 99% of the time out-of-the-box including on virtual machines regardless of the hypervisor. On occasion, when an installation has been altered for whatever reason, or the OS is not the manufacturer’s default OS that NoMachine is expecting, an issue might occur. Reinstallation can help, although it’s not clear from what you write whether you actually reinstalled NoMachine. We’ll consider this case closed.

[Author]

Posts