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: "Piotr Grzybowski" <email@hidden>
- Date: Sat, 27 Sep 2008 00:40:01 +0200
Hullo Ronald,
try running from your home directory
grep -rn DISPLAY *
is the problem the same for other users?
yours,
pg
On Fri, Sep 26, 2008 at 11:20 PM, Ronald Cohen <email@hidden> wrote:
> Daniel, thanks for this reply. So I checked and found that I don't have
> such a plist; (nor do I have a directory ~/.MacOSX). Furthermore after a
> reboot I found that my display variable upon dock launch of X11 was 0:0
> instead of 1:0, so whatever is happening is not the result of an explicit
> setting of the environment variable.
>
> It does seem that if I start up X11 by starting an xterm from terminal.app,
> then the resulting xterm is fine. But an additional xterm started by my
> .xinitrc file has the display variable 0:0 (same as if I launch X11 from the
> dock).
>
> So the problem seems not to be solely related to starting X11 from the dock.
>
> I remain mystified.
>
> -Ron-
>
>
>
> On Sep 25, 2008, at 5:33 PM, Daniel Price wrote:
>
>> I had this problem. My $DISPLAY was being set in
>> ~/.MacOSX/environment.plist (you have to remove the relevant lines and
>> logout and log back in again for changes to take effect).
>>
>> What is more annoying is that I still don't know what was setting it -
>> occasionally I would just find (despite having removed the line) that it
>> would reappear again. Eventually I removed the write permissions on
>> environment.plist and put echo $DISPLAY in my .profile to reassure myself
>> every time I open a terminal.
>>
>> Daniel
>>
>>> Message: 8
>>> Date: Thu, 25 Sep 2008 15:17:05 -0700
>>> From: Ronald Cohen <email@hidden>
>>> Subject: Re: "connection to ":1.0" refused by server
>>> To: Jeremy Huddleston <email@hidden>
>>> Cc: email@hidden
>>> Message-ID: <email@hidden>
>>> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
>>>
>>> Thank you, but this is not the case. I am using tcsh, and DISPLAY is
>>> not being set in my .cshrc. I do notice however that the DISPLAY
>>> environemnt variable has been set by SOMETHING to :1.0. Don't know
>>> what. Is this somehow built into tcsh? I also note that if I unset
>>> this display variable and attempt to open an xterm, I get an error:
>>>
>>> xterm Xt error: Can't open display:
>>> xterm: DISPLAY is not set
>>>
>>> So how do I arrange for DISPLAY to be set to a launchd socket?
>>>
>>> I note that the FAQ says don't run X11 from the dock, which is how
>>> I've done it for ages. Is this the source of the problem?
>>>
>>> On Sep 25, 2008, at 12:20 PM, Jeremy Huddleston wrote:
>>>
>>>> You shouldn't be connecting to :0 or :1. Your DISPLAY variable
>>>> should be to a launchd socket. I'm guessing you are setting DISPLAY
>>>> in your ~/.profile or ~/.bashrc. Remove that, and you should be good.
>>>>
>>>> This answer is in the list FAQ on xquartz.macosforge.org, so you
>>>> might look there (click on mailing lists) for specifics if the above
>>>> was not helpful enough.
>>>>
>>>> --Jeremy
>>>>
>>>> On Sep 25, 2008, at 10:07, Ronald Cohen wrote:
>>>>
>>>>> I'm having a problem which I occasionally had under Tiger which
>>>>> seems to be much worse on Leopard. On my laptop (Macbook Pro),
>>>>> when I have been running X11 at one physical location and move my
>>>>> Mac to another network (from one where the address is assigned by
>>>>> DHCP, to one where I have a fixed IP address, or vice versa), I
>>>>> frequently find that I cannot launch new X applications; I get
>>>>> messages like:
>>>>>
>>>>> Xlib: connection to "1.0" refused by sever
>>>>> Xlib: No protocol specified
>>>>>
>>>>> X server not responding
>>>>>
>>>>> It used to be that if I disconnected the network cable I could then
>>>>> open up an xwindow, and then once the cable was reconnected all was
>>>>> well -- as if the X server figured out who I was while the cable is
>>>>> disconnected. NOW I can still get an xwindow to open up with the
>>>>> cable disconnected, but when I reconnect the cable, the problem
>>>>> (some of the time) returns.
>>>>>
>>>>> It seems I can always fix things by shutting down X11 and
>>>>> restarting, but that is something I don't want to do if I am in the
>>>>> midst of a project.
>>>>>
>>>>> Is there a fix for this? Maybe some shell script that fixes
>>>>> ownership of the X11 server process?
>>>>>
>>>>> Also -- what is the best place to search for answers to questions
>>>>> like this? Searching xquartz.macosforge.org seems to be too small
>>>>> a universe, and a general Google search seems to be too broad.
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Ron Cohen
>>>>> _______________________________________________
>>>>> 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)
> Help/Unsubscribe/Update your Subscription:
>
> 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