topic Re: DISPLAY Error in Operating System - HP-UX

DISPLAY Error

sriharikumar_1 — Mon, 12 Mar 2001 06:32:20 GMT

Hi,

In our B1000 Workstation running HP-UX 11.00,
When we try to open some process in background,
it gives the following error:

Error : can't open display
Error : couldn't find per display information

The system is being used for NNM and Perfview.

This problem is happening only when you login as root. Using some user login we are able to run processes in background.

Can anyone tell what could be the reason?

Awaiting for your valuable replies.

Thanks and Regards.

Re: DISPLAY Error

Stefan Schulz — Mon, 12 Mar 2001 07:25:25 GMT

This sounds like a problem of a missing DISPLAY variable. The process you try to start needs to open some graphical window, but can't find a display to do this.

Check with echo $DISPLAY if this variable is correctly set. If not use something like:

export DISPLAY=xxx:0.0

Where xxx is the hostname of your Workstation.

This should help. Regards Stefan

Re: DISPLAY Error

sriharikumar_1 — Mon, 12 Mar 2001 07:48:16 GMT

Tried by exporting DISPLAY variable.
Still the problem is persisting.

Regards.

Re: DISPLAY Error

Bill McNAMARA_1 — Mon, 12 Mar 2001 08:06:02 GMT

remotehost# xhost +
remotehost# export DISPLAY=192.168.1.123:0

where that IP address is the IP of the
station you want the window to launch up on.

Then launch the app:

remotehost# xclock

Note the xhost is a ~security issue~
you may want to limit to just your
domain man xhost for more.

Later,
Bill

Re: DISPLAY Error

sriharikumar_1 — Mon, 12 Mar 2001 08:20:29 GMT

Tried out by taking a remotehost, not helping out.

Regards.

Re: DISPLAY Error

Alex Glennie — Mon, 12 Mar 2001 08:27:21 GMT

In the terminal window on the B-class, the one which you run NNM etc in the background .... what EXACTLY is returned when you run the commands( and logged in as root) :

echo $DISPLAY ?

use what is returned minus the ":0.0" ending in the following :

nslookup whats returned ?

Re: DISPLAY Error

sriharikumar_1 — Mon, 12 Mar 2001 08:55:26 GMT

Both Forward and Reverse lookup for that system is happening properly.
As far as name resolution is concerned absolutely there is no problem.

Regards.

Re: DISPLAY Error

Bill McNAMARA_1 — Mon, 12 Mar 2001 09:01:02 GMT

Is it just this app that gives the error
or is it everything?

Are you logged into the server via CDE Indirect
login? Do the ICON launchers work but not
commandline?

Try sourcing your .profile first.
From your prompt:

#. ~/.profile
#xhost +
Client access control disabled....
#xclock
does xclock appear?

Try logging in as a non root user and doing the
same. If your problem is limited to one app,
it may be hard configured somewhere to open a
display. See if there is application specific errors or other X error logs. look for X errors in your home directory.

Later,
Bill

Re: DISPLAY Error

Bill McNAMARA_1 — Mon, 12 Mar 2001 09:02:37 GMT

When you mention in the background...
does it work in the foreground!!!??
May help..
Bill

Re: DISPLAY Error

Bill McNAMARA_1 — Mon, 12 Mar 2001 09:13:19 GMT

Sorry to overpost: but lets clear this up,

1: as normal user everything works
no DISPLAY problem,
apps launch
=> no IP/DNS problems
2: Only doesn't work for root
=> not a permission problem!
=> .profile / user specific
3: Nothing got to do with NNM/PerfView
4: Same problem with all X apps under root
user.

You may just want to source the root users
profile on dt login.

. ~/.profile
^There is a space after the dot
echo $DISPLAY
to verify there is a valid IP/name before
launching the task.

Bill

Re: DISPLAY Error

Alex Glennie — Mon, 12 Mar 2001 09:17:27 GMT

.... and are users $HOME directories NFS mounted ?l whilst we clear thing up :)

Re: DISPLAY Error

Bill McNAMARA_1 — Mon, 12 Mar 2001 16:20:04 GMT

4 out of 24 point for this guys posts.
I think the forums need an ignore user
button.

Later,
Bill

Re: DISPLAY Error

Wodisch — Mon, 12 Mar 2001 20:09:33 GMT

Hello sriharikumar,
could it be that your "root" user is loging in using "telnet"
or "rlogin", whereas the other user do a graphical = CDE
login? OR does your "root" NOT login but use "su" or
"su -" to become "root"? Then you need to set the
already mentioned variable "DISPLAY" (all upper case)
to your local graphics display (like "export DISPLAY=:0")
and afterwards disable authentication ("xhost +").
Now try starting your X-application or try "xclock&" - is
it complaining again, or displaying?
Post your "/etc/profile", the "$HOME/.profile" of the
user who is logged ("root" or whoever is su-ing to "root")
and his/her "$HOME.dtprofile" so we can identify the
cause.
HTH,
Wodisch