On Tue, Mar 10, 2026 at 01:38:46AM -0500, [email protected] wrote: > On Mon, 2026-03-09 at 16:27 +0100, Pavel Sanda wrote: > > Looks like a bug indeed. Can you create minimal example showing > > master+child documents with this problem and send it to us? > > Wish I could! I sure tried! I can't figure out how to reproduce this > since deleting those characters. > > I've been having LyX problems for quite some time. I'd pull my hair > out, but I'm bald already! > > At first, it was Latex errors (likely all my fault as the preamble has > too much cut-n-paste), but it would output fine. Then it failed to > give output, but I can still edit. I separated the big file into > chapters in hopes that the latex runs might run a little faster, but > don't remember if that was before or after I failed to get output. I > was trying to fix the preamble and switch away from deprecated latex > libs to squash the warnings and errors, but it amounts to a rather > large rewrite and I'm just not that good at writing Latex! > > I thought I would just use the old backups that were working fine and > actually giving output, but they don't work anymore either, so > something changed in the library file or something. Then there was a > computer failure and everything was moved to a RPi for awhile before > being moved to the new laptop. Now I've got the above issue *and* it > can't run any latex commands. I was hoping the new laptop and fresh > install would help. It didn't. Xetex is installed and runs, but the > log shows nothing: > > This is XeTeX, Version 3.141592653-2.6-0.999998 (TeX Live 2026/Arch > Linux) (preloaded format=xelatex 2026.3.9) 10 MAR 2026 00:49 > entering extended mode > restricted \write18 enabled. > %&-line parsing enabled. > **VRCoreRules.tex > (./VRCoreRules.tex > > I figured I'd go back to an older version of LyX to see what I can > salvage, but the file format has apparently been changed!! Trying to > export in 2.5 format gives me errors when it runs python! Maybe it > was translating from the old 2.5 format to the 2.6 format that doesn't > like UTF? The problem occured when upgrading to the new version of > Lyx, so maybe it was the code reading the 2.5 format that is the > issue? This would explain why I can't reproduce it with a 2.5 file. > I still don't have an explanation as to why I could load the Chapter > 1 file that actually had the error, but was unable to load the Master > (which didn't have any special characters). Loading the Master would > complain about chapter 1 (which loads fine by itself) and then crash. > So ... I'm lost. > > I would export to 2.5 format and then reimport it to see if does it > again, but the exporter just says ... > > An error occurred while running: > python3 $$s/lyx2lyx/lyx2lyx -V 2.5 -o "VRCoreRules.25.lyx" > "VRCoreRules.lyx" > > My guess is $$s isn't expanding, but I have no idea what these codes > are supposed to be or why its not getting expanded or where to even > look. So, I have to find and fix the export bug just to find and test > the crash bug, and then I can figure out why it never runs LaTeX at > all, and then I can finally get back to fixing the preamble to use > different libs. That is honestly too much for me right now. I'll go > back to lurking.
I understand your frustration. Once you get from your cave, we can try to go point by point, there seem to be more issues mixed together. First I would suggest stick always to lyx 2.5 (branch 2.5.x), not to master branch (2.6 in future) which is development version and problems are supposed to happen. Then, if you can share with us problematic files, that would help a lot, the snippets of code you share show nothing useful to debug. And last please keep the emails on dev-list. Cheers :) Pavel -- lyx-devel mailing list [email protected] https://lists.lyx.org/mailman/listinfo/lyx-devel
