X Server Can't Connect and Forcing use of FQDN
Hi,
I have a commercial application that is trying to access an X server that is composed of the machine's FQDN and 0.0. Unfortunately, it seems that there is no way to override this via the application. Is there any workaround so that I can make it use the native :0.0 instead? Thanks for your help. |
Quote:
|
Thanks for you input coolb. I tried it out quickly but unfortunately it didn't work :( What's I'm trying to do is get it to use :0.0 (not localhost:0.0 or FQDN:0.0). Do you think something like creating a socket under /tmp with the FQDN and soft linking it to the :0.0 socket would do the trick?
|
I did a workaround using gdm.conf and adding the necessary cookie. Another approach is to run a vnc server and make it attach to the X server that the application is looking for.
|
I did a workaround using gdm.conf and adding the necessary cookie. Another approach is to run a vnc server and make it attach to the X server that the application is looking for.
|
All times are GMT -5. The time now is 07:20 PM. |