On August 10, 2014 at 9:10:13 PM, Richard Heck (rgh...@lyx.org) wrote: On 08/10/2014 07:09 AM, Kevin Horton wrote: Lyx was working fine for me with OS X 10.8 (I don't think I tried it with OS X 10.9), but I have major problems since installing OS X 10.10 beta on my seconadary computer. The problems are identical with Lyx 2.0.7.1 and Lyx 2.1.1.
When opening Lyx documents, I get messages like: "The selected document class Article (Standard Class) requires external files that are not available. The document class can still be used, but the document cannot be compiled until the following prerequisites are installed: article.cls See section 3.1.2.2 (Class Availability) of the User's Guide for more information." If I select Tools->TeX Information, no classes are shown. Help-> LaTeX Configuration finds no fonts, classes, paper layout packages, etc. I have a working LaTeX, with the various classes, etc installed at /sw/share/texmf-dist. LaTeX itself is found at /sw/bin/latex. /sw/bin is in the PATH prefix listed in the Lyx preferences. I've run texhash, and Tools->Reconfigure, and then restarted Lyx, but that makes no difference. I can't help with the details, but this sounds like a python problem, which we've seen before, on various platforms. LyX needs to run python 2.x, but the default version on some platforms is 3.x. Someone on OSX will be able to help fix this. For now, you might try running LyX from a terminal and seeing what error messages you get when you reconfigure. The OS X 10.10 beta system python (i.e. the one supplied by Apple) is python 2.7.6. I've got python 2.7.8 installed, and it is first in my user PATH. Running Lyx once from the terminal appears to have corrected the problem. It didn’t throw those error messages when ran from the terminal, and it found all the expected classes. This happy situation has persisted after quitting Lyx and starting it normally. Perhaps Lyx sees a different environment when run from the terminal, and this allowed it to find everything and correctly update its config files. Problem solved. Thanks for the help. -- Kevin Horton
