Re: Anyone running X11 apps on Mojave?

[jackcf via macports-users]

I tried installing those but it still crashes on startup.
Did you do anything extra to get it working on OS X 10.14? I'm at 10.14.2

 



--
Sent from: http://mac-os-forge.2317878.n4.nabble.com/MacPorts-Users-f115275.html

Re: Anyone running X11 apps on Mojave? [Solved]

[Pierre Malard]

Hi,

Effectively, the problem was the risk of loop.
My preference would be toward the second solution but with a mechanism like the 
« alternatives » Debian. So, my solution could be:

  # File to replace with alternative
  File="/bin/bash"
  OptFile="/opt/local/bin/bash"
  AlternDir="/etc/alternatives"

  # Creation of a directory to be use with alternative mechanism.
  [ -d "${AlternDir}" ] || mkdir -p "${AlternDir}"

  # If it’s a symbolic?
  if [ -h "${File}" ] ; then
mv "${File}" "${File}.traditional"
ln -s "${File}.traditional" "${File}"
  fi

  # Creation of the alternative
  [ -f "${File}" ] && /bin/rm "${File}"
  ln -s "${OptFile}" "${File}"

As is, if an OS upgrade arrive, if this one change something about /bin/bash, I 
can reactive it simply.

Best wishes.


> Le 22 janv. 2019 à 07:23, Bill Cole 
>  a écrit :
> 
> On 21 Jan 2019, at 5:41, Pierre Malard wrote:
> 
>> It’s a great new for me but I have a subsidiary question:
>>   « How can I use the MacPort BASH in place of Apple one? »
>> 
>> If you have a solution…
> 
> I have options for that specific task...
> 
> 
> 1. Switch to the MacPorts bash without looping
> 
> Put these 4 lines at the top of  ~/.bash_profile:
> 
> if [ -z "$MACPORTS_BASH" ]  && [ -x /opt/local/bin/bash ]
> then
>  MACPORTS_BASH=DONE PATH=/opt/local/bin:$PATH  exec -l bash -l
> fi
> 
> You could probably put those in /etc/profile with equivalent safety and make 
> it happen for all login shells. This approach WILL NOT fix older versions of 
> MacOS X, where /bin/sh (the POSIX default shell) is a version of bash which 
> is vulnerable to serious security flaws. There is a risk in this because the 
> MacPorts bash depends on MacPorts dynamic libraries. Adding precautionary 
> checks inside the conditional might be able to mitigate those risks.
> 
> OR:
> 
> 2. Replace /bin/sh
> 
>   The following patch will add a "static" variant to the bash port and 
> includes a message describing how to replace /bin/sh with that build. If you 
> use it, you MUST re-patch the Portfile every time the bash port is updated. 
> It SHOULD NOT be in the MacPorts core because it is a horrifically 
> unsupportable hack that no one should ever use because it violates the core 
> of the OS.
> 
> HOWEVER: it has worked for me for a few years on a Snow Leopard machine where 
> the last Apple bash cannot be allowed to exist...
> 
>  BEGIN PATCH 
> --- 
> /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/shells/bash/Portfile.orig
>   2018-06-02 09:27:05.0 -0400
> +++ 
> /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/shells/bash/Portfile
>2018-06-09 21:24:27.0 -0400
> @@ -123,6 +123,29 @@
> # Always source .bashrc when connecting remotely with ssh, #40603
> configure.cflags-append -DSSH_SOURCE_BASHRC
> 
> +variant static description "Links all MacPorts library dependencies 
> statically to allow the binary to replace the system shell"  {
> +   system "mkdir -p ${prefix}/lib/statics"
> +   system "ln -f ${prefix}/lib/*.a ${prefix}/lib/statics/"
> +   system "ln -f ${prefix}/lib/*.o ${prefix}/lib/statics/"
> +   configure.args-append  "--with-included-gettext 
> --libdir=/opt/local/lib/statics "
> +   configure.ldflags-delete "-L${prefix}/lib"
> +   configure.ldflags-append "-L${prefix}/lib/statics"
> +}
> +
> +post-install {
> +  if {[variant_isset static]} {
> +  ui_msg 
> "***"
> +  ui_msg "If you want to replace the system shell with this build of 
> bash,"
> +  ui_msg "you must do so manually by copying or hardlinking it into /bin 
> !"
> +  ui_msg "  ln -f /opt/local/bin/bash /bin/bash"
> +  ui_msg "  ln -f /opt/local/bin/bash /bin/sh"
> +  ui_msg "OR:"
> +  ui_msg "  cp /opt/local/bin/bash /bin/bash"
> +  ui_msg "  cp /opt/local/bin/bash /bin/sh"
> +  ui_msg 
> "***"
> +   }
> +}
> +
> livecheck.type  regex
> livecheck.url   
> http://ftp.gnu.org/gnu/${name}/${name}-${bash_version}-patches/?C=M=D
> livecheck.version   [format %03d ${bash_patchlevel}]
>  END PATCH 
> 
> The goal here is to build a shell that can replace /bin/sh and be independent 
> of every dynamic shared library for which a linkable static library exists. 
> The result on the Snow Leopard machine where I hacked this up is a /bin/sh 
> which depends only on /usr/lib/libSystem.B.dylib, so in an emergency 
> single-user boot where /opt/local is unmounted or mangled, the shell still 
> can work.
> 
> 
> 
> --
> Bill Cole
> b...@scconsult.com or billc...@apache.org
> (AKA @grumpybozo and many *@billmail.scconsult.com addresses)
> Available For Hire: https://linkedin.com/in/billcole

--
Pierre Malard

  « Ce qui tombe sous le sens 

Re: Anyone running X11 apps on Mojave? [Solved]

[Bill Cole]

On 21 Jan 2019, at 5:41, Pierre Malard wrote:


It’s a great new for me but I have a subsidiary question:
   « How can I use the MacPort BASH in place of Apple one? »

If you have a solution…


I have options for that specific task...


1. Switch to the MacPorts bash without looping

Put these 4 lines at the top of  ~/.bash_profile:

if [ -z "$MACPORTS_BASH" ]  && [ -x /opt/local/bin/bash ]
then
  MACPORTS_BASH=DONE PATH=/opt/local/bin:$PATH  exec -l bash -l
fi

You could probably put those in /etc/profile with equivalent safety and 
make it happen for all login shells. This approach WILL NOT fix older 
versions of MacOS X, where /bin/sh (the POSIX default shell) is a 
version of bash which is vulnerable to serious security flaws. There is 
a risk in this because the MacPorts bash depends on MacPorts dynamic 
libraries. Adding precautionary checks inside the conditional might be 
able to mitigate those risks.


OR:

2. Replace /bin/sh

   The following patch will add a "static" variant to the bash port and 
includes a message describing how to replace /bin/sh with that build. If 
you use it, you MUST re-patch the Portfile every time the bash port is 
updated. It SHOULD NOT be in the MacPorts core because it is a 
horrifically unsupportable hack that no one should ever use because it 
violates the core of the OS.


HOWEVER: it has worked for me for a few years on a Snow Leopard machine 
where the last Apple bash cannot be allowed to exist...


 BEGIN PATCH 
--- 
/opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/shells/bash/Portfile.orig	2018-06-02 
09:27:05.0 -0400
+++ 
/opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/shells/bash/Portfile	2018-06-09 
21:24:27.0 -0400

@@ -123,6 +123,29 @@
 # Always source .bashrc when connecting remotely with ssh, #40603
 configure.cflags-append -DSSH_SOURCE_BASHRC

+variant static description "Links all MacPorts library dependencies 
statically to allow the binary to replace the system shell"  {

+   system "mkdir -p ${prefix}/lib/statics"
+   system "ln -f ${prefix}/lib/*.a ${prefix}/lib/statics/"
+   system "ln -f ${prefix}/lib/*.o ${prefix}/lib/statics/"
+   configure.args-append  "--with-included-gettext 
--libdir=/opt/local/lib/statics "

+   configure.ldflags-delete "-L${prefix}/lib"
+   configure.ldflags-append "-L${prefix}/lib/statics"
+}
+
+post-install {
+  if {[variant_isset static]} {
+  ui_msg 
"***"
+  ui_msg "If you want to replace the system shell with this build 
of bash,"
+  ui_msg "you must do so manually by copying or hardlinking it into 
/bin !"

+  ui_msg "  ln -f /opt/local/bin/bash /bin/bash"
+  ui_msg "  ln -f /opt/local/bin/bash /bin/sh"
+  ui_msg "OR:"
+  ui_msg "  cp /opt/local/bin/bash /bin/bash"
+  ui_msg "  cp /opt/local/bin/bash /bin/sh"
+  ui_msg 
"***"

+   }
+}
+
 livecheck.type  regex
 livecheck.url   
http://ftp.gnu.org/gnu/${name}/${name}-${bash_version}-patches/?C=M=D

 livecheck.version   [format %03d ${bash_patchlevel}]
 END PATCH 

The goal here is to build a shell that can replace /bin/sh and be 
independent of every dynamic shared library for which a linkable static 
library exists. The result on the Snow Leopard machine where I hacked 
this up is a /bin/sh which depends only on /usr/lib/libSystem.B.dylib, 
so in an emergency single-user boot where /opt/local is unmounted or 
mangled, the shell still can work.




--
Bill Cole
b...@scconsult.com or billc...@apache.org
(AKA @grumpybozo and many *@billmail.scconsult.com addresses)
Available For Hire: https://linkedin.com/in/billcole

Re: Anyone running X11 apps on Mojave? [Solved]

[Pierre Malard]

I’m a stupid guy!

Effectively, the easiest way is to configure the Terminal to use 
/opt/local/bin/bash!
I prefer this solution because of OS upgrades which erase any local 
configuration.

