Lyx and Yosemite

[Anders Engelsvold]

Hello,

I am a complete beginner to Tex, and have recently installed Lyx in conjunction with MacTex.
Lyx doesn’t appear to be recognizing the Tex-distribution though, because as soon as I start the program I get a message saying that I’m missing a document class. If I go to Document -> Settings, all the document classes are listed as unavailable.

I have got a Macbook Pro 2011 running Yosemite (OS X 10.10). I installed Lyx and MacTex after installing Yosemite.

What I have tried to fix it:
- Uninstalling and reinstalling both MacTex and Lyx
- Reconfigure
- Running the configure.py module in the resources folder (almost every line in the output is followed by a "no")

I have been in touch with Herb Schulz at MacTex and he concluded that everything was running fine on the MacTex-end on my computer.
He came with the following suggestion:

"From some discussions on the TeXworks list it appears that TeXworks has been struck by a bug in Yosemite that passes the incorrect PATH value to sub-processes. This might be true for Lyx too. Please report this to the authors of Lyx."


Best regards,
Anders Engelsvold

[Murat Yildizoglu]

Hi,
I have upgraded my MBP 2011 to Yosemite and I meet similar problems.
When I launch LyX from the Console (sudo and not sudo), I get a Lyx with
a French interface and it can see all latex packages installed by
MacTeX2014 when I do Tools/Tex Information.
When I launch it using the Applications folder icon, I get a LyX with an
English UI and it cannot see any of the packages.
Really strange problem...

Post by Anders Engelsvold
Hello,
I am a complete beginner to Tex, and have recently installed Lyx in conjunction with MacTex.
Lyx doesn’t appear to be recognizing the Tex-distribution though, because as soon as I start the program I get a message saying that I’m missing a document class. If I go to Document -> Settings, all the document classes are listed as unavailable.
I have got a Macbook Pro 2011 running Yosemite (OS X 10.10). I installed Lyx and MacTex after installing Yosemite.
- Uninstalling and reinstalling both MacTex and Lyx
- Reconfigure
- Running the configure.py module in the resources folder (almost every line in the output is followed by a "no")
I have been in touch with Herb Schulz at MacTex and he concluded that everything was running fine on the MacTex-end on my computer.
"From some discussions on the TeXworks list it appears that TeXworks has been struck by a bug in Yosemite that passes the incorrect PATH value to sub-processes. This might be true for Lyx too. Please report this to the authors of Lyx."
Best regards,
Anders Engelsvold

--
Université de Bordeaux <http://www.u-bordeaux.fr> CNRS
<http://www.cnrs.fr/aquitaine-limousin>

Prof. Murat Yildizoglu <mailto:***@u-bordeaux4.fr>

GREThA (UMR CNRS 5113)
UNIVERSITE DE BORDEAUX
GREThA (UMR CNRS 5113)
MURAT YILDIZOGLU
16 AVENUE LEON DUGUIT
CS 50057
33608 PESSAC CEDEX
FRANCE

Bureau : E-331

yildizoglu.info <http://yildizoglu.info>

[Murat Yildizoglu]

I do not know why it worked, but this method has worked after having
restarted my laptop today. After having launched through the terminal and
run Reconfigure, I can now find everything in LyX. I ma relieved.

Thanks a lot for this solution.

