severity 831843 normal thanks Hi Martin, I'm sorry for the long delay in any answer to this bugreport but the Debian LyX package is barely maintained at the moment.
I understand your frustration and for your usecase LyX might be broken which is a grave issue, but I think LyX in general still works fine so I'm now downgrading the bug to make it none release critical. >From my point of view it would be easier to maybe give you hints on how to move on with your setup if you contact the LyX developers either via their own mailinglist or via their bugtracking system. That could avoid a lot of back and forth. For example I would like to see your layouts to understand why and where it breaks. http://www.lyx.org/MailingLists https://www.lyx.org/trac/wiki/BugTrackerHome I can still forward your issue if you absolutely would like to avoid doing that on your own, but that's usually very time consuming for all involved parties with me acting as the human proxy. Beside of that it's a common issue that LyX format changes are not backwards compatible. Usually the lyx2lyx tool is able to handle a conversion in both directions. For example from the last 2.1.x release to 2.2.0 and back. But I guess the lyx2lyx in Debian/stable as shipped with 2.1.2 is too old to do that. So if you maybe build the 2.1.5 release it might be able to read the 2.2.0 imported document. ftp://ftp.lyx.org/pub/lyx/stable/2.1.x/lyx-2.1.5.tar.xz ftp://ftp.lyx.org/pub/lyx/stable/2.1.x/lyx-2.1.5.tar.xz.sig But to be honest I've moved out of the LyX community 6 years ago, so my advise might be outdated. Beside of that we've now uploaded LyX 2.2.2, maybe that fixed one of your issues, though the chance might be slim if you did not report the issue upstream. Regards, Sven