topic Problem with Xwindows in Operating System - HP-UX

Problem with Xwindows

Leonard G — Fri, 17 Mar 2006 02:11:53 GMT

Hi,

I have a HP 9000 machine running hp UX 11.11. I was using xmanager 2.0 to access this server from my windows XP desktop. This is a newly installed server and xmanager (xwindows) was working fine till I installed GoldApps and GoldBase. Now I am unable to view sam or swinstall form my windows desktop.

It says the "Display environment is set to :0.0. but the current configuration won't allow swinstall to run on that display."

Should I change any files to make this work as before ?

Regards,
Leo.

Re: Problem with Xwindows

Muthukumar_5 — Fri, 17 Mar 2006 02:16:08 GMT

Can you reopen another terminal and set DISPLAY variable with windows-ip:0.1 and try now.

Is it working now.

--
Muthu

Re: Problem with Xwindows

Leonard G — Fri, 17 Mar 2006 02:31:17 GMT

Hi Muthukumar,

I tried your solution. It is not working even now.

Thanks
Leo

Re: Problem with Xwindows

Peter Godron — Fri, 17 Mar 2006 02:33:24 GMT

Leo,
so you can start up a terminal window to the hp box to issue your swinstall command.
As I don't use xmanager, can you check whether an X server needs to be started (it needs to for Reflection X).
Then try the command:
xhost +:0.0

Re: Problem with Xwindows

Muthukumar_5 — Fri, 17 Mar 2006 02:45:41 GMT

After setting DISPLAY variable, try to start sam or swinstall without using through dterm or anything.

# export DISPLAY=ip:0.0
# sam

Are you getting window?

--
Muthu

Re: Problem with Xwindows

Antonio Cardoso_1 — Fri, 17 Mar 2006 02:54:35 GMT

Leo,

DISPLAY should be set to IP-address of your Windows desktop, not server's address.
What about :
export DISPLAY=:0
xterm &

does it start the xterm ?

Re: Problem with Xwindows

Leonard G — Fri, 17 Mar 2006 08:01:21 GMT

Thanks guys for all the input you have provided.

I was able to solve the problem with your help and an administrator here too. There was a lock file created in /var/sam/lock. After deleting this file it seemed to work fine now.

I don't know what happened because of this. But now I am able to run SAM.

Thanks,
Leo.