Re: lyx crash 2.3.3.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Just kidding, by pointing out that there are crashes and crashes :-)-O el On 2019-07-24 12:00 , Kornel Benko wrote: > Am Mittwoch, 24. Juli 2019, 11:30:01 CEST schrieb Dr Eberhard > Lisse: >> Then it wasn't really a crash :-)-O >> >> el >> >> >> On 23/07/2019 17:38, Wolfgang Engelmann wrote: [...] >>> p.s. I could recover the document from the emergency file >>> >>> Wolfgang >> > > It was a real crash, and we definitely are interested in the > cause. The fact, that lyx was able to create the emergency file > means that lyx could catch some (probably also unexpected) > exception. > > Kornel > -BEGIN PGP SIGNATURE- Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/ iQIzBAEBCAAdFiEEc5m+C677SuXtuUpUlwUdo3lFP6sFAl04gXUACgkQlwUdo3lF P6tcnRAAi/Aq94N5vduhnPJWBQ23VXXSEcqKJl8owbF8ctmdbi8AK04EVElDFd2w /Hwl9TU4DNg4IoVXNYmAhn7YgpQ5HVdRNv4DNABwTgZ3PzwD0YGHfhSPT2LD+/4Z 85iuYMUNqLTfSeZpeJ/JyXsOPi37BuBY8XCI3pnbspV+x3rgbb61fpTDBIo4YQPx yf7x5DM4oLIU9MVoRhbov/UVdwJnJdpfWl+hKhA1zARq6/J9tocC09IIIxd/mE1O nAStPib8oyP6Pruu6r++gE/IMqAiaFpo3pd5uWqJ9TKe/dt7womkTUgsvnG04jR/ Ia6DIv1W2DjSkPSlDdyRJe+Y8fjwEGu+AhFDNJcbdzhijc8k+U5XFaoEDlZd3dJZ lDjEywR8snEy4DxJYWd2miwyPYIB9yte/A4y3GAqpLMcZufMsGHcfugy8NZjBn83 qSHv3mETYPEuh/MeF98Vq5a6G/VfaS1YtV9KO8dzLprZcl/88iyyM2W8dP3L+5ap 7XhLNgi28SYnqqTj9AFjA1H285TubMdpPP1B8WmQ9WoGeSELmmrcMEcHLeqU/r2n cQs/yau4Fybu4wVknWe3h0thSqPjb6RRoAiaiKcXforqbQoIT7bGTiFI2kumt3zC DGyly3dwDdhY3A0i0Fhnt3jfwBmUzKW5zkvPijsIDqHNCgJ1tek= =FGud -END PGP SIGNATURE-
Re: lyx crash 2.3.3.
On Tue, Jul 23, 2019 at 06:24:40PM +0200, Wolfgang Engelmann wrote: > which means I should next time run lyx with -dbg, right? Or can I lyx -dbg won't be of any help. The best would be to get the backtrace if you run lyx under gdb with and debuging symbols were linked to the binary. ( https://wiki.lyx.org/FAQ/FurtherHelp#backtrace ) If you are 'lucky' enough to trigger this crash once a day this would be bery helpful and we can help you to setup you up for the stuff mentioned above. If you can't reproduce the error anymore then we are probably out of luck to spot what was going on. Pavel
Re: lyx crash 2.3.3.
Le 24/07/2019 à 12:00, Kornel Benko a écrit : It was a real crash, and we definitely are interested in the cause. The fact, that lyx was able to create the emergency file means that lyx could catch some (probably also unexpected) exception. It looks like an assertion, but I might be wrong. JMarc
Re: lyx crash 2.3.3.
Am Mittwoch, 24. Juli 2019, 11:30:01 CEST schrieb Dr Eberhard Lisse: > Then it wasn't really a crash :-)-O > > el > > > On 23/07/2019 17:38, Wolfgang Engelmann wrote: > [...] > > p.s. I could recover the document from the emergency file > > > > Wolfgang > It was a real crash, and we definitely are interested in the cause. The fact, that lyx was able to create the emergency file means that lyx could catch some (probably also unexpected) exception. Kornel signature.asc Description: This is a digitally signed message part.
Re: lyx crash 2.3.3.
Then it wasn't really a crash :-)-O el On 23/07/2019 17:38, Wolfgang Engelmann wrote: [...] > p.s. I could recover the document from the emergency file > > Wolfgang
Re: lyx crash 2.3.3.
Le 23/07/2019 à 19:01, Wolfgang Engelmann a écrit : On 23.07.19 18:36, Jean-Marc Lasgouttes wrote: Le 23/07/2019 à 18:24, Wolfgang Engelmann a écrit : Being able to reproduce the issue would be the best. JMarc which means I should next time run lyx with -dbg, right? Or can I still find a file with error messages now? Or trying to reproduce the situation if you remember it a bit. How maney paragraph in each nested note? Were there insets around? short note(s) in a longer note. No insets. A typical scenario is: the cursor is in position 10 in a paragraph and after some action the paragraph has a smaller size, say 5. The there is an assertion because the cursor position is after the end of the paragraph. Good hunt. JMarc
Re: lyx crash 2.3.3.
On 23.07.19 18:36, Jean-Marc Lasgouttes wrote: Le 23/07/2019 à 18:24, Wolfgang Engelmann a écrit : Being able to reproduce the issue would be the best. JMarc which means I should next time run lyx with -dbg, right? Or can I still find a file with error messages now? Or trying to reproduce the situation if you remember it a bit. How maney paragraph in each nested note? Were there insets around? short note(s) in a longer note. No insets. If you can give me a document that contains the part of text you were working on, and tell me what you think you were doing, I can try to have a look. will try to use an older file with this part and try to reproduce it. JMarc Wolfgang
Re: lyx crash 2.3.3.
Le 23/07/2019 à 18:24, Wolfgang Engelmann a écrit : Being able to reproduce the issue would be the best. JMarc which means I should next time run lyx with -dbg, right? Or can I still find a file with error messages now? Or trying to reproduce the situation if you remember it a bit. How maney paragraph in each nested note? Were there insets around? If you can give me a document that contains the part of text you were working on, and tell me what you think you were doing, I can try to have a look. JMarc
Re: lyx crash 2.3.3.
On 23.07.19 18:01, Jean-Marc Lasgouttes wrote: Le 23/07/2019 à 17:45, Wolfgang Engelmann a écrit : On 23.07.19 17:38, Wolfgang Engelmann wrote: On 23.07.19 17:35, Wolfgang Engelmann wrote: Its the second time today that lyx crashed suddenly. I was trying to insert a reference via jabref. I am including the lines from the terminal, perhaps it gives some clue of what happened. QEventLoop::exec(QFlags) ( 24) /usr/lib/x86_64-linux-gnu/libQtCore.so.4: QCoreApplication::exec() ( 25) lyx: lyx() [0xa4105f] ( 26) lyx: lyx() [0x63a617] ( 27) lyx: lyx() [0x43b973] ( 28) /lib/x86_64-linux-gnu/libc.so.6: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7f6cb8490830] ( 29) lyx: lyx() [0x43b859] Assertion triggered in void lyx::doAssertWithCallstack(bool) by failing check "false" in file lassert.cpp:44 Buffer.cpp (1601): /mnt/sdb/we/Publikationen-eigene-20170530/PBR-4thEdition/PBR-4thEdition-20190723-n.lyx.emergency We are missing the debug information, so it is a bit difficult to conclude. Is this a version of LyX that you compiled by yourself? p.s. I could recover the document from the emergency file Good news. p.p.s. I think, I tried to dissolve a note in a note, which led to the crash. Being able to reproduce the iddue would e the best. JMarc which means I should next time run lyx with -dbg, right? Or can I still find a file with error messages now? Wolfgang Wolfgang
Re: lyx crash 2.3.3.
Le 23/07/2019 à 17:45, Wolfgang Engelmann a écrit : On 23.07.19 17:38, Wolfgang Engelmann wrote: On 23.07.19 17:35, Wolfgang Engelmann wrote: Its the second time today that lyx crashed suddenly. I was trying to insert a reference via jabref. I am including the lines from the terminal, perhaps it gives some clue of what happened. QEventLoop::exec(QFlags) ( 24) /usr/lib/x86_64-linux-gnu/libQtCore.so.4: QCoreApplication::exec() ( 25) lyx: lyx() [0xa4105f] ( 26) lyx: lyx() [0x63a617] ( 27) lyx: lyx() [0x43b973] ( 28) /lib/x86_64-linux-gnu/libc.so.6: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7f6cb8490830] ( 29) lyx: lyx() [0x43b859] Assertion triggered in void lyx::doAssertWithCallstack(bool) by failing check "false" in file lassert.cpp:44 Buffer.cpp (1601): /mnt/sdb/we/Publikationen-eigene-20170530/PBR-4thEdition/PBR-4thEdition-20190723-n.lyx.emergency We are missing the debug information, so it is a bit difficult to conclude. Is this a version of LyX that you compiled by yourself? p.s. I could recover the document from the emergency file Good news. p.p.s. I think, I tried to dissolve a note in a note, which led to the crash. Being able to reproduce the iddue would e the best. JMarc
Re: lyx crash 2.3.3.
On 23.07.19 17:38, Wolfgang Engelmann wrote: On 23.07.19 17:35, Wolfgang Engelmann wrote: Its the second time today that lyx crashed suddenly. I was trying to insert a reference via jabref. I am including the lines from the terminal, perhaps it gives some clue of what happened. Wolfgang ] ( 8) lyx: lyx() [0xcb20c8] ( 9) /usr/lib/x86_64-linux-gnu/libQtCore.so.4: QMetaObject::activate(QObject*, QMetaObject const*, int, void**) ( 10) /usr/lib/x86_64-linux-gnu/libQtCore.so.4: QObject::event(QEvent*) ( 11) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: QApplicationPrivate::notify_helper(QObject*, QEvent*) ( 12) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: QApplication::notify(QObject*, QEvent*) ( 13) lyx: lyx() [0xa56ec0] ( 14) /usr/lib/x86_64-linux-gnu/libQtCore.so.4: QCoreApplication::notifyInternal(QObject*, QEvent*) ( 15) /usr/lib/x86_64-linux-gnu/libQtCore.so.4: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(+0x1bd6f0) [0x7f6cb95ed6f0] ( 16) /usr/lib/x86_64-linux-gnu/libQtCore.so.4: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(+0x1ba899) [0x7f6cb95ea899] ( 17) /lib/x86_64-linux-gnu/libglib-2.0.so.0: /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x2a7) [0x7f6cb7f9a197] ( 18) /lib/x86_64-linux-gnu/libglib-2.0.so.0: /lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x4a3f0) [0x7f6cb7f9a3f0] ( 19) /lib/x86_64-linux-gnu/libglib-2.0.so.0: /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_iteration+0x2c) [0x7f6cb7f9a49c] ( 20) /usr/lib/x86_64-linux-gnu/libQtCore.so.4: QEventDispatcherGlib::processEvents(QFlags) ( 21) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: /usr/lib/x86_64-linux-gnu/libQtGui.so.4(+0x272616) [0x7f6cb9b9a616] ( 22) /usr/lib/x86_64-linux-gnu/libQtCore.so.4: QEventLoop::processEvents(QFlags) ( 23) /usr/lib/x86_64-linux-gnu/libQtCore.so.4: QEventLoop::exec(QFlags) ( 24) /usr/lib/x86_64-linux-gnu/libQtCore.so.4: QCoreApplication::exec() ( 25) lyx: lyx() [0xa4105f] ( 26) lyx: lyx() [0x63a617] ( 27) lyx: lyx() [0x43b973] ( 28) /lib/x86_64-linux-gnu/libc.so.6: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7f6cb8490830] ( 29) lyx: lyx() [0x43b859] Assertion triggered in void lyx::doAssertWithCallstack(bool) by failing check "false" in file lassert.cpp:44 Buffer.cpp (1601): /mnt/sdb/we/Publikationen-eigene-20170530/PBR-4thEdition/PBR-4thEdition-20190723-n.lyx.emergency p.s. I could recover the document from the emergency file Wolfgang p.p.s. I think, I tried to dissolve a note in a note, which led to the crash. W.
Re: lyx crash 2.3.3.
On 23.07.19 17:35, Wolfgang Engelmann wrote: Its the second time today that lyx crashed suddenly. I was trying to insert a reference via jabref. I am including the lines from the terminal, perhaps it gives some clue of what happened. Wolfgang ] ( 8) lyx: lyx() [0xcb20c8] ( 9) /usr/lib/x86_64-linux-gnu/libQtCore.so.4: QMetaObject::activate(QObject*, QMetaObject const*, int, void**) ( 10) /usr/lib/x86_64-linux-gnu/libQtCore.so.4: QObject::event(QEvent*) ( 11) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: QApplicationPrivate::notify_helper(QObject*, QEvent*) ( 12) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: QApplication::notify(QObject*, QEvent*) ( 13) lyx: lyx() [0xa56ec0] ( 14) /usr/lib/x86_64-linux-gnu/libQtCore.so.4: QCoreApplication::notifyInternal(QObject*, QEvent*) ( 15) /usr/lib/x86_64-linux-gnu/libQtCore.so.4: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(+0x1bd6f0) [0x7f6cb95ed6f0] ( 16) /usr/lib/x86_64-linux-gnu/libQtCore.so.4: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(+0x1ba899) [0x7f6cb95ea899] ( 17) /lib/x86_64-linux-gnu/libglib-2.0.so.0: /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x2a7) [0x7f6cb7f9a197] ( 18) /lib/x86_64-linux-gnu/libglib-2.0.so.0: /lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x4a3f0) [0x7f6cb7f9a3f0] ( 19) /lib/x86_64-linux-gnu/libglib-2.0.so.0: /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_iteration+0x2c) [0x7f6cb7f9a49c] ( 20) /usr/lib/x86_64-linux-gnu/libQtCore.so.4: QEventDispatcherGlib::processEvents(QFlags) ( 21) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: /usr/lib/x86_64-linux-gnu/libQtGui.so.4(+0x272616) [0x7f6cb9b9a616] ( 22) /usr/lib/x86_64-linux-gnu/libQtCore.so.4: QEventLoop::processEvents(QFlags) ( 23) /usr/lib/x86_64-linux-gnu/libQtCore.so.4: QEventLoop::exec(QFlags) ( 24) /usr/lib/x86_64-linux-gnu/libQtCore.so.4: QCoreApplication::exec() ( 25) lyx: lyx() [0xa4105f] ( 26) lyx: lyx() [0x63a617] ( 27) lyx: lyx() [0x43b973] ( 28) /lib/x86_64-linux-gnu/libc.so.6: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7f6cb8490830] ( 29) lyx: lyx() [0x43b859] Assertion triggered in void lyx::doAssertWithCallstack(bool) by failing check "false" in file lassert.cpp:44 Buffer.cpp (1601): /mnt/sdb/we/Publikationen-eigene-20170530/PBR-4thEdition/PBR-4thEdition-20190723-n.lyx.emergency p.s. I could recover the document from the emergency file Wolfgang
