I’ve been working with a user to figure out why his system has become unstable, and the root cause is your software package. You setup a ~/.MacOSX/environment.plist which essentially breaks all the user’s LaunchAgents:
$ cat ~/.MacOSX/environment.plist
<?xml version="1.0" encoding="UTF-8"?> DYLD_LIBRARY_PATH /Developer/Panda3D/lib MAYA_PLUG_IN_PATH /Developer/Panda3D/plugins MAYA_SCRIPT_PATH /Developer/Panda3D/plugins PATH /Developer/Tools/Panda3D PYTHONPATH /Developer/Panda3D/lib-
You are telling launchd to use /Developer/Tools/Panda3D as PATH. This means that no system directories are in PATH, and any other script started by at LaunchAgent will not have access to /usr/bin /bin, etc.
-
Ditto for PYTHONPATH.
-
Do NOT EVER EVER EVER EVER set DYLD_LIBRARY_PATH in a deployment scenario. If you find you need to, then you are doing something ELSE wrong, and setting DYLD_LIBRARY_PATH is NOT the solution.