However your suggestion to use exec -a -bash /opt/local/bin/bash —noprofile 
work.

Thanks a lot

> Le 21 janv. 2019 à 12:36, Richard L. Hamilton  a écrit :
> 
> Instead of that line in .bash_profile, as long as all the systems you use 
> your login (if you're using OpenDirectory) on have /opt/local/bin/bash 
> installed,
> the Unix way would be to add /opt/local/bin/bash to the list of shells in 
> /etc/shells (if that file doesn't exist, it's as if it existed with just 
> /bin/sh and /bin/csh,
> one per line), and edit your account so that your login shell was 
> /opt/local/bin/bash.
> 
> The one gotcha when reinstalling MacPorts after an OS upgrade, (actually, 
> just before the OS upgrade) you'd have to edit your account again to use an 
> OS supplied shell that will be there throughout the MacPorts reinstall, and 
> change it back when done.
> 
> If your account info is just in local files, you can probably use the chsh 
> command rather than the Directory Editor app to change your shell, but it 
> still needs to be in /etc/shells.
> 
> FYI, my /etc/shells contains
> /bin/bash
> /bin/csh
> /bin/ksh
> /bin/sh
> /bin/tcsh
> /bin/zsh
> 
> You cannot add --login to your line in .bash_profile, because that would loop 
> (you're already reading .bash_profile, so you exec a login shell which reads 
> it again, exec's again, etc).  Maybe there's some other tricky thing you 
> could do with your own files that might work; perhaps if it were the last 
> line in .bash_profile, and looked like
> 
> [ -x /opt/local/bin/bash ] && exec -a -bash /opt/local/bin/bash --noprofile
> 
> that _might_ work (it would look like a login shell with $0 set to -bash, but 
> not actually run the profile files again), but I'm not going to make all those
> changes (I use /bin/ksh as my login shell), log out, log back in to test, and 
> then reverse all that, just to find out if it works.
> 
> If the only way you run interactive shells where you really want 
> /opt/local/bin/bash is with Terminal, you can change its settings to use that 
> as your shell, only for what's run under Terminal (won't affect xterm, ssh, 
> etc).
> 
> Those are the only sorts of ways I can see around whatever problem that line 
> is causing you, while still running the shell of your choice.
> 
> 
>> On Jan 21, 2019, at 05:41, Pierre Malard  wrote:
>> 
>> Hi, a great thanks!
>> 
>> You were right, it was my specific configuration which was in cause, even if 
>> it was not a DISPLAY error.
>> 
>> After a long wile and successives tests I found why it doesn’t work :-)
>> 
>> First, I found that was the « —login » parameter of X11 script which was in 
>> cause. If I launch X11 without it, it works. In piratical:
>> 1- the « exec -l /bin/bash --login -c 'exec 
>> /Applications/MacPorts/X11.app/Contents/MacOS/X11.bin' - 
>> /Applications/MacPorts/X11.app/Contents/MacOS/X11.bin » of X11 script won’t 
>> work.
>> 2- An «  exec -l /bin/bash -c 'exec 
>> /Applications/MacPorts/X11.app/Contents/MacOS/X11.bin' - 
>> /Applications/MacPorts/X11.app/Contents/MacOS/X11.bin » world fine.
>> It’s the same thing with XQuartz.
>> 
>> The explanation now:
>> As I have a BASH v4.3 installed with MacPort, I would use it in my « 
>> Terminal.app » sessions and I just add this line in my « ~/.bash_profile » 
>> file:
>>  [ -x /opt/local/bin/bash ] && exec /opt/local/bin/bash
>> to launch BASH v4.3. I remove it and everything work with X11…
>> 
>> As it is evident now, this « exec » line trouble opening X11 with the other 
>> « exec —login ». As explain in the « man bash »:
>>  When bash is invoked as an interactive login shell, or as a 
>> non-interactive shell  with
>>  the --login option, it first reads and executes commands from the file 
>> /etc/profile, if
>>  that  file  exists.   After  reading  that  file,   it   looks   for   
>> ~/.bash_profile,
>>  ~/.bash_login,  and ~/.profile, in that order, and reads and executes 
>> commands from the
>>  first one that exists and is readable.
>> So, my « ~/.bash_profile » were read with the first call, not with the 
>> second one.
>> 
>> It’s a great new for me but I have a subsidiary question:
>>  « How can I use the MacPort BASH in place of Apple one? »
>> 
>> If you have a solution…
>> 
>> 
>> Le 19 janv. 2019 à 12:03, Christopher Jones  a 
>> écrit :
>>> 
>>> The logs below indicate problems with DISPLAY. They also suggest you have 
>>> some residual parts of the non-macports Xquartz installed.
>>> 
>>> Do you set DISPLAY at all in any of your shell login scripts. If so remove 
>>> this. Try creating a new test user on your system, log in as that and see 
>>> if it works from there. If so it would indicate something in your user 
>>> environment.
>>> 
>>> Make sure you have all parts of the other Xquartz removed. In 

Re: Anyone running X11 apps on Mojave? [Solved]

[Richard L. Hamilton]

Instead of that line in .bash_profile, as long as all the systems you use your 
login (if you're using OpenDirectory) on have /opt/local/bin/bash installed, 
the Unix way would be to add /opt/local/bin/bash to the list of shells in 
/etc/shells (if that file doesn't exist, it's as if it existed with just 
/bin/sh and /bin/csh,
one per line), and edit your account so that your login shell was 
/opt/local/bin/bash.

The one gotcha when reinstalling MacPorts after an OS upgrade, (actually, just 
before the OS upgrade) you'd have to edit your account again to use an OS 
supplied shell that will be there throughout the MacPorts reinstall, and change 
it back when done.

If your account info is just in local files, you can probably use the chsh 
command rather than the Directory Editor app to change your shell, but it still 
needs to be in /etc/shells.

FYI, my /etc/shells contains
/bin/bash
/bin/csh
/bin/ksh
/bin/sh
/bin/tcsh
/bin/zsh

You cannot add --login to your line in .bash_profile, because that would loop 
(you're already reading .bash_profile, so you exec a login shell which reads it 
again, exec's again, etc).  Maybe there's some other tricky thing you could do 
with your own files that might work; perhaps if it were the last line in 
.bash_profile, and looked like

[ -x /opt/local/bin/bash ] && exec -a -bash /opt/local/bin/bash --noprofile

that _might_ work (it would look like a login shell with $0 set to -bash, but 
not actually run the profile files again), but I'm not going to make all those
changes (I use /bin/ksh as my login shell), log out, log back in to test, and 
then reverse all that, just to find out if it works.

If the only way you run interactive shells where you really want 
/opt/local/bin/bash is with Terminal, you can change its settings to use that 
as your shell, only for what's run under Terminal (won't affect xterm, ssh, 
etc).

Those are the only sorts of ways I can see around whatever problem that line is 
causing you, while still running the shell of your choice.


> On Jan 21, 2019, at 05:41, Pierre Malard  wrote:
> 
> Hi, a great thanks!
> 
> You were right, it was my specific configuration which was in cause, even if 
> it was not a DISPLAY error.
> 
> After a long wile and successives tests I found why it doesn’t work :-)
> 
> First, I found that was the « —login » parameter of X11 script which was in 
> cause. If I launch X11 without it, it works. In piratical:
> 1- the « exec -l /bin/bash --login -c 'exec 
> /Applications/MacPorts/X11.app/Contents/MacOS/X11.bin' - 
> /Applications/MacPorts/X11.app/Contents/MacOS/X11.bin » of X11 script won’t 
> work.
> 2- An «  exec -l /bin/bash -c 'exec 
> /Applications/MacPorts/X11.app/Contents/MacOS/X11.bin' - 
> /Applications/MacPorts/X11.app/Contents/MacOS/X11.bin » world fine.
> It’s the same thing with XQuartz.
> 
> The explanation now:
> As I have a BASH v4.3 installed with MacPort, I would use it in my « 
> Terminal.app » sessions and I just add this line in my « ~/.bash_profile » 
> file:
>   [ -x /opt/local/bin/bash ] && exec /opt/local/bin/bash
> to launch BASH v4.3. I remove it and everything work with X11…
> 
> As it is evident now, this « exec » line trouble opening X11 with the other « 
> exec —login ». As explain in the « man bash »:
>   When bash is invoked as an interactive login shell, or as a 
> non-interactive shell  with
>   the --login option, it first reads and executes commands from the file 
> /etc/profile, if
>   that  file  exists.   After  reading  that  file,   it   looks   for   
> ~/.bash_profile,
>   ~/.bash_login,  and ~/.profile, in that order, and reads and executes 
> commands from the
>   first one that exists and is readable.
> So, my « ~/.bash_profile » were read with the first call, not with the second 
> one.
> 
> It’s a great new for me but I have a subsidiary question:
>   « How can I use the MacPort BASH in place of Apple one? »
> 
> If you have a solution…
> 
> 
> Le 19 janv. 2019 à 12:03, Christopher Jones  a 
> écrit :
>> 
>> The logs below indicate problems with DISPLAY. They also suggest you have 
>> some residual parts of the non-macports Xquartz installed.
>> 
>> Do you set DISPLAY at all in any of your shell login scripts. If so remove 
>> this. Try creating a new test user on your system, log in as that and see if 
>> it works from there. If so it would indicate something in your user 
>> environment.
>> 
>> Make sure you have all parts of the other Xquartz removed. In particlar make 
>> sure all the plist entries under Library are removed.
>> 
>> cheers Chris
>> 
>>> On 19 Jan 2019, at 10:58 am, Pierre Malard  wrote:
>>> 
>>> Thanks again,
>>> 
>>> There is no crash but here are the only logs I found. I don’t understand 
>>> why it doesn’t work. The log file « ~/Library/Logs/X11/org.macports.log » 
>>> is generate when I launch X11.bin directly on a Terminal. When I try to 
>>> open App, there is nothing neither logs.
>>> However, I have the same trouble on 

