y2controlcenter: cannot connect to X server

I have this strange problem on SLES9. Things I did: telnet from a SLES9 (A) machine to SLES9 ( su to root export DISPLAY=A:0. 0 When I try to bring up yast2 I get the error y2controlcenter:cannot connect to X server.

Linux Software 434 This topic was started by ,


data/avatar/default/avatar15.webp

1 Posts
Location -
Joined 2004-10-16
I have this strange problem on SLES9.Things I did:
 
telnet from a SLES9 (A) machine to SLES9 (
 
su to root
export DISPLAY=A:0.0
When I try to bring up yast2 I get the error
y2controlcenter:cannot connect to X server..
 
This behavior is observed only on SLES 9 machine..I can bring up yast2 fine using Solaris or other SUSE linux and also RED HAT..
 
Appreciate any help towards this issue.
Thanks
 
 
 
 

Participate on our website and join the conversation

You have already an account on our website? Use the link below to login.
Login
Create a new user account. Registration is free and takes only a few seconds.
Register
This topic is archived. New comments cannot be posted and votes cannot be cast.

Responses to this topic


data/avatar/default/avatar10.webp

2895 Posts
Location -
Joined 2002-08-30
I know nothing about SLES9, but it sounds like a permissions issue. Try the following;
 
type "xhost localhost" in a terminal window (without the quotes). This will grants the local
system rights to the X sessions.
 
Does this work?
 
If so, edit your .profile file in your home directory and add it. Then you will not have to enter it each time you are prompted.

data/avatar/default/avatar39.webp

336 Posts
Location -
Joined 2004-07-09
when logged in to host A, "xhost + localhost" is very similar to doing
"xhost + A" on host A. Note that you must specifically permit any user on
your host to make requests of your user's X server. Otherwise, the default
is to deny all except requests made by X clients initiated by you.
 
when logged in to host B, and you want the X client on host B to create
a window on host A, then you'll need to permit B to do so with "xhost + B"
on host A.
 
it's all a consequence of the new X server permission security-mindedness.