Re: No Terminal Opening
Re: No Terminal Opening
- Subject: Re: No Terminal Opening
- From: Bill Janssen <email@hidden>
- Date: Sat, 28 Jun 2008 10:52:22 PDT
- Comments: In-reply-to Brandon Allbery <email@hidden> message dated "Fri, 27 Jun 2008 15:54:35 -0700."
> > muninn% xterm
> > Xlib: connection to "/tmp/launch-wUHHdr/:0" refused by server
> > Xlib: No protocol specified
That's kind of an interesting error. Trying to get the Python Xlib
working, I had to read the X11 docs from x.org. If you look at
xorg-docs-1.4/specs/X11/CH02, you'll find this (I've re-formatted it
a bit from the troff original):
``On POSIX-conformant systems, the display name or DISPLAY environment
variable can be a string in the format:
[<protocol>/][<hostname>]:<number>[.<screen-number>]
'<protocol>' specifies a protocol family or an alias for a protocol
family. Supported protocol families are implementation dependent.
The <protocol> entry is optional. If <protocol> is not specified,
the / separating <protocol> and <hostname> must also not be specified.''
News to me, and not very constraining -- the text says "can be", not
"must be" -- but it suggests that a DISPLAY value which starts with a
'/' might cause problems with some existing libraries. Apparently an
appropriate value for Apple's scheme should be something more like
'local//tmp/launch-XXXXX/:0' or even 'apple//tmp/launch-XXXXX/:0'.
I'd say your version of Xlib is seeing the leading '/', and wondering
where the 'protocol' is. That suggests you're not picking up the OS X
system version of Xlib.
Bill
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
This email sent to email@hidden