Re: [Xquartz-dev] XQuartz 2.7.0_beta2

2011-09-26 Thread Louis Zulli
On Sep 27, 2011, at 12:25 AM, Jeremy Huddleston wrote: > So that looks like you haven't done a: > launchctl unload -w /System/Library/LaunchAgents/org.x.startx.plist > > Do that, then reboot (logout should be fine, but meh) ... I'm still curious > why you're seeing that rather than the MacOSFor

Re: [Xquartz-dev] XQuartz 2.7.0_beta2

2011-09-26 Thread Jeremy Huddleston
So that looks like you haven't done a: launchctl unload -w /System/Library/LaunchAgents/org.x.startx.plist 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? On Sep 26, 2011, at 7:59 PM, Louis Zulli wrot

Re: [Xquartz-dev] XQuartz 2.7.0_beta2

2011-09-26 Thread Louis Zulli
ProcyonLeo: ~] echo $DISPLAY /tmp/launch-SBODpp/org.x:0 ProcyonLeo: ~] launchctl list org.x.startx { "Label" = "org.x.startx"; "LimitLoadToSessionType" = "Aqua"; "OnDemand" = true; "LastExitStatus" = 0; "TimeOut" = 30; "ProgramArguments" = (

Re: [Xquartz-dev] XQuartz 2.7.0_beta2

2011-09-26 Thread Jeremy Huddleston
What is the output of: echo $DISPLAY launchctl list org.x.startx On Sep 26, 2011, at 3:39 PM, Louis Zulli wrote: > > On Sep 26, 2011, at 4:00 PM, Jeremy Huddleston wrote: > >> You need to logout and log back in after you disable it. Your environment >> still contains the old $DISPLAY > > Sti

Re: [Xquartz-dev] XQuartz 2.7.0_beta2

2011-09-26 Thread Louis Zulli
On Sep 26, 2011, at 4:00 PM, Jeremy Huddleston wrote: > You need to logout and log back in after you disable it. Your environment > still contains the old $DISPLAY Still not working. I do launchctl unload /System/Library/LaunchAgents/org.x.startx.plist I then quit Terminal and log out. I lo

Re: [Xquartz-dev] XQuartz 2.7.0_beta2

2011-09-26 Thread Jeremy Huddleston
You need to logout and log back in after you disable it. Your environment still contains the old $DISPLAY On Sep 26, 2011, at 02:38, Louis Zulli wrote: > > On Sep 26, 2011, at 3:34 AM, Jeremy Huddleston wrote: > >> You shouldn't need to move them. The one in /Library should take precedence

Re: [Xquartz-dev] XQuartz 2.7.0 (xorg-server 1.11.0) and MIT-MAGIC-COOKIE-1

2011-09-26 Thread Jeremy Huddleston
It looks like ~/.Xauthority is incorrect. Nuke it and restart your server. On Sep 26, 2011, at 02:05, Peter Dyballa wrote: > Hello! > > Yesterday I launched this X server from MacPorts for the first time. This > morning, after waking my MacBook, I get > > Invalid MIT-MAGIC-COOKIE-1 keyI

Re: [Xquartz-dev] XQuartz 2.7.0_beta2

2011-09-26 Thread Louis Zulli
On Sep 26, 2011, at 3:34 AM, Jeremy Huddleston wrote: > You shouldn't need to move them. The one in /Library should take precedence > over the one in /System/Library. > > Instead of messing with the files on your FS, you should just use launchctl > to disable that LaunchAgent: > launchctl unl

[Xquartz-dev] XQuartz 2.7.0 (xorg-server 1.11.0) and MIT-MAGIC-COOKIE-1

2011-09-26 Thread Peter Dyballa
Hello! Yesterday I launched this X server from MacPorts for the first time. This morning, after waking my MacBook, I get Invalid MIT-MAGIC-COOKIE-1 keyInvalid MIT-MAGIC-COOKIE-1 keyInvalid MIT-MAGIC-COOKIE-1 keyInvalid MIT-MAGIC-COOKIE-1 keygv: Unable to open the display. in the shell

Re: [Xquartz-dev] XQuartz 2.7.0_beta2

2011-09-26 Thread Jeremy Huddleston
You shouldn't need to move them. The one in /Library should take precedence over the one in /System/Library. Instead of messing with the files on your FS, you should just use launchctl to disable that LaunchAgent: launchctl unload /System/Library/LaunchAgents/org.x.startx.plist I'm curious why