Differences between version 16 and predecessor to the previous major change of XFree86Notes.
Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 16 | Last edited on Tuesday, March 29, 2005 2:59:39 pm | by FelineGrace | Revert |
| Older page: | version 15 | Last edited on Sunday, March 13, 2005 3:12:04 am | by JanHolstJensen | Revert |
@@ -72,8 +72,16 @@
Xlib: connection to ":0.0" refused by server
Xlib: Client is not authorized to connect to Server
xhost: unable to open display ":0.0"
The only solution (I've found) is to log out and re-start your X session. However, if you are cunning, you might be able to get the cookie from one of your currently running processes, especially an ssh connection with X forwarding (do __xauth list__ on the remote machine). After getting some free disk space again, use the __xauth merge__ command as above.
+
+!! It just might be X11 is not forwarded properly
+
+Don't forget to check that your remote login has the DISPLAY environmental variable set correctly. With recent versions of OpenSSH, this will default to localhost:10.0.
+
+The point is that if DISPLAY is not getting set at all, then you probably don't have X11 forwarding set up properly. One way to do this is in the global ssh_config file. A second way is in your personal config file. Or you can set it on the command line with the -X option to ssh.
+
+Lastly, if DISPLAY is set but it still doesn't work, don't forget to check your target sshd_config file to make sure that the option in sshd is turned on. It won't work if the server doesn't support it.
!! Preventing the server from listening for TCP connections
The stock [XFree86] startx(1) script assumes that you want X listening on port 6000. On the common standalone desktop machines, this is an unnecessary potential security risk. To disable this behaviour, edit __/usr/X11R6/bin/startx__, changing the line
