Re: X11 no longer working
Ok, everything seems to be Ok in the target side! > Le 9 mai 2020 à 09:04, Christoph Kukulies a écrit : > > Here is the output. Nothing happens on the macOS side. I remembered that X11 > (Quartz) popped up automatically iin the dock and the xclock appeared on the > Mac desktop, last time it worked. > A last test is to launch X11 « by the hand » on terminal and look if the XQuartz is really launched: $ /Applications/Utilities/XQuartz.app/Contents/MacOS/X11 I remember I had some problems with XQuartz since Catalina upgrade. There has been no XQuartz update since 2016 and they indicate another solution to have X11 on Mac OS X: MacPorts (https://www.xquartz.org/releases/index.html). So I have switched to MacPorts install and I have no problems with Catalina. Other thing, take a look on this URL: https://askubuntu.com/questions/1029909/x11-forwarding-for-non-root-user-not-working > > > > The X11DisplayOffset seems to be 10, although the line in sshd_config is > commented out. 10 seems to be the default. But it used to work the day before > yesterday. Don’t know what happened unless I had done something to the PATH > or macports tree. > > What I did was remove the X11 icon from the dock, but that after it stopped > working. It is so that X11 Quartz normally launches automatically when a > client requests an X11 connection, right? > > Still clueless. Maybe I’m overlooking something very obvious? > — > Christoph > >> Am 08.05.2020 um 17:41 schrieb Pierre Malard : >> >> Hi, >> >> Some possibilities: >> 1) Try your « ssh -Y » in verbose mode like « ssh -v -Y » or >> « ssh -vv -Y » for more verbose and take a look at the displayed >> messages. >> 2) Is « xauth » package is on your target? >> 3) What about the « X11DisplayOffset » on your target? >> 4) What about these lines: >> Source% ssh -Y user@cible >> Target% echo $DISPLAY >> Target% xclock >> >> It’s not an SHELL problem. >> >> Good luck >> >>> Le 8 mai 2020 à 16:10, Christoph Kukulies a écrit : >>> >>> Today is a havoc day. I changed my login shell to bash. Also added this >>> BASH Silencing variable succesfully. >>> Was playing around for hours with my FreeBSD system in the network and in >>> the morning I ran some X clients. >>> Alway saw the X11 Quartz icon in the dock. >>> >>> Is it correct, the X server starts automatically if an X cient wants to >>> connect over the network, right. >>> Last thing I did was to remove the X11 icon from the dock. Now suddenly >>> when I ssh -Y to the FreeBSD system, start xclock there, >>> nothing happens. The xclock command line hangs on the client side. But no >>> message at all. DISPLAY is localhost:10.0. >>> >>> I did a reboot of the FreeBSD system already to no avail. What’s going on? >>> Will reboot my Mac and next thing I’ll do is revert to zsh to see whether >>> it has got to do with that. >>> >>> — >>> Christoph >>> >> >> -- >> Pierre Malard -- 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: X11 no longer working
Hi, Some possibilities: 1) Try your « ssh -Y » in verbose mode like « ssh -v -Y » or « ssh -vv -Y » for more verbose and take a look at the displayed messages. 2) Is « xauth » package is on your target? 3) What about the « X11DisplayOffset » on your target? 4) What about these lines: Source% ssh -Y user@cible Target% echo $DISPLAY Target% xclock It’s not an SHELL problem. Good luck > Le 8 mai 2020 à 16:10, Christoph Kukulies a écrit : > > Today is a havoc day. I changed my login shell to bash. Also added this BASH > Silencing variable succesfully. > Was playing around for hours with my FreeBSD system in the network and in the > morning I ran some X clients. > Alway saw the X11 Quartz icon in the dock. > > Is it correct, the X server starts automatically if an X cient wants to > connect over the network, right. > Last thing I did was to remove the X11 icon from the dock. Now suddenly when > I ssh -Y to the FreeBSD system, start xclock there, > nothing happens. The xclock command line hangs on the client side. But no > message at all. DISPLAY is localhost:10.0. > > I did a reboot of the FreeBSD system already to no avail. What’s going on? > Will reboot my Mac and next thing I’ll do is revert to zsh to see whether it > has got to do with that. > > — > Christoph > -- Pierre Malard « Je n'ai jamais séparé la République des idées de justice sociale, sans laquelle elle n'est qu'un mot » Jean Jaures - 1887 |\ _,,,---,,_ /,`.-'`'-. ;-;;,_ |,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: Catalina installation problems
Hi Tarik, > Le 26 nov. 2019 à 13:49, Tarik Cicic a écrit : > > Hi Pierre, > > normal rsync works fine “by hand” tested toward another server. it would have been better to run the rsync from that same server rather than another. The only proven is ... that works from the other server, nothing about this Mac. >I have no proxy configured, and my “/opt/local/etc/macports/macports.conf” > is unmodified. Ok > > Could it be that the file > rsync.macports.org/macports/release/tarballs/base.tar > <http://rsync.macports.org/macports/release/tarballs/base.tar> redirects to > (in Erlangen?) simply is not there? Do people normally use preinstalled > rsync on Mac, or some more recent package? Do you see if the file exist? or the directory « /opt/local/…/tarballs »? Personally I use the old MacOS rsync. There is no problem. > > Thanks, > > Tarik > >> On 26 Nov 2019, at 11:29, Pierre Malard > <mailto:p...@teledetection.fr>> wrote: >> >> Hi, >> >> Did you try the rsync command « by hand » on a terminal session? >> An other way: is it a proxy between your PC and MacPorts? Global or specific >> to MacPorts (file « /opt/local/etc/macports/macports.conf » and « proxy » >> key)? >> >>> Le 26 nov. 2019 à 11:20, Tarik Cicic >> <mailto:tarik.ci...@gmail.com>> a écrit : >>> >>> Hi, >>> >>> I have been using Macports for years, and for first time have problems >>> installing, after upgrade to MacOS 10.15 Catalina. >>> >>> Gray-MBP:~ tarik$ sudo port -d selfupdate >>> Password: >>> DEBUG: Copying /Users/tarik/Library/Preferences/com.apple.dt.Xcode.plist to >>> /opt/local/var/macports/home/Library/Preferences >>> DEBUG: MacPorts sources location: >>> /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs >>> <http://rsync.macports.org/macports/release/tarballs> >>> ---> Updating MacPorts base sources using rsync >>> DEBUG: system: /usr/bin/rsync -rtzvl --delete-after >>> rsync://rsync.macports.org/macports/release/tarballs/base.tar >>> >>> /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs >>> <http://rsync.macports.org/macports/release/tarballs> >>> rsync: failed to connect to rsync.macports.org >>> <http://rsync.macports.org/>: Operation timed out (60) >>> rsync error: error in socket IO (code 10) at >>> /BuildRoot/Library/Caches/com.apple.xbs/Sources/rsync/rsync-54/rsync/clientserver.c(106) >>> [receiver=2.6.9] >>> Command failed: /usr/bin/rsync -rtzvl --delete-after >>> rsync://rsync.macports.org/macports/release/tarballs/base.tar >>> >>> /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs >>> <http://rsync.macports.org/macports/release/tarballs> >>> Exit code: 10 >>> Gray-MBP:~ tarik$ >>> >>> The site is available: >>> >>> Gray-MBP:~ tarik$ ping rsync.macports.org <http://rsync.macports.org/> >>> PING ftp.rrze.uni-erlangen.de <http://ftp.rrze.uni-erlangen.de/> >>> (131.188.12.211): 56 data bytes >>> 64 bytes from 131.188.12.211: icmp_seq=0 ttl=52 time=38.689 ms >>> 64 bytes from 131.188.12.211: icmp_seq=1 ttl=52 time=32.265 ms >>> 64 bytes from 131.188.12.211: icmp_seq=2 ttl=52 time=38.667 ms >>> ^C >>> --- ftp.rrze.uni-erlangen.de <http://ftp.rrze.uni-erlangen.de/> ping >>> statistics --- >>> 3 packets transmitted, 3 packets received, 0.0% packet loss >>> round-trip min/avg/max/stddev = 32.265/36.540/38.689/3.023 ms >>> >>> Xcode Version 11.2.1 (11B500) and command line tools are installed. Port >>> version is 2.6.2. Any suggestion is welcome! >>> >>> Thanks, >>> >>> Tarik >> >> -- >> Pierre Malard >> >> « Les utopies ne sont souvent que des vérités prématurées » >> Alphonse de >> Lamartine >>|\ _,,,---,,_ >>/,`.-'`'-. ;-;;,_ >> |,4- ) )-,_. ,\ ( `'-' >> '---''(_/--' `-'\_) πr >> >> perl -e '$_=q#: 3|\ 5_,3-3,2_: 3/,`.'"'"'`'"'"' 5-. ;-;;,_: |,A- ) )-,_. >> ,\ ( `'"'"'-'"'"': '"'"'-3'"'"'2(_/--'"'"' `-'"'"'\
Re: Catalina installation problems
Hi, Did you try the rsync command « by hand » on a terminal session? An other way: is it a proxy between your PC and MacPorts? Global or specific to MacPorts (file « /opt/local/etc/macports/macports.conf » and « proxy » key)? > Le 26 nov. 2019 à 11:20, Tarik Cicic a écrit : > > Hi, > > I have been using Macports for years, and for first time have problems > installing, after upgrade to MacOS 10.15 Catalina. > > Gray-MBP:~ tarik$ sudo port -d selfupdate > Password: > DEBUG: Copying /Users/tarik/Library/Preferences/com.apple.dt.Xcode.plist to > /opt/local/var/macports/home/Library/Preferences > DEBUG: MacPorts sources location: > /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs > <http://rsync.macports.org/macports/release/tarballs> > ---> Updating MacPorts base sources using rsync > DEBUG: system: /usr/bin/rsync -rtzvl --delete-after > rsync://rsync.macports.org/macports/release/tarballs/base.tar > > /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs > <http://rsync.macports.org/macports/release/tarballs> > rsync: failed to connect to rsync.macports.org <http://rsync.macports.org/>: > Operation timed out (60) > rsync error: error in socket IO (code 10) at > /BuildRoot/Library/Caches/com.apple.xbs/Sources/rsync/rsync-54/rsync/clientserver.c(106) > [receiver=2.6.9] > Command failed: /usr/bin/rsync -rtzvl --delete-after > rsync://rsync.macports.org/macports/release/tarballs/base.tar > > /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs > <http://rsync.macports.org/macports/release/tarballs> > Exit code: 10 > Gray-MBP:~ tarik$ > > The site is available: > > Gray-MBP:~ tarik$ ping rsync.macports.org <http://rsync.macports.org/> > PING ftp.rrze.uni-erlangen.de <http://ftp.rrze.uni-erlangen.de/> > (131.188.12.211): 56 data bytes > 64 bytes from 131.188.12.211: icmp_seq=0 ttl=52 time=38.689 ms > 64 bytes from 131.188.12.211: icmp_seq=1 ttl=52 time=32.265 ms > 64 bytes from 131.188.12.211: icmp_seq=2 ttl=52 time=38.667 ms > ^C > --- ftp.rrze.uni-erlangen.de <http://ftp.rrze.uni-erlangen.de/> ping > statistics --- > 3 packets transmitted, 3 packets received, 0.0% packet loss > round-trip min/avg/max/stddev = 32.265/36.540/38.689/3.023 ms > > Xcode Version 11.2.1 (11B500) and command line tools are installed. Port > version is 2.6.2. Any suggestion is welcome! > > Thanks, > > Tarik -- Pierre Malard « Les utopies ne sont souvent que des vérités prématurées » Alphonse de Lamartine |\ _,,,---,,_ /,`.-'`'-. ;-;;,_ |,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: Catalina ante portas - wine, wine-bottler LTSpice
Stay in 10.14 actually. The update message of OSX is just an incitation not an obligation. And all 10.14 update are stil here, just under Catalina suggest. > Le 22 oct. 2019 à 17:30, Christoph Kukulies a écrit : > > My macOS wants to update (Mojave->Catalina 10.15). > > I’ve heard wine emulator based programs will cease working. > > Has anyone heard there will be an escape for this situation? > > Best regards, > > Christoph Kukulies > -- Pierre Malard « La liberté de la presse ne s'use que lorsqu'on ne s'en sert pas ! » Slogan du "Canard enchaîné" |\ _,,,---,,_ /,`.-'`'-. ;-;;,_ |,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? [Solved]
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&O=D
> livecheck.version [format %03d ${bash_patchlevel}]
> END PATCH ********
>
> The goal here
Re: Anyone running X11 apps on Mojave? [Solved]
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 jan
Re: Anyone running X11 apps on Mojave? [Solved]
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(): arg
Re: Anyone running X11 apps on Mojave?
eudoramiXExtension=0, pseudoramiXNumScreens=1 [330967.553] x: 0, y: 0, w: 2560, h: 1418 [330967.566] noPseudoramiXExtension=0, pseudoramiXNumScreens=1 [334605.847] x: 0, y: 0, w: 2560, h: 1418 [334613.763] noPseudoramiXExtension=0, pseudoramiXNumScreens=1 [340157.573] (II) Server terminated successfully (0). Closing log file. > Le 18 janv. 2019 à 23:57, Ken Cunningham a > écrit : > > 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 >> > -- 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?
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?
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 <--
signature.asc
Description: Message signed with OpenPGP
Re: echo and tty issue
A simple Shell question: just send standard output to this TTY like that: echo toto > /dev/ where is the serial device used. > Le 18 nov. 2018 à 18:49, Philip Yao a écrit : > > Hi, > > I'm experiencing an issue with echoing into a tty serial port on my mac. Does > there exist any issues relevant to this with MacPorts? > > Thanks -- Pierre Malard «[...]développer la science ? Noble ambition ; mais qu'est-ce que la science ? Une puissance et une joie ; et, si elle ne s'anime pas de l'esprit de justice, [...] de la vie des hommes, [...] elle est un privilège en plus.» Jean Jaures - "L'idéal de justice" - 1889 |\ _,,,---,,_ /,`.-'`'-. ;-;;,_ |,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