Re: Anyone running X11 apps on Mojave? [Solved]

[Pierre Malard]

Hi, a great thanks!

You were right, it was my specific configuration which was in cause, even if it 
was not a DISPLAY error.

After a long wile and successives tests I found why it doesn’t work :-)

First, I found that was the « —login » parameter of X11 script which was in 
cause. If I launch X11 without it, it works. In piratical:
1- the « exec -l /bin/bash --login -c 'exec 
/Applications/MacPorts/X11.app/Contents/MacOS/X11.bin' - 
/Applications/MacPorts/X11.app/Contents/MacOS/X11.bin » of X11 script won’t 
work.
2- An «  exec -l /bin/bash -c 'exec 
/Applications/MacPorts/X11.app/Contents/MacOS/X11.bin' - 
/Applications/MacPorts/X11.app/Contents/MacOS/X11.bin » world fine.
It’s the same thing with XQuartz.

The explanation now:
As I have a BASH v4.3 installed with MacPort, I would use it in my « 
Terminal.app » sessions and I just add this line in my « ~/.bash_profile » file:
[ -x /opt/local/bin/bash ] && exec /opt/local/bin/bash
to launch BASH v4.3. I remove it and everything work with X11…

As it is evident now, this « exec » line trouble opening X11 with the other « 
exec —login ». As explain in the « man bash »:
   When bash is invoked as an interactive login shell, or as a 
non-interactive shell  with
   the --login option, it first reads and executes commands from the file 
/etc/profile, if
   that  file  exists.   After  reading  that  file,   it   looks   for   
~/.bash_profile,
   ~/.bash_login,  and ~/.profile, in that order, and reads and executes 
commands from the
   first one that exists and is readable.
So, my « ~/.bash_profile » were read with the first call, not with the second 
one.

It’s a great new for me but I have a subsidiary question:
   « How can I use the MacPort BASH in place of Apple one? »

If you have a solution…


Le 19 janv. 2019 à 12:03, Christopher Jones  a écrit :
> 
> The logs below indicate problems with DISPLAY. They also suggest you have 
> some residual parts of the non-macports Xquartz installed.
> 
> Do you set DISPLAY at all in any of your shell login scripts. If so remove 
> this. Try creating a new test user on your system, log in as that and see if 
> it works from there. If so it would indicate something in your user 
> environment.
> 
> Make sure you have all parts of the other Xquartz removed. In particlar make 
> sure all the plist entries under Library are removed.
> 
> cheers Chris
> 
>> On 19 Jan 2019, at 10:58 am, Pierre Malard  wrote:
>> 
>> Thanks again,
>> 
>> There is no crash but here are the only logs I found. I don’t understand why 
>> it doesn’t work. The log file « ~/Library/Logs/X11/org.macports.log » is 
>> generate when I launch X11.bin directly on a Terminal. When I try to open 
>> App, there is nothing neither logs.
>> However, I have the same trouble on all my Mac on Mojave. Is it a new « 
>> security » mesure from Apple?
>> 
>> piotr@Rascasse:~/Library/Logs/X11$ cat org.macosforge.xquartz.log
>> X11.app: DISPLAY does not look like a launchd set variable, unsetting.
>> X11.app: main(): argc=1
>>  argv[0] = /Applications/Utilities/XQuartz.app/Contents/MacOS/X11.bin
>> Waiting for startup parameters via Mach IPC.
>> X11.app: No launchd socket handed off, unsetting DISPLAY
>> X11.app: do_start_x11_server(): argc=7
>>  argv[0] = /opt/X11/bin/X
>>  argv[1] = :0
>>  argv[2] = -listen
>>  argv[3] = tcp
>>  argv[4] = -iglx
>>  argv[5] = -auth
>>  argv[6] = /Users/piotr/.serverauth.38793
>> [1706135.851] Xquartz starting:
>> [1706135.851] X.Org X Server 1.18.4
>> [1706135.851] Build Date: 20161025
>> [1706135.870] x: 0, y: 0, w: 2560, h: 1418
>> [1706135.883] (II) GLX: Initialized Core OpenGL GL provider for screen 0
>> [1706135.965] X11.app: DarwinProcessFDAdditionQueue_thread: Sleeping to 
>> allow xinitrc to catchup.
>> [1706135.982] (EE) Error loading keymap /tmp/server-0.xkm
>> [1706135.982] (EE) XKB: Failed to load keymap. Loading default keymap 
>> instead.
>> [1706137.861] noPseudoramiXExtension=0, pseudoramiXNumScreens=1
>> [1706160.556] (II) Server terminated successfully (0). Closing log file.
>> 
>> 
>> 
>> piotr@Rascasse:~/Library/Logs/X11$ cat org.macports.log
>> X11.app: DISPLAY 
>> ("/private/tmp/com.apple.launchd.SKs4xIJJVq/org.macosforge.xquartz:0") does 
>> not match our id ("org.macports"), unsetting.
>> X11.app: main(): argc=2
>>  argv[0] = /Applications/MacPorts/X11.app/Contents/MacOS/X11.bin
>>  argv[1] = -psn_0_340051
>> Waiting for startup parameters via Mach IPC.
>> X11.app: No launchd socket handed off, unsetting DISPLAY
>> X11.app: do_start_x11_server(): argc=7
>>  argv[0] = /opt/local/bin/Xquartz
>>  argv[1] = :0
>>  argv[2] = -nolisten
>>  argv[3] = tcp
>>  argv[4] = -iglx
>>  argv[5] = -auth
>>  argv[6] = /Users/piotr/.serverauth.1026
>> [   227.231] Xquartz starting:
>> [   227.231] X.Org X Server 1.18.4
>> [   227.231] Build Date: 20180831
>> [   227.238] x: 0, y: 0, w: 2560, h: 1418
>> [   227.303] (II) GLX: 

Re: Anyone running X11 apps on Mojave?

[dan d.]

Did you try the open command in terminaal first?

On Fri, 18 Jan 2019, Pierre Malard wrote:

