Am 16.02.2024 um 07:53 schrieb list_em...@icloud.com: > > Sorry for the slow response. > > Running from a terminal indeed showed repeated configuration runs. Near the > top of the first run (and only the first run) were these lines: > > +Running LyX configure with Python 3.9.18 > Checking for upgrade from previous version. > Found directory "/Users/me/Library/Application Support/LyX-2.3". > Skip cache /Users/me/Library/Application Support/LyX-2.3/cache > Content copied from directory "/Users/me/Library/Application Support/LyX-2.3”. > > I found three identical copies of chkconfig.ltx in each of > > /Users/me/Library/Application Support/LyX-2.1/chkconfig.ltx > /Users/me/Library/Application Support/LyX-2.2/chkconfig.ltx > /Users/me/Library/Application Support/LyX-2.3/chkconfig.ltx > > > I zipped all of them and trashed the original. Now LyX 2.4.0 RC3 runs great. > > Thanks for that tip. > > I know how that file got there: LyX put it there. Maybe if the configuration > file has changed for 2.4 then it shouldn’t copy old versions. > > Note that 2.4 apparently just copies a bunch of stuff from the 2.3 directory > because now there is this file: > > /Users/me/Library/Application Support/LyX-2.4/chkconfig.ltx.zip > > which is obviously a copy of the file that I zipped, likely from the > corresponding 2.3 directory. > > There is now no chkconfig.ltx in the 2.4 directory. > > Jerry
Hi Jerry, you’re right with your assumptions. The idea is to mimic the in-place update of LyX to avoid a reset of the user configuration to system defaults in case of an upgrade to a new LyX major version. Therefore the copy of the contents of the previous LyX major versions user directory to the fresh created one. This copy operation happens only once. I’m trying to reproduce your problem to find a solution for it. I’m unable to get repeated configuration runs. I’ve put the chkconfig.ltx as of version lyx-2.0.6 into ~/Library/Application Support/LyX-2.3 to test it. May I ask you to send me a copy of your chkconfig.ltx, please? (The old version causing the problem…) Thank you and best regards, Stephan >> On Feb 14, 2024, at 4:13 AM, Jürgen Spitzmüller <jspi...@gmail.com> wrote: >> >> Am Montag, dem 12.02.2024 um 22:59 -0700 schrieb list_em...@icloud.com: >>> I’m sorry to report continuing problems on macOS 12.7.2, Monterey >>> with LyX 2.4.0 RC3. >>> >>> Hangs (pinwheel) on first launch with only Apple and LyX menu items, >>> then same on second launch. Very low CPU and memory use. Force quit >>> both. >>> >>> Deleted /Users/me/Library/Application Support/LyX-2.4/ >>> >>> Re-launch. Opens “Welcome to LyX!”. Then I did Document -> View -> >>> (PDF (pdflatex)). No PDF is created. Instead, rapid looping of some >>> messages in the status bar, apparently involved with TeX stuff, such >>> as “Indexing TeX files… .” Document -> Cancel Export has no effect. >>> At the same time, about 24 files are being written or modified in >>> /Users/me/Library/Application Support/LyX-2.4/ every 1-3 seconds. I >>> am able to capture the contents of e.g. configure.log. Attempt to >>> quit normally causes this dialog: " LyX could not be closed because >>> documents are being processed by LyX.” >>> >>> Force quit again. >>> >>> Re-launch. Hangs as on first launch; no Welcome. >>> >>> Re-boot. Same sort of behavior. Safe boot. Same: Sometimes opens >>> Welcome then hangs. Sometimes doesn’t finish drawing menu bar and >>> hangs. Sometimes opens Welcome and hangs when trying to open a new >>> file. Can no longer get to where I can attempt to make a PDF. >> >> Can you open LyX from a Terminal window and observe the output? Is it >> possible that the configuration of LyX gets repeatedly run in a loop? >> >> I have had that when I first installed 2.4.x without version suffix, >> and it turned out I had an old version of chkconfig.ltx in my personal >> LyX directory (no idea how it ended there). As the configure syntax >> significantly changed, this broke configuration. Removing the file >> fixed the issue for me. >> >> Maybe LyX 2.4 also accesses some outdated configuration files in your >> case. Or the configuration (or some conversion) fails for another >> reason. >> >> Terminal output might help us pinpointing the issue. >> >> -- >> Jürgen >> -- >> lyx-devel mailing list >> lyx-devel@lists.lyx.org >> http://lists.lyx.org/mailman/listinfo/lyx-devel > > -- > lyx-devel mailing list > lyx-devel@lists.lyx.org > http://lists.lyx.org/mailman/listinfo/lyx-devel -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
