SOLVED: Full qualified $DISPLAY name not working, only local works ( e.g. :12.0)


we tryout Thinlinc, since we are currently using NoMachine.

Both are using XFCE as desktop.

Thinlinc works fine, except remote Display.

When starting a new shell / session Display is set to:

[hoepken@st008 ~/Desktop]$ echo $DISPLAY

With this I can start any X tool like “xclock” for testing. Works.

Since we are using also a load sharing compute farm (slurm), I must export a $DISPLAY with fully qualified name to allow remote display.

My host is:

[hoepken@st008 ~/Desktop]$ hostname

After settings my remote display with full qualified name:

[hoepken@st008 ~/Desktop]$ setenv DISPLAY

Enable access:

[hoepken@st008 ~/Desktop]$ xhost +
access control disabled, clients can connect from any host

Display is no longer working:

[hoepken@st008 ~/Desktop]$ xclock
Error: Can’t open display:

If I set back to simple old value it works again:

[hoepken@st008 ~/Desktop]$ setenv DISPLAY :12.0

How to solve that issue.

What I have done so far :slight_smile:

  1. Googled
  2. Read the manual
  3. Checked the forum

Does anyone have an idea?

For us this is go / nogo for ThinLinc.

Thanks Marko

Hello @marko_dct, and welcome to the forum!

Is there any particular reason why you want to use the X11 protocol instead of X11 Forwarding over ssh?

By default, the Xvnc server that comes with ThinLinc does not listen for remote TCP connections.

You can modify /opt/thinlinc/etc/conf.d/vsmagent.hconf and append -listen tcp to xserver_args and then issue a sudo systemctl restart vsmagent.

After that, you’ll have to log out your session and start it again.

Kind regards,

Hello Martin,

thanks for the fast respone.

Your suggestion WORKS. Thanks.

To your question why to we use X11:

Our current load sharing Slurm uses that.
We do chip developement with a large computefarm for simulation.
The ThinLinc will be just termial server for Gui work, simulation is done on remote hist with X-Forward.

Thanks Marko

Thanks for the update, and glad to hear that you managed get it working!

Kind regards,

Keep in mind that the legacy X11 forwarding is unencrypted and insecure :slight_smile: