[Xquartz-dev] Getting bad DISPLAY value during use of 2.6.1-2.6.2 (not with 2.6.0 & before).
sci-fi at hush.ai
sci-fi at hush.ai
Sun Apr 24 10:22:54 PDT 2011
> On 04/24/2011 at 11:44 AM, Jeremy Huddleston <jeremyhu at apple.com> wrote:On Apr 24, 2011, at 09:31, sci-fi at hush.ai wrote:
>
> >
> > Hello,
> >
> > I think DISPLAY is getting a weird value on my system here.
> >
> > We've completely rebooted, and this is still occurring on my system
> > with any of the 2.6.1-2.6.2 incarnations of Xquartz.
> > (IIRC this didn't happen with 2.6.0 and earlier.)
> > Presently I have the beta1 of 2.6.2 installed and trying to get it
> > started-up here.
> > (Yes I did re-run the installer for 2.6.2_beta1 after the 10.6.7/etc
> > system updates.)
> >
> > The user's env-var matches what launchctl returns:
> >
> > $ launchctl getenv DISPLAY
> > /tmp/launch-s9kPWX/org.x:0
>
> You should have
> /Library/LaunchAgents/org.macosforge.xquartz.startx.plist
>
> What is the output of "launchctl list org.macosforge.xquartz.startx"
$ launchctl list org.macosforge.xquartz.startx
{
"Label" = "org.macosforge.xquartz.startx";
"LimitLoadToSessionType" = "Background";
"OnDemand" = true;
"LastExitStatus" = 0;
"TimeOut" = 30;
"ProgramArguments" = (
"/opt/X11/bin/startx";
);
"EnableTransactions" = true;
"TransactionCount" = -1;
"Sockets" = {
"org.macosforge.xquartz:0" = (
file-descriptor-object;
);
};
};
> > <snip/>
> >
> > (There is no critter named /tmp/.X11-unix (shown via ls -al) presently
> > on my system.
> > The /tmp dir itself does have root:wheel ownership with "drwxrwxrwt"
> > flags.)
>
> It should be created by /Library/LaunchDaemons/org.macosforge.xquartz.privileged_startx.plist
>
> What is the output of "sudo launchctl list org.macosforge.xquartz.privileged_startx"
$ sudo launchctl list org.macosforge.xquartz.privileged_startx
Password:
{
"Label" = "org.macosforge.xquartz.privileged_startx";
"LimitLoadToSessionType" = "System";
"OnDemand" = true;
"LastExitStatus" = 0;
"TimeOut" = 120;
"ProgramArguments" = (
"/opt/X11/lib/X11/xinit/privileged_startx";
"-d";
"/opt/X11/lib/X11/xinit/privileged_startx.d";
);
"EnableTransactions" = true;
"TransactionCount" = -1;
"MachServices" = {
"org.macosforge.xquartz.privileged_startx" = mach-port-object;
};
};
> […]
During these lists, none of the X (sub)tasks are running now.
BTW I dug a bit and found:
$ ls -al /tmp/launch-34Cqdu
total 0
drwx------ 2 scifi wheel 102 Apr 24 10:25 .
drwxrwxrwt 11 root wheel 544 Apr 24 11:56 ..
srwx------ 1 scifi wheel 0 Apr 24 10:25 org.macosforge.xquartz:0
so _something_ was trying to work right.
But the timestamps might tell something -- the "wrong" one might've been created during when we rebooted, 19-minutes earlier:
$ ls -al /tmp/launch-s9kPWX
total 0
drwx------ 2 scifi wheel 102 Apr 24 10:06 .
drwxrwxrwt 11 root wheel 544 Apr 24 11:56 ..
srwx------ 1 scifi wheel 0 Apr 24 10:06 org.x:0
Another BTW -- I don't have anything like ~/.x* critters either, nor in /etc . ;)
Thanks again.
More information about the Xquartz-dev
mailing list