Re: pdftex process on MAC OSX Lyx 2.0.0 - more

2011-05-15 Thread Robert Betz
Jens, The process that is left running is called pdftex (not pdflatex), and its parent process is called Python, whose parent process is Lyx. That is the sequence of parent to child processes. In relation to what I inserted into the koma-let2.lyx template file it was simply a → inserted in MAT

Re: pdftex process on MAC OSX Lyx 2.0.0 - more

2011-05-15 Thread Jens Nöckel
Bob, I'm not sure I understand the problem, but I'm guessing you inserted a character like → into the text, while not in math mode. If so, you could try to circumvent the problem by going to Document > Settings > Fonts and changing the template's Roman font from "Palatino" to "Default". I don't

Re: pdftex process on MAC OSX Lyx 2.0.0 - more

2011-05-15 Thread Robert Betz
Jens, It is not happening all the time with the system, but only under a very specific class file. Having thought about it a bit more after the initial posting it may be an issue with pdftex itself, or with the Python script the invokes it (from Lyx). If you create new file using the koma-lett

Re: pdftex process on MAC OSX Lyx 2.0.0 - more

2011-05-15 Thread Jens Nöckel
On May 14, 2011, at 7:52 PM, Robert Betz wrote: > Tried uninstalling Lyx 2.0.0 and reinstalled Lyx 1.6.10 and also 1.6.9. All > doing the same thing (pdftex not closing and using 100% CPU), so it may be my > system. Doing on two though. The parent process for pdftex is Python, whose > parent

pdftex process on MAC OSX Lyx 2.0.0 - more

2011-05-14 Thread Robert Betz
Tried uninstalling Lyx 2.0.0 and reinstalled Lyx 1.6.10 and also 1.6.9. All doing the same thing (pdftex not closing and using 100% CPU), so it may be my system. Doing on two though. The parent process for pdftex is Python, whose parent in turn is Lyx. When Lyx closes down, Python closes but p

pdftex process on MAC OSX Lyx 2.0.0

2011-05-14 Thread Robert Betz
I was wondering if other users have noticed that pdftex continues to run after one closes down Lyx 2.0.0 on MAC OSX. It consumes 100% of one of the CPUs on my machine, and I have to do a Forced Quit to stop it. I have tried this on two different machines, and am getting the same effect. I only