On Thursday March 26 2015 11:22:44 Brandon Allbery wrote:
It shouldn't be using :0.0 but instead the launchd socket. Or have you
improved that? In which case you get to debug your own breakage.
I have done nothing to improve that, this is what I get by launching X11 by
hand. Period.
So
On 26/03/15 17:46, René J.V. Bertin wrote:
On Thursday March 26 2015 11:22:44 Brandon Allbery wrote:
It shouldn't be using :0.0 but instead the launchd socket. Or have you
improved that? In which case you get to debug your own breakage.
I have done nothing to improve that, this is what I get
On Thu, Mar 26, 2015 at 1:46 PM, René J.V. rjvber...@gmail.com wrote:
So according to you, I shouldn't be able to connect to foo.local:0.0
because that's not using a launchd socket either?
That's using TCP which is also disabled by default for security reasons,
although there's a checkbox to
Well I'll be ...
I tried once more, launched XQuartz (2.7.4) without my own .xinitrc in place,
noted it had taken :1.0 (which sometimes happens when a previous instance
didn't exit cleanly), and then tried to use a fully specified DISPLAY
(${HOST}.local:1.0) and port:xterm. Whatever happened
On Thu, Mar 26, 2015 at 2:23 PM, René J.V. rjvber...@gmail.com wrote:
So according to you, I shouldn't be able to connect to foo.local:0.0
because that's not using a launchd socket either?
That's using TCP which is also disabled by default for security reasons,
although there's a
On Thursday March 26 2015 13:49:54 Brandon Allbery wrote:
On Thu, Mar 26, 2015 at 1:46 PM, René J.V. rjvber...@gmail.com wrote:
Yes, I did remove the launchd plist, because I don't want that functionality.
ANd that's always been perfectly supported in XQuartz at least. I did not yet
do
On Thursday March 26 2015 13:10:31 Jeremy Huddleston Sequoia wrote:
Well, if you remove the launchd.plist, then you're basically stuck with the
Tiger-era behavior of having to either launch your apps from X11's
Applications menu (or from an xterm launched from that menu) because
On Thursday March 26 2015 15:18:20 Jeremy Huddleston Sequoia wrote:
In the situation that I reported, my $DISPLAY was really :0.0 as verified
by starting /opt/X11/bin/xterm through the X11 Application menu. I just
couldn't connect to it through the X11 client libraries in MacPorts, only
At 3:44 PM +0100 3/26/15, René J.V. Bertin wrote:
I've got a 10.6 VM which is more or less a clone
of my 10.6.8 system of about 18 months ago. I'm
pretty sure that it used to run my X11
environment, and the same host (Parallels
Desktop 10) also runs X11 applications just fine
when I boot it
Hello,
I've got a 10.6 VM which is more or less a clone of my 10.6.8 system of about
18 months ago. I'm pretty sure that it used to run my X11 environment, and the
same host (Parallels Desktop 10) also runs X11 applications just fine when I
boot it into OS X 10.9 .
Not so (anymore) with
10 matches
Mail list logo
