I can share a bit as a win10 user of 2.2.2. One annoying quirk of LyX and MikTeX is the fact that MikTeX on-the-fly installs can sometimes fail for weird but not rare reasons. For example, you configured MikTeX to use server ABC but for some strange reason that server's archive is broken and the package LyX needs fails a sanity check. When these failures occur, LyX gives a vague answer, probably due to the level of nesting. It wasn't until I ran MikTeX update as administrator that I got the helpful message that let me know to switch servers. The average user might not be so tolerant or persistent. It's too bad the MikTeX redundant system is not more robust.
Another problem I encounter is with long file paths, but only when using, say, PNG images in my LyX files. LyX again fails with an obscure error. Debugging the image conversion in the cache showed that my the filename was really long and at some point the converted image was "not found". I moved my LyX file directory to a path closer to the root, thus making the cache file names shorter, and the errors stop. I can probably reproduce this easily, if more info is needed. On Apr 13, 2017 09:53, "Stephan Witt" <st.w...@gmx.net> wrote: > Am 13.04.2017 um 15:44 schrieb Mitch Gusat <mgu...@gmail.com>: > > > > Seen the same issues on Mac and Linux, but it's particularly vexing on > Windows since the recent (April'17) Miktex 2.9 release: Lyx 2.0/1/2 used to > work flawlessly for years before the new miktex release. > > Hi Mitch, > > I’d like to get more detailed infos regarding the problems you’ve > mentioned for LyX on Mac. > > Thank you > Stephan > >
