Re: lyx file from 2015 not converted to pdf
Am 24.03.20 um 20:24 schrieb Jean-Marc Lasgouttes: Le 24/03/2020 à 20:23, Wolfgang Engelmann a écrit : What does Help>About>Information on Compilation say? It should tell us what options where active when configuring LyX. LyX Version 2.3.4.2 (Friday, February 7, 2020) Library directory: /usr/share/lyx/ User directory: ~/.lyx/ Qt Version (run-time): 5.12.5 Qt Version (compile-time): 5.12.5 This is the first tab of the dialog. I am interested by the 4th one. JMarc Here it is: Build Info: LyX 2.3.4.2 (2020-02-07) Configuration Host type: x86_64-pc-linux-gnu Special build flags: build=release std-regex warnings use-enchant Bundled libraries: (none) C++ Compiler:g++ (9.2.1) C++ Compiler flags: -Wall -Wextra -Wno-deprecated-copy -fPIC -O2 -std=c++14 C++ Compiler user flags: -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++14 -g -O2 -fdebug-prefix-map=/build/lyx-Jf4jAS/lyx-2.3.4.2=. -fstack-protector-strong -Wformat -Werror=format-security -fPIC Linker flags: Linker user flags: -Wl,-z,defs -Wl,--as-needed -Wl,-z,relro -Wl,-z,now Qt Frontend: Qt version: 5.12.5 Packaging: posix LyX binary dir: /usr/bin LyX files dir: /usr/share/lyx Wolfgang -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: lyx file from 2015 not converted to pdf
Le 24/03/2020 à 20:23, Wolfgang Engelmann a écrit : What does Help>About>Information on Compilation say? It should tell us what options where active when configuring LyX. LyX Version 2.3.4.2 (Friday, February 7, 2020) Library directory: /usr/share/lyx/ User directory: ~/.lyx/ Qt Version (run-time): 5.12.5 Qt Version (compile-time): 5.12.5 This is the first tab of the dialog. I am interested by the 4th one. JMarc -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: lyx file from 2015 not converted to pdf
Am 24.03.20 um 19:59 schrieb Jean-Marc Lasgouttes: Le 24/03/2020 à 19:41, Wolfgang Engelmann a écrit : Am 24.03.20 um 19:29 schrieb Pavel Sanda: On Tue, Mar 24, 2020 at 07:21:27PM +0100, Wolfgang Engelmann wrote: LyX: Software exception Detected LyX has caught an exception, it will now attempt to save all unsaved documents and exit. Exception: std::exception Did I understand you correctly, that you did not receive this message? No, but you might have assertions enabled. what does assertion mean? Did you self compile or do you use distribution binary? no, I used the Debian actualizations What does Help>About>Information on Compilation say? It should tell us what options where active when configuring LyX. JMarc LyX Version 2.3.4.2 (Friday, February 7, 2020) Library directory: /usr/share/lyx/ User directory: ~/.lyx/ Qt Version (run-time): 5.12.5 Qt Version (compile-time): 5.12.5 not sure whether I understood: This is the version I am using now. I can't tell what I used when I wrote the 2015 Lyx version. Wolfgang -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: lyx file from 2015 not converted to pdf
Le 24/03/2020 à 19:41, Wolfgang Engelmann a écrit : Am 24.03.20 um 19:29 schrieb Pavel Sanda: On Tue, Mar 24, 2020 at 07:21:27PM +0100, Wolfgang Engelmann wrote: LyX: Software exception Detected LyX has caught an exception, it will now attempt to save all unsaved documents and exit. Exception: std::exception Did I understand you correctly, that you did not receive this message? No, but you might have assertions enabled. what does assertion mean? Did you self compile or do you use distribution binary? no, I used the Debian actualizations What does Help>About>Information on Compilation say? It should tell us what options where active when configuring LyX. JMarc -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: lyx file from 2015 not converted to pdf
Am 24.03.20 um 19:45 schrieb Pavel Sanda: On Tue, Mar 24, 2020 at 07:41:39PM +0100, Wolfgang Engelmann wrote: No, but you might have assertions enabled. what does assertion mean? These are special conditions in which we let lyx shutdown and should be enabled only by developers. If you use debian binaries, you should be safe and need not worry about it. Pavel Thanks, Paul, for the explanation. Wolfgang -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: lyx file from 2015 not converted to pdf
On Tue, Mar 24, 2020 at 07:41:39PM +0100, Wolfgang Engelmann wrote: > > No, but you might have assertions enabled. > > what does assertion mean? These are special conditions in which we let lyx shutdown and should be enabled only by developers. If you use debian binaries, you should be safe and need not worry about it. Pavel -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: lyx file from 2015 not converted to pdf
Am 24.03.20 um 19:36 schrieb Jürgen Spitzmüller: Am Dienstag, den 24.03.2020, 19:28 +0100 schrieb Wolfgang Engelmann: Yes Jürgen, you are right. I unchecked literal and pdf output is ok. Can I uncheck all 'literal' in the various nomenclature inserts at once? Only if you open the LyX file in a text editor. Search for literal "true" and replace it by literal "false" good idea, but I checked already all entries and its now working well. Your help saved me a lot of time and nerves, thanks a lot! Wolfgang You should check the output of all nomenclature entries carefully after that, though. Jürgen -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: lyx file from 2015 not converted to pdf
Am 24.03.20 um 19:29 schrieb Pavel Sanda: On Tue, Mar 24, 2020 at 07:21:27PM +0100, Wolfgang Engelmann wrote: LyX: Software exception Detected LyX has caught an exception, it will now attempt to save all unsaved documents and exit. Exception: std::exception Did I understand you correctly, that you did not receive this message? No, but you might have assertions enabled. what does assertion mean? Did you self compile or do you use distribution binary? no, I used the Debian actualizations Wolfgang Pavel -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: lyx file from 2015 not converted to pdf
Am Dienstag, den 24.03.2020, 19:28 +0100 schrieb Wolfgang Engelmann: > Yes Jürgen, you are right. I unchecked literal and pdf output is ok. > Can I uncheck all 'literal' in the various nomenclature inserts at > once? Only if you open the LyX file in a text editor. Search for literal "true" and replace it by literal "false" You should check the output of all nomenclature entries carefully after that, though. Jürgen signature.asc Description: This is a digitally signed message part -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: lyx file from 2015 not converted to pdf
On Tue, Mar 24, 2020 at 07:21:27PM +0100, Wolfgang Engelmann wrote: > LyX: Software exception Detected > LyX has caught an exception, it will now attempt to save all unsaved > documents and exit. > Exception: std::exception > > Did I understand you correctly, that you did not receive this message? No, but you might have assertions enabled. Did you self compile or do you use distribution binary? Pavel -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: lyx file from 2015 not converted to pdf
Am 24.03.20 um 19:17 schrieb Jürgen Spitzmüller: Am Dienstag, den 24.03.2020, 19:08 +0100 schrieb Pavel Sanda: As we figured out in background, the problem is using ligature 'fl' as one character instead of normally using two characters. Replacing them fixes the problem. Attached is minimal example. I was not capable to have lyx segfault because of it. Question, I guess either for Juergen or Guenter, is whether we should know unicode inside nomenclature and should be fixing this issue or this kind of use should not be supported. From the users point of view we don't report any useful error. Of course it shouldn't crash but rather report the uncodable character. Can you file a report wrt this? However, if you uncheck "Literal" in the nomencl dialog, then the character is resolved properly (this is the default mode with newer documents; older documents are converted with Literal=true as this was the only possibility back then). "Literal" means that you can enter LaTeX code. Jürgen Yes Jürgen, you are right. I unchecked literal and pdf output is ok. Can I uncheck all 'literal' in the various nomenclature inserts at once? Wolfgang -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: lyx file from 2015 not converted to pdf
On Tue, Mar 24, 2020 at 07:17:16PM +0100, Jürgen Spitzmüller wrote: > Can you file a report wrt this? #11797 P -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: lyx file from 2015 not converted to pdf
Am 24.03.20 um 19:21 schrieb Wolfgang Engelmann: Am 24.03.20 um 19:08 schrieb Pavel Sanda: On Fri, Mar 20, 2020 at 09:43:00AM +0100, Wolfgang Engelmann wrote: Thanks all for suggestions. The file did compile in 2015. I tried to remove parts of the original. It turned out that a nomenclature lead to the error As we figured out in background, the problem is using ligature 'fl' as one character instead of normally using two characters. Replacing them fixes the problem. Attached is minimal example. I was not capable to have lyx segfault because of it. Question, I guess either for Juergen or Guenter, is whether we should know unicode inside nomenclature and should be fixing this issue or this kind of use should not be supported. From the users point of view we don't report any useful error. Pavel Pavel, I ran your mwe-lyx and got LyX: Software exception Detected LyX has caught an exception, it will now attempt to save all unsaved documents and exit. Exception: std::exception Did I understand you correctly, that you did not receive this message? I am using Debian bullseye and Lyx 2.3.3 Should I upgrade to 2.3.4? Wolfgang I am sorry, I just see that I use lyx version 2.3.4.2 Wolfgang -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: lyx file from 2015 not converted to pdf
Am 24.03.20 um 19:08 schrieb Pavel Sanda: On Fri, Mar 20, 2020 at 09:43:00AM +0100, Wolfgang Engelmann wrote: Thanks all for suggestions. The file did compile in 2015. I tried to remove parts of the original. It turned out that a nomenclature lead to the error As we figured out in background, the problem is using ligature 'fl' as one character instead of normally using two characters. Replacing them fixes the problem. Attached is minimal example. I was not capable to have lyx segfault because of it. Question, I guess either for Juergen or Guenter, is whether we should know unicode inside nomenclature and should be fixing this issue or this kind of use should not be supported. From the users point of view we don't report any useful error. Pavel Pavel, I ran your mwe-lyx and got LyX: Software exception Detected LyX has caught an exception, it will now attempt to save all unsaved documents and exit. Exception: std::exception Did I understand you correctly, that you did not receive this message? I am using Debian bullseye and Lyx 2.3.3 Should I upgrade to 2.3.4? Wolfgang -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: lyx file from 2015 not converted to pdf
Am Dienstag, den 24.03.2020, 19:08 +0100 schrieb Pavel Sanda: > As we figured out in background, the problem is using ligature 'fl' > as one character instead of normally using two characters. Replacing > them fixes the problem. > > Attached is minimal example. > > I was not capable to have lyx segfault because of it. > > Question, I guess either for Juergen or Guenter, is whether > we should know unicode inside nomenclature and should be fixing > this issue or this kind of use should not be supported. > From the users point of view we don't report any useful error. Of course it shouldn't crash but rather report the uncodable character. Can you file a report wrt this? However, if you uncheck "Literal" in the nomencl dialog, then the character is resolved properly (this is the default mode with newer documents; older documents are converted with Literal=true as this was the only possibility back then). "Literal" means that you can enter LaTeX code. Jürgen > > Pavel signature.asc Description: This is a digitally signed message part -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: lyx file from 2015 not converted to pdf
On Fri, Mar 20, 2020 at 09:43:00AM +0100, Wolfgang Engelmann wrote: > Thanks all for suggestions. > The file did compile in 2015. > I tried to remove parts of the original. > It turned out that a nomenclature lead to the error As we figured out in background, the problem is using ligature 'fl' as one character instead of normally using two characters. Replacing them fixes the problem. Attached is minimal example. I was not capable to have lyx segfault because of it. Question, I guess either for Juergen or Guenter, is whether we should know unicode inside nomenclature and should be fixing this issue or this kind of use should not be supported. >From the users point of view we don't report any useful error. Pavel mwe.lyx Description: application/lyx -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: lyx file from 2015 not converted to pdf
On 2020-03-20, Wolfgang Engelmann wrote: > Am 19.03.20 um 22:20 schrieb Guenter Milde: >> On 2020-03-19, Richard Kimberly Heck wrote: >>> On 3/19/20 12:20 PM, Paul A. Rubin wrote: On 3/19/20 12:03 PM, Wolfgang Engelmann wrote: > I am trying to export from a lyx file produced in 2015 a pdf file, > but get this error: >> ... > further errors: > Error 84 returned from iconv when converting from UCS-4LE to > ISO-8859-15: Ungültiges oder unvollständiges Multi-Byte- oder > Wide-Zeichen >> This seems to indicate that there is an invalid utf8 multi-byte character >> somewhere in the *.lyx file. ... >> Keep the original file, and from a copy remove parts until it compiles. .. > I tried to remove parts of the original. > It turned out that a nomenclature lead to the error > However, I can't find any mistake in it (and as said before, it compiled > in 2015) > > VVD > VIVID is a small flavin-binding blue-light photoreceptor and consists of > a LOV domain and an N-terminal cap > I put it in a lyx Note and the part converted. > Than I found an other nomenclature causing trouble. > removed it, but now a nomenclature which went through alright before was > causing troubles. This may be due to the error reason beeing at a different place than the "trigger". > I gave up after spending hours. > Questions: > If I remove the nomenclature after bibtex and index at the end of the > document, that does apparently not prevent the nomenclatures in the text > to be neglected during compiling, since lyx clashes. This is in contrast > to the bibtex produced references, which, if removed, prevents clashes > if references are giving troubles. I.e. I have to remove (or put in Lyx > notes) the nomenclatures. Perhaps I should work with a latex file, where > I could remove the nomenclatures more easily with a text editor (or use > the lyx file with an editor). > For the time being I have to recover - otherwise I might get the corona Working with the exported LaTeX file may be a good idea, one layer less that may confuse things. If you have an old LyX version lying around, you may also try this. Evt. also export to LaTeX with the old version and re-import into current LyX. Günter -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: lyx file from 2015 not converted to pdf
Am 19.03.20 um 22:20 schrieb Guenter Milde: On 2020-03-19, Richard Kimberly Heck wrote: On 3/19/20 12:20 PM, Paul A. Rubin wrote: On 3/19/20 12:03 PM, Wolfgang Engelmann wrote: I am trying to export from a lyx file produced in 2015 a pdf file, but get this error: ... further errors: Error 84 returned from iconv when converting from UCS-4LE to ISO-8859-15: Ungültiges oder unvollständiges Multi-Byte- oder Wide-Zeichen This seems to indicate that there is an invalid utf8 multi-byte character somewhere in the *.lyx file. How should I proceed? The last message (error 84) suggests that there may be a problem with character encoding. If it is in a preview snipped, that could explain the preceding message. You can try to isolate the problematic portion of the document by bisection. Once you know where the problem is, we may be able to offer more specific advise. It's weird that you'd see the problem now and not in 2015. As Paul suggests, this is a problem with one of the characters in the document: We're trying to convert it to the right encoding and that's failing. LyX should not crash when that happens, but sometimes it does. It may be due to a lyx2lyx problem, some mistake when converting the document from an old lyx format to the current one. Keep the original file, and from a copy remove parts until it compiles. Günter Thanks all for suggestions. The file did compile in 2015. I tried to remove parts of the original. It turned out that a nomenclature lead to the error However, I can't find any mistake in it (and as said before, it compiled in 2015) > VVD VIVID is a small flavin-binding blue-light photoreceptor and consists of a LOV domain and an N-terminal cap I put it in a lyx Note and the part converted. Than I found an other nomenclature causing trouble. removed it, but now a nomenclature which went through alright before was causing troubles. I gave up after spending hours. Questions: If I remove the nomenclature after bibtex and index at the end of the document, that does apparently not prevent the nomenclatures in the text to be neglected during compiling, since lyx clashes. This is in contrast to the bibtex produced references, which, if removed, prevents clashes if references are giving troubles. I.e. I have to remove (or put in Lyx notes) the nomenclatures. Perhaps I should work with a latex file, where I could remove the nomenclatures more easily with a text editor (or use the lyx file with an editor). For the time being I have to recover - otherwise I might get the corona Cheers, Wolfgng VVD VIVID is a small flavin-binding blue-light photoreceptor and consists of a LOV domain and an N-terminal cap -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: lyx file from 2015 not converted to pdf
On 2020-03-19, Richard Kimberly Heck wrote: > On 3/19/20 12:20 PM, Paul A. Rubin wrote: >> On 3/19/20 12:03 PM, Wolfgang Engelmann wrote: >>> I am trying to export from a lyx file produced in 2015 a pdf file, >>> but get this error: ... >>> further errors: >>> Error 84 returned from iconv when converting from UCS-4LE to >>> ISO-8859-15: Ungültiges oder unvollständiges Multi-Byte- oder >>> Wide-Zeichen This seems to indicate that there is an invalid utf8 multi-byte character somewhere in the *.lyx file. >>> How should I proceed? >> The last message (error 84) suggests that there may be a problem with >> character encoding. If it is in a preview snipped, that could explain >> the preceding message. >> You can try to isolate the problematic portion of the document by >> bisection. Once you know where the problem is, we may be able to offer >> more specific advise. > It's weird that you'd see the problem now and not in 2015. As Paul > suggests, this is a problem with one of the characters in the document: > We're trying to convert it to the right encoding and that's failing. > LyX should not crash when that happens, but sometimes it does. It may be due to a lyx2lyx problem, some mistake when converting the document from an old lyx format to the current one. Keep the original file, and from a copy remove parts until it compiles. Günter -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: lyx file from 2015 not converted to pdf
On 3/19/20 12:20 PM, Paul A. Rubin wrote: > On 3/19/20 12:03 PM, Wolfgang Engelmann wrote: >> I am trying to export from a lyx file produced in 2015 a pdf file, >> but get this error: >> >> Error: Softwareausnahme erkannt >> >> LyX hat einen Fehler (Exception) entdeckt. Das Programm wird jetzt >> versuchen, alle ungespeicherten Dateien zu speichern, und dann beendet. >> >> Exception: std::exception >> Buffer.cpp (1601): >> /home/wolfgang/Dokumente/Photobiology-2015-3/PBR-FINAL--NN.lyx.emergency >> Buffer.cpp (1601): >> /home/wolfgang/Dokumente/Photobiology-2015-3/PBR-FINAL-NN.lyx.emergency >> Abgebrochen >> >> what might this mean > Exception: std::exception ?? >> >> I started the lyx on a terminal and there it starts with >> >> $ lyx PBR-FINAL--NN.lyx >> kf5.kio.core: "Ordner tags:/ lässt sich nicht öffnen." >> Warning: Failed to produce 1 preview snippet(s) >> QXcbClipboard: SelectionRequest too old >> >> further errors: >> Error 84 returned from iconv when converting from UCS-4LE to >> ISO-8859-15: Ungültiges oder unvollständiges Multi-Byte- oder >> Wide-Zeichen >> >> How should I proceed? >> Wolfgang > The last message (error 84) suggests that there may be a problem with > character encoding. If it is in a preview snipped, that could explain > the preceding message. > > You can try to isolate the problematic portion of the document by > bisection. Once you know where the problem is, we may be able to offer > more specific advise. It's weird that you'd see the problem now and not in 2015. As Paul suggests, this is a problem with one of the characters in the document: We're trying to convert it to the right encoding and that's failing. LyX should not crash when that happens, but sometimes it does. Riki -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: lyx file from 2015 not converted to pdf
On 3/19/20 12:03 PM, Wolfgang Engelmann wrote: I am trying to export from a lyx file produced in 2015 a pdf file, but get this error: Error: Softwareausnahme erkannt LyX hat einen Fehler (Exception) entdeckt. Das Programm wird jetzt versuchen, alle ungespeicherten Dateien zu speichern, und dann beendet. Exception: std::exception Buffer.cpp (1601): /home/wolfgang/Dokumente/Photobiology-2015-3/PBR-FINAL--NN.lyx.emergency Buffer.cpp (1601): /home/wolfgang/Dokumente/Photobiology-2015-3/PBR-FINAL-NN.lyx.emergency Abgebrochen what might this mean > Exception: std::exception ?? I started the lyx on a terminal and there it starts with $ lyx PBR-FINAL--NN.lyx kf5.kio.core: "Ordner tags:/ lässt sich nicht öffnen." Warning: Failed to produce 1 preview snippet(s) QXcbClipboard: SelectionRequest too old further errors: Error 84 returned from iconv when converting from UCS-4LE to ISO-8859-15: Ungültiges oder unvollständiges Multi-Byte- oder Wide-Zeichen How should I proceed? Wolfgang The last message (error 84) suggests that there may be a problem with character encoding. If it is in a preview snipped, that could explain the preceding message. You can try to isolate the problematic portion of the document by bisection. Once you know where the problem is, we may be able to offer more specific advise. Paul -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
