Updates Xquartz to 2.7.8 on Yosemite and everything worked well. After upgrading to El Capitán I observe several things: Clicking on the icon in my menubar doesn't open XTerm, 'open -a XQuartz' either '/Applications/Utilities/XQuartz.app/Contents/MacOS/X11' either Only '/Applications/Utilities/XQuartz.app/Contents/MacOS/X11.bin' ends up by launching the server and launching XTerm An excerpt of my /var/log/syslog (hope it's enough) that appears periodically Apr 29 12:45:53 paag org.macosforge.xquartz.X11.stub[15633]: Xquartz: bootstrap_look_up(): Unknown service name Apr 29 12:45:53 paag org.macosforge.xquartz.startx[15463]: waiting for X server to begin accepting connections Apr 29 12:45:53 paag org.macosforge.xquartz.startx[15463]: /opt/X11/bin/xinit: giving up Apr 29 12:45:53 paag org.macosforge.xquartz.startx[15463]: /opt/X11/bin/xinit: unable to connect to X server: Operation timed out Apr 29 12:45:53 paag org.macosforge.xquartz.startx[15463]: /opt/X11/bin/xinit: server error Apr 29 12:45:53 paag org.macosforge.xquartz.startx[15463]: /opt/X11/bin/xinit: unable to connect to X server Apr 29 12:45:53 paag com.apple.xpc.launchd[1] (org.macosforge.xquartz.startx[15463]): FairPlay decryption failed on binary. Apr 29 12:45:54 paag org.macosforge.xquartz.startx[15700]: xauth: file /Volumes/Macintosh-HD/Users/paag/.serverauth.15701 does not exist Apr 29 12:45:54 paag org.macosforge.xquartz.X11.stub[15870]: Xquartz: Unable to locate waiting server: org.macosforge.xquartz.X11 Apr 29 12:45:54 paag org.macosforge.xquartz.X11.stub[15871]: Xquartz: Starting X server: /Applications/Utilities/XQuartz.app/Contents/MacOS/X11 --listenonly Apr 29 12:45:56 paag org.macosforge.xquartz.startx[15700]: Apr 29 12:45:58 paag org.macosforge.xquartz.startx[15700]: waiting for X server to begin accepting connections
It sounds like you have a bad ~/.profile or something. I suggest you start there.
If running X11.bin works but not X11, then that just means that your login environment is causing a problem. I can't really be more specific than that because that's all that the error indicates. I suggest you move aside ~/.profile or ~/.bash_profiles or /etc/profiles or other shell init scripts to figure out what the problem is.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.