<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Sep 27, 2011, at 3:05 AM, Jeremy Huddleston wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div><br>On Sep 26, 2011, at 11:20 PM, Louis Zulli wrote:<br><br><blockquote type="cite"><br></blockquote><blockquote type="cite">On Sep 27, 2011, at 12:25 AM, Jeremy Huddleston wrote:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><blockquote type="cite">So that looks like you haven't done a:<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">launchctl unload -w /System/Library/LaunchAgents/org.x.startx.plist<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Do that, then reboot (logout should be fine, but meh) ... I'm still curious why you're seeing that rather than the MacOSForge one... any ideas?<br></blockquote></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">I just reinstalled the beta2. Here's what I see<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">-rw-rw-r-- 1 root admin 654 Sep 24 16:10 org.macosforge.xquartz.startx.plist<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Does a Lion security feature prevent launch due to ownership/permissions issue?<br></blockquote><br>No. Read up on launchd for more info. </div></blockquote><br></div><div>From the launchctl man page:</div><div><br></div><blockquote class="webkit-indent-blockquote" style="margin: 0 0 0 40px; border: none; padding: 0px;"><div>Load the specified configuration files or directories of configuration files. Jobs that are not on-demand will be started as soon as possible.</div><div><div>All specified jobs will be loaded before any of them are allowed to start. Note that per-user configuration files (LaunchAgents) must be owned by</div></div><div><div>the user loading them. All system-wide daemons (LaunchDaemons) must be owned by root. <b>Configuration files must not be group- or world-writable.</b></div></div><div><div>These restrictions are in place for security reasons, as allowing writability to a launchd configuration file allows one to specify which exe-</div></div><div><div>cutable will be launched.</div></div></blockquote><div><div><br></div><div>The scope of the bolded sentence is not clear to me, but ...</div></div></body></html>