Re: Weird Looping Crash
Re: Weird Looping Crash
- Subject: Re: Weird Looping Crash
- From: Jeremy Huddleston <email@hidden>
- Date: Tue, 02 Feb 2010 14:51:11 -0800
Well, ~/.MacOSX/environment.plist was created by Panda3D. That file is stating what PATH should be. launchd is honoring that (incorrect) request in SnowLeopard (it ignored it in Leopard).
Panda3D should NOT be setting up that file. Furthermore, they should really NOT be using DYLD_LIBRARY_PATH.
It doesn't "mess up Xephyr". It messes up every single one of your LaunchAgents (including org.x.X11.startx, which launches when you run Xephyr to start X11.app).
On Feb 2, 2010, at 14:36, Nathan wrote:
> On Mon, Feb 1, 2010 at 4:27 PM, Jeremy Huddleston <email@hidden> wrote:
>>
>> On Feb 1, 2010, at 15:20, Nathan wrote:
>>
>>> On Mon, Feb 1, 2010 at 4:13 PM, Jeremy Huddleston <email@hidden> wrote:
>>>> Well... for some reason, /usr/bin doesn't seem to be in your $PATH when startx is launched from launchd.
>>>>
>>>> Try putting in an "echo PATH is: $PATH" lines in /usr/X11/bin/startx to see what it's set to (it'll be printed with the rest of those error messages in /var/log/system.log).
>>>
>>> Okay, I added {echo "PATH is: \"$PATH\""} to /usr/X11/bin/startx and
>>> in the logs it says:
>>>
>>> PATH is: "/Developer/Tools/Panda3D"
>>>
>>> What the heck??? I just installed Panda3D over the weekend (it
>>> appears to be completely broken on Snow Leopard, the demos that ship
>>> with it wouldn't even work). But I don't see that messed-up PATH in
>>> my own bash or sh sessions:
>>
>>> ...
>>
>>> ...and the Panda3D path is right in the middle of the string, so how
>>> is that ending up as the only path when startx launches from
>>> /bin/sh???
>>
>> /shrug ... I'd start by looking for matches in ~/Library and /Library:
>>
>> grep -R /Developer/Tools/Panda3D ~/Library /Library
>
>
> After a ton of searching, I finally found it!
>
> $ cat ~/.MacOSX/environment.plist
> <?xml version="1.0" encoding="UTF-8"?>
> <!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN"
> "http://www.apple.com/DTDs/PropertyList-1.0.dtd";>
> <plist version="1.0">
> <dict>
> <key>DYLD_LIBRARY_PATH</key>
> <string>/Developer/Panda3D/lib</string>
> <key>MAYA_PLUG_IN_PATH</key>
> <string>/Developer/Panda3D/plugins</string>
> <key>MAYA_SCRIPT_PATH</key>
> <string>/Developer/Panda3D/plugins</string>
> <key>PATH</key>
> <string>/Developer/Tools/Panda3D</string>
> <key>PYTHONPATH</key>
> <string>/Developer/Panda3D/lib</string>
> </dict>
> </plist>
>
> I had to rename/move/or delete that file AND REBOOT and then Xephyr
> worked like normal again. I've been using OS X for Unixy stuff since
> 10.3, and this is the first time that I've ever encountered ~/.MacOSX
> -- why would that mess up Xephyr, anyway?
>
> ~ Nathan
>
> ~ Nathan
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> X11-users mailing list (email@hidden)
>
> This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
This email sent to email@hidden