[Xquartz-dev] XQuartz 2.7.10

Discussion:

[Xquartz-dev] XQuartz 2.7.10_rc2

Jeremy Huddleston Sequoia

2016-09-11 06:56:20 UTC

Hi all,

XQuartz 2.7.10_rc2 is available. It's essentially the same as 2.7.10_rc1 but should work fine on older OS versions.

If you got bit by that, my apologies. Please give this one a go.

Thanks,
Jeremy

SciFi

2016-09-11 08:59:43 UTC

Permalink

Hi,

Thank you for recompiling 2.7.10_rc1 for us old-folk as ~_rc2.

Now, I've found another problem
but was able to do a quick symlink fix,
let me know if this is correct.
My typed notes says this:

- -*- quick fix for 2.7.10_rc2 -*-

Oops, upon starting the XQuartz.app from 2.7.10_rc2,

Sep 11 02:45:00 SciFi com.apple.launchd.peruser.501[610] (org.macosforge.xquartz.startx[49123]): posix_spawn("/opt/X11/lib/X11/xinit/launchd_startx", ...): No such file or directory
Sep 11 02:45:00 SciFi com.apple.launchd.peruser.501[610] (org.macosforge.xquartz.startx[49123]): Exited with exit code: 1
Sep 11 02:45:00 SciFi com.apple.launchd.peruser.501[610] (org.macosforge.xquartz.startx): Throttling respawn: Will start in 10 seconds

Jeremy Huddleston Sequoia

2016-09-11 10:46:27 UTC

Permalink

Yeah, that should work as a workaround.

The real fix is to update the postinstall script to detect this situation and advise users to logout and log back in.

--Jeremy

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hi,
Thank you for recompiling 2.7.10_rc1 for us old-folk as ~_rc2.
Now, I've found another problem
but was able to do a quick symlink fix,
let me know if this is correct.
- -*- quick fix for 2.7.10_rc2 -*-
Oops, upon starting the XQuartz.app from 2.7.10_rc2,

I think the installer for 2.7.10_rc2 removed launchd_startx which used to be located as shown above.
Now, I found it under /opt/X11/libexec
so I quickly put a symlink for it, e.g.
# cd /opt/X11/lib/X11/xinit
# ln -s ../../../libexec/launchd_start?
(yes as root)
so this seems to work
as the system.log shows now.
;p
- -*- end quick fix for 2.7.10_rc2 -*-
And so
I am using ~_rc2 with the Pan newsreader
to enter this message thru the GMane system.
-----BEGIN PGP SIGNATURE-----
iQEcBAEBCAAGBQJX1RWuAAoJEKkeWNKet7+KKeoH/iO9ePGlWPp3EoyCNQY4OFcA
gQlFjSRs3KxufCwqaM1pFkkQZAlMsOEwtkHpU0V1scBSVjzb3fnjTocnruJ5iBcu
QpO5XemXDrdD4cxqM6SIwhUMLNajGD5xez0F5vNMoysW8Lyt6HdamRnrsT0T5pVb
izeshAMvXbkmKpFO/y15T714LgQBvjs8j5Vgp6ZBxVFi+EUb/O3qWcg6SYLKju3r
meQQqG0FbSXZd9veV02Rlw5dzwrjUTZQDP25pzVO1diX1v4IP5AOzrSsRhls8DKl
NMOT2VpAfiFo2ekZqDjjC2fs9t5iCrCQN3MVyHkYUv/YtOC1ZZn64UZHpx8tPF0=
=mp2a
-----END PGP SIGNATURE-----
_______________________________________________
Xquartz-dev mailing list
https://lists.macosforge.org/mailman/listinfo/xquartz-dev

SciFi

2016-09-17 07:11:39 UTC

Permalink

Hi,

Post by Jeremy Huddleston Sequoia
Yeah, that should work as a workaround.
The real fix is to update the postinstall script to detect this situation and advise users to logout and log back in.
--Jeremy

Jeremy Huddleston Sequoia

2016-09-17 09:02:47 UTC

Permalink

It is possible to unload and reload the LaunchAgent, but all existing processes spawned by launchd in your session will have the wrong value for the DISPLAY environment variable. That's why the (not currently shown) dialog will encourage the user to logout in this scenario.

--Jeremy

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hi,

ah yes,
I have this app,
http://www.soma-zone.com/LaunchControl/ .
It does show the changed value for
'org.macosforge.xquartz.startx'.
But me not having logged-out/in
then apparently I was using the 'old in-core value' for this.
Is there a mechanism to update this "on the fly" as it were?
Anyway,
yes please insert some kind of wordage somehow
to explain this change
and how to properly pick it up
etc..
btw
I still have not signed-out/in during these days
since I need the iMac to do several scheduled tasks
(usually via 'cron', some via EyeTV.app, etc.)
thru the 24-hour period.
fwiw
latest LaunchControl.app version still works for me,
since it's designed to run on SL
and this "iMac6,1" has a 64-bit CPU (Core2Duo)
(but its EFI/BIOS ROM is still 32-bit
which is why I must be able to afford another [newer] model
to do any 'upgrade' whatsoever,
`sigh`).
So I need to re-iterate,
if it's possible for such values
to be altered
"dynamically"
in such way
that a sign-out/in is _not_ required
?
Please consider doing this if possible.
(as of 'now', I _did_ sign-out/in to pick-up the change[s])
TY
-----BEGIN PGP SIGNATURE-----
iQEcBAEBCAAGBQJX3ORUAAoJEKkeWNKet7+KYjYH+wWyTk1ujIzdYq/SP/sDOyrN
8gJVoPv8djkh+3Wampa0AbU1pX0QzZgPEtDdGdu2kGVQPZLVTiym3mjSw4hoq3yN
72X/n1ChNWf8lvJ6o4xdI7T279CsUUSm2D4QzezJP0ftuWVJMPdAFRw5GqMFAq3e
msOncyBtg7svzHVjbDuVHg1h48EIvd/+GCKI67ZtIARVBAoETeGJEtlvFFGIkWg+
1AFVMOjQTHVO7E7EI9jP/7o9MuVYgOGfY5nnoaGN2qLvQ3FGVO81Yc0S/mfR9E5e
ZKDub7EcNVAByi6cBlBce4fjS7qz8yTspV/QidssUH2wJpZoT5kDu8KqsJVlVEI=
=zae/
-----END PGP SIGNATURE-----
_______________________________________________
Xquartz-dev mailing list
https://lists.macosforge.org/mailman/listinfo/xquartz-dev