Re: "connection to ":1.0" refused by server
Re: "connection to ":1.0" refused by server
- Subject: Re: "connection to ":1.0" refused by server
- From: Ronald Cohen <email@hidden>
- Date: Sat, 27 Sep 2008 14:35:37 -0700
Dave, thanks I will look for residue of old X11's. But RE xterm, I
find that by adding the standard flags after "xterm" in "app_to_run"
in org.x.X11.plist, I can customize my initial xterm the same as I
would from .xinitrc. It seems that it is the .xinitrc-launched
xterm that is getting the undesirable DISPLAY variable, and others
responding to this thread have indicated that I should expect that.
Ron
On Sep 27, 2008, at 2:24 PM, Dave Ray wrote:
Ronald Cohen <email@hidden>
If I launch X11 from the dock on my MacBook Pro, then when I change
locations/networks, I fairly frequently get a message like the one
above, and can't launch x applications. The problem is sometimes
solved by turning on and off my network connection (by unplugging the
network cable, starting an xterm, then reconnecting the cable, or
doing the same by turning off airport).
A previous respondent suggested that the problem was that the DISPLAY
environment variable was being set to 1:0 (or 0:0) rather than to a
launchd socket. Nothing under my control is doing that.
It is likely that some script that you aren't aware of is setting
DISPLAY in a way you don't want. At the terminal prompt run "env |
grep DISPLAY" and report what you see.
It should look something like:
DISPLAY=/tmp/launch-qvH6qc/:0
This should be a unique value that gets set at X11 startup,
automatically without it being set in startup scripts, and as of
10.5.5, must not get set or it will cause the kind of problems you
see. DISPLAY shouldn't change when you change networks. I just tried
this on my system and the DISPLAY variable remains the same across
network changes between my airport and ethernet. You may have to do
some more hunting to see where that variable is getting set (or not
being set). Try deleting all the stubs from previous X11 sessions
in /private/tmp and ~/.Xauthority*, and use Cocktail to flush all
your cache.
Regarding your comments about the xterm, Unless you specifically
want xterm to run before your window manager, it would be better to
disble the startup xterm altogether (as described in the FAQ), and
launch it (if you really want it) from your .xinitrc, because you
that's a more standard model of how startup apps are launched. You
can control the scroll bar, drag bar, etc through standard shell
commands and flags.
Dave
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription: http:// lists.apple.com/
mailman/options/x11-users/email@hidden
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
This email sent to email@hidden