XQuartz 2.8.3_beta4

[jeremyhu]

Hey folks,

I just released XQuartz 2.8.6_beta4. 2.8.6_beta3 was a targeted update to focus on CVEs and a few specific bugs. This release pulls in many updates from upstream repositories. Almost all projects have now been updated to the latest upstream versions. The major exception are the GLX related projects, which I don't have a good way to test at the moment.

This releaes also includes ASan to help catch memory issues (beta3 had it disabled) and is signed with a newer signing certificate that will allow it to remain valid through 2031.

[robohack]

I've had some problems installing this on an older 15.7.5 intel machine.

The installer seems to have finished, according to what I see in /var/db/install.log, but the "Installing Update" window just sits there looking like the front bumper of KITT, and the installer process sits idle.

I can copy the output from install.log here if that helps, but in the mean time I'm just going kill the installer process and see if the updated install works.

[robohack]

Killing the installer process seemed to "work". The resulting upgrade to 2.8.6_beta4 is usable (except for things which ASAN complains about, of course, like xrandr and xclock).

[jeremyhu]

I suspect it was just taking a while in post install building font caches. I noticed the cache generation taking a long time.

[robohack]

Hmmm.... I doubt that it was still rebuilding font caches -- I left it running for several hours, and I checked for other activity and could find none.

Something just got stuck and it didn't think it was done the upgrade even though it was.

[robohack]

Beta5 installed and relaunched without any problems and in reasonable time on my 15.7.5 macbook air, so this little side-issue is no longer an issue.

[pherepanov]

Are you planning to fix the incompatibility with Tahoe?

[jeremyhu]

If you're referring to the GLX issue, I think @kencu has a pull request up to address that, and I'll try to get that into a beta6 in the next few weeks.

[kencu]

a potentially better fix for the GLX issue has been proposed here:

#446 (comment)

and that has several advantages if it plays out