- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- DISPLAY Error
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-11-2001 10:32 PM
03-11-2001 10:32 PM
DISPLAY Error
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-11-2001 11:25 PM
03-11-2001 11:25 PM
Re: DISPLAY Error
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-11-2001 11:48 PM
03-11-2001 11:48 PM
Re: DISPLAY Error
Still the problem is persisting.
Regards.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-12-2001 12:06 AM
03-12-2001 12:06 AM
Re: DISPLAY Error
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-12-2001 12:20 AM
03-12-2001 12:20 AM
Re: DISPLAY Error
Regards.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-12-2001 12:27 AM
03-12-2001 12:27 AM
Re: DISPLAY Error
echo $DISPLAY ?
use what is returned minus the ":0.0" ending in the following :
nslookup
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-12-2001 12:55 AM
03-12-2001 12:55 AM
Re: DISPLAY Error
As far as name resolution is concerned absolutely there is no problem.
Regards.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-12-2001 01:01 AM
03-12-2001 01:01 AM
Re: DISPLAY 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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-12-2001 01:02 AM
03-12-2001 01:02 AM
Re: DISPLAY Error
does it work in the foreground!!!??
May help..
Bill
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-12-2001 01:13 AM
03-12-2001 01:13 AM
Re: DISPLAY Error
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-12-2001 01:17 AM
03-12-2001 01:17 AM
Re: DISPLAY Error
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-12-2001 08:20 AM
03-12-2001 08:20 AM
Re: DISPLAY Error
I think the forums need an ignore user
button.
Later,
Bill
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-12-2001 12:09 PM
03-12-2001 12:09 PM
Re: DISPLAY Error
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