Jonathan Levi, M.D. wrote: > > At 6:13 PM -0500 2/8/09, Alexander Hansen wrote: >> [email protected] wrote: >> >> <snip> >> >> Can we please just get a transcript of the output of "fontforge >> --version" from your system? >> >> On my system I get: >> >> $ fontforge --version >> Copyright (c) 2000-2008 by George Williams. >> Executable based on sources from 16:11 GMT 24-Dec-2008-ML. >> Library based on sources from 16:11 GMT 24-Dec-2008. >> fontforge 20081224 >> libfontforge 20081224-ML >> >> -- > > Here it is. I don't know what the osascript problems in the middle are > about. -- Jonathan > > Copyright (c) 2000-2008 by George Williams. > Executable based on sources from 16:11 GMT 24-Dec-2008-ML. > Library based on sources from 16:11 GMT 24-Dec-2008. > 2009-02-08 22:10:59.090 osascript[19963] *** _NSAutoreleaseNoPool(): > Object 0x3239c0 of class NSPathStore2 autoreleased with no pool in place > - just leaking
Phew! Thanks, Alex, for helping to pull the forceps :-) Now that we know that it is fontforge that produces this garbage output, we can focus on the way how it starts up and reacts on the --version flag. Looking at the sources, I see that this is rather complicated, and there is no immediate and obvious answer. Two points to check, however: In principle, and this is what happens for me, "fontforge -- version" should *not* try to start X11, which it seems to do in your case. So far, I have no idea why this could be. Is the result different if you have X11 running when you do "fontforge --version" compared to when it is not running? Second thing to check: Other people who were seeing the "osacript[]...leaking" error messages tracked it down to some 3rd-party scripting addition (in one case related to a logitech mouse) sitting in /Library/ScriptingAdditions/ or ~/Library/ScriptingAdditions/. Do you have anything in one of these 2 directories? -- Martin ------------------------------------------------------------------------------ Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM) software. With Adobe AIR, Ajax developers can use existing skills and code to build responsive, highly engaging applications that combine the power of local resources and data with the reach of the web. Download the Adobe AIR SDK and Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com _______________________________________________ Fink-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fink-users
