Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

XQuartz crashes on Mac Studio after upgrading to Sonoma

I upgraded my Mac Studio from Monterey (12.5.1) to Sonoma (14.3.1). I had been running the X11 windows system (XQuartz 2.8.2) with no problems in Monterey, and for many years before on earlier Mac systems. But when I upgraded to Sonoma, XQuartz crashes the Mac horribly every time. Has anyone else seen this problem? I can't even downgrade my Studio back to Monterey, so I'm stuck...




[Re-Titled by Moderator]

Mac Studio, macOS 14.3

Posted on Feb 12, 2024 1:15 PM

Reply
6 replies
Sort By: 

Feb 12, 2024 1:23 PM in response to DrThip

Contact the XQuartz team and see if they can provide any insight for successfully moving forward, or for removing XQuartz. The last stable version (2.8.5) of XQuartz was released in Jan 2023, so never tested with Sonoma. Installing XQuartx 2.8.2 was asking for trouble based on its age (June 2022).

Reply

Feb 15, 2024 3:21 PM in response to VikingOSX

Thanks for your response. I wound up talking to a helpful AppleCare person, who suspected the problem lay within XQuartz, since none of my other apps were giving me problems. He suggested I try XQ with a new, "clean" login to test this idea, and he was right. The clean user could boot XQ with no problem.


This meant it was something in my personal XQ environment. I spent the next day looking at various pieces, and eventually zoomed in on the customisations in my ~/.xinitrc file. (This was something I had added to over the years, through several prior versions of XQ well before 2.8.2, and also several prior OSX incarnations going back to Tiger, at least.) Still, when I moved this file elsewhere and tried booting up XQ, it worked fine in my own login. I discovered that the system-default file (in /opt/X11/etc/X11/xinit/xinitrc) kicked in upon starting XQ, and I examined the differences between that and my .xinitrc file. There were very few; the only meaningful one was that the system default starts up the twm window manager (in /opt/X11/bin/twm) instead of the quartz-wm WM (in that same directory), which is what I had been using for years as above. My understanding was that twm was older and deprecated. Apparently not!


However, by this time I was anxious to get back up and running, so I didn't try any further experiments with WMs, and can't say whether the quartz-wm itself was the problem. Rather than try to reinvent the wheel, I left my .xinitrc file in its non-functional state, and arranged to invoke my X11 customisations in a more harmless way, ie, *after* XQ startup, as a simple c-shell command.


At any rate, I now have a functioning X11 system (with XQ 2.8.2) and everything that depends on it works fine again, in Sonoma. Some other points in response to your suggestions:


I did also try XQ 2.8.5 (the latest version), although as you say, no version of XQ has been "officially" released for Sonoma. But this failed as utterly as 2.8.2, so the XQ version wasn't the problem, as I explained above. I am also disinclined to muck around further with any upgrades: getting a working X11 environment back was critical for my work progress, so "removing XQuartz" would have been disastrous (sorry!).


Anyway, I do plan to contact the XQ team and relay the above saga. Thanks again for your comments and suggestions, I appreciate the effort!


PS: The fact that I had a working version of XQ with Monterey, with all customisations and any other warts present in their full glory, but that this very same setup caused the Mac OS to crash when running under Sonoma, does mean that some default action (either of the OS or of XQ) was no longer compatible with my existing setup. So, this problem was not *entirely* of my making!

Reply

Mar 21, 2024 10:14 PM in response to DrThip

Resolved. Sonoma : xquartz 2.8.5

I found that I had disabled the xquartz startup for my login.

Apple : System Settings / Login Items. : Turn on xquartz.


Also, since xquartz seems to install itself into Login Items for each MacOS user, make sure you're not logging into / on to your Mac simultaneously e.g, David & Tom, since these two login sessions could be interfering with the DISPLAY variable.


ssh -Y dave@servername

<or>

ssh -X dave@servername

echo $DISPLAY

xeyes


Reply

Mar 22, 2024 8:23 AM in response to graved70

graved70 wrote:

Resolved. Sonoma : xquartz 2.8.5
I found that I had disabled the xquartz startup for my login.
Apple : System Settings / Login Items. : Turn on xquartz.

Never use that new user interface. Apple unexpectedly sprang that capability on 3rd party developers. Even with a few months of advance notice in the beta, that isn't enough time to make architectural changes on this level. Even a couple of years later, most 3rd party developers still haven't adapted to it. Those who have adapted are doing so in various dark pattern methods - i.e. they are developing clever and sneaky way to get around it.


Apparently, even Apple itself is struggling to adapt with XQuartz.

Also, since xquartz seems to install itself into Login Items for each MacOS user, make sure you're not logging into / on to your Mac simultaneously e.g, David & Tom, since these two login sessions could be interfering with the DISPLAY variable.

You shouldn't have to worry about that. In theory at least, environments from different users should be unique.

Reply

XQuartz crashes on Mac Studio after upgrading to Sonoma

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.