> On Jun 17, 2016, at 14:50, Viv Kendon <v...@trellick.net> wrote: > > launchctl print gui/`id -u`/org.macosforge.xquartz > launchctl: unknown subcommand “print"
It looks like you're on an older OS version. That should work for Yosemite and later. What version is your OS? Run 'launchctl list org.macosforge.xquartz.startx' instead > I’m not sure what this is supposed to do, so I tried launchctl list | grep > startx and got > - 2 org.macosforge.xquartz.startx > > however, I manually killed all the X11 running jobs before I left work today > so that may be all the “2” is telling us, and I’m now ssh’d in remotely. > I’ll be back in front of the machine on Monday. > > ls -l /opt/X11/libexec > total 212 > 0 drwxr-xr-x 2 root wheel 136 May 31 10:42 ./ > 0 drwxr-xr-x+ 9 root wheel 306 Jun 17 14:24 ../ > 84 -rwxr-xr-x 1 root wheel 83728 May 31 10:42 launchd_startx* > 128 -rwxr-xr-x 1 root wheel 129360 May 31 10:42 privileged_startx* > > (I have ls aliased with extra arguments) > > — Viv > > On 17 Jun 2016, at 17:39, Jeremy Huddleston Sequoia <jerem...@apple.com> > wrote: > >> What's the output of: >> >> launchctl print gui/`id -u`/org.macosforge.xquartz.startx >> ls -l /opt/X11/libexec >> >> >>> On Jun 17, 2016, at 06:56, Viv Kendon <v...@trellick.org> wrote: >>> >>> This sparkled its way onto my mac just now, but won’t launch properly. >>> Error in console log is: >>> >>> 17/06/2016 14:36:21.860 com.apple.launchd.peruser.502[175]: >>> (org.macosforge.xquartz.startx[34868]) Job failed to exec(3). Setting up >>> event to tell us when to try again: 2: No such file or directory >>> 17/06/2016 14:36:21.860 com.apple.launchd.peruser.502[175]: >>> (org.macosforge.xquartz.startx[34868]) Job failed to exec(3) for weird >>> reason: 2 >>> >>> There is some sort of running process (dock icon is lit) but finder says it >>> is unresponsive. top shows >>> >>> 34867 X11.bin 0.0 00:00.00 1 0 7 163985 532K 472K 0B >>> 34832 X11.bin 0.0 00:00.19 2 0 34 163982 13M 264K 0B >>> >>> Needless to say I haven’t changed anything X-related since the previous >>> version was working just fine. >>> >>> Suggestions? Anything I could useful do/send to debug this? >>> >>> many thanks, >>> — Viv >>> >>> On 31 May 2016, at 18:14, Jeremy Huddleston Sequoia <jerem...@apple.com> >>> wrote: >>> >>>> I've released the second beta of XQuartz 2.7.10. The main changes since >>>> the previous beta include: >>>> fixes for TCP connections >>>> enabling of IGLX support >>>> the stuck "h" after hiding bug >>>> improved WM_PROTOCOLS support >>>> fixed a buffer overrun in libXfont >>>> various package version updates. >>>> >>>> https://www.xquartz.org/releases/XQuartz-2.7.10_beta2.html >>>> >>>> >>>> _______________________________________________ >>>> Xquartz-dev mailing list >>>> Xquartz-dev@lists.macosforge.org >>>> https://lists.macosforge.org/mailman/listinfo/xquartz-dev >>> >>> >>> _______________________________________________ >>> Xquartz-dev mailing list >>> Xquartz-dev@lists.macosforge.org >>> https://lists.macosforge.org/mailman/listinfo/xquartz-dev >>> >> >> >> _______________________________________________ >> Xquartz-dev mailing list >> Xquartz-dev@lists.macosforge.org >> https://lists.macosforge.org/mailman/listinfo/xquartz-dev > > > _______________________________________________ > Xquartz-dev mailing list > Xquartz-dev@lists.macosforge.org > https://lists.macosforge.org/mailman/listinfo/xquartz-dev >
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/xquartz-dev