> And what about the question?
>
> I have X11-server installed from MacPorts. An Aqua App is installed in 
> /Applications/MacPorts/X11.app. When I want to launch it, nothing since my 
> update to Mojave :-(
>
> The only way I found is to execute the binary directly from a Terminal like 
> that:
>   $ /Applications/MacPorts/X11.app/Contents.MacOS/X11.bin &
> It???s not really fun.
>
> Is anyone have a solution?
>
> > Le 13 d??c. 2018 ?? 02:36, Ryan Schmidt  a ??crit :
> >
> >
> >
> > On Dec 12, 2018, at 03:02, Tabitha McNerney wrote:
> >
> >> I just installed XQuartz 2.7.11 today on a fresh Mac running Mojave 
> >> 10.14.2. I installed XQuartz from the XQuartz.pkg found in the disk image 
> >> (dmg) file on the XQuartz support site: https://www.xquartz.org/
> >>
> >> I didn't have any problems installing and then later running XQuartz. 
> >> However, on Mojave, there was an interesting alert panel which appeared 
> >> during the pkg installation process which I have not seen on previous 
> >> versions of macOS when installing XQuartz, which alert panel with two 
> >> buttons, one which stated "Don't Allow" and the other stated "OK", and 
> >> text which stated the following:
> >>
> >> "Installer.app" wants access to control "System Events.app". Allowing 
> >> control will provide access to documents and data in "System Events.app", 
> >> and to perform actions within that app.
> >>
> >> I didn't know what to do so I waited. There must have been a timeout 
> >> because the panel disappeared on its own without me making a selection. 
> >> The package installer process then finished on its own and stated XQuartz 
> >> had been installed successfully. I was then able to run XQuartz without 
> >> any issues. Interestingly, when I now run System Preferences and select 
> >> Security & Privacy -> Privacy -> Automation there is an entry for 
> >> "Installer.app" and underneath a check box next to "System Events.app". 
> >> The check box is unchecked. I gather this all has something to do with 
> >> changes to Mojave's security and privacy settings. Has anyone else seen 
> >> this with or without XQuartz involved? If so, any ideas of what this means?
> >
> > The XQuartz.pkg installer's postinstall script uses System Events to 
> > display a dialog:
> >
> >
> >/usr/bin/osascript < >tell application "System Events"
> >activate
> >display dialog "You will need to log out and log back in to make 
> > XQuartz your default X11 server." buttons {"OK"}
> >end tell
> >
> >
> > If you don't allow the installer to control System Events, then it cannot 
> > display that dialog for you.
> >
> > I guess previous versions of macOS didn't restrict scripting access in this 
> > way and just always allowed it. Probably a good thing for security that the 
> > OS now warns you about this, but the installer was built 2 years ago, so 
> > the developer couldn't have anticipated that macOS would be changed in this 
> > way.
> >
> > This has nothing to do with MacPorts. You could report the issue to the 
> > developer of XQuartz:
> >
> > https://bugs.freedesktop.org/enter_bug.cgi
> >
> >
>
> --
> Pierre Malard
>
>??Mittler zwischen hirn und h??nden muss das hirz sein !??
>??La m??diation entre le cerveau et les mains doit ??tre le c??ur !??
>  Fritz Lang - "M??tropolis" - 
> 1929
>|\  _,,,---,,_
>/,`.-'`'-.  ;-;;,_
>   |,4-  ) )-,_. ,\ (  `'-'
>  '---''(_/--'  `-'\_)   ??r
>
> perl -e '$_=q#: 3|\ 5_,3-3,2_: 3/,`.'"'"'`'"'"' 5-.  ;-;;,_:  |,A-  ) )-,_. 
> ,\ (  `'"'"'-'"'"': '"'"'-3'"'"'2(_/--'"'"'  `-'"'"'\_): 
> 24??r::#;y#:#\n#;s#(\D)(\d+)#$1x$2#ge;print'
> - --> Ce message n???engage que son auteur <--
>
>
>
> [ Part 2, "Message signed with OpenPGP"  Application/PGP-SIGNATURE ]
> [ (Name: "signature.asc") 849 bytes. ]
> [ Unable to print this part. ]
>

-- 
XB
m

Re: Anyone running X11 apps on Mojave?

[Christopher Jones]

The logs below indicate problems with DISPLAY. They also suggest you have some 
residual parts of the non-macports Xquartz installed.

Do you set DISPLAY at all in any of your shell login scripts. If so remove 
this. Try creating a new test user on your system, log in as that and see if it 
works from there. If so it would indicate something in your user environment.

Make sure you have all parts of the other Xquartz removed. In particlar make 
sure all the plist entries under Library are removed.

cheers Chris

> On 19 Jan 2019, at 10:58 am, Pierre Malard  wrote:
> 
> Thanks again,
> 
> There is no crash but here are the only logs I found. I don’t understand why 
> it doesn’t work. The log file « ~/Library/Logs/X11/org.macports.log » is 
> generate when I launch X11.bin directly on a Terminal. When I try to open 
> App, there is nothing neither logs.
> However, I have the same trouble on all my Mac on Mojave. Is it a new « 
> security » mesure from Apple?
> 
> piotr@Rascasse:~/Library/Logs/X11$ cat org.macosforge.xquartz.log
> X11.app: DISPLAY does not look like a launchd set variable, unsetting.
> X11.app: main(): argc=1
>   argv[0] = /Applications/Utilities/XQuartz.app/Contents/MacOS/X11.bin
> Waiting for startup parameters via Mach IPC.
> X11.app: No launchd socket handed off, unsetting DISPLAY
> X11.app: do_start_x11_server(): argc=7
>   argv[0] = /opt/X11/bin/X
>   argv[1] = :0
>   argv[2] = -listen
>   argv[3] = tcp
>   argv[4] = -iglx
>   argv[5] = -auth
>   argv[6] = /Users/piotr/.serverauth.38793
> [1706135.851] Xquartz starting:
> [1706135.851] X.Org X Server 1.18.4
> [1706135.851] Build Date: 20161025
> [1706135.870] x: 0, y: 0, w: 2560, h: 1418
> [1706135.883] (II) GLX: Initialized Core OpenGL GL provider for screen 0
> [1706135.965] X11.app: DarwinProcessFDAdditionQueue_thread: Sleeping to allow 
> xinitrc to catchup.
> [1706135.982] (EE) Error loading keymap /tmp/server-0.xkm
> [1706135.982] (EE) XKB: Failed to load keymap. Loading default keymap instead.
> [1706137.861] noPseudoramiXExtension=0, pseudoramiXNumScreens=1
> [1706160.556] (II) Server terminated successfully (0). Closing log file.
> 
> 
> 
> piotr@Rascasse:~/Library/Logs/X11$ cat org.macports.log
> X11.app: DISPLAY 
> ("/private/tmp/com.apple.launchd.SKs4xIJJVq/org.macosforge.xquartz:0") does 
> not match our id ("org.macports"), unsetting.
> X11.app: main(): argc=2
>   argv[0] = /Applications/MacPorts/X11.app/Contents/MacOS/X11.bin
>   argv[1] = -psn_0_340051
> Waiting for startup parameters via Mach IPC.
> X11.app: No launchd socket handed off, unsetting DISPLAY
> X11.app: do_start_x11_server(): argc=7
>   argv[0] = /opt/local/bin/Xquartz
>   argv[1] = :0
>   argv[2] = -nolisten
>   argv[3] = tcp
>   argv[4] = -iglx
>   argv[5] = -auth
>   argv[6] = /Users/piotr/.serverauth.1026
> [   227.231] Xquartz starting:
> [   227.231] X.Org X Server 1.18.4
> [   227.231] Build Date: 20180831
> [   227.238] x: 0, y: 0, w: 2560, h: 1418
> [   227.303] (II) GLX: Initialized Core OpenGL GL provider for screen 0
> [   229.063] X11.app: DarwinProcessFDAdditionQueue_thread: Sleeping to allow 
> xinitrc to catchup.
> [   229.087] (EE) Error loading keymap /tmp/server-0.xkm
> [   229.087] (EE) XKB: Failed to load keymap. Loading default keymap instead.
> [   229.872] noPseudoramiXExtension=0, pseudoramiXNumScreens=1
> [ 25122.470] x: 0, y: 0, w: 2560, h: 1418
> [ 25122.522] noPseudoramiXExtension=0, pseudoramiXNumScreens=1
> [ 25122.522] noPseudoramiXExtension=0, pseudoramiXNumScreens=1
> [ 26144.274] x: 0, y: 0, w: 2560, h: 1418
> [ 26144.278] noPseudoramiXExtension=0, pseudoramiXNumScreens=1
> [ 31657.125] x: 0, y: 0, w: 2560, h: 1418
> [ 31657.128] noPseudoramiXExtension=0, pseudoramiXNumScreens=1
> [ 63133.955] x: 0, y: 0, w: 2560, h: 1418
> [ 63133.960] noPseudoramiXExtension=0, pseudoramiXNumScreens=1
> [ 70910.981] x: 0, y: 0, w: 2560, h: 1418
> [ 70910.985] noPseudoramiXExtension=0, pseudoramiXNumScreens=1
> [ 83867.215] x: 0, y: 0, w: 2560, h: 1418
> [ 83867.229] noPseudoramiXExtension=0, pseudoramiXNumScreens=1
> [110886.434] x: 0, y: 0, w: 2560, h: 1418
> [110886.438] noPseudoramiXExtension=0, pseudoramiXNumScreens=1
> [153571.180] x: 0, y: 0, w: 2560, h: 1418
> [153571.188] noPseudoramiXExtension=0, pseudoramiXNumScreens=1
> [162162.765] x: 0, y: 0, w: 2560, h: 1418
> [162162.769] noPseudoramiXExtension=0, pseudoramiXNumScreens=1
> [197919.300] x: 0, y: 0, w: 2560, h: 1418
> [197919.305] noPseudoramiXExtension=0, pseudoramiXNumScreens=1
> [198637.899] x: 0, y: 0, w: 2560, h: 1418
> [198637.907] noPseudoramiXExtension=0, pseudoramiXNumScreens=1
> [242705.063] x: 0, y: 0, w: 2560, h: 1418
> [242705.068] noPseudoramiXExtension=0, pseudoramiXNumScreens=1
> [250616.473] x: 0, y: 0, w: 2560, h: 1418
> [250616.478] noPseudoramiXExtension=0, pseudoramiXNumScreens=1
> [257996.670] x: 0, y: 0, w: 2560, h: 1418
> [257996.699] noPseudoramiXExtension=0, pseudoramiXNumScreens=1

Re: Anyone running X11 apps on Mojave?

[Pierre Malard]

Thanks again,

There is no crash but here are the only logs I found. I don’t understand why it 
doesn’t work. The log file « ~/Library/Logs/X11/org.macports.log » is generate 
when I launch X11.bin directly on a Terminal. When I try to open App, there is 
nothing neither logs.
However, I have the same trouble on all my Mac on Mojave. Is it a new « 
security » mesure from Apple?

piotr@Rascasse:~/Library/Logs/X11$ cat org.macosforge.xquartz.log
X11.app: DISPLAY does not look like a launchd set variable, unsetting.
X11.app: main(): argc=1
argv[0] = /Applications/Utilities/XQuartz.app/Contents/MacOS/X11.bin
Waiting for startup parameters via Mach IPC.
X11.app: No launchd socket handed off, unsetting DISPLAY
X11.app: do_start_x11_server(): argc=7
argv[0] = /opt/X11/bin/X
argv[1] = :0
argv[2] = -listen
argv[3] = tcp
argv[4] = -iglx
argv[5] = -auth
argv[6] = /Users/piotr/.serverauth.38793
[1706135.851] Xquartz starting:
[1706135.851] X.Org X Server 1.18.4
[1706135.851] Build Date: 20161025
[1706135.870] x: 0, y: 0, w: 2560, h: 1418
[1706135.883] (II) GLX: Initialized Core OpenGL GL provider for screen 0
[1706135.965] X11.app: DarwinProcessFDAdditionQueue_thread: Sleeping to allow 
xinitrc to catchup.
[1706135.982] (EE) Error loading keymap /tmp/server-0.xkm
[1706135.982] (EE) XKB: Failed to load keymap. Loading default keymap instead.
[1706137.861] noPseudoramiXExtension=0, pseudoramiXNumScreens=1
[1706160.556] (II) Server terminated successfully (0). Closing log file.



piotr@Rascasse:~/Library/Logs/X11$ cat org.macports.log
X11.app: DISPLAY 
("/private/tmp/com.apple.launchd.SKs4xIJJVq/org.macosforge.xquartz:0") does not 
match our id ("org.macports"), unsetting.
X11.app: main(): argc=2
argv[0] = /Applications/MacPorts/X11.app/Contents/MacOS/X11.bin
argv[1] = -psn_0_340051
Waiting for startup parameters via Mach IPC.
X11.app: No launchd socket handed off, unsetting DISPLAY
X11.app: do_start_x11_server(): argc=7
argv[0] = /opt/local/bin/Xquartz
argv[1] = :0
argv[2] = -nolisten
argv[3] = tcp
argv[4] = -iglx
argv[5] = -auth
argv[6] = /Users/piotr/.serverauth.1026
[   227.231] Xquartz starting:
[   227.231] X.Org X Server 1.18.4
[   227.231] Build Date: 20180831
[   227.238] x: 0, y: 0, w: 2560, h: 1418
[   227.303] (II) GLX: Initialized Core OpenGL GL provider for screen 0
[   229.063] X11.app: DarwinProcessFDAdditionQueue_thread: Sleeping to allow 
xinitrc to catchup.
[   229.087] (EE) Error loading keymap /tmp/server-0.xkm
[   229.087] (EE) XKB: Failed to load keymap. Loading default keymap instead.
[   229.872] noPseudoramiXExtension=0, pseudoramiXNumScreens=1
[ 25122.470] x: 0, y: 0, w: 2560, h: 1418
[ 25122.522] noPseudoramiXExtension=0, pseudoramiXNumScreens=1
[ 25122.522] noPseudoramiXExtension=0, pseudoramiXNumScreens=1
[ 26144.274] x: 0, y: 0, w: 2560, h: 1418
[ 26144.278] noPseudoramiXExtension=0, pseudoramiXNumScreens=1
[ 31657.125] x: 0, y: 0, w: 2560, h: 1418
[ 31657.128] noPseudoramiXExtension=0, pseudoramiXNumScreens=1
[ 63133.955] x: 0, y: 0, w: 2560, h: 1418
[ 63133.960] noPseudoramiXExtension=0, pseudoramiXNumScreens=1
[ 70910.981] x: 0, y: 0, w: 2560, h: 1418
[ 70910.985] noPseudoramiXExtension=0, pseudoramiXNumScreens=1
[ 83867.215] x: 0, y: 0, w: 2560, h: 1418
[ 83867.229] noPseudoramiXExtension=0, pseudoramiXNumScreens=1
[110886.434] x: 0, y: 0, w: 2560, h: 1418
[110886.438] noPseudoramiXExtension=0, pseudoramiXNumScreens=1
[153571.180] x: 0, y: 0, w: 2560, h: 1418
[153571.188] noPseudoramiXExtension=0, pseudoramiXNumScreens=1
[162162.765] x: 0, y: 0, w: 2560, h: 1418
[162162.769] noPseudoramiXExtension=0, pseudoramiXNumScreens=1
[197919.300] x: 0, y: 0, w: 2560, h: 1418
[197919.305] noPseudoramiXExtension=0, pseudoramiXNumScreens=1
[198637.899] x: 0, y: 0, w: 2560, h: 1418
[198637.907] noPseudoramiXExtension=0, pseudoramiXNumScreens=1
[242705.063] x: 0, y: 0, w: 2560, h: 1418
[242705.068] noPseudoramiXExtension=0, pseudoramiXNumScreens=1
[250616.473] x: 0, y: 0, w: 2560, h: 1418
[250616.478] noPseudoramiXExtension=0, pseudoramiXNumScreens=1
[257996.670] x: 0, y: 0, w: 2560, h: 1418
[257996.699] noPseudoramiXExtension=0, pseudoramiXNumScreens=1
[258021.249] x: 0, y: 0, w: 2560, h: 1418
[258021.255] noPseudoramiXExtension=0, pseudoramiXNumScreens=1
[284319.324] x: 0, y: 0, w: 2560, h: 1418
[284319.338] noPseudoramiXExtension=0, pseudoramiXNumScreens=1
[302091.351] x: 0, y: 0, w: 2560, h: 1418
[302091.356] noPseudoramiXExtension=0, pseudoramiXNumScreens=1
[302104.560] x: 0, y: 0, w: 2560, h: 1418
[302104.565] noPseudoramiXExtension=0, pseudoramiXNumScreens=1
[309253.186] x: 0, y: 0, w: 2560, h: 1418
[309253.194] noPseudoramiXExtension=0, pseudoramiXNumScreens=1
[310341.088] x: 0, y: 0, w: 2560, h: 1418
[310341.093] noPseudoramiXExtension=0, pseudoramiXNumScreens=1
[326829.422] x: 0, y: 0, w: 2560, h: 1418
[326829.434] noPseudoramiXExtension=0, 

Re: Anyone running X11 apps on Mojave?

[Alejandro Imass]

I run DIA on Mojave and just run it from XTerm once XQuartz starts up.

On Fri, Jan 18, 2019 at 5:40 PM Ken Cunningham <
ken.cunningham.web...@gmail.com> wrote:

> Can you open the X11.app application by double-clicking on it in
> /Applications/MacPorts ?
>
> If so, under the X11 applications menu, choose the first option to open a
> terminal, and then open your application that way.
>
> Can you open it like this, from a terminal?
>
> open /Applications/MacPorts/X11.app
>
>
> It is not terribly unusual for the automatic launching of the X11.app (ie
> when you try to run an application that needs it from the command line) to
> get a bit confused.
>
> About every few months one of my machines gets confused about this --- no
> doubt my fault somehow -- but I mess around with this and that for an hour,
> often using google for advice, and it usually works itself out, whatever it
> is I do to mess it up. (That's not great advice, I know...)
>
>
> Ken
>
>
>
>
> On 2019-01-18, at 8:32 AM, Pierre Malard wrote:
>
> I have X11-server installed from MacPorts. An Aqua App is installed in
> /Applications/MacPorts/X11.app. When I want to launch it, nothing since my
> update to Mojave :-(
>
> The only way I found is to execute the binary directly from a Terminal
> like that:
> $ /Applications/MacPorts/X11.app/Contents.MacOS/X11.bin &
> It’s not really fun.
>
> Is anyone have a solution?
>
>
>

Re: Anyone running X11 apps on Mojave?

[Ken Cunningham]

Oh, I see. No launch at all, under any circumstances.

To get anywhere with that, we would need to see the whole crash report to find 
out what happened.

Best,

Ken


On 2019-01-18, at 2:49 PM, Pierre Malard wrote:

> Each time I try to open X11.app (or XQuartz.app) by double-clicking or via « 
> open -a », it doesn’t work, the application is not open. The only way I have 
> to launch X11 is via a terminal as I explain.
> 
> The log I have on console is:
> -[PersistentAppsSupport applicationReady:] | App: X11, ready, updating active 
> tracking timer
> -[ApplicationManager checkInAppContext:refCon:eventData:] |  checked in 
> app : X11
> -[PersistentAppsSupport applicationQuit:] | for app:X11, _appTrackingState = 2
> -[PersistentAppsSupport applicationQuit:] | App: X11, quit, updating active 
> tracking timer
> 

Re: Anyone running X11 apps on Mojave?

[Pierre Malard]

Ok, thanks for your answer,

My explanation was visibly not good.

Each time I try to open X11.app (or XQuartz.app) by double-clicking or via « 
open -a », it doesn’t work, the application is not open. The only way I have to 
launch X11 is via a terminal as I explain.

The log I have on console is:
-[PersistentAppsSupport applicationReady:] | App: X11, ready, updating active 
tracking timer
-[ApplicationManager checkInAppContext:refCon:eventData:] |  checked in app 
: X11
-[PersistentAppsSupport applicationQuit:] | for app:X11, _appTrackingState = 2
-[PersistentAppsSupport applicationQuit:] | App: X11, quit, updating active 
tracking timer

I don’t understand what does it mean



> Le 18 janv. 2019 à 23:40, Ken Cunningham  a 
> écrit :
> 
> Can you open the X11.app application by double-clicking on it in 
> /Applications/MacPorts ?
> 
> If so, under the X11 applications menu, choose the first option to open a 
> terminal, and then open your application that way.
> 
> Can you open it like this, from a terminal?
> 
> open /Applications/MacPorts/X11.app
> 
> 
> It is not terribly unusual for the automatic launching of the X11.app (ie 
> when you try to run an application that needs it from the command line) to 
> get a bit confused.
> 
> About every few months one of my machines gets confused about this --- no 
> doubt my fault somehow -- but I mess around with this and that for an hour, 
> often using google for advice, and it usually works itself out, whatever it 
> is I do to mess it up. (That's not great advice, I know...)
> 
> 
> Ken
> 
> 
> 
> 
> On 2019-01-18, at 8:32 AM, Pierre Malard wrote:
> 
>> I have X11-server installed from MacPorts. An Aqua App is installed in 
>> /Applications/MacPorts/X11.app. When I want to launch it, nothing since my 
>> update to Mojave :-(
>> 
>> The only way I found is to execute the binary directly from a Terminal like 
>> that:
>>  $ /Applications/MacPorts/X11.app/Contents.MacOS/X11.bin &
>> It’s not really fun.
>> 
>> Is anyone have a solution?
> 

--
Pierre Malard

   « La vérité ne triomphe jamais, mais ses ennemis finissent
toujours par mourir... »
   Max Placnk (1858-1947)
   |\  _,,,---,,_
   /,`.-'`'-.  ;-;;,_
  |,4-  ) )-,_. ,\ (  `'-'
 '---''(_/--'  `-'\_)   πr

perl -e '$_=q#: 3|\ 5_,3-3,2_: 3/,`.'"'"'`'"'"' 5-.  ;-;;,_:  |,A-  ) )-,_. ,\ 
(  `'"'"'-'"'"': '"'"'-3'"'"'2(_/--'"'"'  `-'"'"'\_): 
24πr::#;y#:#\n#;s#(\D)(\d+)#$1x$2#ge;print'
- --> Ce message n’engage que son auteur <--



signature.asc
Description: Message signed with OpenPGP

Re: Anyone running X11 apps on Mojave?

[Ken Cunningham]

Can you open the X11.app application by double-clicking on it in 
/Applications/MacPorts ? 

If so, under the X11 applications menu, choose the first option to open a 
terminal, and then open your application that way.

Can you open it like this, from a terminal?

open /Applications/MacPorts/X11.app


It is not terribly unusual for the automatic launching of the X11.app (ie when 
you try to run an application that needs it from the command line) to get a bit 
confused.

About every few months one of my machines gets confused about this --- no doubt 
my fault somehow -- but I mess around with this and that for an hour, often 
using google for advice, and it usually works itself out, whatever it is I do 
to mess it up. (That's not great advice, I know...)


Ken




On 2019-01-18, at 8:32 AM, Pierre Malard wrote:

> I have X11-server installed from MacPorts. An Aqua App is installed in 
> /Applications/MacPorts/X11.app. When I want to launch it, nothing since my 
> update to Mojave :-(
> 
> The only way I found is to execute the binary directly from a Terminal like 
> that:
>   $ /Applications/MacPorts/X11.app/Contents.MacOS/X11.bin &
> It’s not really fun.
> 
> Is anyone have a solution?

Re: Anyone running X11 apps on Mojave?

[Pierre Malard]

And what about the question?

I have X11-server installed from MacPorts. An Aqua App is installed in 
/Applications/MacPorts/X11.app. When I want to launch it, nothing since my 
update to Mojave :-(

The only way I found is to execute the binary directly from a Terminal like 
that:
$ /Applications/MacPorts/X11.app/Contents.MacOS/X11.bin &
It’s not really fun.

Is anyone have a solution?

> Le 13 déc. 2018 à 02:36, Ryan Schmidt  a écrit :
> 
> 
> 
> On Dec 12, 2018, at 03:02, Tabitha McNerney wrote:
> 
>> I just installed XQuartz 2.7.11 today on a fresh Mac running Mojave 10.14.2. 
>> I installed XQuartz from the XQuartz.pkg found in the disk image (dmg) file 
>> on the XQuartz support site: https://www.xquartz.org/
>> 
>> I didn't have any problems installing and then later running XQuartz. 
>> However, on Mojave, there was an interesting alert panel which appeared 
>> during the pkg installation process which I have not seen on previous 
>> versions of macOS when installing XQuartz, which alert panel with two 
>> buttons, one which stated "Don't Allow" and the other stated "OK", and text 
>> which stated the following:
>> 
>> "Installer.app" wants access to control "System Events.app". Allowing 
>> control will provide access to documents and data in "System Events.app", 
>> and to perform actions within that app.
>> 
>> I didn't know what to do so I waited. There must have been a timeout because 
>> the panel disappeared on its own without me making a selection. The package 
>> installer process then finished on its own and stated XQuartz had been 
>> installed successfully. I was then able to run XQuartz without any issues. 
>> Interestingly, when I now run System Preferences and select Security & 
>> Privacy -> Privacy -> Automation there is an entry for "Installer.app" and 
>> underneath a check box next to "System Events.app". The check box is 
>> unchecked. I gather this all has something to do with changes to Mojave's 
>> security and privacy settings. Has anyone else seen this with or without 
>> XQuartz involved? If so, any ideas of what this means?
> 
> The XQuartz.pkg installer's postinstall script uses System Events to display 
> a dialog:
> 
> 
>/usr/bin/osascript activate
>display dialog "You will need to log out and log back in to make 
> XQuartz your default X11 server." buttons {"OK"}
>end tell
> 
> 
> If you don't allow the installer to control System Events, then it cannot 
> display that dialog for you.
> 
> I guess previous versions of macOS didn't restrict scripting access in this 
> way and just always allowed it. Probably a good thing for security that the 
> OS now warns you about this, but the installer was built 2 years ago, so the 
> developer couldn't have anticipated that macOS would be changed in this way.
> 
> This has nothing to do with MacPorts. You could report the issue to the 
> developer of XQuartz:
> 
> https://bugs.freedesktop.org/enter_bug.cgi
> 
> 

--
Pierre Malard

   «Mittler zwischen hirn und händen muss das hirz sein !»
   «La médiation entre le cerveau et les mains doit être le cœur !»
 Fritz Lang - "Métropolis" - 
1929
   |\  _,,,---,,_
   /,`.-'`'-.  ;-;;,_
  |,4-  ) )-,_. ,\ (  `'-'
 '---''(_/--'  `-'\_)   πr

perl -e '$_=q#: 3|\ 5_,3-3,2_: 3/,`.'"'"'`'"'"' 5-.  ;-;;,_:  |,A-  ) )-,_. ,\ 
(  `'"'"'-'"'"': '"'"'-3'"'"'2(_/--'"'"'  `-'"'"'\_): 
24πr::#;y#:#\n#;s#(\D)(\d+)#$1x$2#ge;print'
- --> Ce message n’engage que son auteur <--



signature.asc
Description: Message signed with OpenPGP

Re: Anyone running X11 apps on Mojave?

[Ryan Schmidt]

On Dec 12, 2018, at 03:02, Tabitha McNerney wrote:

> I just installed XQuartz 2.7.11 today on a fresh Mac running Mojave 10.14.2. 
> I installed XQuartz from the XQuartz.pkg found in the disk image (dmg) file 
> on the XQuartz support site: https://www.xquartz.org/
> 
> I didn't have any problems installing and then later running XQuartz. 
> However, on Mojave, there was an interesting alert panel which appeared 
> during the pkg installation process which I have not seen on previous 
> versions of macOS when installing XQuartz, which alert panel with two 
> buttons, one which stated "Don't Allow" and the other stated "OK", and text 
> which stated the following:
> 
> "Installer.app" wants access to control "System Events.app". Allowing control 
> will provide access to documents and data in "System Events.app", and to 
> perform actions within that app. 
> 
> I didn't know what to do so I waited. There must have been a timeout because 
> the panel disappeared on its own without me making a selection. The package 
> installer process then finished on its own and stated XQuartz had been 
> installed successfully. I was then able to run XQuartz without any issues. 
> Interestingly, when I now run System Preferences and select Security & 
> Privacy -> Privacy -> Automation there is an entry for "Installer.app" and 
> underneath a check box next to "System Events.app". The check box is 
> unchecked. I gather this all has something to do with changes to Mojave's 
> security and privacy settings. Has anyone else seen this with or without 
> XQuartz involved? If so, any ideas of what this means? 

The XQuartz.pkg installer's postinstall script uses System Events to display a 
dialog:


/usr/bin/osascript 

Re: Anyone running X11 apps on Mojave?

[Tabitha McNerney]

Hi,

I just installed XQuartz 2.7.11 today on a fresh Mac running Mojave
10.14.2. I installed XQuartz from the XQuartz.pkg found in the disk image
(dmg) file on the XQuartz support site: https://www.xquartz.org/

I didn't have any problems installing and then later running XQuartz.
However, on Mojave, there was an interesting alert panel which appeared
during the pkg installation process which I have not seen on previous
versions of macOS when installing XQuartz, which alert panel with two
buttons, one which stated "Don't Allow" and the other stated "OK", and text
which stated the following:

"Installer.app" wants access to control "System Events.app". Allowing
control will provide access to documents and data in "System Events.app",
and to perform actions within that app.

I didn't know what to do so I waited. There must have been a timeout
because the panel disappeared on its own without me making a selection. The
package installer process then finished on its own and stated XQuartz had
been installed successfully. I was then able to run XQuartz without any
issues. Interestingly, when I now run System Preferences and select
Security & Privacy -> Privacy -> Automation there is an entry for
"Installer.app" and underneath a check box next to "System Events.app". The
check box is unchecked. I gather this all has something to do with changes
to Mojave's security and privacy settings. Has anyone else seen this with
or without XQuartz involved? If so, any ideas of what this means?

Thanks,
-T.M.


On Fri, Nov 23, 2018 at 8:37 PM Ken Cunningham <
ken.cunningham.web...@gmail.com> wrote:

>
>
> On Nov 23, 2018, at 9:52 PM, Randolph M. Fritz  wrote:
>
> Does Xquartz still work? or MacPorts X11? Or…?
>
>
> yep, just fine.
>
> XQuartz 2.7.11 works from the XQuartz website, which is what I’m using
> right now, and the MacPorts versions are there as well:
>
>
> http://packages.macports.org/xorg-server-devel/xorg-server-devel-1.20.1_0.darwin_18.x86_64.tbz2
>
>
> http://packages.macports.org/xorg-server/xorg-server-1.18.4_3.darwin_18.x86_64.tbz2
>
>
> Ken
>

Re: Anyone running X11 apps on Mojave?

[Chris Jones]

> On 3 Dec 2018, at 9:59 am, Russell Jones  
> wrote:
> 
> 
>> On 01/12/2018 15:05, Christopher Jones wrote:
>> 
>>> On 26 Nov 2018, at 9:36 am, Dr M J Carter  
>>> wrote:
>>> 
>>> On Sat, Nov 24, 2018 at 11:58:16AM +, Christopher Jones wrote:
>>> 
 Note that the version of Xquartz from [2]www.xquartz.com is in fact
 just a packaging of the MacPorts version ! In fact, the maintainer
 of the Xquartz releases has stated that they may well no longer make
 releases there, and only maintain the MacPorts provided version (via
 the xorg-server port) going forward.
>>> That's going to prove interesting for those of us using MacTeX: its
>>> copy of gs-X11 seems to request and require libraries in /opt/X11 at
>>> runtime, not just at setup.  (In our setups, /usr/local/bin comes
>>> before /opt/local/bin, for reasons I can be tedious about on request,
>>> so MacTeX's gs preempts MacPorts's.)
>> well, the easy solution is to use macPorts provided TexLive ports.. These 
>> are built against MacPorts X11 dependencies….
>> 
>> 
> Except where they're in TeXLive and not in MacPorts, or not on the MacPorts 
> build server and take a while to build.

If macports is indeed missing something, Github PRs are always welcome to add 
it. 

The build time not relevant to the point I was making, which is simply macports 
provides a texlive installation, that works against the MP x11 server, that I 
am sure provides everything the majority of users need. If you want this taking 
a little time to build it should not be a concern.

> 
> Russell
> 

Re: Anyone running X11 apps on Mojave?

[Russell Jones]

On 01/12/2018 15:05, Christopher Jones wrote:



On 26 Nov 2018, at 9:36 am, Dr M J Carter  
wrote:

On Sat, Nov 24, 2018 at 11:58:16AM +, Christopher Jones wrote:


Note that the version of Xquartz from [2]www.xquartz.com is in fact
just a packaging of the MacPorts version ! In fact, the maintainer
of the Xquartz releases has stated that they may well no longer make
releases there, and only maintain the MacPorts provided version (via
the xorg-server port) going forward.

That's going to prove interesting for those of us using MacTeX: its
copy of gs-X11 seems to request and require libraries in /opt/X11 at
runtime, not just at setup.  (In our setups, /usr/local/bin comes
before /opt/local/bin, for reasons I can be tedious about on request,
so MacTeX's gs preempts MacPorts's.)

well, the easy solution is to use macPorts provided TexLive ports.. These are 
built against MacPorts X11 dependencies….


Except where they're in TeXLive and not in MacPorts, or not on the 
MacPorts build server and take a while to build.


Russell

Re: Anyone running X11 apps on Mojave?

[Christopher Jones]

> On 26 Nov 2018, at 9:36 am, Dr M J Carter  
> wrote:
> 
> On Sat, Nov 24, 2018 at 11:58:16AM +, Christopher Jones wrote:
> 
>> Note that the version of Xquartz from [2]www.xquartz.com is in fact
>> just a packaging of the MacPorts version ! In fact, the maintainer
>> of the Xquartz releases has stated that they may well no longer make
>> releases there, and only maintain the MacPorts provided version (via
>> the xorg-server port) going forward.
> 
> That's going to prove interesting for those of us using MacTeX: its
> copy of gs-X11 seems to request and require libraries in /opt/X11 at
> runtime, not just at setup.  (In our setups, /usr/local/bin comes
> before /opt/local/bin, for reasons I can be tedious about on request,
> so MacTeX's gs preempts MacPorts's.)

well, the easy solution is to use macPorts provided TexLive ports.. These are 
built against MacPorts X11 dependencies….


> 
> -- 
> Dr Martin J Carter
> Computer System Administrator
> Astrophysics, University of Oxford



smime.p7s
Description: S/MIME cryptographic signature

Re: Anyone running X11 apps on Mojave?

[Mojca Miklavec]

On Mon, 26 Nov 2018 at 10:36, Dr M J Carter wrote:
> On Sat, Nov 24, 2018 at 11:58:16AM +, Christopher Jones wrote:
>
> > Note that the version of Xquartz from [2]www.xquartz.com is in fact
> > just a packaging of the MacPorts version ! In fact, the maintainer
> > of the Xquartz releases has stated that they may well no longer make
> > releases there, and only maintain the MacPorts provided version (via
> > the xorg-server port) going forward.
>
> That's going to prove interesting for those of us using MacTeX: its
> copy of gs-X11 seems to request and require libraries in /opt/X11 at
> runtime, not just at setup.

There's no easy solution to this.

The only workaround would be using @rpath trickery to allow using a
dylib from a different path (but even then you could only perhaps
check /opt/local/lib, not any other random prefix that MacPorts might
be installed under). Or load the library at runtime. But if you do
require X11, you need to get it from somewhere, and defaulting to the
version from MacPorts for ghoscript in MacTeX would be utterly
strange. MacPorts ships with its own version of ghostscript (which
doesn't need /opt/X11), and there's no need to install ghostscript
with MacTeX (I never do) if you have MacPorts installed already.

Additionally, when I built the binaries for legacy macs (for any
system that's no longer supported by Apple; shipped with TeX Live by
default, but not with MacTeX which no longer works there), I tried to
make sure to not support X11 in any way, so you don't get any X11
bindings with metafont for example. Precisely because I hate to have
failing binaries just because the user did not install /opt/X11.

> (In our setups, /usr/local/bin comes
> before /opt/local/bin, for reasons I can be tedious about on request,
> so MacTeX's gs preempts MacPorts's.)

Mojca

Re: Anyone running X11 apps on Mojave?

[Dr M J Carter]

On Sat, Nov 24, 2018 at 11:58:16AM +, Christopher Jones wrote:

> Note that the version of Xquartz from [2]www.xquartz.com is in fact
> just a packaging of the MacPorts version ! In fact, the maintainer
> of the Xquartz releases has stated that they may well no longer make
> releases there, and only maintain the MacPorts provided version (via
> the xorg-server port) going forward.

That's going to prove interesting for those of us using MacTeX: its
copy of gs-X11 seems to request and require libraries in /opt/X11 at
runtime, not just at setup.  (In our setups, /usr/local/bin comes
before /opt/local/bin, for reasons I can be tedious about on request,
so MacTeX's gs preempts MacPorts's.)

-- 
Dr Martin J Carter
Computer System Administrator
Astrophysics, University of Oxford

Re: Anyone running X11 apps on Mojave?

[Ryan Schmidt]

On Nov 25, 2018, at 02:58, pagani laurent wrote:

> nice summary of X11/XQuartz history. I miss something about Terminal.app 
> which (I suppose) is still supported by Apple even in Mojave (but I stop at 
> Sierra as long as my present bookpro lives, so I don’t know). Isn’t it 
> another variant of X11 (except that there are some differences but I am not 
> sure to know all of them) ?

Terminal.app is a macOS application included by Apple as part of every version 
of macOS. Each tab in each terminal window runs a separate copy of a shell, 
such as bash. You use such a shell to run commands, such as the MacPorts port 
command.

There is an X11 program called xterm which serves a similar function, but 
running under X11 instead of running directly under macOS. In some X11 
installations, and depending on how you've set up your X11 configuration files, 
an xterm may launch automatically when you start X11, which might be what's 
giving you the incorrect association between Terminal and X11.

Re: Anyone running X11 apps on Mojave?

[pagani laurent via macports-users]

Hi Ryan,

nice summary of X11/XQuartz history. I miss something about Terminal.app which 
(I suppose) is still supported by Apple even in Mojave (but I stop at Sierra as 
long as my present bookpro lives, so I don’t know). Isn’t it another variant of 
X11 (except that there are some differences but I am not sure to know all of 
them) ?
Thanks.
L.
> Le 25 nov. 2018 à 09:49, Ryan Schmidt  a écrit :
> 
> 
> 
> On Nov 23, 2018, at 23:59, Fred Weinhaus wrote:
> 
>> I use Xquartz on my Mac OSX Sierra just fine. But I got it from 
>> https://www.xquartz.org. I do not think Apple supports X11 any longer, only 
>> Quartz.
> 
> Let's make sure we're not confusing terms. Your last sentence makes it sound 
> like X11 and Quartz are somehow related or equivalent things, but they have 
> nothing to do with one another. There have been some unfortunate naming 
> choices, however, which can lead to confusion.
> 
> "X11" is the X window system, a framework for creating GUI applications on 
> UNIX-like operating systems. Apple used to bundle a copy of X11 with macOS, 
> but hasn't done so for many years now. The extent to which Apple supports X11 
> on those systems on which they bundled it probably amounts to verifying that 
> it launches, and maybe helping you reinstall it if you removed it. The extent 
> to which Apple supports X11 on systems it was not bundled with would be the 
> same as their support of any other non-bundled third-party application, which 
> is to say not at all. Whether or not Apple supports X11 or any other 
> third-party application has no bearing on whether or not it will work.
> 
> "Quartz" is a macOS API for drawing two-dimensional graphics. It's also known 
> as Core Graphics. Most any macOS app that draws anything on the screen will 
> use Quartz / Core Graphics at some point.
> 
> "XQuartz" is a standalone build of X11 for macOS by Jeremy Huddleston 
> Sequoia, an evolution of the X11 Apple used to bundle. (Jeremy is an Apple 
> employee.) It has nothing to do with Quartz, except to the extent that it 
> uses the Quartz graphics routines. It might have been less confusing if it 
> had been called "X11 for macOS".
> 
> You can get the same software as in the XQuartz distribution by installing 
> the MacPorts xorg-server port (or the xorg-server-devel port, if you'd like a 
> newer development version rather than the latest stable version). In this 
> case the application will be called X11.app instead of XQuartz.app but it is 
> the same software. The MacPorts xorg ports are also maintained by Jeremy.
> 
> Many MacPorts ports that use X11 (or more precisely, ports that use GTK, 
> which usually uses X11) can be changed (by selecting the +quartz variant) so 
> that they use Quartz graphics directly, bypassing the X11 routines. This lets 
> those ports provide a mode macOS-native GUI experience and eliminates the 
> need to launch the separate X window environment.
> 

"S'il n'y a pas de solution, c'est qu'il n'y a pas de problème" (devise Shadok)

Re: Anyone running X11 apps on Mojave?

[Randolph M. Fritz]

Thanks. That is both helpful and discouraging.
-- 
Randolph M. Fritz || +1 206 659-8617 || rmfri...@gmail.com


On Sat, Nov 24, 2018 at 3:58 AM Christopher Jones 
wrote:

>
> On Nov 23, 2018, at 10:13 PM, Randolph M. Fritz 
> wrote:
>
> No, they don't. It's been open-sourced. Up to High Sierra, at least, it
> works. There hasn't been a formal release since two years ago October, so
> I'm wondering about Mojave.
> --
>
>
>
> Apple have not supported (i.e. shipped with the OS) X11 or Xquartz for
> some time now.
>
> Note that the version of Xquartz from www.xquartz.com is in fact just a
> packaging of the MacPorts version ! In fact, the maintainer of the Xquartz
> releases has stated that they may well no longer make releases there, and
> only maintain the MacPorts provided version (via the xorg-server port)
> going forward.
>
> I have exclusively used the MacPorts port for a number of years now, and
> it works flawlessly, on all OSes including 10.14. I recommend switching to
> it, if you currently are running the Xquartz installer version.
>
> Chris
>
> Randolph M. Fritz || +1 206 659-8617 || rmfri...@gmail.com
>
>
> On Fri, Nov 23, 2018 at 9:59 PM Fred Weinhaus  wrote:
>
>> I use Xquartz on my Mac OSX Sierra just fine. But I got it from
>> https://www.xquartz.org. I do not think Apple supports X11 any longer,
>> only Quartz.
>>
>>
>>
>>
>>
>> On Nov 23, 2018, at 9:52 PM, Randolph M. Fritz 
>> wrote:
>>
>> Does Xquartz still work? or MacPorts X11? Or…?
>> --
>> Randolph M. Fritz || +1 206 659-8617 || rmfri...@gmail.com
>>
>>
>>
>
>

Re: Anyone running X11 apps on Mojave?

[Christopher Jones]

> On 24 Nov 2018, at 4:22 pm, Richard L. Hamilton  wrote:
> 
> One might suppose there are still people for which the standalone packaging 
> of Xquartz might be preferable - people that for whatever reason, don't want 
> to deal with the extra steps involved in installing MacPorts (including 
> installing Xcode plus command line tools), let alone updating it, and don't 
> think they'd want any of the other packages it offers.

I am simply stating what the maintainer himself has stated on the Xquartz 
mailing lists. 

I don’t disagree, but also I made the comment on this list on the assumption 
everything here does have MP installed. In that case I would suggest using the 
port is the better option.

The maintainer has also stated if someone wanted to do the work to simplify the 
task of creating a standalone installer from the MP installation, he would 
welcome it, as he has very limited time to devote to maintaining X11 on macOS 
(which is why he might only focus on MP going forward).

Chris

smime.p7s
Description: S/MIME cryptographic signature

Re: Anyone running X11 apps on Mojave?

[Richard L. Hamilton]

One might suppose there are still people for which the standalone packaging of 
Xquartz might be preferable - people that for whatever reason, don't want to 
deal with the extra steps involved in installing MacPorts (including installing 
Xcode plus command line tools), let alone updating it, and don't think they'd 
want any of the other packages it offers.

> On Nov 24, 2018, at 06:58, Christopher Jones  wrote:
> 
>> 
>>> On Nov 23, 2018, at 10:13 PM, Randolph M. Fritz >> > wrote:
>>> 
>>> No, they don't. It's been open-sourced. Up to High Sierra, at least, it 
>>> works. There hasn't been a formal release since two years ago October, so 
>>> I'm wondering about Mojave.
>>> -- 
> 
> 
> Apple have not supported (i.e. shipped with the OS) X11 or Xquartz for some 
> time now.
> 
> Note that the version of Xquartz from www.xquartz.com 
>  is in fact just a packaging of the MacPorts version 
> ! In fact, the maintainer of the Xquartz releases has stated that they may 
> well no longer make releases there, and only maintain the MacPorts provided 
> version (via the xorg-server port) going forward.
> 
> I have exclusively used the MacPorts port for a number of years now, and it 
> works flawlessly, on all OSes including 10.14. I recommend switching to it, 
> if you currently are running the Xquartz installer version.
> 
> Chris
> 
>>> Randolph M. Fritz || +1 206 659-8617 || rmfri...@gmail.com 
>>> 
>>> 
>>> On Fri, Nov 23, 2018 at 9:59 PM Fred Weinhaus >> > wrote:
>>> I use Xquartz on my Mac OSX Sierra just fine. But I got it from 
>>> https://www.xquartz.org . I do not think Apple 
>>> supports X11 any longer, only Quartz.
>>> 
>>> 
>>> 
>>> 
>>> 
 On Nov 23, 2018, at 9:52 PM, Randolph M. Fritz >>> > wrote:
 
 Does Xquartz still work? or MacPorts X11? Or…?
 -- 
 Randolph M. Fritz || +1 206 659-8617 || rmfri...@gmail.com 
 
>> 
> 

Re: Anyone running X11 apps on Mojave?

[Christopher Jones]

> 
>> On Nov 23, 2018, at 10:13 PM, Randolph M. Fritz > > wrote:
>> 
>> No, they don't. It's been open-sourced. Up to High Sierra, at least, it 
>> works. There hasn't been a formal release since two years ago October, so 
>> I'm wondering about Mojave.
>> -- 


Apple have not supported (i.e. shipped with the OS) X11 or Xquartz for some 
time now.

Note that the version of Xquartz from www.xquartz.com  
is in fact just a packaging of the MacPorts version ! In fact, the maintainer 
of the Xquartz releases has stated that they may well no longer make releases 
there, and only maintain the MacPorts provided version (via the xorg-server 
port) going forward.

I have exclusively used the MacPorts port for a number of years now, and it 
works flawlessly, on all OSes including 10.14. I recommend switching to it, if 
you currently are running the Xquartz installer version.

Chris

>> Randolph M. Fritz || +1 206 659-8617 || rmfri...@gmail.com 
>> 
>> 
>> On Fri, Nov 23, 2018 at 9:59 PM Fred Weinhaus > > wrote:
>> I use Xquartz on my Mac OSX Sierra just fine. But I got it from 
>> https://www.xquartz.org . I do not think Apple 
>> supports X11 any longer, only Quartz.
>> 
>> 
>> 
>> 
>> 
>>> On Nov 23, 2018, at 9:52 PM, Randolph M. Fritz >> > wrote:
>>> 
>>> Does Xquartz still work? or MacPorts X11? Or…?
>>> -- 
>>> Randolph M. Fritz || +1 206 659-8617 || rmfri...@gmail.com 
>>> 
> 



smime.p7s
Description: S/MIME cryptographic signature

Re: Anyone running X11 apps on Mojave?

[Ken Cunningham]

> On Nov 23, 2018, at 9:52 PM, Randolph M. Fritz  wrote:
> 
> Does Xquartz still work? or MacPorts X11? Or…?

yep, just fine.

XQuartz 2.7.11 works from the XQuartz website, which is what I’m using right 
now, and the MacPorts versions are there as well:

http://packages.macports.org/xorg-server-devel/xorg-server-devel-1.20.1_0.darwin_18.x86_64.tbz2
 


http://packages.macports.org/xorg-server/xorg-server-1.18.4_3.darwin_18.x86_64.tbz2


Ken

Re: Anyone running X11 apps on Mojave?

[Fred Weinhaus]

Sorry, what do you mean by "No, they don't"?  Are you saying that Apple no 
longer supports XQuartz or no longer supports X11 for perhaps Mojave?



> On Nov 23, 2018, at 10:13 PM, Randolph M. Fritz  wrote:
> 
> No, they don't. It's been open-sourced. Up to High Sierra, at least, it 
> works. There hasn't been a formal release since two years ago October, so I'm 
> wondering about Mojave.
> -- 
> Randolph M. Fritz || +1 206 659-8617 || rmfri...@gmail.com 
> 
> 
> On Fri, Nov 23, 2018 at 9:59 PM Fred Weinhaus  > wrote:
> I use Xquartz on my Mac OSX Sierra just fine. But I got it from 
> https://www.xquartz.org . I do not think Apple 
> supports X11 any longer, only Quartz.
> 
> 
> 
> 
> 
>> On Nov 23, 2018, at 9:52 PM, Randolph M. Fritz > > wrote:
>> 
>> Does Xquartz still work? or MacPorts X11? Or…?
>> -- 
>> Randolph M. Fritz || +1 206 659-8617 || rmfri...@gmail.com 
>> 

Re: Anyone running X11 apps on Mojave?

[Randolph M. Fritz]

No, they don't. It's been open-sourced. Up to High Sierra (10.13), at
least, it works. There hasn't been a formal release since two years ago
October, so I'm wondering about Mojave.

(Fred, sorry for the dup. I forgot to hit "reply all.")
-- 
Randolph M. Fritz || +1 206 659-8617 || rmfri...@gmail.com


On Fri, Nov 23, 2018 at 9:59 PM Fred Weinhaus  wrote:

> I use Xquartz on my Mac OSX Sierra just fine. But I got it from
> https://www.xquartz.org. I do not think Apple supports X11 any longer,
> only Quartz.
>
>
>
>
>
> On Nov 23, 2018, at 9:52 PM, Randolph M. Fritz  wrote:
>
> Does Xquartz still work? or MacPorts X11? Or…?
> --
> Randolph M. Fritz || +1 206 659-8617 || rmfri...@gmail.com
>
>
>

Re: Anyone running X11 apps on Mojave?

[Fred Weinhaus]

I use Xquartz on my Mac OSX Sierra just fine. But I got it from 
https://www.xquartz.org . I do not think Apple 
supports X11 any longer, only Quartz.





> On Nov 23, 2018, at 9:52 PM, Randolph M. Fritz  wrote:
> 
> Does Xquartz still work? or MacPorts X11? Or…?
> -- 
> Randolph M. Fritz || +1 206 659-8617 || rmfri...@gmail.com 
>