X refuses connection

slim27616 · 02-14-2005, 02:09 AM

im having a bit of problem that im sure is easy to fix but im not sure were to look to fix it. whenever im login as su or logged in to another system through ssh, i can open a gui. im sure that x is running (mostly because im typing this on konqueror). So i think that its just some setting refusing the connection but have no clue were to find it. Here is the error i receive so that people can find what i should change.

Code:

Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified

kded: cannot connect to X server :0.0
DCOP aborting call from 'anonymous-24835' to 'kded'
kded: ERROR: Communication problem with kded, it probably crashed.
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified

kdeinit: Can't connect to the X Server.
kdeinit: Might not terminate at end of session.
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified

apollon: cannot connect to X server :0.0
DCOP aborting call from 'anonymous-24820' to 'apollon'
ERROR: Communication problem with apollon, it probably crashed.
 Mutex destroy failure: Device or resource busy

if anyone was a solution through yast i would appreciate it.
oh yeah i know its not apollon's fault because i can open it by using the run function in the Kmenu(as im doing now). im running suse 9.2 pro.

oh yeah i have a second question but this is more of an add on.
suse seems to only look for bash commands in a few places, so i would like to know how do u add to the list of places were bash will look on it.

abisko00 · 02-14-2005, 04:37 AM

There is a security setting that is activated by default to prevent the start of an X-server via remote connections. Unfortunately, I am not sure where to find this setting, but I have some ideas:

in /etc/X11/xdm/Xservers, delete the -nolisten tcp option, to enabel the server to reply on such requests.

in /etc/X11/xdm/xdm-config, comment out the line 'DisplayManager.requestPort: 0'

I know that there has been a similar thread recently, so you may find the solution via the 'Search' page.

To your second question: I guess you mean the PATH variable. If you would like to extend this variable, add 'export PATH=$PATH:/your/path/' to either /etc/profile.local or /home/<user>/.bashrc. The first setting is system wide, the later user specific.
Good luck!