Problem getting the display

[Sivaram G]

I am unable to get the display to my terminal from HP-UX11 server. It gives the following errors

Error: Can't open display: :0.0
Error: Couldn't find per display information

please someone help.

Thanx

[Alex Glennie]

1. First check your terminal or session is capable of support X / bit-mapped displays : ie not a green console.

2. Make sure hostname resolution is OK : run nslookup on the terminals ip address : does it resolve ?

3. If yes try exporting DISPLAY=:0.0 or :0.0 if not already set.

4. Often X may have problems getting through firewalls, routers etc is this the case ?

5. Describe the H/W involved ... is the teminal an Xterminal or PC or just a remote display on a series 9000 or similar else where on the network. If HP check the Xservers log file : usually in /var/dt/Xerrors or / var/vue/Xerrors for further clues.

[Albert E. Whale, CISSP]

Sivaram,

You need to type this command on the Unix Prompt:

xhost +

or

xhost

In order to allow the X Server to cconnect to your workstation.

This is a session dependant command and needs to be repleated each time you reboot. You may want to consider placing it in your /etc/profile or .profile.

Hope that helps.

[Alex Glennie]

I'm not convinced Albert ! If it were a case of X authority you'd normally receive an Xlib error :

Xlib connection to refused by server
Xlib Client is not authorised to connect to Server ....

followed by the :

Error: Can't open display: :0.0
Error: Couldn't find per display information

We've only seen the per display bit which you generally get if a display cannot be opened due to the fact it doesn't exist.

Also under CDE (default at 11.xx) a lot of customers forget we have 2 types of X authority running : check out MIT Magic cookies and User-based authority either on the X man page or /usr/dt/config/Xconfig (section marked dtlogin*authorise : False).

Best of luck and let us know how you get on ...... ?

[Mark Hudson_1]

I struggled with this for days.

Turns out it must be some kind of DNS issue, since I eventually solved it by simply specifying the numeric IP address instead of hostname.

i.e.

xterm -display dhcp38:0

failed

but xterm -display 192.8.1.38:0

works great!

This also applies to the DISPLAY environment variable.