On Jan 27, 2011, at 03:25, Peter Dyballa wrote: > > Am 27.12.2010 um 02:13 schrieb Jeremy Huddleston: > >>> When I launch for example FontForge from the first Terminal window (no >>> DISPLAY set) >> >> Why is DISPLAY not set? I thought you said it was set to >> DISPLAY=/tmp/launch-OtsB9G/org.x:0 ... ? > > > Hello Jeremy! > > I had to reboot my PowerBook and login again due to a software installation. > Before I managed to make the org.macports.startx plist active in launch > services. DISPLAY is now something like > DISPLAY=/tmp/launch-QFqPcx/org.macports:0. The X server running is X.Org X > Server 1.9.3/Build Date: 20101229 from MacPorts. It works again with > BlackboxWM. But: GNU Emacs does not launch. None of my many X client variants > (22.3, 23.0.60, 23.0.94, 23.1.93, 23.2, 24.0.50) launches as X client. All > what happens is that the CPU load rises to maximum. And eight minutes at this > level clearly is not normal behaviour.
Can you mail me a stackshot (ctrl-opt-cmd-shift-. will put it in /Library/Logs/stackshot*.log ... wait a few seconds after taking it) and a spindump (sudo spindump ... filename will be reported to you) while it's in this state? > > The same behaviour with the latest org.x.x11.pkg 2.6.6. (Which sets DISPLAY > to :0.) > > -- > Greetings > > Pete > > Who the fsck is "General Failure," and why is he reading my disk? > > > _______________________________________________ > Xquartz-dev mailing list > [email protected] > http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev _______________________________________________ Xquartz-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