Hi,
I have upgraded my MBP 2011 to Yosemite and I meet similar problems. When
I launch LyX from the Console (sudo and not sudo), I get a Lyx with a
French interface and it can see all latex packages installed by MacTeX2014
when I do Tools/Tex Information.
When I launch it using the Applications folder icon, I get a LyX with an
English UI and it cannot see any of the packages.
Really strange problem...
Hello,
I am a complete beginner to Tex, and have recently installed Lyx in conjunction with MacTex.
Lyx doesn’t appear to be recognizing the Tex-distribution though, because as soon as I start the program I get a message saying that I’m missing a document class. If I go to Document -> Settings, all the document classes are listed as unavailable.
I have got a Macbook Pro 2011 running Yosemite (OS X 10.10). I installed Lyx and MacTex after installing Yosemite.
- Uninstalling and reinstalling both MacTex and Lyx
- Reconfigure
- Running the configure.py module in the resources folder (almost every line in the output is followed by a "no")
I have been in touch with Herb Schulz at MacTex and he concluded that everything was running fine on the MacTex-end on my computer.
"From some discussions on the TeXworks list it appears that TeXworks has been struck by a bug in Yosemite that passes the incorrect PATH value to sub-processes. This might be true for Lyx too. Please report this to the authors of Lyx."
Best regards,
Anders Engelsvold
--
[image: Université de Bordeaux] <http://www.u-bordeaux.fr> [image: CNRS]
<http://www.cnrs.fr/aquitaine-limousin>
GREThA (UMR CNRS 5113)
UNIVERSITE DE BORDEAUX
GREThA (UMR CNRS 5113)
MURAT YILDIZOGLU
16 AVENUE LEON DUGUIT
CS 50057
33608 PESSAC CEDEX
FRANCE
Bureau : E-331
yildizoglu.info

--
Prof. Murat Yildizoglu

Université Montesquieu Bordeaux IV
GREThA (UMR CNRS 5113)
Avenue Léon Duguit
33608 Pessac cedex
France

Bureau : E-331

mail: yildi-at-u-bordeaux4.fr

web: yildizoglu.info

[Scott Kostyshak]

Hi Anders,

Post by Anders Engelsvold
Hello,
I am a complete beginner to Tex, and have recently installed Lyx in conjunction with MacTex.
Lyx doesn’t appear to be recognizing the Tex-distribution though, because as soon as I start the program I get a message saying that I’m missing a document class. If I go to Document -> Settings, all the document classes are listed as unavailable.
I have got a Macbook Pro 2011 running Yosemite (OS X 10.10). I installed Lyx and MacTex after installing Yosemite.
- Uninstalling and reinstalling both MacTex and Lyx
- Reconfigure
- Running the configure.py module in the resources folder (almost every line in the output is followed by a "no")

Does the solution here work?
http://tex.stackexchange.com/questions/203810/lyx-2-x-document-class-not-available-mac-os-x-10-10-yosemite-pb-3

Post by Anders Engelsvold
I have been in touch with Herb Schulz at MacTex and he concluded that everything was running fine on the MacTex-end on my computer.
"From some discussions on the TeXworks list it appears that TeXworks has been struck by a bug in Yosemite that passes the incorrect PATH value to sub-processes. This might be true for Lyx too. Please report this to the authors of Lyx."

Thanks for the report. This is good to know. If this is true though,
it seems kind of silly of me to report the bug to every piece of
software you use. Why not report the bug to Mac? If it already exists,
can you find a URL to a bug report?

Best,

Scott

[Anders Engelsvold]

Scott,

Thanks for the reply.
Someone already suggested that solution to me, and it worked perfectly!

Anders

Post by Scott Kostyshak
Hi Anders,

Post by Anders Engelsvold
Hello,
I am a complete beginner to Tex, and have recently installed Lyx in conjunction with MacTex.
Lyx doesn’t appear to be recognizing the Tex-distribution though, because as soon as I start the program I get a message saying that I’m missing a document class. If I go to Document -> Settings, all the document classes are listed as unavailable.
I have got a Macbook Pro 2011 running Yosemite (OS X 10.10). I installed Lyx and MacTex after installing Yosemite.
- Uninstalling and reinstalling both MacTex and Lyx
- Reconfigure
- Running the configure.py module in the resources folder (almost every line in the output is followed by a "no")

Does the solution here work?
http://tex.stackexchange.com/questions/203810/lyx-2-x-document-class-not-available-mac-os-x-10-10-yosemite-pb-3

Post by Anders Engelsvold
I have been in touch with Herb Schulz at MacTex and he concluded that everything was running fine on the MacTex-end on my computer.
"From some discussions on the TeXworks list it appears that TeXworks has been struck by a bug in Yosemite that passes the incorrect PATH value to sub-processes. This might be true for Lyx too. Please report this to the authors of Lyx."

Thanks for the report. This is good to know. If this is true though,
it seems kind of silly of me to report the bug to every piece of
software you use. Why not report the bug to Mac? If it already exists,
can you find a URL to a bug report?
Best,
Scott