This normally applies only to native OSX apps but may affect the X server in this case.ģ) If you recent updated to Yosemite but are using an older XQuartz installation you might install the latest XQuartz from their site at Since X is no longer distributed as part of the OSX base system it must be installed separately, and I remember other issues being fixed by reinstalling XQuartz after a Yosemite update. If so, use "sudo chown root:wheel /iraf/iraf/vendor/x11iraf/bin.macintel/xgterm" to change the ownership.Ģ) Some applications reporting similar problems were fixed by going to the 'Security & Privacy" panel of System Preferences to change the "Allow apps downloaded from:" option to be "Anywhere", starting the task at least one time. To see if running as root fixes the problem. I still can't reproduce the problem on my 10.10.3 system, but there are a few things you can check:ġ) The XTerm binary is owned by root and in the past has been required to be a setuid binary, try executing as usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 88.3.10) usr/lib/libncurses.5.4.dylib (compatibility version 5.4.0, current version 5.4.0) usr/X11R6/lib/libX11.6.dylib (compatibility version 6.2.0, current version 6.2.0) usr/X11R6/lib/libXext.6.dylib (compatibility version 6.4.0, current version 6.4.0) usr/X11R6/lib/libICE.6.dylib (compatibility version 6.3.0, current version 6.3.0) usr/X11R6/lib/libSM.6.dylib (compatibility version 6.0.0, current version 6.0.0) usr/X11R6/lib/libXt.6.dylib (compatibility version 6.0.0, current version 6.0.0) usr/X11R6/lib/libXmu.6.dylib (compatibility version 6.2.0, current version 6.2.0)
usr/X11R6/lib/libXpm.4.dylib (compatibility version 4.11.0, current version 4.11.0) 1 It formally replaced Apples internal X11 app. ~\$this->_split2($m) otool -L /usr/local/bin/xgterm XQuartz is an open-source version of the X.Org X server, a component of the X Window System (X11, or shortened to simply X, and sometimes informally X-Windows) that runs on macOS.
~\$this->_split2($m) ls -las /usr/local/bin/xgtermĨ lrwxr-xr-x 1 root staff 45B Jun 7 02:04 -\$this->_split2($m) /iraf/iraf/vendor/x11iraf/bin.macintel/xgterm I verified that it works well with xterm (as well as xterm can ). 1 It formally replaced Apple's internal X11 app. But I now run into exactly the same problem described above: xgterm crashing with splot, reporting Bus Error: 10. XQuartz is an open-source version of the X.Org X server, a component of the X Window System (X11, or shortened to simply X, and sometimes informally X-Windows) that runs on macOS.
#Xquartz for yosemite code#
Setuid (aka set-user-ID-on-execution and SUID) presents a serious security risk when used on executables owned by root, because if a vulnerability exists in the executable then an attacker might be able to execute code as root, giving them limitless control over the system.I only recently managed to install iraf on a new mac, with yosemite. In the above example, if user Bob launches someapp then it will run with the effective user id of 'wsee' even though it is Bob running the app. When an executable has its setuid bit set then it will be run as the file owner no matter which user launches it.
#Xquartz for yosemite update#
Since the XQuartz X11 package clobbers Apple's X11.app, their software update will clobber the XQuartz X11 package. Sure enough, when I checked the setuid bit was set (bolded in example below): wsee$ ls 3 wsee staff 96 someapp Gameboy dmg 01.OS X Software Updates have included some of the work done by the XQuartz project, but for various reasons, Apple cannot ship the latest and greatest version offered by the XQuartz site. 11:34:06.010 someapp The application with bundle ID XYZ is running setugid() which is not allowed. Following the answer (trying to launch the app's binary) gave me a more instructive message: wsee$ cd /Applications/someapp/Contents/MacOS I got the same error when trying to run an app on my system.