Re: Compiling causes LyX to crash [UPDATE]

[Dr Eberhard Lisse]

What I do for long documents is to split it by chapter into child
documents which (may) include a .tex file where I can do a lot of things
including conditionals.

I can then compile those also individually if I have an issue which then
makes "bisecting" it down to the error (or an MWE) easier.

greetings, el

On 2024-01-19 04:47 , Rich Shepard wrote:
[...]
> I'm done futzing with it. I'm using the PDF from last July (when it 
> was last compiled) and copying text into a new document. It's 
> compiling each time I complete a secion.
[...]

-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: Compiling causes LyX to crash [UPDATE]

[Rich Shepard]

On Thu, 18 Jan 2024, Steve Litt wrote:


Sure you can. Reduce it down to your own MWE, and then replace the English
with nonsense Latin. The only thing remaining that's proprietary to the
client is any commands or environments specific to the client.


SteveT,

I'm done futzing with it. I'm using the PDF from last July (when it was last
compiled) and copying text into a new document. It's compiling each time I
complete a secion.

Thanks,

Rich
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: Compiling causes LyX to crash [UPDATE]

[Steve Litt]

Rich Shepard said on Wed, 17 Jan 2024 11:32:48 -0800 (PST)

>On Wed, 17 Jan 2024, Rich Shepard wrote:
>
>> Modifying a fifth document I notice that a sub-section is not
>> numbered and while I can save it pressing ctrl-h to build it with
>> pdflatex causes a message box to appear saying I've hit a bug.  
>
>I corrected a couple of spelling errors in one of the other files,
>saved, and compiled it without error. This is a client document so I
>cannot make a MWE from it or share it with the world.

Sure you can. Reduce it down to your own MWE, and then replace the
English with nonsense Latin. The only thing remaining that's
proprietary to the client is any commands or environments specific to
the client.

SteveT

Steve Litt 

Autumn 2023 featured book: Rapid Learning for the 21st Century
http://www.troubleshooters.com/rl21
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: Compiling causes LyX to crash [UPDATE]

[Eberhard W Lisse]

This is not an MWE.

el

On 17/01/2024 23:12, Rich Shepard wrote:
> On Wed, 17 Jan 2024, Richard Kimberly Heck wrote:
[...]
> mwe.lyx (anonymized file) attached. So it the error message box. Clicking on
> the OK button kills LyX and removes all open tabs.
[...]

-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: Compiling causes LyX to crash [UPDATE]

[Richard Kimberly Heck]

On 1/17/24 16:12, Rich Shepard wrote:

On Wed, 17 Jan 2024, Richard Kimberly Heck wrote:

Given that 2.3.6-1 is quite old now, one would hope this did not 
crash is

more recent versions.


Riki,

Until I have a working Slackware64-15.0 host I rely on my -14.2 host.
LyX-2.3.6.1 has worked since it came out. Today it has no issues building
files other than the one, which built without problems a couple of months
ago before today's mods. (And I added those mods to two other files today
and they built with no issues.)


It is possible to anonymize the file. Open the minibuffer and type
"buffer-anonymize". Maybe first save it under a different filename! Does
it still crash?


mwe.lyx (anonymized file) attached. So it the error message box. 
Clicking on

the OK button kills LyX and removes all open tabs.

I've no idea where to start looking for why adding a bunch of text in 
this

file causes a crash.


With all the missing images and such, I can't actually compile it. But 
it doesn't crash in 2.4.0-RC1 when I try to do so, so that's a plus.


Riki


--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: Compiling causes LyX to crash [UPDATE]

[Richard Kimberly Heck]

On 1/17/24 14:32, Rich Shepard wrote:

On Wed, 17 Jan 2024, Rich Shepard wrote:

Modifying a fifth document I notice that a sub-section is not 
numbered and

while I can save it pressing ctrl-h to build it with pdflatex causes a
message box to appear saying I've hit a bug.


I corrected a couple of spelling errors in one of the other files, saved,
and compiled it without error. This is a client document so I cannot 
make a

MWE from it or share it with the world.


Given that 2.3.6-1 is quite old now, one would hope this did not crash 
is more recent versions.


It is possible to anonymize the file. Open the minibuffer and type 
"buffer-anonymize". Maybe first save it under a different filename! Does 
it still crash?


Riki


--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: Compiling causes LyX to crash [UPDATE]

[Rich Shepard]

On Wed, 17 Jan 2024, Rich Shepard wrote:


Modifying a fifth document I notice that a sub-section is not numbered and
while I can save it pressing ctrl-h to build it with pdflatex causes a
message box to appear saying I've hit a bug.


I corrected a couple of spelling errors in one of the other files, saved,
and compiled it without error. This is a client document so I cannot make a
MWE from it or share it with the world.

Regards,

Rich
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Compiling causes LyX to crash

[Rich Shepard]

Using lyx-2.3.6.1 I've worked today on four documents, saving and compiling
them with pdflatex. No problems, as usual.

Modifying a fifth document I notice that a sub-section is not numbered and
while I can save it pressing ctrl-h to build it with pdflatex causes a
message box to appear saying I've hit a bug. The message contains:
(  1) /usr/bin/lyx: /usr/bin/lyx() [0x981cd5]
(  2) /usr/bin/lyx: /usr/bin/lyx() [0x9f5032]
(  3) /usr/lib64/libQtCore.so.4: QObject::event(QEvent*)
(  4) /usr/lib64/libQtGui.so.4: QApplicationPrivate::notify_helper(QObject*, 
QEvent*)
(  5) /usr/lib64/libQtGui.so.4: QApplication::notify(QObject*, QEvent*)
(  6) /usr/bin/lyx: /usr/bin/lyx() [0x997386]
(  7) /usr/lib64/libQtCore.so.4: QCoreApplication::notifyInternal(QObject*, 
QEvent*)
(  8) /usr/lib64/libQtCore.so.4: 
QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*)
(  9) /usr/lib64/libQtCore.so.4: /usr/lib64/libQtCore.so.4(+0x1bef3e) 
[0x7fa06b936f3e]
( 10) /usr/lib64/libglib-2.0.so.0: 
/usr/lib64/libglib-2.0.so.0(g_main_context_dispatch+0x287) [0x7fa06d548787]
( 11) /usr/lib64/libglib-2.0.so.0: /usr/lib64/libglib-2.0.so.0(+0x489b8) 
[0x7fa06d5489b8]
( 12) /usr/lib64/libglib-2.0.so.0: 
/usr/lib64/libglib-2.0.so.0(g_main_context_iteration+0x2c) [0x7fa06d548a5c]
( 13) /usr/lib64/libQtCore.so.4: 
QEventDispatcherGlib::processEvents(QFlags)
( 14) /usr/lib64/libQtGui.so.4: /usr/lib64/libQtGui.so.4(+0x2a29e6) 
[0x7fa06bf149e6]
( 15) /usr/lib64/libQtCore.so.4: 
QEventLoop::processEvents(QFlags)
( 16) /usr/lib64/libQtCore.so.4: 
QEventLoop::exec(QFlags)
( 17) /usr/lib64/libQtCore.so.4: QCoreApplication::exec()
( 18) /usr/bin/lyx: /usr/bin/lyx() [0x5f667d]
( 19) /usr/bin/lyx: /usr/bin/lyx() [0x469816]
( 20) /lib64/libc.so.6: /lib64/libc.so.6(__libc_start_main+0xf0) 
[0x7fa06a5d97d0]
( 21) /usr/bin/lyx: /usr/bin/lyx() [0x475e89]

Not before with any LyX version have I encountered this. Help's needed!

TIA,

Rich
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: 2.4 crash report

[Jean-Marc Lasgouttes]

Le 12/03/2023 à 15:18, Wolfgang Engelmann a écrit :



Am 12.03.23 um 15:14 schrieb Jean-Marc Lasgouttes:

Le 12/03/2023 à 13:24, Wolfgang Engelmann a écrit :
did I send the correct infos? I am still not sure what I should do in 
case of a crash in gdb. Was 'where' helpful?


I did not find the output very useful, but it is probably not you fault.

Is the problem reproducible? What were you doing at the time of the 
freeze?


If you can reproduce, it would be nice to know whether you can obtain 
a different backtrace.


JMarc


whether you can obtain a
 > different backtrace.

you mean instead of using gdb?


Or rather in a different run. You say that LyX is frozen, does this mean 
that you have to abort it yourself?


Another possibility is to run LyX under a tool like valgrind (which 
detects memory errors before they cause crashes).


JMarc

--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: 2.4 crash report

[Wolfgang Engelmann]

Am 12.03.23 um 15:14 schrieb Jean-Marc Lasgouttes:

Le 12/03/2023 à 13:24, Wolfgang Engelmann a écrit :
did I send the correct infos? I am still not sure what I should do in 
case of a crash in gdb. Was 'where' helpful?


I did not find the output very useful, but it is probably not you fault.

Is the problem reproducible? What were you doing at the time of the freeze?

If you can reproduce, it would be nice to know whether you can obtain a 
different backtrace.


JMarc


whether you can obtain a
> different backtrace.

you mean instead of using gdb?

Wolfgang
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: 2.4 crash report

[Jean-Marc Lasgouttes]

Le 12/03/2023 à 13:24, Wolfgang Engelmann a écrit :
did I send the correct infos? I am still not sure what I should do in 
case of a crash in gdb. Was 'where' helpful?


I did not find the output very useful, but it is probably not you fault.

Is the problem reproducible? What were you doing at the time of the freeze?

If you can reproduce, it would be nice to know whether you can obtain a 
different backtrace.


JMarc
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: 2.4 crash report

[Wolfgang Engelmann]

Am 12.03.23 um 01:42 schrieb Richard Kimberly Heck:

On 3/11/23 08:05, Wolfgang Engelmann wrote:


This I got in the terminal
and in the gdb

Wolfgang
>>>

insets/InsetCommandParams.cpp (278): InsetCommand: Incompatible 
command name Standard.


That will lead to an assertion, at least. It also should not happen. 
"Standard" sounds like a layout name that has been somehow construed as 
an inset parameter.


Riki


did I send the correct infos? I am still not sure what I should do in 
case of a crash in gdb. Was 'where' helpful?


Wolfgang
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: 2.4 crash report

[Richard Kimberly Heck]

On 3/11/23 08:05, Wolfgang Engelmann wrote:


This I got in the terminal
and in the gdb

Wolfgang
>>>

insets/InsetCommandParams.cpp (278): InsetCommand: Incompatible 
command name Standard.


That will lead to an assertion, at least. It also should not happen. 
"Standard" sounds like a layout name that has been somehow construed as 
an inset parameter.


Riki


--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: 2.4 crash report

[Wolfgang Engelmann]

Am 11.03.23 um 13:31 schrieb José Matos:

On Sat, 2023-03-11 at 10:16 +0100, Wolfgang Engelmann wrote:

To whom should I report a 2.4.0 crash?
I use
Version 2.4.0-beta2 (Sonntag, 11. Dezember 2022)
Qt-Version (Laufzeit): 5.15.2 (Plattform: xcb)
Qt-Version (bei Erstellung): 5.15.2
OS-Version (bei Erstellung): Debian GNU/Linux 11 (bullseye)
Python-Aufruf: python3 -tt

and started the document with
   gdb lyx2.4.0
run

Symptom: The document was frozen, I got infos from the terminal which
I
could send on request

Wolfgang


What do you get when you "bt" that corresponds to backtrace.


where should I say bt?



Or it simply froze and there is no feedback?


yes, it was frozen, I had to stop the gdb


Best regards,


This I got in the terminal
and in the gdb

Wolfgang
>>>

insets/InsetCommandParams.cpp (278): InsetCommand: Incompatible command 
name Standard.

Warning: Befehl für Einfügung:

Inkompatibler Befehlsname.
[Thread 0x7fffc087d700 (LWP 5536) exited]
[Thread 0x7fff9f7fe700 (LWP 5535) exited]
[Thread 0x7fff9700 (LWP 5534) exited]
[Thread 0x7fff9e7fc700 (LWP 5533) exited]
Empty filename passed to function
Empty filename passed to function

##
[Thread 0x7fff9700 (LWP 5657) exited]

^C--Type  for more, q to quit, c to continue without paging--c

Thread 1 "lyx2.4.0" received signal SIGINT, Interrupt.
futex_wait_cancelable (private=0, expected=0, futex_word=0x7fffd488) 
at ../sysdeps/nptl/f
utex-internal.h:186 

186 ../sysdeps/nptl/futex-internal.h: Datei oder Verzeichnis nicht 
gefunden.

(gdb)

##

.
(gdb) where
#0  futex_wait_cancelable (private=0, expected=0, 
futex_word=0x7fffd488)

   at ../sysdeps/nptl/futex-internal.h:186
#1  __pthread_cond_wait_common
   (abstime=0x0, clockid=0, mutex=0x5633cc48, cond=0x7fffd460)
   at pthread_cond_wait.c:508
#2  __pthread_cond_wait (cond=0x7fffd460, mutex=0x5633cc48)
   at pthread_cond_wait.c:638
#3  0x73ed9edf in  () at /usr/lib/x86_64-linux-gnu/libxcb.so.1
#4  0x73edbd7f in  () at /usr/lib/x86_64-linux-gnu/libxcb.so.1
#5  0x73edbe91 in xcb_wait_for_reply () at 
/usr/lib/x86_64-linux-gnu/libxcb.so.1

#6  0x735c4eaa in QXcbConnection::sync() ()
   at /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#7  0x735dbea3 in  () at 
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#8  0x735dc2c0 in  () at 
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5

#9  0x77499abe in QBackingStore::beginPaint(QRegion const&) ()
   at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#10 0x779d36a2 in  () at 
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5

#11 0x77a036d7 in QWidget::event(QEvent*) ()
   at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
--Type  for more, q to quit, c to continue without paging--
##
]

^C--Type  for more, q to quit, c to continue without paging--c

Thread 1 "lyx2.4.0" received signal SIGINT, Interrupt.
futex_wait_cancelable (private=0, expected=0, futex_word=0x7fffd488) 
at ../sysdeps/nptl/f
utex-internal.h:186 

186 ../sysdeps/nptl/futex-internal.h: Datei oder Verzeichnis nicht 
gefunden.

(gdb) where
#0  futex_wait_cancelable (private=0, expected=0, 
futex_word=0x7fffd488)

   at ../sysdeps/nptl/futex-internal.h:186
#1  __pthread_cond_wait_common
   (abstime=0x0, clockid=0, mutex=0x5633cc48, cond=0x7fffd460)
   at pthread_cond_wait.c:508
#2  __pthread_cond_wait (cond=0x7fffd460, mutex=0x5633cc48)
   at pthread_cond_wait.c:638
#3  0x73ed9edf in  () at /usr/lib/x86_64-linux-gnu/libxcb.so.1
#4  0x73edbd7f in  () at /usr/lib/x86_64-linux-gnu/libxcb.so.1
#5  0x73edbe91 in xcb_wait_for_reply () at 
/usr/lib/x86_64-linux-gnu/libxcb.so.1

#6  0x735c4eaa in QXcbConnection::sync() ()
   at /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#7  0x735dbea3 in  () at 
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#8  0x735dc2c0 in  () at 
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5

#9  0x77499abe in QBackingStore::beginPaint(QRegion const&) ()
   at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#10 0x779d36a2 in  () at 
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5

#11 0x77a036d7 in QWidget::event(QEvent*) ()
   at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
--Type  for more, q to quit, c to continue without paging--c
#12 0x779c315f in QApplicationPrivate::notify_helper(QObject*, 
QEvent*) () at /usr/li
b/x86_64-linux-gnu/libQt5Widgets.so.5 

#13 0x55d984d9 in 
lyx::frontend::GuiApplication::notify(QObject*, QEvent*) (this=0x55
555631d390, receiver=, event=) at 
GuiApplication.cpp:2998
#14 0x76efefca in QCoreApplication::notifyInternal2(QObject*, 
QEvent*) () at /usr/lib
/x86_64-linux-gnu/libQt5Core.so.5 

#15 0x76f01a01 in 
QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadDat
a*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 


#16 0x76f56e93 in  () a

Re: 2.4 crash report

[José Matos]

On Sat, 2023-03-11 at 10:16 +0100, Wolfgang Engelmann wrote:
> To whom should I report a 2.4.0 crash?
> I use
> Version 2.4.0-beta2 (Sonntag, 11. Dezember 2022)
> Qt-Version (Laufzeit): 5.15.2 (Plattform: xcb)
> Qt-Version (bei Erstellung): 5.15.2
> OS-Version (bei Erstellung): Debian GNU/Linux 11 (bullseye)
> Python-Aufruf: python3 -tt
> 
> and started the document with
>   gdb lyx2.4.0
> run
> 
> Symptom: The document was frozen, I got infos from the terminal which
> I 
> could send on request
> 
> Wolfgang

What do you get when you "bt" that corresponds to backtrace.

Or it simply froze and there is no feedback?

Best regards,
-- 
José Abílio
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

2.4 crash report

[Wolfgang Engelmann]

To whom should I report a 2.4.0 crash?
I use
Version 2.4.0-beta2 (Sonntag, 11. Dezember 2022)
Qt-Version (Laufzeit): 5.15.2 (Plattform: xcb)
Qt-Version (bei Erstellung): 5.15.2
OS-Version (bei Erstellung): Debian GNU/Linux 11 (bullseye)
Python-Aufruf: python3 -tt

and started the document with
 gdb lyx2.4.0
run

Symptom: The document was frozen, I got infos from the terminal which I 
could send on request


Wolfgang
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: how to report crash recorded with gdb

[Richard Kimberly Heck]

On 2/25/23 09:01, Wolfgang Engelmann wrote:
I ran a lyx document under 2.4 which was started with gdb. It crashed 
and I do not know how to report it to the maintainers. 


You can either email the lyx-devel list or file a bug here:

https://www.lyx.org/trac/newticket

Riki


--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: how to report crash recorded with gdb

[Neal Becker]

"where" should give a traceback

On Sat, Feb 25, 2023, 9:01 AM Wolfgang Engelmann 
wrote:

> I ran a lyx document under 2.4 which was started with gdb. It crashed
> and I do not know how to report it to the maintainers. This is the
> terminal >
>
> text-user-interface -- TUI is the GDB text based interface.
> tracepoints -- Tracing of program execution without stopping the program.
> user-defined -- User-defined commands.
>
> Type "help" followed by a class name for a list of commands in
> that class.
> Type "help all" for the list of all commands.
> Type "help" followed by command name for full documentation.
> Type "apropos word" to search for commands related to "word".
> Type "apropos -v word" for full documentation
>   of commands related to "word".
> Command name abbreviations are allowed if unambiguous.
> (gdb) q
> A debugging session is active.
>
>  Inferior 1 [process 2797] will be killed.
>
> Quit anyway? (y or n) n
> Not confirmed.
> (gdb)
>
> It is still running, so if you or somebody else could tell me what to do
> to report it.
>
> Wolfgang
> --
> lyx-users mailing list
> lyx-users@lists.lyx.org
> http://lists.lyx.org/mailman/listinfo/lyx-users
>
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

how to report crash recorded with gdb

[Wolfgang Engelmann]

I ran a lyx document under 2.4 which was started with gdb. It crashed 
and I do not know how to report it to the maintainers. This is the 
terminal >


text-user-interface -- TUI is the GDB text based interface.
tracepoints -- Tracing of program execution without stopping the program.
user-defined -- User-defined commands.

Type "help" followed by a class name for a list of commands in
that class.
Type "help all" for the list of all commands.
Type "help" followed by command name for full documentation.
Type "apropos word" to search for commands related to "word".
Type "apropos -v word" for full documentation
 of commands related to "word".
Command name abbreviations are allowed if unambiguous.
(gdb) q
A debugging session is active.

Inferior 1 [process 2797] will be killed.

Quit anyway? (y or n) n
Not confirmed.
(gdb)

It is still running, so if you or somebody else could tell me what to do 
to report it.


Wolfgang
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: lyx 2.4.0 crash

[Jean-Marc Lasgouttes]

Le 06/02/2023 à 09:42, Wolfgang Engelmann a écrit :
By clicking on a figure in a lyx koma book document in order to see it 
it crashed with this message:


SIGSEGV-Signal empfangen!
Sie haben einen Fehler in LyX gefunden. Entschuldigung; hoffentlich 
haben Sie keine Daten verloren.
Bitte lesen Sie im LyX-Menü 'Hilfe->Einführung', wie man Fehler meldet, 
und erstellen Sie einen Fehlerbericht, falls notwendig. Vielen Dank!

Tschüs.


Hello,

Is the issue reproducible ? If this is the case, could you try to run 
LyX under gdb to have more information?


$gdb /path/to/lyx
(gdb) run
[...make LyX crash...]
(gdb) bt

JMarc


--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

lyx 2.4.0 crash

[Wolfgang Engelmann]

By clicking on a figure in a lyx koma book document in order to see it 
it crashed with this message:


SIGSEGV-Signal empfangen!
Sie haben einen Fehler in LyX gefunden. Entschuldigung; hoffentlich 
haben Sie keine Daten verloren.
Bitte lesen Sie im LyX-Menü 'Hilfe->Einführung', wie man Fehler meldet, 
und erstellen Sie einen Fehlerbericht, falls notwendig. Vielen Dank!

Tschüs.

SIGSEGV-Signal empfangen!
Sie haben einen Fehler in LyX gefunden. Entschuldigung; hoffentlich 
haben Sie keine Daten verloren.
Bitte lesen Sie im LyX-Menü 'Hilfe->Einführung', wie man Fehler meldet, 
und erstellen Sie einen Fehlerbericht, falls notwendig. Vielen Dank!

Tschüs.

You found an error in lyx:

(  1) lyx2.4.0: 
lyx::frontend::Alert::doError(std::__cxx11::basic_stringstd::char_traits, std::allocator > const&, 
std::__cxx11::basic_string, 
std::allocator > const&, bool)
(  2) lyx2.4.0: 
lyx::frontend::Alert::error(std::__cxx11::basic_stringstd::char_traits, std::allocator > const&, 
std::__cxx11::basic_string, 
std::allocator > const&, bool)

(  3) lyx2.4.0: lyx2.4.0(+0x48df07) [0x557275f6cf07]
(  4) /lib/x86_64-linux-gnu/libc.so.6: 
/lib/x86_64-linux-gnu/libc.so.6(+0x38d60) [0x7ff9355b0d60]

(  5) [0x5572924d20d0]: [0x5572924d20d0]


Wolfgang
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Lyx 2.3.6 crash on opening file

[Anirban Banerjee]

Hello,

I am facing an irritating Lyx crash on opening files (File->Open->Select
file from dialog->Click Open).
I am on Kubuntu 22.04 Jammy, updated to the latest recommended versions
of Qt libs etc.

This has been happening since I upgraded to Kubuntu 22.04 from 21.10.
The crash does not happen if I open the file from the command line or from
the file manager.

See below for the trace. Any insights would be helpful.

LyX 2.3.6 (2020-11-27)
Configuration
Host type:   x86_64-pc-linux-gnu
Special build flags:  build=release std-regex warnings use-enchant
Bundled libraries:   (none)
C++ Compiler:g++ (10.2.0)
C++ Compiler flags:   -Wall -Wextra -fPIC -O2 -std=c++14
 -Wno-deprecated-copy
C++ Compiler user flags:  -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++14  -g
-O2 -fdebug-prefix-map=/build/lyx-ufkcxK/lyx-2.3.6=.
-fstack-protector-strong -Wformat -Werror=format-security -fPIC
Linker flags:
Linker user flags:   -Wl,-z,defs -Wl,-Bsymbolic-functions -Wl,-z,relro
-Wl,-z,now
Qt Frontend:
Qt version:  5.15.2
Packaging:   posix
LyX binary dir:  /usr/bin
LyX files dir:   /usr/share/lyx


(  1) /usr/bin/lyx: /usr/bin/lyx(+0x63d1f8) [0x5642ea4741f8]
(  2) /usr/bin/lyx: /usr/bin/lyx(+0x63c652) [0x5642ea473652]
(  3) /usr/bin/lyx: /usr/bin/lyx(+0x2feb27) [0x5642ea135b27]
(  4) /lib/x86_64-linux-gnu/libc.so.6:
/lib/x86_64-linux-gnu/libc.so.6(+0x42520) [0x7f17937fc520]
(  5) /lib/x86_64-linux-gnu/libQt5Core.so.5:
QObjectPrivate::maybeSignalConnected(unsigned int) const
(  6) /lib/x86_64-linux-gnu/libQt5Core.so.5:
/lib/x86_64-linux-gnu/libQt5Core.so.5(+0x2f131f) [0x7f179400631f]
(  7) /usr/bin/lyx: /usr/bin/lyx(+0x6cfd53) [0x5642ea506d53]
(  8) /lib/x86_64-linux-gnu/libQt5Core.so.5:
/lib/x86_64-linux-gnu/libQt5Core.so.5(+0x2f17b8) [0x7f17940067b8]
(  9) /lib/x86_64-linux-gnu/libQt5Widgets.so.5: QAction::triggered(bool)
( 10) /lib/x86_64-linux-gnu/libQt5Widgets.so.5:
QAction::activate(QAction::ActionEvent)
( 11) /lib/x86_64-linux-gnu/libQt5Core.so.5: QObject::event(QEvent*)
( 12) /lib/x86_64-linux-gnu/libQt5Widgets.so.5:
QApplicationPrivate::notify_helper(QObject*, QEvent*)
( 13) /usr/bin/lyx: /usr/bin/lyx(+0x64edb0) [0x5642ea485db0]
( 14) /lib/x86_64-linux-gnu/libQt5Core.so.5:
QCoreApplication::notifyInternal2(QObject*, QEvent*)
( 15) /lib/x86_64-linux-gnu/libQt5Core.so.5:
QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*)
( 16) /lib/x86_64-linux-gnu/libQt5Core.so.5:
/lib/x86_64-linux-gnu/libQt5Core.so.5(+0x313a57) [0x7f1794028a57]
( 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+0x26b)
[0x7f17936ccd1b]
( 18) /lib/x86_64-linux-gnu/libglib-2.0.so.0:
/lib/x86_64-linux-gnu/libglib-2.0.so.0(+0xaa6f8) [0x7f17937216f8]
( 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+0x33)
[0x7f17936ca3c3]
( 20) /lib/x86_64-linux-gnu/libQt5Core.so.5:
QEventDispatcherGlib::processEvents(QFlags)
( 21) /lib/x86_64-linux-gnu/libQt5Core.so.5:
QEventLoop::exec(QFlags)
( 22) /lib/x86_64-linux-gnu/libQt5Core.so.5: QCoreApplication::exec()
( 23) /usr/bin/lyx: /usr/bin/lyx(+0x307c0d) [0x5642ea13ec0d]
( 24) /usr/bin/lyx: /usr/bin/lyx(+0x1a3939) [0x5642e9fda939]
( 25) /lib/x86_64-linux-gnu/libc.so.6:
/lib/x86_64-linux-gnu/libc.so.6(+0x29d90) [0x7f17937e3d90]
( 26) /lib/x86_64-linux-gnu/libc.so.6:
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x80) [0x7f17937e3e40]
( 27) /usr/bin/lyx: /usr/bin/lyx(+0x1af63e) [0x5642e9fe663e]



Thank you

Anirban
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

lyx crash on latex export

[Neal Becker]

I get a repeatable crash on latex export.  Quite unfortunate since
that's the only way to debug latex errors.

Error: Software exception Detected

LyX has caught an exception, it will now attempt to save all unsaved
documents and exit.

Exception: std::exception
Buffer.cpp (1601):   /home/nbecker/itri_sls/vtc2020.lyx.emergency
KCrash: Application 'lyx' crashing...
KCrash: Attempting to start /usr/libexec/drkonqi from kdeinit
sock_file=/run/user/1000/kdeinit5__0
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: lyx crash 2.3.3.

[Dr Eberhard Lisse]

-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.

[Pavel Sanda]

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.

[Jean-Marc Lasgouttes]

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.

[Kornel Benko]

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.

[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

Re: lyx crash 2.3.3.

[Jean-Marc Lasgouttes]

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.

[Wolfgang Engelmann]

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.

[Jean-Marc Lasgouttes]

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.

[Wolfgang Engelmann]

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.

[Jean-Marc Lasgouttes]

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.

[Wolfgang Engelmann]

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.

[Wolfgang Engelmann]

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

lyx crash 2.3.3.

[Wolfgang Engelmann]

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

Re: crash

[Jean-Marc Lasgouttes]

Le 19/01/2019 à 11:18, Patrick Dupre a écrit :

How can I "buffer-anonymize"?


Type Alt-x, and then type "buffer-anonimize" and return.

JMarc

Re: crash

[Patrick Dupre]

Hello,

 

You are right.

Today the same file does not generate a crash!

In the mind time, I just reboot the computer.

Random behaviors are just difficult to debug.

 

How can I "buffer-anonymize"?

 

Linux Teucidide 4.19.15-200.fc28.x86_64 #1 SMP Mon Jan 14 17:06:39 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

lyx-2.3.2-1.fc28.x86_64

 

Thank.

 

===
Patrick DUPRÉ | | email: pdu...@gmx.com
===

 
 

Sent: Saturday, January 19, 2019 at 12:55 AM
From: "John White" 
To: lyx-users@lists.lyx.org
Cc: "Patrick Dupre" , "Scott Kostyshak" 
Subject: Re: crash



 

 

On Friday, January 18, 2019 10:22:55 PM PST Patrick Dupre wrote:

> Hello,

>

> Yes, you are right. I did not response to the mentioned message

> because I did not understand the point.

> Now, I cannot give you the previous lyx file, it is too long, too sensitive

> and it has a lot of pictures that I cannot communicate.

> I expect that the attached file will be more helpful.

> It just crashes when I try to open the inlet

> (before it was when I run the spellchecker).

>

> For me, all these crashes seem due to a memory leak.

>

> Best.

> \> ===

> Patrick DUPRÉ | | email: pdu...@gmx.com

> ===

>

> > Sent: Friday, January 18, 2019 at 9:44 PM

> > From: "Scott Kostyshak" 

> > To: lyx-users@lists.lyx.org

> > Subject: Re: crash

> >

> > On Fri, Jan 18, 2019 at 09:30:02PM +0100, Patrick Dupre wrote:

> > > Hello,

> > >

> > > Where are you with the crash report that I submitted in December?

> > > Actually, I can also crash lyx by using trhe option "go to label"

> > > when I click on a figure reference.

> >

> > Hi Patrick,

> >

> > In the furture can you please respond to the relevant email thread or if

> > it is a trac ticket, please post on trac? We get lots of emails (and

> > unfortunately, several mysterious crashes) and I personally have a

> > horrible memory, so keeping things organized helps out a lot.

> >

> > I think I found the crash you're referring to. For anyone who is

> >

> > curious, see here:

> > https://www.mail-archive.com/search?l=mid=trinity-4267d203-5264-439d-8

> > 4e6-c54806590235-1541597713075%403c-app-mailcom-bs04>

> > Also, it seems you might have missed a question asked by Jean-Marc in

> >

> > that email thread. The question was the following:

> > Is it enough to obfuscate it with "buffer-anonymize"?

> >

> > The reason why this question is so important is that it would really

> > help us to have a minimal example file. Without an example file, it is

> > quite difficult to track down the problem since we can't reproduce it.

> > If you're not sure what "buffer-anonymize" is, please let us know and we

> > can give you instructions for how to use it.

> >

> > Thanks for following up on this important issue. Hopefully we can figure

> > out the crash.

> >

> > Best,

> >

> > Scott

 

It doesn't crash on 2.3.0 debian linux.

 

John

 

Re: crash

[Scott Kostyshak]

On Fri, Jan 18, 2019 at 10:22:55PM +0100, Patrick Dupre wrote:
> Hello,
> 
> Yes, you are right. I did not response to the mentioned message
> because I did not understand the point.
> Now, I cannot give you the previous lyx file, it is too long, too sensitive
> and it has a lot of pictures that I cannot communicate.

I see, thanks for the explanation. buffer-anonymize basically replaces
all of your characters with the character "a", in order to remove the
sensitive information. Are the pictures necessary to reproduce the
problem?

> I expect that the attached file will be more helpful.
> It just crashes when I try to open the inlet
> (before it was when I run the spellchecker).

Strange. It does not crash for me with LyX 2.3.x. Does it matter whether
you have continuous spell-checking enabled or not?

> For me, all these crashes seem due to a memory leak.

What makes you think that? I know little about these low-level issues so
I'm always trying to learn more intuition. If it is indeed due to a
memory link, perhaps Valgrind would be helpful?

Scott


signature.asc
Description: PGP signature

Re: crash

[John White]

On Friday, January 18, 2019 10:22:55 PM PST Patrick Dupre wrote:
> Hello,
> 
> Yes, you are right. I did not response to the mentioned message
> because I did not understand the point.
> Now, I cannot give you the previous lyx file, it is too long, too sensitive
> and it has a lot of pictures that I cannot communicate.
> I expect that the attached file will be more helpful.
> It just crashes when I try to open the inlet
> (before it was when I run the spellchecker).
> 
> For me, all these crashes seem due to a memory leak.
> 
> Best.
> \> 
=
==
>  Patrick DUPRÉ | | email: pdu...@gmx.com
> 
=
==
> 
> > Sent: Friday, January 18, 2019 at 9:44 PM
> > From: "Scott Kostyshak" 
> > To: lyx-users@lists.lyx.org
> > Subject: Re: crash
> > 
> > On Fri, Jan 18, 2019 at 09:30:02PM +0100, Patrick Dupre wrote:
> > > Hello,
> > > 
> > > Where are you with the crash report that I submitted in December?
> > > Actually, I can also crash lyx by using trhe option "go to label"
> > > when I click on a figure reference.
> > 
> > Hi Patrick,
> > 
> > In the furture can you please respond to the relevant email thread or if
> > it is a trac ticket, please post on trac? We get lots of emails (and
> > unfortunately, several mysterious crashes) and I personally have a
> > horrible memory, so keeping things organized helps out a lot.
> > 
> > I think I found the crash you're referring to. For anyone who is
> > 
> > curious, see here:
> >   https://www.mail-archive.com/search?l=mid=trinity-4267d203-5264-439d-8
> >   4e6-c54806590235-1541597713075%403c-app-mailcom-bs04> 
> > Also, it seems you might have missed a question asked by Jean-Marc in
> > 
> > that email thread. The question was the following:
> >   Is it enough to obfuscate it with "buffer-anonymize"?
> > 
> > The reason why this question is so important is that it would really
> > help us to have a minimal example file. Without an example file, it is
> > quite difficult to track down the problem since we can't reproduce it.
> > If you're not sure what "buffer-anonymize" is, please let us know and we
> > can give you instructions for how to use it.
> > 
> > Thanks for following up on this important issue. Hopefully we can figure
> > out the crash.
> > 
> > Best,
> > 
> > Scott

It doesn't crash on 2.3.0 debian linux.

John

Re: crash

[Patrick Dupre]

Hello,

Yes, you are right. I did not response to the mentioned message
because I did not understand the point.
Now, I cannot give you the previous lyx file, it is too long, too sensitive
and it has a lot of pictures that I cannot communicate.
I expect that the attached file will be more helpful.
It just crashes when I try to open the inlet
(before it was when I run the spellchecker).

For me, all these crashes seem due to a memory leak.

Best.

===
 Patrick DUPRÉ | | email: pdu...@gmx.com
===


> Sent: Friday, January 18, 2019 at 9:44 PM
> From: "Scott Kostyshak" 
> To: lyx-users@lists.lyx.org
> Subject: Re: crash
>
> On Fri, Jan 18, 2019 at 09:30:02PM +0100, Patrick Dupre wrote:
> > Hello,
> > 
> > Where are you with the crash report that I submitted in December?
> > Actually, I can also crash lyx by using trhe option "go to label"
> > when I click on a figure reference.
> 
> Hi Patrick,
> 
> In the furture can you please respond to the relevant email thread or if
> it is a trac ticket, please post on trac? We get lots of emails (and
> unfortunately, several mysterious crashes) and I personally have a
> horrible memory, so keeping things organized helps out a lot.
> 
> I think I found the crash you're referring to. For anyone who is
> curious, see here:
> 
>   
> https://www.mail-archive.com/search?l=mid=trinity-4267d203-5264-439d-84e6-c54806590235-1541597713075%403c-app-mailcom-bs04
> 
> Also, it seems you might have missed a question asked by Jean-Marc in
> that email thread. The question was the following:
> 
>   Is it enough to obfuscate it with "buffer-anonymize"?
> 
> The reason why this question is so important is that it would really
> help us to have a minimal example file. Without an example file, it is
> quite difficult to track down the problem since we can't reproduce it.
> If you're not sure what "buffer-anonymize" is, please let us know and we
> can give you instructions for how to use it.
> 
> Thanks for following up on this important issue. Hopefully we can figure
> out the crash.
> 
> Best,
> 
> Scott
>

crash.lyx
Description: application/lyx

Re: crash

[Patrick Dupre]

This code crash immediately when I try to open the inlet.

===
 Patrick DUPRÉ | | email: pdu...@gmx.com
===


> Sent: Friday, January 18, 2019 at 9:30 PM
> From: "Patrick Dupre" 
> To: lyx 
> Subject: crash
>
> Hello,
> 
> Where are you with the crash report that I submitted in December?
> Actually, I can also crash lyx by using trhe option "go to label"
> when I click on a figure reference.
> 
> ===
>  Patrick DUPRÉ | | email: pdu...@gmx.com
> ===
>

crash.lyx
Description: application/lyx

Re: crash

[Scott Kostyshak]

On Fri, Jan 18, 2019 at 09:30:02PM +0100, Patrick Dupre wrote:
> Hello,
> 
> Where are you with the crash report that I submitted in December?
> Actually, I can also crash lyx by using trhe option "go to label"
> when I click on a figure reference.

Hi Patrick,

In the furture can you please respond to the relevant email thread or if
it is a trac ticket, please post on trac? We get lots of emails (and
unfortunately, several mysterious crashes) and I personally have a
horrible memory, so keeping things organized helps out a lot.

I think I found the crash you're referring to. For anyone who is
curious, see here:

  
https://www.mail-archive.com/search?l=mid=trinity-4267d203-5264-439d-84e6-c54806590235-1541597713075%403c-app-mailcom-bs04

Also, it seems you might have missed a question asked by Jean-Marc in
that email thread. The question was the following:

  Is it enough to obfuscate it with "buffer-anonymize"?

The reason why this question is so important is that it would really
help us to have a minimal example file. Without an example file, it is
quite difficult to track down the problem since we can't reproduce it.
If you're not sure what "buffer-anonymize" is, please let us know and we
can give you instructions for how to use it.

Thanks for following up on this important issue. Hopefully we can figure
out the crash.

Best,

Scott


signature.asc
Description: PGP signature

crash

[Patrick Dupre]

Hello,

Where are you with the crash report that I submitted in December?
Actually, I can also crash lyx by using trhe option "go to label"
when I click on a figure reference.

===
 Patrick DUPRÉ | | email: pdu...@gmx.com
===

Re: crash when spell checking

[José Abílio Matos]

On Tuesday, 4 December 2018 07.10.53 WET Patrick Dupre wrote:
> Hello,
> 
> I do not understand why lyx crashes when I run the spell checker.
> Then it crashes every time that I try to reload it!!!
> It is a BEARMER document.
> Unfortunately, it is not a document that I can broadcast, and I am in
> rush.
> 
> fedora 28,

Hi Patrick,
have you been able to fix this issue?

Regards,
-- 
José Abílio

Re: crash when spell checking

[Paul A. Rubin]

On 12/4/18 2:10 AM, Patrick Dupre wrote:

Hello,

I do not understand why lyx crashes when I run the spell checker.
Then it crashes every time that I try to reload it!!!
It is a BEARMER document.
Unfortunately, it is not a document that I can broadcast, and I am in
rush.

fedora 28,
===
  Patrick DUPRÉ | | email: pdu...@gmx.com
  Laboratoire de Physico-Chimie de l'Atmosphère | |
  Université du Littoral-Côte d'Opale   | |
  Tel.  (33)-(0)3 28 23 76 12   | | Fax: 03 28 65 82 44
  189A, avenue Maurice Schumann | | 59140 Dunkerque, France
===
This is a bit of a shot in the dark, but you can try the following. Move 
your ~/.lyx directory someplace (as a backup), then start LyX, 
reconfigure, and restart LyX. See if that lets you load the beamer 
document safely.


Paul

crash when spell checking

[Patrick Dupre]

Hello,

I do not understand why lyx crashes when I run the spell checker.
Then it crashes every time that I try to reload it!!!
It is a BEARMER document.
Unfortunately, it is not a document that I can broadcast, and I am in
rush.

fedora 28,
===
 Patrick DUPRÉ | | email: pdu...@gmx.com
 Laboratoire de Physico-Chimie de l'Atmosphère | |
 Université du Littoral-Côte d'Opale   | |
 Tel.  (33)-(0)3 28 23 76 12   | | Fax: 03 28 65 82 44
 189A, avenue Maurice Schumann | | 59140 Dunkerque, France
===

Re: Crash

[Jürgen Spitzmüller]

Am Freitag, den 13.10.2017, 11:59 +0200 schrieb Patrick Dupre:
> When I open the file Formalism_NL_v8.lyx, after I have
> open the file Formalism_FM_0.lyx,
> lyx crashes.
> It does not crash if,
> 1) I reverse the order of opening
> 2) I change the name of the file causing the crash.

It will be impossible to debug this without either a backtrace or a set
of minimal example files with which we can generate a backtrace
ourselves. You can also send the original files to a developer by
private mail if you fail to construct a minimal example file and do not
want to publicly post your documents.

Jürgen

signature.asc
Description: This is a digitally signed message part

Crash

[Patrick Dupre]

Hello,

When I open the file Formalism_NL_v8.lyx, after I have
open the file Formalism_FM_0.lyx,
lyx crashes.
It does not crash if,
1) I reverse the order of opening
2) I change the name of the file causing the crash.

It there something wrong it the session file,

Thank.

## Automatically generated lyx session file 
## Editing this file manually may cause lyx to crash.

[recent files]
/home/pdupre/Reviews/Tittel/pd.lyx
/home/pdupre/publications/Formalism_FM/Formalism_FM_0.lyx
/home/pdupre/publications/Formalism_NL/Formalism_NL_v8.lyx
/home/pdupre/Sacher/addon.lyx
/home/pdupre/publications/Help/FT.lyx
/home/pdupre/publications/Formalism_NL/Formalism_NL_v4.lyx
/home/pdupre/H2_Isot/Notes.lyx
/home/pdupre/publications/Saturation/Saturation.lyx
/home/pdupre/Spectroscopy/Notes/Absorption.lyx
/home/pdupre/NICE-OHMS/Notes.lyx
/home/pdupre/NICE-OHMS/Noise.lyx
/home/pdupre/NICE-OHMS/Chi_NL.lyx
/home/pdupre/publications/Quadrupole/Quadrupole.lyx
/home/pdupre/Amsterdam/Collaboration/MSCA/MSCA_2017_v2.lyx
/home/pdupre/Talks/Lille_2017.lyx
/home/pdupre/Amsterdam/Collaboration/MSCA/CV.lyx
/home/pdupre/Amsterdam/Collaboration/MSCA/MSCA_2017_v1.lyx
/home/pdupre/Amsterdam/Collaboration/MSCA/MSCA_2017_summary.lyx
/home/pdupre/Amsterdam/Collaboration/MSCA/MSCA_2017.lyx

[last opened files]
1, /home/pdupre/publications/Formalism_NL/Formalism_NL_v8.lyx

[cursor positions]
175, 1, /home/pdupre/Amsterdam/Collaboration/ANR-DFG_2017/Talk_LPCA.lyx
19, 1429, /home/pdupre/Amsterdam/Collaboration/ANR_2017_v10.lyx
81, 55, /home/pdupre/Amsterdam/Collaboration/MSCA/CV.lyx
17, 49, /home/pdupre/Amsterdam/Collaboration/MSCA/MSCA_2017.lyx
3, 323, /home/pdupre/Amsterdam/Collaboration/MSCA/MSCA_2017_summary.lyx
164, 158, /home/pdupre/Amsterdam/Collaboration/MSCA/MSCA_2017_v1.lyx
177, 88, /home/pdupre/Amsterdam/Collaboration/MSCA/MSCA_2017_v2.lyx
5, 92, /home/pdupre/CNRS/Lambrecht_August2017.lyx
300, 1, /home/pdupre/H2_Isot/Notes.lyx
0, 0, /home/pdupre/NICE-OHMS/Chi_NL.lyx
0, 0, /home/pdupre/NICE-OHMS/Noise.lyx
0, 0, /home/pdupre/NICE-OHMS/Notes.lyx
35, 141, /home/pdupre/Reviews/Tittel/pd.lyx
3, 4, /home/pdupre/Sacher/addon.lyx
1, 7, /home/pdupre/Spectroscopy/Notes/Absorption.lyx
126, 28, /home/pdupre/Talks/Lille_2017.lyx
271, 0, /home/pdupre/Talks/Paris_2017.lyx
148, 24, /home/pdupre/publications/Formalism_FM/Formalism_FM_0.lyx
6, 861, /home/pdupre/publications/Formalism_NL/Comment_to_reviewer.lyx
41, 110, /home/pdupre/publications/Formalism_NL/Formalism_NL_v4.lyx
188, 0, /home/pdupre/publications/Formalism_NL/Formalism_NL_v8.lyx
64, 0, /home/pdupre/publications/Help/FT.lyx
11, 0, /home/pdupre/publications/Quadrupole/Quadrupole.lyx
41, 0, /home/pdupre/publications/Saturation/Saturation.lyx
518, 199, /usr/share/lyx/doc/Math.lyx
0, 0, /usr/share/lyx/examples/splash.lyx

[last commands]

[bookmarks]


===
 Patrick DUPRÉ | | email: pdu...@gmx.com
 Laboratoire de Physico-Chimie de l'Atmosphère | |
 Université du Littoral-Côte d'Opale   | |
 Tel.  (33)-(0)3 28 23 76 12   | | Fax: 03 28 65 82 44
 189A, avenue Maurice Schumann | | 59140 Dunkerque, France
===

Re: Is this crash a bug?

[Steve Hnizdur]

Bug filed

On 05/10/17 14:14, Jürgen Spitzmüller wrote:
2017-10-05 15:09 GMT+02:00 Joel Kulesza >:


On Thu, Oct 5, 2017 at 6:01 AM, Steve Hnizdur > wrote:

Is this local to me? Any thoughts.


I can reproduce on LyX 2.2.3 on OS X 10.11.6.


And with both LyX 2.2.4dev and 2.3dev.

Please file a bug report.

Jürgen



--

Steve Hnizdur

Re: Is this crash a bug?

[Jürgen Spitzmüller]

2017-10-05 15:09 GMT+02:00 Joel Kulesza :

> On Thu, Oct 5, 2017 at 6:01 AM, Steve Hnizdur  wrote:
>
>> Is this local to me? Any thoughts.
>
>
> I can reproduce on LyX 2.2.3 on OS X 10.11.6.
>

And with both LyX 2.2.4dev and 2.3dev.

Please file a bug report.

Jürgen

Re: Is this crash a bug?

[Joel Kulesza]

On Thu, Oct 5, 2017 at 6:01 AM, Steve Hnizdur  wrote:

> Is this local to me? Any thoughts.


I can reproduce on LyX 2.2.3 on OS X 10.11.6.

Re: Is this crash a bug?

[Paul A. Rubin]

On 10/05/2017 08:01 AM, Steve Hnizdur wrote:

Hi

I create a new document (standard article will do) and enter math 
input mode. I then enter \xx followed by left cursor arrow, I then 
move the cursor to between the two x's enter \ and then the right 
cursor. This then gives me (without the asterisks)




Assertion false violated in
file: ../../src/CoordCache.cpp, line: 31
There has been an error with this document.
LyX will attempt to close it safely.
LyX: Attempting to save document newfile1.lyx
  Saved to /home/steve/newfile1.lyx.emergency. Phew.

The current document was closed.

*

Is this local to me? Any thoughts.


It's not local to you. I just reproduced it here (Linux Mint 18.2, LyX 
2.2.3) with exactly the same error message. I would suggest searching 
the bug tracker for "CoordCache", to see if there's already a bug for 
it, and filing one if not.


Paul

Is this crash a bug?

[Steve Hnizdur]

Hi

I create a new document (standard article will do) and enter math input 
mode. I then enter \xx followed by left cursor arrow, I then move the 
cursor to between the two x's enter \ and then the right cursor. This 
then gives me (without the asterisks)




Assertion false violated in
file: ../../src/CoordCache.cpp, line: 31
There has been an error with this document.
LyX will attempt to close it safely.
LyX: Attempting to save document newfile1.lyx
  Saved to /home/steve/newfile1.lyx.emergency. Phew.

The current document was closed.

*

Is this local to me? Any thoughts.
--

Steve Hnizdur

Re: crash

[Richard Heck]

On 07/28/2017 04:57 PM, Patrick Dupre wrote:
> I still have this issue with version 2.2.3 (on fedora 26)

Unfortunately, this sort of crash report doesn't help us. With debug
symbols activated, we can't really tell anything from this backtrace. If
you could compile 2.2.3 yourself, and activate debug symbols, then that
would give us a much more useful crash report. Please also let us know
what you were doing when the crash occurred. It'd be even better if you
could figure out how reproduce it in a reliable way.

Richard


> (  1) lyx: lyx(+0x56d8dc) [0x560f21dbd8dc]
> (  2) lyx: lyx(+0x5d0ea6) [0x560f21e20ea6]
> (  3) lyx: lyx(+0x56c68e) [0x560f21dbc68e]
> (  4) lyx: lyx(+0x25ee38) [0x560f21aaee38]
> (  5) /lib64/libc.so.6: /lib64/libc.so.6(+0x366f0) [0x7f65176c06f0]
> (  6) lyx: lyx(+0x318fa6) [0x560f21b68fa6]
> (  7) lyx: lyx(+0x31a068) [0x560f21b6a068]
> (  8) lyx: lyx(+0x5465be) [0x560f21d965be]
> (  9) lyx: lyx(+0x488968) [0x560f21cd8968]
> ( 10) lyx: lyx(+0x318db0) [0x560f21b68db0]
> ( 11) lyx: lyx(+0x360ab0) [0x560f21bb0ab0]
> ( 12) lyx: lyx(+0x5c7f68) [0x560f21e17f68]
> ( 13) lyx: lyx(+0x5c3de1) [0x560f21e13de1]
> ( 14) /lib64/libQt5Core.so.5: QMetaObject::activate(QObject*, int, int, 
> void**)
> ( 15) /lib64/libQt5Widgets.so.5: QTabWidget::currentChanged(int)
> ( 16) /lib64/libQt5Widgets.so.5: /lib64/libQt5Widgets.so.5(+0x2f4e27) 
> [0x7f651915be27]
> ( 17) /lib64/libQt5Core.so.5: QMetaObject::activate(QObject*, int, int, 
> void**)
> ( 18) /lib64/libQt5Widgets.so.5: QTabBar::currentChanged(int)
> ( 19) /lib64/libQt5Widgets.so.5: QTabBar::setCurrentIndex(int)
> ( 20) lyx: lyx(+0x5c3f67) [0x560f21e13f67]
> ( 21) lyx: lyx(+0x5a10a7) [0x560f21df10a7]
> ( 22) lyx: lyx(+0x5a170f) [0x560f21df170f]
> ( 23) lyx: lyx(+0x5a1908) [0x560f21df1908]
> ( 24) lyx: lyx(+0x5a34e9) [0x560f21df34e9]
> ( 25) lyx: lyx(+0x57c2c7) [0x560f21dcc2c7]
> ( 26) lyx: lyx(+0x573ce0) [0x560f21dc3ce0]
> ( 27) lyx: lyx(+0x5feafd) [0x560f21e4eafd]
> ( 28) /lib64/libQt5Core.so.5: QMetaObject::activate(QObject*, int, int, 
> void**)
> ( 29) /lib64/libQt5Widgets.so.5: QAction::triggered(bool)
> ( 30) /lib64/libQt5Widgets.so.5: QAction::activate(QAction::ActionEvent)
> ( 31) /lib64/libQt5Widgets.so.5: /lib64/libQt5Widgets.so.5(+0x2c0424) 
> [0x7f6519127424]
> ( 32) /lib64/libQt5Widgets.so.5: /lib64/libQt5Widgets.so.5(+0x2c7e8b) 
> [0x7f651912ee8b]
> ( 33) /lib64/libQt5Widgets.so.5: QMenu::mouseReleaseEvent(QMouseEvent*)
> ( 34) /lib64/libQt5Widgets.so.5: QWidget::event(QEvent*)
> ( 35) /lib64/libQt5Widgets.so.5: QMenu::event(QEvent*)
> ( 36) /lib64/libQt5Widgets.so.5: QApplicationPrivate::notify_helper(QObject*, 
> QEvent*)
> ( 37) /lib64/libQt5Widgets.so.5: QApplication::notify(QObject*, QEvent*)
> ( 38) lyx: lyx(+0x57e3aa) [0x560f21dce3aa]
> ( 39) /lib64/libQt5Core.so.5: QCoreApplication::notifyInternal2(QObject*, 
> QEvent*)
> ( 40) /lib64/libQt5Widgets.so.5: 
> QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, 
> QWidget*, QWidget**, QPointer&, bool)
> ( 41) /lib64/libQt5Widgets.so.5: /lib64/libQt5Widgets.so.5(+0x1bc073) 
> [0x7f6519023073]
> ( 42) /lib64/libQt5Widgets.so.5: /lib64/libQt5Widgets.so.5(+0x1bea64) 
> [0x7f6519025a64]
> ( 43) /lib64/libQt5Widgets.so.5: QApplicationPrivate::notify_helper(QObject*, 
> QEvent*)
> ( 44) /lib64/libQt5Widgets.so.5: QApplication::notify(QObject*, QEvent*)
> ( 45) lyx: lyx(+0x57e3aa) [0x560f21dce3aa]
> ( 46) /lib64/libQt5Core.so.5: QCoreApplication::notifyInternal2(QObject*, 
> QEvent*)
> ( 47) /lib64/libQt5Gui.so.5: 
> QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*)
> ( 48) /lib64/libQt5Gui.so.5: 
> QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*)
> ( 49) /lib64/libQt5Gui.so.5: 
> QWindowSystemInterface::sendWindowSystemEvents(QFlags)
> ( 50) /lib64/libQt5XcbQpa.so.5: /lib64/libQt5XcbQpa.so.5(+0x6e7a0) 
> [0x7f650a2667a0]
> ( 51) /lib64/libglib-2.0.so.0: 
> /lib64/libglib-2.0.so.0(g_main_context_dispatch+0x157) [0x7f6519bd8247]
> ( 52) /lib64/libglib-2.0.so.0: /lib64/libglib-2.0.so.0(+0x4a5e8) 
> [0x7f6519bd85e8]
> ( 53) /lib64/libglib-2.0.so.0: 
> /lib64/libglib-2.0.so.0(g_main_context_iteration+0x2c) [0x7f6519bd867c]
> ( 54) /lib64/libQt5Core.so.5: 
> QEventDispatcherGlib::processEvents(QFlags)
> ( 55) /lib64/libQt5Core.so.5: 
> QEventLoop::exec(QFlags)
> ( 56) /lib64/libQt5Core.so.5: QCoreApplication::exec()
> ( 57) lyx: lyx(+0x266ed5) [0x560f21ab6ed5]
> ( 58) lyx: lyx(+0x11be66) [0x560f2196be66]
> ( 59) /lib64/libc.so.6: /lib64/libc.so.6(__libc_start_main+0xea) 
> [0x7f65176aa4da]
> ( 60) lyx: lyx(+0x12491a) [0x560f2197491a]
>
>
> ===
>  Pat

crash

[Patrick Dupre]

I still have this issue with version 2.2.3 (on fedora 26)



(  1) lyx: lyx(+0x56d8dc) [0x560f21dbd8dc]
(  2) lyx: lyx(+0x5d0ea6) [0x560f21e20ea6]
(  3) lyx: lyx(+0x56c68e) [0x560f21dbc68e]
(  4) lyx: lyx(+0x25ee38) [0x560f21aaee38]
(  5) /lib64/libc.so.6: /lib64/libc.so.6(+0x366f0) [0x7f65176c06f0]
(  6) lyx: lyx(+0x318fa6) [0x560f21b68fa6]
(  7) lyx: lyx(+0x31a068) [0x560f21b6a068]
(  8) lyx: lyx(+0x5465be) [0x560f21d965be]
(  9) lyx: lyx(+0x488968) [0x560f21cd8968]
( 10) lyx: lyx(+0x318db0) [0x560f21b68db0]
( 11) lyx: lyx(+0x360ab0) [0x560f21bb0ab0]
( 12) lyx: lyx(+0x5c7f68) [0x560f21e17f68]
( 13) lyx: lyx(+0x5c3de1) [0x560f21e13de1]
( 14) /lib64/libQt5Core.so.5: QMetaObject::activate(QObject*, int, int, void**)
( 15) /lib64/libQt5Widgets.so.5: QTabWidget::currentChanged(int)
( 16) /lib64/libQt5Widgets.so.5: /lib64/libQt5Widgets.so.5(+0x2f4e27) 
[0x7f651915be27]
( 17) /lib64/libQt5Core.so.5: QMetaObject::activate(QObject*, int, int, void**)
( 18) /lib64/libQt5Widgets.so.5: QTabBar::currentChanged(int)
( 19) /lib64/libQt5Widgets.so.5: QTabBar::setCurrentIndex(int)
( 20) lyx: lyx(+0x5c3f67) [0x560f21e13f67]
( 21) lyx: lyx(+0x5a10a7) [0x560f21df10a7]
( 22) lyx: lyx(+0x5a170f) [0x560f21df170f]
( 23) lyx: lyx(+0x5a1908) [0x560f21df1908]
( 24) lyx: lyx(+0x5a34e9) [0x560f21df34e9]
( 25) lyx: lyx(+0x57c2c7) [0x560f21dcc2c7]
( 26) lyx: lyx(+0x573ce0) [0x560f21dc3ce0]
( 27) lyx: lyx(+0x5feafd) [0x560f21e4eafd]
( 28) /lib64/libQt5Core.so.5: QMetaObject::activate(QObject*, int, int, void**)
( 29) /lib64/libQt5Widgets.so.5: QAction::triggered(bool)
( 30) /lib64/libQt5Widgets.so.5: QAction::activate(QAction::ActionEvent)
( 31) /lib64/libQt5Widgets.so.5: /lib64/libQt5Widgets.so.5(+0x2c0424) 
[0x7f6519127424]
( 32) /lib64/libQt5Widgets.so.5: /lib64/libQt5Widgets.so.5(+0x2c7e8b) 
[0x7f651912ee8b]
( 33) /lib64/libQt5Widgets.so.5: QMenu::mouseReleaseEvent(QMouseEvent*)
( 34) /lib64/libQt5Widgets.so.5: QWidget::event(QEvent*)
( 35) /lib64/libQt5Widgets.so.5: QMenu::event(QEvent*)
( 36) /lib64/libQt5Widgets.so.5: QApplicationPrivate::notify_helper(QObject*, 
QEvent*)
( 37) /lib64/libQt5Widgets.so.5: QApplication::notify(QObject*, QEvent*)
( 38) lyx: lyx(+0x57e3aa) [0x560f21dce3aa]
( 39) /lib64/libQt5Core.so.5: QCoreApplication::notifyInternal2(QObject*, 
QEvent*)
( 40) /lib64/libQt5Widgets.so.5: QApplicationPrivate::sendMouseEvent(QWidget*, 
QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool)
( 41) /lib64/libQt5Widgets.so.5: /lib64/libQt5Widgets.so.5(+0x1bc073) 
[0x7f6519023073]
( 42) /lib64/libQt5Widgets.so.5: /lib64/libQt5Widgets.so.5(+0x1bea64) 
[0x7f6519025a64]
( 43) /lib64/libQt5Widgets.so.5: QApplicationPrivate::notify_helper(QObject*, 
QEvent*)
( 44) /lib64/libQt5Widgets.so.5: QApplication::notify(QObject*, QEvent*)
( 45) lyx: lyx(+0x57e3aa) [0x560f21dce3aa]
( 46) /lib64/libQt5Core.so.5: QCoreApplication::notifyInternal2(QObject*, 
QEvent*)
( 47) /lib64/libQt5Gui.so.5: 
QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*)
( 48) /lib64/libQt5Gui.so.5: 
QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*)
( 49) /lib64/libQt5Gui.so.5: 
QWindowSystemInterface::sendWindowSystemEvents(QFlags)
( 50) /lib64/libQt5XcbQpa.so.5: /lib64/libQt5XcbQpa.so.5(+0x6e7a0) 
[0x7f650a2667a0]
( 51) /lib64/libglib-2.0.so.0: 
/lib64/libglib-2.0.so.0(g_main_context_dispatch+0x157) [0x7f6519bd8247]
( 52) /lib64/libglib-2.0.so.0: /lib64/libglib-2.0.so.0(+0x4a5e8) 
[0x7f6519bd85e8]
( 53) /lib64/libglib-2.0.so.0: 
/lib64/libglib-2.0.so.0(g_main_context_iteration+0x2c) [0x7f6519bd867c]
( 54) /lib64/libQt5Core.so.5: 
QEventDispatcherGlib::processEvents(QFlags)
( 55) /lib64/libQt5Core.so.5: 
QEventLoop::exec(QFlags)
( 56) /lib64/libQt5Core.so.5: QCoreApplication::exec()
( 57) lyx: lyx(+0x266ed5) [0x560f21ab6ed5]
( 58) lyx: lyx(+0x11be66) [0x560f2196be66]
( 59) /lib64/libc.so.6: /lib64/libc.so.6(__libc_start_main+0xea) 
[0x7f65176aa4da]
( 60) lyx: lyx(+0x12491a) [0x560f2197491a]


===
 Patrick DUPRÉ | | email: pdu...@gmx.com
 Laboratoire de Physico-Chimie de l'Atmosphère | |
 Université du Littoral-Côte d'Opale   | |
 Tel.  (33)-(0)3 28 23 76 12   | | Fax: 03 28 65 82 44
 189A, avenue Maurice Schumann | | 59140 Dunkerque, France
===

Re: lyx-2.3.0alpha1-1 crash

[PhilipPirrip]

I think I caught this one too. I was working on a document with a few 
float figures exported from inkscape as pdf, LyX 2.3.0alpha1 crashed 
after updating (saving as pdf) one of the figures.
I was running J. Matos' version from 
https://copr.fedorainfracloud.org/coprs/jamatos/lyx-next/

Will try to reproduce.










On 05/26/2017 04:48 AM, Wolfgang Engelmann wrote:
This might not be of interest to the readers of the lyx-users list, 
perhaps it could be forwarded to the developers, if of importance at all.


I got with lyx-2.3.0alpha1-1 under Debian a crash with the following 
output (see below). What I did, was, that i had changed a figure which 
was already inserted in a figure float. Nothing serious for me, since 
the lyx file was recovered and everything worked fine again.


If this matters: I have started the newly installed lyx-2.3.0alpha1-1 by 
using src/lyx, since I have 2.2.0 running besides.


Wolfgang

(  1) src/lyx: src/lyx() [0x92967a]
(  2) src/lyx: src/lyx() [0x9288c8]
(  3) src/lyx: src/lyx() [0x5b23de]
(  4) /lib/x86_64-linux-gnu/libc.so.6: 
/lib/x86_64-linux-gnu/libc.so.6(+0x350e0) [0x7f34a38b50e0]
(  5) /usr/lib/x86_64-linux-gnu/libQtCore.so.4: 
QFileInfo::absoluteFilePath() const

(  6) src/lyx: src/lyx() [0xb54099]
(  7) src/lyx: src/lyx() [0xb35108]
(  8) src/lyx: src/lyx() [0xb67baf]
(  9) src/lyx: src/lyx() [0xb67f4d]
( 10) src/lyx: src/lyx() [0xb6642d]
( 11) /usr/lib/x86_64-linux-gnu/libQtCore.so.4: 
QMetaObject::activate(QObject*, QMetaObject const*, int, void**)

( 12) /usr/lib/x86_64-linux-gnu/libQtCore.so.4: QObject::event(QEvent*)
( 13) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: 
QApplicationPrivate::notify_helper(QObject*, QEvent*)
( 14) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: 
QApplication::notify(QObject*, QEvent*)

( 15) src/lyx: src/lyx() [0x93d8d6]
( 16) /usr/lib/x86_64-linux-gnu/libQtCore.so.4: 
QCoreApplication::notifyInternal(QObject*, QEvent*)
( 17) /usr/lib/x86_64-linux-gnu/libQtCore.so.4: 
/usr/lib/x86_64-linux-gnu/libQtCore.so.4(+0x1b838b) [0x7f34a496038b]
( 18) /usr/lib/x86_64-linux-gnu/libQtCore.so.4: 
/usr/lib/x86_64-linux-gnu/libQtCore.so.4(+0x1b53f9) [0x7f34a495d3f9]
( 19) /lib/x86_64-linux-gnu/libglib-2.0.so.0: 
/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x24d) 
[0x7f34a33b1c5d]
( 20) /lib/x86_64-linux-gnu/libglib-2.0.so.0: 
/lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x49f48) [0x7f34a33b1f48]
( 21) /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) 
[0x7f34a33b1ffc]
( 22) /usr/lib/x86_64-linux-gnu/libQtCore.so.4: 
QEventDispatcherGlib::processEvents(QFlags)
( 23) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: 
/usr/lib/x86_64-linux-gnu/libQtGui.so.4(+0x26bf96) [0x7f34a4f03f96]
( 24) /usr/lib/x86_64-linux-gnu/libQtCore.so.4: 
QEventLoop::processEvents(QFlags)
( 25) /usr/lib/x86_64-linux-gnu/libQtCore.so.4: 
QEventLoop::exec(QFlags)

( 26) /usr/lib/x86_64-linux-gnu/libQtCore.so.4: QCoreApplication::exec()
( 27) src/lyx: src/lyx() [0x5ba925]
( 28) src/lyx: src/lyx() [0x44008d]
( 29) /lib/x86_64-linux-gnu/libc.so.6: 
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7f34a38a1b45]

( 30) src/lyx: src/lyx() [0x448eff]

Re: lyx-2.3.0alpha1-1 crash

[Wolfgang Engelmann]

Am 26.05.2017 um 12:40 schrieb Scott Kostyshak:

On Fri, May 26, 2017 at 10:48:28AM +0200, Wolfgang Engelmann wrote:

This might not be of interest to the readers of the lyx-users list, perhaps
it could be forwarded to the developers, if of importance at all.

I got with lyx-2.3.0alpha1-1 under Debian

How did you install lyx-2.3.0alpha1-1?
Am 05.05.2017 um 11:47 schrieb Scott Kostyshak: Public release of LyX 
version 2.3.0alpha1-1

We are proud to announce 2.3.0alpha1-1 of the new LyX 2.3 series..
You can download LyX 2.3.0alpha1-1 from ftp://ftp.lyx.org/pub/lyx/devel/
The LyX team.http://www.lyx.org


Note that your backtrace below would be more useful if you had the debug
symobls installed.

Do you mean using that: Am 05.05.2017 um 11:47 schrieb Scott Kostyshak:
Can you also do the same as the above, but this time add the option
 -dbg info
to the command? For me, this would be lyx -dbg info myfile.lyx
can you then copy the output from the terminal to a log file, and post 
it to the list?

a crash with the following output
(see below). What I did, was, that i had changed a figure which was already
inserted in a figure float. Nothing serious for me, since the lyx file was
recovered and everything worked fine again.

Thanks for testing, Wolfgang. This is definitely important. Indeed
please send future such emails to lyx-devel.

The big question is: are you able to reproduce the crash? i.e. if you do
the same steps you did, do you get the crash again?

Will try it during my next work with lyx



If this matters: I have started the newly installed lyx-2.3.0alpha1-1 by
using src/lyx, since I have 2.2.0 running besides.

Are they sharing the same user directory? That might not be a good idea.

Scott

no, they are in different directories. Thanks for your response.
Will send this also to the developers
lyx-devel-h...@lists.lyx.org (correct??)
Wolfgang

Re: lyx-2.3.0alpha1-1 crash

[Scott Kostyshak]

On Fri, May 26, 2017 at 10:48:28AM +0200, Wolfgang Engelmann wrote:
> This might not be of interest to the readers of the lyx-users list, perhaps
> it could be forwarded to the developers, if of importance at all.
> 
> I got with lyx-2.3.0alpha1-1 under Debian

How did you install lyx-2.3.0alpha1-1?

Note that your backtrace below would be more useful if you had the debug
symobls installed.

> a crash with the following output
> (see below). What I did, was, that i had changed a figure which was already
> inserted in a figure float. Nothing serious for me, since the lyx file was
> recovered and everything worked fine again.

Thanks for testing, Wolfgang. This is definitely important. Indeed
please send future such emails to lyx-devel.

The big question is: are you able to reproduce the crash? i.e. if you do
the same steps you did, do you get the crash again?

> If this matters: I have started the newly installed lyx-2.3.0alpha1-1 by
> using src/lyx, since I have 2.2.0 running besides.

Are they sharing the same user directory? That might not be a good idea.

Scott


signature.asc
Description: PGP signature

lyx-2.3.0alpha1-1 crash

[Wolfgang Engelmann]

This might not be of interest to the readers of the lyx-users list, 
perhaps it could be forwarded to the developers, if of importance at all.


I got with lyx-2.3.0alpha1-1 under Debian a crash with the following 
output (see below). What I did, was, that i had changed a figure which 
was already inserted in a figure float. Nothing serious for me, since 
the lyx file was recovered and everything worked fine again.


If this matters: I have started the newly installed lyx-2.3.0alpha1-1 by 
using src/lyx, since I have 2.2.0 running besides.


Wolfgang

(  1) src/lyx: src/lyx() [0x92967a]
(  2) src/lyx: src/lyx() [0x9288c8]
(  3) src/lyx: src/lyx() [0x5b23de]
(  4) /lib/x86_64-linux-gnu/libc.so.6: 
/lib/x86_64-linux-gnu/libc.so.6(+0x350e0) [0x7f34a38b50e0]
(  5) /usr/lib/x86_64-linux-gnu/libQtCore.so.4: 
QFileInfo::absoluteFilePath() const

(  6) src/lyx: src/lyx() [0xb54099]
(  7) src/lyx: src/lyx() [0xb35108]
(  8) src/lyx: src/lyx() [0xb67baf]
(  9) src/lyx: src/lyx() [0xb67f4d]
( 10) src/lyx: src/lyx() [0xb6642d]
( 11) /usr/lib/x86_64-linux-gnu/libQtCore.so.4: 
QMetaObject::activate(QObject*, QMetaObject const*, int, void**)

( 12) /usr/lib/x86_64-linux-gnu/libQtCore.so.4: QObject::event(QEvent*)
( 13) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: 
QApplicationPrivate::notify_helper(QObject*, QEvent*)
( 14) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: 
QApplication::notify(QObject*, QEvent*)

( 15) src/lyx: src/lyx() [0x93d8d6]
( 16) /usr/lib/x86_64-linux-gnu/libQtCore.so.4: 
QCoreApplication::notifyInternal(QObject*, QEvent*)
( 17) /usr/lib/x86_64-linux-gnu/libQtCore.so.4: 
/usr/lib/x86_64-linux-gnu/libQtCore.so.4(+0x1b838b) [0x7f34a496038b]
( 18) /usr/lib/x86_64-linux-gnu/libQtCore.so.4: 
/usr/lib/x86_64-linux-gnu/libQtCore.so.4(+0x1b53f9) [0x7f34a495d3f9]
( 19) /lib/x86_64-linux-gnu/libglib-2.0.so.0: 
/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x24d) 
[0x7f34a33b1c5d]
( 20) /lib/x86_64-linux-gnu/libglib-2.0.so.0: 
/lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x49f48) [0x7f34a33b1f48]
( 21) /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) 
[0x7f34a33b1ffc]
( 22) /usr/lib/x86_64-linux-gnu/libQtCore.so.4: 
QEventDispatcherGlib::processEvents(QFlags)
( 23) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: 
/usr/lib/x86_64-linux-gnu/libQtGui.so.4(+0x26bf96) [0x7f34a4f03f96]
( 24) /usr/lib/x86_64-linux-gnu/libQtCore.so.4: 
QEventLoop::processEvents(QFlags)
( 25) /usr/lib/x86_64-linux-gnu/libQtCore.so.4: 
QEventLoop::exec(QFlags)

( 26) /usr/lib/x86_64-linux-gnu/libQtCore.so.4: QCoreApplication::exec()
( 27) src/lyx: src/lyx() [0x5ba925]
( 28) src/lyx: src/lyx() [0x44008d]
( 29) /lib/x86_64-linux-gnu/libc.so.6: 
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7f34a38a1b45]

( 30) src/lyx: src/lyx() [0x448eff]

Re: crash

[Jean-Marc Lasgouttes]

Le 30/01/2017 à 11:44, Patrick Dupre a écrit :

Actually, the issue seems coming from the session file:
the file causing the crash is Amsterdam_2017.lyx


Hello,

What makes you think that it is the case?

JMarc

crash

[Patrick Dupre]

Hello,

Bug hard to debug.
If I open a lyx file normally (revtex), then if I open a 2nd lyx file (beamer), 
lyx just crashes
(see below).
This is absolutely reproducible.
If I change the name of the 2nd file, then it opens without crash.
If I also open the 2nd file only (ie with the name which makes it crashes in the
sequence that I just described), it opens normally.


Actually, the issue seems coming from the session file:
the file causing the crash is Amsterdam_2017.lyx

## Automatically generated lyx session file 
## Editing this file manually may cause lyx to crash.

[recent files]
/home/pdupre/Amsterdam/Collaborations/ANR.lyx
/home/pdupre/publications/Formalism_NL/Formalism_NL_v1.lyx
/home/pdupre/Talks/Amsterdam_2017.lyx
/home/pdupre/publications/Formalism_NL/Formalism_NL.lyx
/home/pdupre/publications/Help/FT.lyx
/home/pdupre/publications/Saturation/Saturation.lyx
/home/pdupre/NICE-OHMS/Chi_NL.lyx
/home/pdupre/BNL/TS.lyx
/home/pdupre/publications/Gaussian/Gaussian.lyx
/home/pdupre/BNL/Annoucement.lyx
/home/pdupre/Talks/Line_Modeling.lyx
/home/pdupre/Talks/Amsterdam_2016.lyx
/home/pdupre/conferences/Lunteren_2016/Line_Modelling.lyx
/home/pdupre/H2_Isot/Notes.lyx
/home/pdupre/CNRS/DRH_18.lyx
/home/pdupre/Dunkerque/BQR_I/Presentation_BQR_2016.lyx
/home/pdupre/Talks/CNRS_VU_HD.lyx
/home/pdupre/Talks/CNRS_14CO2.lyx
/home/pdupre/Talks/CNRS.lyx
/home/pdupre/Talks/CNRS0.lyx

[last opened files]
1, /home/pdupre/Amsterdam/Collaborations/ANR.lyx

[cursor positions]
0, 0, /home/pdupre/Amsterdam/Collaborations/ANR.lyx
4, 0, /home/pdupre/Applications/RP.lyx
0, 0, /home/pdupre/Applications/Syrte/Presentation.lyx
85, 2, /home/pdupre/Applications/Tuscon/RP.lyx
34, 509, /home/pdupre/Applications/York/RP_Chemistry.lyx
79, 31, /home/pdupre/Applications/York/RP_Physics.lyx
7, 1, /home/pdupre/BNL/Annoucement.lyx
34, 80, /home/pdupre/BNL/TS.lyx
3, 1, /home/pdupre/Beamer/Overlay_pict.lyx
54, 170, /home/pdupre/CNRS/DRH_18.lyx
132, 0, /home/pdupre/CNRS/evaluation_2014.lyx
0, 0, /home/pdupre/CNRS/evaluation_2014_complement.lyx
42, 0, /home/pdupre/CNRS/evaluation_2015.lyx
164, 447, /home/pdupre/CNRS/evaluation_2016.lyx
2, 2, /home/pdupre/CO2/Notes.lyx
12, 516, /home/pdupre/CO2/Notes2.lyx
50, 661, /home/pdupre/CO2/Notes2_v2.lyx
5, 1, /home/pdupre/Dunkerque/BQR_I/Presentation_BQR_2016.lyx
6, 17, /home/pdupre/Dunkerque/LPCA_Seminars/Good_Practise.lyx
34, 324, /home/pdupre/Dunkerque/PhD/Allocation_2016.lyx
28, 1119, /home/pdupre/Dunkerque/PhD/Allocation_2016_Reg.lyx
77, 0, /home/pdupre/Dunkerque/Presentation_July13.lyx
68, 0, /home/pdupre/Dunkerque/Presentation_March15.lyx
21, 786, /home/pdupre/Dunkerque/Projects/AIRR_2015/CV_short.lyx
18, 1, /home/pdupre/Dunkerque/Projects/AIRR_2015/Presentation.lyx
1, 432, /home/pdupre/Dunkerque/Projects/AIRR_2015/Resume.lyx
63, 372, /home/pdupre/Dunkerque/Projects/AIRR_2015/VisioAIRR.lyx
80, 237, /home/pdupre/Dunkerque/Projects/ANR_2013/Pre-ANR_2014_final.lyx
25, 222, /home/pdupre/Dunkerque/Projects/ANR_2013/Pre-ANR_2014_v5.lyx
5, 1, /home/pdupre/Dunkerque/Projects/ANR_2014/Risk.lyx
2, 0, /home/pdupre/Dunkerque/Projects/ANR_2014/Risk_b.lyx
15, 127, /home/pdupre/Dunkerque/Projects/ANR_2014/Summaries.lyx
78, 216, /home/pdupre/Dunkerque/Projects/ANR_2016/ANR_MRSEI.lyx
0, 180, /home/pdupre/Dunkerque/Projects/ANR_2016/Pre-ANR_2016_Resume.lyx
106, 0, /home/pdupre/Dunkerque/Projects/ANR_2016/Pre-ANR_2016_v0.lyx
21, 207, /home/pdupre/Dunkerque/Projects/ANR_2016/Pre-ANR_2016_v2.lyx
71, 0, /home/pdupre/Dunkerque/Projects/Defi_CNRS/Defi_instrumentation_2014_3.lyx
13, 0, 
/home/pdupre/Dunkerque/Projects/Defi_CNRS/Defi_instrumentation_2014_post.lyx
0, 0, /home/pdupre/Dunkerque/Projects/FET/ConfCall1.lyx
0, 0, /home/pdupre/Dunkerque/Projects/FET/ConfCall2.lyx
1, 0, /home/pdupre/Dunkerque/Projects/FET/Initial.lyx
234, 11, /home/pdupre/Dunkerque/Projects/FET/Presentation.lyx
12, 265, /home/pdupre/Dunkerque/Projects/Horizon2020/ERC-2014.lyx
249, 1, /home/pdupre/Dunkerque/Projects/Horizon2020/ERC-2015.lyx
41, 12, /home/pdupre/Dunkerque/Projects/Horizon2020/FET_NICE-OHMS.lyx
13, 70, /home/pdupre/Dunkerque/Projects/Interreg/PreProject_2015.lyx
0, 0, /home/pdupre/Dunkerque/Projects/PD_prog.lyx
38, 570, /home/pdupre/Dunkerque/Projects/PD_prog2.lyx
25, 0, /home/pdupre/Dunkerque/Projects/Pre-OH_UV.lyx
13, 0, /home/pdupre/Dunkerque/Setup/EOM/Notes.lyx
0, 0, /home/pdupre/Dunkerque/Setup/EOM/Test.lyx
14, 26, /home/pdupre/Dunkerque/test.lyx
0, 506, /home/pdupre/Dusseldorf/Projects/HD/Proposal.lyx
0, 0, /home/pdupre/Dusseldorf/Projects/part_list_2.lyx
18, 4, /home/pdupre/H2_Isot/Notes.lyx
130, 11, /home/pdupre/NICE-OHMS/Chi_NL.lyx
33, 1, /home/pdupre/NICE-OHMS/Notes.lyx
0, 0, /home/pdupre/NICE-OHMS/Other_Schematics/Nuggets.lyx
0, 0, /home/pdupre/NICE-OHMS/Presentation_2014.lyx
53, 0, /home/pdupre/NO2/Spectroscopy_data.lyx
4, 0, /home/pdupre/NO2/tmp.lyx
231, 0, /home/pdupre/Resonators/Birefringence/Notes.lyx
31, 22, /home/pdupre/Review/Ashurbekov/pdR1.lyx
6, 27, /home/pdupre/Review/Ayrapetian/pd.lyx
28, 93, /home/pdupre

Re: Crash (sigsegv) when dragging a pdf file onto the Lyx window (on Windows)

[Sven Schreiber]

Am 27.09.2016 um 18:32 schrieb Richard Heck:



Can you please file this as a bug at http://www.lyx.org/trac/newticket?
You will have to create an account if you do not have one.

Say there, too, whether you can reproduce the bug by doing the same
sequence of events again.



OK, this is now at http://www.lyx.org/trac/ticket/10406, and yes I can 
reproduce and did explain there how.


thanks,
sven

Re: Crash (sigsegv) when dragging a pdf file onto the Lyx window (on Windows)

[Richard Heck]

On 09/27/2016 08:45 AM, Sven Schreiber wrote:
> Hi,
> this is with Lyx 2.2.1 on Windows 7 64bit.
> By mistake I dragged a pdf file onto the Lyx window, then nothing
> happened, I realized my mistake, and dragged the corresponding lyx
> file. That one was opened alright, and a dialog appeared that Lyx
> cannot open the (pdf) file. Then Lyx crashed ("You found a bug..." or
> something like that).
>
> Perhaps it has something to do with the fact the the file names were
> identical except for the suffix.
>
> Perhaps it's also known already?
>
> It's nothing dramatic, but I thought a crash deserves to be reported
> anyway.

Thanks, yes, all crashes are bad.

Can you please file this as a bug at http://www.lyx.org/trac/newticket?
You will have to create an account if you do not have one.

Say there, too, whether you can reproduce the bug by doing the same
sequence of events again.

Richard

Crash (sigsegv) when dragging a pdf file onto the Lyx window (on Windows)

[Sven Schreiber]

Hi,
this is with Lyx 2.2.1 on Windows 7 64bit.
By mistake I dragged a pdf file onto the Lyx window, then nothing 
happened, I realized my mistake, and dragged the corresponding lyx file. 
That one was opened alright, and a dialog appeared that Lyx cannot open 
the (pdf) file. Then Lyx crashed ("You found a bug..." or something like 
that).


Perhaps it has something to do with the fact the the file names were 
identical except for the suffix.


Perhaps it's also known already?

It's nothing dramatic, but I thought a crash deserves to be reported anyway.

thanks,
sven

Re: LyX 2.2.0 crash from command line

[Dr Eberhard Lisse]

Works on the Mac.

Load it into lyx, modify it and save it again so it changes from 2.1 to
2.2 format. Try it then.

el

On 2016-07-12 15:56, Jesse Shapiro wrote:
> Please see ticket here:
> http://www.lyx.org/trac/ticket/10286
> Per rgheck's question, has anyone else encountered this and can you
> reproduce it?

LyX 2.2.0 crash from command line

[Jesse Shapiro]

Please see ticket here:
http://www.lyx.org/trac/ticket/10286
Per rgheck's question, has anyone else encountered this and can you
reproduce it?

Crash when quitting on OS X

[disinteres...@gmail.com]

With LyX 2.1.4 and OS X 10.10.5, I often get crashes when quitting using
command+q. Oddly, the release notes for 2.1.4 say that it fixes another
crashes on quitting bug (#8637). I was getting these crashes with previous
versions of LyX when I was on Mavericks, but upgrading to Yosemite solved
the problem until I updated to 2.1.4, which reintroduced the behavior.

Is anyone else seeing this?

Re: Crash when quitting on OS X

[Stephan Witt]

Am 15.10.2015 um 01:31 schrieb disinteres...@gmail.com:

> With LyX 2.1.4 and OS X 10.10.5, I often get crashes when quitting using 
> command+q. Oddly, the release notes for 2.1.4 say that it fixes another 
> crashes on quitting bug (#8637). I was getting these crashes with previous 
> versions of LyX when I was on Mavericks, but upgrading to Yosemite solved the 
> problem until I updated to 2.1.4, which reintroduced the behavior.
> 
> Is anyone else seeing this?

These crashes are difficult to reproduce on a developer system. I had them once 
and the change fixed it. Later I got them again and now they are gone again 
without any change. Sorry, it's not clear what's triggering them. It happens on 
destruction of the LinkBack-machinery on exit of LyX.

I want to give it another try and made a change to address the cause of the 
problem. I can make a LyX 2.1.4 with this change and will be happy if you are 
willing to test it.

Regards,
Stephan

crash

[Patrick Dupre]

Hello,

I can reproduce a crash:
lyx: SIGSEGV signal caught!
Sorry, you have found a bug in LyX, hope you have not lost any data.
Please read the bug-reporting instructions in 'Help-Introduction' and send us 
a bug report, if necessary. Thanks!
Bye.
Error: LyX crashed!

SIGSEGV signal caught!
Sorry, you have found a bug in LyX, hope you have not lost any data.
Please read the bug-reporting instructions in 'Help-Introduction' and send us 
a bug report, if necessary. Thanks!
Bye.


How?
When I have a first lyx loaded (
CRDS_Polar_v0.lyx
then I open a recently open file:
NO2_threshold_v4.lyx

However, if I change the name (or copy) the file NO2_threshold_v4.lyx
Than, I cannot reproduce the crash.

How the file name can control the lyx crash?

Thank for your help.

===
 Patrick DUPRÉ | | email: pdu...@gmx.com
 Laboratoire de Physico-Chimie de l'Atmosphère | |
 Université du Littoral-Côte d'Opale   | |
 Tel.  (33)-(0)3 28 23 76 12   | | Fax: 03 28 65 82 44
 189A, avenue Maurice Schumann | | 59140 Dunkerque, France
===

Re: crash

[Richard Heck]

On 01/28/2015 10:50 AM, Patrick Dupre wrote:

Hello,

I can reproduce a crash:
lyx: SIGSEGV signal caught!
Sorry, you have found a bug in LyX, hope you have not lost any data.
Please read the bug-reporting instructions in 'Help-Introduction' and send us 
a bug report, if necessary. Thanks!
Bye.
Error: LyX crashed!

SIGSEGV signal caught!
Sorry, you have found a bug in LyX, hope you have not lost any data.
Please read the bug-reporting instructions in 'Help-Introduction' and send us 
a bug report, if necessary. Thanks!
Bye.


How?
When I have a first lyx loaded (
CRDS_Polar_v0.lyx
then I open a recently open file:
NO2_threshold_v4.lyx

However, if I change the name (or copy) the file NO2_threshold_v4.lyx
Than, I cannot reproduce the crash.

How the file name can control the lyx crash?


Is one of them a child file?

Richard

crash

[Patrick Dupre]

Hello,

I can reproduce a crash:
lyx: SIGSEGV signal caught!
Sorry, you have found a bug in LyX, hope you have not lost any data.
Please read the bug-reporting instructions in 'Help-Introduction' and send us 
a bug report, if necessary. Thanks!
Bye.
Error: LyX crashed!

SIGSEGV signal caught!
Sorry, you have found a bug in LyX, hope you have not lost any data.
Please read the bug-reporting instructions in 'Help-Introduction' and send us 
a bug report, if necessary. Thanks!
Bye.


How?
When I have a first lyx loaded (
CRDS_Polar_v0.lyx
then I open a recently open file:
NO2_threshold_v4.lyx

However, if I change the name (or copy) the file NO2_threshold_v4.lyx
Than, I cannot reproduce the crash.

How the file name can control the lyx crash?

Thank for your help.

===
 Patrick DUPRÉ | | email: pdu...@gmx.com
 Laboratoire de Physico-Chimie de l'Atmosphère | |
 Université du Littoral-Côte d'Opale   | |
 Tel.  (33)-(0)3 28 23 76 12   | | Fax: 03 28 65 82 44
 189A, avenue Maurice Schumann | | 59140 Dunkerque, France
===

Re: crash

[Richard Heck]

On 01/28/2015 10:50 AM, Patrick Dupre wrote:

Hello,

I can reproduce a crash:
lyx: SIGSEGV signal caught!
Sorry, you have found a bug in LyX, hope you have not lost any data.
Please read the bug-reporting instructions in 'Help-Introduction' and send us 
a bug report, if necessary. Thanks!
Bye.
Error: LyX crashed!

SIGSEGV signal caught!
Sorry, you have found a bug in LyX, hope you have not lost any data.
Please read the bug-reporting instructions in 'Help-Introduction' and send us 
a bug report, if necessary. Thanks!
Bye.


How?
When I have a first lyx loaded (
CRDS_Polar_v0.lyx
then I open a recently open file:
NO2_threshold_v4.lyx

However, if I change the name (or copy) the file NO2_threshold_v4.lyx
Than, I cannot reproduce the crash.

How the file name can control the lyx crash?


Is one of them a child file?

Richard

crash

[Patrick Dupre]

Hello,

I can reproduce a crash:
lyx: SIGSEGV signal caught!
Sorry, you have found a bug in LyX, hope you have not lost any data.
Please read the bug-reporting instructions in 'Help->Introduction' and send us 
a bug report, if necessary. Thanks!
Bye.
Error: LyX crashed!

SIGSEGV signal caught!
Sorry, you have found a bug in LyX, hope you have not lost any data.
Please read the bug-reporting instructions in 'Help->Introduction' and send us 
a bug report, if necessary. Thanks!
Bye.


How?
When I have a first lyx loaded (
CRDS_Polar_v0.lyx
then I open a recently open file:
NO2_threshold_v4.lyx

However, if I change the name (or copy) the file NO2_threshold_v4.lyx
Than, I cannot reproduce the crash.

How the file name can control the lyx crash?

Thank for your help.

===
 Patrick DUPRÉ | | email: pdu...@gmx.com
 Laboratoire de Physico-Chimie de l'Atmosphère | |
 Université du Littoral-Côte d'Opale   | |
 Tel.  (33)-(0)3 28 23 76 12   | | Fax: 03 28 65 82 44
 189A, avenue Maurice Schumann | | 59140 Dunkerque, France
===

Re: crash

[Richard Heck]

On 01/28/2015 10:50 AM, Patrick Dupre wrote:

Hello,

I can reproduce a crash:
lyx: SIGSEGV signal caught!
Sorry, you have found a bug in LyX, hope you have not lost any data.
Please read the bug-reporting instructions in 'Help->Introduction' and send us 
a bug report, if necessary. Thanks!
Bye.
Error: LyX crashed!

SIGSEGV signal caught!
Sorry, you have found a bug in LyX, hope you have not lost any data.
Please read the bug-reporting instructions in 'Help->Introduction' and send us 
a bug report, if necessary. Thanks!
Bye.


How?
When I have a first lyx loaded (
CRDS_Polar_v0.lyx
then I open a recently open file:
NO2_threshold_v4.lyx

However, if I change the name (or copy) the file NO2_threshold_v4.lyx
Than, I cannot reproduce the crash.

How the file name can control the lyx crash?


Is one of them a child file?

Richard

Re: crash

[Jean-Marc Lasgouttes]

Le 09/10/14 01:18, Patrick Dupre a écrit :

The issue seems to be due to a table. The file has been cut in the middle
of it!

I finally was able to use a lyx~ file.


I advise you to update to LyX 2.1.2, where this bug is fixed.

JMarc

Re: crash

[Jean-Marc Lasgouttes]

Le 09/10/14 01:18, Patrick Dupre a écrit :

The issue seems to be due to a table. The file has been cut in the middle
of it!

I finally was able to use a lyx~ file.


I advise you to update to LyX 2.1.2, where this bug is fixed.

JMarc

Re: crash

[Jean-Marc Lasgouttes]

Le 09/10/14 01:18, Patrick Dupre a écrit :

The issue seems to be due to a table. The file has been cut in the middle
of it!

I finally was able to use a lyx~ file.


I advise you to update to LyX 2.1.2, where this bug is fixed.

JMarc

crash

[Patrick Dupre]

Hello,

I have to submit in 12 h a proposal and lyx crashed!!!
I cannot reopen the file.
It run for ever.
Can some body help me?

Thank.

===
 Patrick DUPRÉ | | email: pdu...@gmx.com
 Laboratoire de Physico-Chimie de l'Atmosphère | |
 Université du Littoral-Côte d'Opale   | |
 Tel.  (33)-(0)3 28 23 76 12   | | Fax: 03 28 65 82 44
 189A, avenue Maurice Schumann | | 59140 Dunkerque, France
===

Re: crash

[Patrick Dupre]

The issue seems to be due to a table. The file has been cut in the middle
of it!

I finally was able to use a lyx~ file.


===
 Patrick DUPRÉ | | email: pdu...@gmx.com
 Laboratoire de Physico-Chimie de l'Atmosphère | |
 Université du Littoral-Côte d'Opale   | |
 Tel.  (33)-(0)3 28 23 76 12   | | Fax: 03 28 65 82 44
 189A, avenue Maurice Schumann | | 59140 Dunkerque, France
===


 Sent: Wednesday, October 08, 2014 at 10:11 PM
 From: Patrick Dupre pdu...@gmx.com
 To: lyx lyx-users@lists.lyx.org
 Subject: crash

 Hello,
 
 I have to submit in 12 h a proposal and lyx crashed!!!
 I cannot reopen the file.
 It run for ever.
 Can some body help me?
 
 Thank.
 
 ===
  Patrick DUPRÉ | | email: pdu...@gmx.com
  Laboratoire de Physico-Chimie de l'Atmosphère | |
  Université du Littoral-Côte d'Opale   | |
  Tel.  (33)-(0)3 28 23 76 12   | | Fax: 03 28 65 82 44
  189A, avenue Maurice Schumann | | 59140 Dunkerque, France
 ===

crash

[Patrick Dupre]

Hello,

I have to submit in 12 h a proposal and lyx crashed!!!
I cannot reopen the file.
It run for ever.
Can some body help me?

Thank.

===
 Patrick DUPRÉ | | email: pdu...@gmx.com
 Laboratoire de Physico-Chimie de l'Atmosphère | |
 Université du Littoral-Côte d'Opale   | |
 Tel.  (33)-(0)3 28 23 76 12   | | Fax: 03 28 65 82 44
 189A, avenue Maurice Schumann | | 59140 Dunkerque, France
===

Re: crash

[Patrick Dupre]

The issue seems to be due to a table. The file has been cut in the middle
of it!

I finally was able to use a lyx~ file.


===
 Patrick DUPRÉ | | email: pdu...@gmx.com
 Laboratoire de Physico-Chimie de l'Atmosphère | |
 Université du Littoral-Côte d'Opale   | |
 Tel.  (33)-(0)3 28 23 76 12   | | Fax: 03 28 65 82 44
 189A, avenue Maurice Schumann | | 59140 Dunkerque, France
===


 Sent: Wednesday, October 08, 2014 at 10:11 PM
 From: Patrick Dupre pdu...@gmx.com
 To: lyx lyx-users@lists.lyx.org
 Subject: crash

 Hello,
 
 I have to submit in 12 h a proposal and lyx crashed!!!
 I cannot reopen the file.
 It run for ever.
 Can some body help me?
 
 Thank.
 
 ===
  Patrick DUPRÉ | | email: pdu...@gmx.com
  Laboratoire de Physico-Chimie de l'Atmosphère | |
  Université du Littoral-Côte d'Opale   | |
  Tel.  (33)-(0)3 28 23 76 12   | | Fax: 03 28 65 82 44
  189A, avenue Maurice Schumann | | 59140 Dunkerque, France
 ===

crash

[Patrick Dupre]

Hello,

I have to submit in 12 h a proposal and lyx crashed!!!
I cannot reopen the file.
It run for ever.
Can some body help me?

Thank.

===
 Patrick DUPRÉ | | email: pdu...@gmx.com
 Laboratoire de Physico-Chimie de l'Atmosphère | |
 Université du Littoral-Côte d'Opale   | |
 Tel.  (33)-(0)3 28 23 76 12   | | Fax: 03 28 65 82 44
 189A, avenue Maurice Schumann | | 59140 Dunkerque, France
===

Re: crash

[Patrick Dupre]

The issue seems to be due to a table. The file has been cut in the middle
of it!

I finally was able to use a lyx~ file.


===
 Patrick DUPRÉ | | email: pdu...@gmx.com
 Laboratoire de Physico-Chimie de l'Atmosphère | |
 Université du Littoral-Côte d'Opale   | |
 Tel.  (33)-(0)3 28 23 76 12   | | Fax: 03 28 65 82 44
 189A, avenue Maurice Schumann | | 59140 Dunkerque, France
===


> Sent: Wednesday, October 08, 2014 at 10:11 PM
> From: "Patrick Dupre" <pdu...@gmx.com>
> To: lyx <lyx-users@lists.lyx.org>
> Subject: crash
>
> Hello,
> 
> I have to submit in 12 h a proposal and lyx crashed!!!
> I cannot reopen the file.
> It run for ever.
> Can some body help me?
> 
> Thank.
> 
> ===
>  Patrick DUPRÉ | | email: pdu...@gmx.com
>  Laboratoire de Physico-Chimie de l'Atmosphère | |
>  Université du Littoral-Côte d'Opale   | |
>  Tel.  (33)-(0)3 28 23 76 12   | | Fax: 03 28 65 82 44
>  189A, avenue Maurice Schumann | | 59140 Dunkerque, France
> ===
>

crash

[Patrick Dupre]

Hello,

I still have this continuous issue that if I have a first document 
.lyx file open and that I want to open another complex lyx file.
It just crashes!

SIGSEGV signal caught!

It starting to really bother me!

Thank.

===
 Patrick DUPRÉ | | email: pdu...@gmx.com
 Laboratoire de Physico-Chimie de l'Atmosphère | |
 Université du Littoral-Côte d'Opale   | |
 Tel.  (33)-(0)3 28 23 76 12   | | Fax: 03 28 65 82 44
 189A, avenue Maurice Schumann | | 59140 Dunkerque, France
===

Re: crash

[Jürgen Spitzmüller]

Am Montag 22 September 2014, 17:37:16 schrieb Patrick Dupre:
 Hello,
 
 I still have this continuous issue that if I have a first document
 .lyx file open and that I want to open another complex lyx file.
 It just crashes!
 
 SIGSEGV signal caught!
 
 It starting to really bother me!

In order to help, we need more information:

* a backtrace of the crash (http://wiki.lyx.org/FAQ/FurtherHelp#backtrace)
* an example document

Did you already file a bug report for this? If so, what is the ticket number? 
If not, please do and provide all necessary information there.

Thanks,
Jürgen

Fwd: Re: crash

[Jürgen Spitzmüller]

--  Weitergeleitete Nachricht  --

Betreff: Re: crash
Datum: Montag 22 September 2014, 18:00:17
Von: Patrick Dupre pdu...@gmx.com
An: Jürgen Spitzmüller sp...@lyx.org

Hello Jurgen,

Here a sort of trace back.

Unfortunately, right now, I do not have time to send you examples because
my files cannot be disseminated as is.

Sorry.
When I will have more time, I will try to do it!

Regards.

===
 Patrick DUPRÉ | | email: pdu...@gmx.com
 Laboratoire de Physico-Chimie de l'Atmosphère | |
 Université du Littoral-Côte d'Opale   | |
 Tel.  (33)-(0)3 28 23 76 12   | | Fax: 03 28 65 82 44
 189A, avenue Maurice Schumann | | 59140 Dunkerque, France
===


 Sent: Monday, September 22, 2014 at 5:45 PM
 From: Jürgen Spitzmüller sp...@lyx.org
 To: lyx-users@lists.lyx.org
 Subject: Re: crash

 Am Montag 22 September 2014, 17:37:16 schrieb Patrick Dupre:
  Hello,
  
  I still have this continuous issue that if I have a first document
  .lyx file open and that I want to open another complex lyx file.
  It just crashes!
  
  SIGSEGV signal caught!
  
  It starting to really bother me!
 
 In order to help, we need more information:
 
 * a backtrace of the crash (http://wiki.lyx.org/FAQ/FurtherHelp#backtrace)
 * an example document
 
 Did you already file a bug report for this? If so, what is the ticket number? 
 If not, please do and provide all necessary information there.
 
 Thanks,
 Jürgen
 
 

-gdb lyx 
GNU gdb (GDB) Fedora 7.7.1-18.fc20
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type show copying
and show warranty for details.
This GDB was configured as x86_64-redhat-linux-gnu.
Type show configuration for configuration details.
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/.
Find the GDB manual and other documentation resources online at:
http://www.gnu.org/software/gdb/documentation/.
For help, type help.
Type apropos word to search for commands related to word...
Reading symbols from lyx...Reading symbols from 
/home/pdupre/Dunkerque/Projects/ANR_2014/lyx...(no debugging symbols 
found)...done.
(no debugging symbols found)...done.
Missing separate debuginfos, use: debuginfo-install lyx-2.1.1-1.fc20.x86_64
(gdb) run
Starting program: /usr/bin/lyx 
[Thread debugging using libthread_db enabled]
Using host libthread_db library /lib64/libthread_db.so.1.
Traceback (most recent call last):
  File /usr/share/gdb/auto-load/usr/lib64/libgobject-2.0.so.0.3800.2-gdb.py, 
line 9, in module
from gobject import register
  File /usr/share/glib-2.0/gdb/gobject.py, line 3, in module
import gdb.backtrace
ImportError: No module named backtrace
Traceback (most recent call last):
  File /usr/share/gdb/auto-load/usr/lib64/libgobject-2.0.so.0.3800.2-gdb.py, 
line 9, in module
from gobject import register
  File /usr/share/glib-2.0/gdb/gobject.py, line 3, in module
import gdb.backtrace
ImportError: No module named backtrace
Detaching after fork from child process 15726.
Detaching after fork from child process 15728.
Detaching after fork from child process 15729.
[New Thread 0x7fffec08d700 (LWP 15730)]
Detaching after fork from child process 15735.
Detaching after fork from child process 15736.
Detaching after fork from child process 15737.
Detaching after fork from child process 15738.
Detaching after fork from child process 15739.
Detaching after fork from child process 15740.
Detaching after fork from child process 15741.
Detaching after fork from child process 15742.
Detaching after fork from child process 15743.
Detaching after fork from child process 15744.
Detaching after fork from child process 15745.
Detaching after fork from child process 15746.
Detaching after fork from child process 15747.
Detaching after fork from child process 15748.
Detaching after fork from child process 15749.
Detaching after fork from child process 15750.
Detaching after fork from child process 15751.
Detaching after fork from child process 15752.
Detaching after fork from child process 15753.
Detaching after fork from child process 15754.
Detaching after fork from child process 15755.
Detaching after fork from child process 15756.
Detaching after fork from child process 15757.
Detaching after fork from child process 15758.
Detaching after fork from child process 15759.
Detaching after fork from child process 15760.
Detaching after fork from child process 15761.
Detaching after fork from child process 15762.
Detaching after fork from child process 15763.
Detaching after fork from child process 15764.
Detaching after fork

Re: Re: crash

[Scott Kostyshak]

On Mon, Sep 22, 2014 at 12:09 PM, Jürgen Spitzmüller sp...@lyx.org wrote:

 --  Weitergeleitete Nachricht  --

 Betreff: Re: crash
 Datum: Montag 22 September 2014, 18:00:17
 Von: Patrick Dupre pdu...@gmx.com
 An: Jürgen Spitzmüller sp...@lyx.org

 Hello Jurgen,

 Here a sort of trace back.

 Unfortunately, right now, I do not have time to send you examples because
 my files cannot be disseminated as is.

 Sorry.
 When I will have more time, I will try to do it!

 Regards.

 ===
  Patrick DUPRÉ | | email: pdu...@gmx.com
  Laboratoire de Physico-Chimie de l'Atmosphère | |
  Université du Littoral-Côte d'Opale   | |
  Tel.  (33)-(0)3 28 23 76 12   | | Fax: 03 28 65 82 44
  189A, avenue Maurice Schumann | | 59140 Dunkerque, France
 ===

Hi Patrick,

It's useful if you respond to the list (don't worry if you forgot, I
forget also sometimes). Also, let's note for archival purposes
(someone might have the same problem you're having and find through
google this email thread, which is archived) that you opened at ticket
here: http://www.lyx.org/trac/ticket/9278

Best,

Scott

crash

[Patrick Dupre]

Hello,

I still have this continuous issue that if I have a first document 
.lyx file open and that I want to open another complex lyx file.
It just crashes!

SIGSEGV signal caught!

It starting to really bother me!

Thank.

===
 Patrick DUPRÉ | | email: pdu...@gmx.com
 Laboratoire de Physico-Chimie de l'Atmosphère | |
 Université du Littoral-Côte d'Opale   | |
 Tel.  (33)-(0)3 28 23 76 12   | | Fax: 03 28 65 82 44
 189A, avenue Maurice Schumann | | 59140 Dunkerque, France
===

Re: crash

[Jürgen Spitzmüller]

Am Montag 22 September 2014, 17:37:16 schrieb Patrick Dupre:
 Hello,
 
 I still have this continuous issue that if I have a first document
 .lyx file open and that I want to open another complex lyx file.
 It just crashes!
 
 SIGSEGV signal caught!
 
 It starting to really bother me!

In order to help, we need more information:

* a backtrace of the crash (http://wiki.lyx.org/FAQ/FurtherHelp#backtrace)
* an example document

Did you already file a bug report for this? If so, what is the ticket number? 
If not, please do and provide all necessary information there.

Thanks,
Jürgen

Fwd: Re: crash

[Jürgen Spitzmüller]

--  Weitergeleitete Nachricht  --

Betreff: Re: crash
Datum: Montag 22 September 2014, 18:00:17
Von: Patrick Dupre pdu...@gmx.com
An: Jürgen Spitzmüller sp...@lyx.org

Hello Jurgen,

Here a sort of trace back.

Unfortunately, right now, I do not have time to send you examples because
my files cannot be disseminated as is.

Sorry.
When I will have more time, I will try to do it!

Regards.

===
 Patrick DUPRÉ | | email: pdu...@gmx.com
 Laboratoire de Physico-Chimie de l'Atmosphère | |
 Université du Littoral-Côte d'Opale   | |
 Tel.  (33)-(0)3 28 23 76 12   | | Fax: 03 28 65 82 44
 189A, avenue Maurice Schumann | | 59140 Dunkerque, France
===


 Sent: Monday, September 22, 2014 at 5:45 PM
 From: Jürgen Spitzmüller sp...@lyx.org
 To: lyx-users@lists.lyx.org
 Subject: Re: crash

 Am Montag 22 September 2014, 17:37:16 schrieb Patrick Dupre:
  Hello,
  
  I still have this continuous issue that if I have a first document
  .lyx file open and that I want to open another complex lyx file.
  It just crashes!
  
  SIGSEGV signal caught!
  
  It starting to really bother me!
 
 In order to help, we need more information:
 
 * a backtrace of the crash (http://wiki.lyx.org/FAQ/FurtherHelp#backtrace)
 * an example document
 
 Did you already file a bug report for this? If so, what is the ticket number? 
 If not, please do and provide all necessary information there.
 
 Thanks,
 Jürgen
 
 

-gdb lyx 
GNU gdb (GDB) Fedora 7.7.1-18.fc20
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type show copying
and show warranty for details.
This GDB was configured as x86_64-redhat-linux-gnu.
Type show configuration for configuration details.
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/.
Find the GDB manual and other documentation resources online at:
http://www.gnu.org/software/gdb/documentation/.
For help, type help.
Type apropos word to search for commands related to word...
Reading symbols from lyx...Reading symbols from 
/home/pdupre/Dunkerque/Projects/ANR_2014/lyx...(no debugging symbols 
found)...done.
(no debugging symbols found)...done.
Missing separate debuginfos, use: debuginfo-install lyx-2.1.1-1.fc20.x86_64
(gdb) run
Starting program: /usr/bin/lyx 
[Thread debugging using libthread_db enabled]
Using host libthread_db library /lib64/libthread_db.so.1.
Traceback (most recent call last):
  File /usr/share/gdb/auto-load/usr/lib64/libgobject-2.0.so.0.3800.2-gdb.py, 
line 9, in module
from gobject import register
  File /usr/share/glib-2.0/gdb/gobject.py, line 3, in module
import gdb.backtrace
ImportError: No module named backtrace
Traceback (most recent call last):
  File /usr/share/gdb/auto-load/usr/lib64/libgobject-2.0.so.0.3800.2-gdb.py, 
line 9, in module
from gobject import register
  File /usr/share/glib-2.0/gdb/gobject.py, line 3, in module
import gdb.backtrace
ImportError: No module named backtrace
Detaching after fork from child process 15726.
Detaching after fork from child process 15728.
Detaching after fork from child process 15729.
[New Thread 0x7fffec08d700 (LWP 15730)]
Detaching after fork from child process 15735.
Detaching after fork from child process 15736.
Detaching after fork from child process 15737.
Detaching after fork from child process 15738.
Detaching after fork from child process 15739.
Detaching after fork from child process 15740.
Detaching after fork from child process 15741.
Detaching after fork from child process 15742.
Detaching after fork from child process 15743.
Detaching after fork from child process 15744.
Detaching after fork from child process 15745.
Detaching after fork from child process 15746.
Detaching after fork from child process 15747.
Detaching after fork from child process 15748.
Detaching after fork from child process 15749.
Detaching after fork from child process 15750.
Detaching after fork from child process 15751.
Detaching after fork from child process 15752.
Detaching after fork from child process 15753.
Detaching after fork from child process 15754.
Detaching after fork from child process 15755.
Detaching after fork from child process 15756.
Detaching after fork from child process 15757.
Detaching after fork from child process 15758.
Detaching after fork from child process 15759.
Detaching after fork from child process 15760.
Detaching after fork from child process 15761.
Detaching after fork from child process 15762.
Detaching after fork from child process 15763.
Detaching after fork from child process 15764.
Detaching after fork

Re: Re: crash

[Scott Kostyshak]

On Mon, Sep 22, 2014 at 12:09 PM, Jürgen Spitzmüller sp...@lyx.org wrote:

 --  Weitergeleitete Nachricht  --

 Betreff: Re: crash
 Datum: Montag 22 September 2014, 18:00:17
 Von: Patrick Dupre pdu...@gmx.com
 An: Jürgen Spitzmüller sp...@lyx.org

 Hello Jurgen,

 Here a sort of trace back.

 Unfortunately, right now, I do not have time to send you examples because
 my files cannot be disseminated as is.

 Sorry.
 When I will have more time, I will try to do it!

 Regards.

 ===
  Patrick DUPRÉ | | email: pdu...@gmx.com
  Laboratoire de Physico-Chimie de l'Atmosphère | |
  Université du Littoral-Côte d'Opale   | |
  Tel.  (33)-(0)3 28 23 76 12   | | Fax: 03 28 65 82 44
  189A, avenue Maurice Schumann | | 59140 Dunkerque, France
 ===

Hi Patrick,

It's useful if you respond to the list (don't worry if you forgot, I
forget also sometimes). Also, let's note for archival purposes
(someone might have the same problem you're having and find through
google this email thread, which is archived) that you opened at ticket
here: http://www.lyx.org/trac/ticket/9278

Best,

Scott

crash

[Patrick Dupre]

Hello,

I still have this continuous issue that if I have a first document 
.lyx file open and that I want to open another "complex" lyx file.
It just crashes!

SIGSEGV signal caught!

It starting to really bother me!

Thank.

===
 Patrick DUPRÉ | | email: pdu...@gmx.com
 Laboratoire de Physico-Chimie de l'Atmosphère | |
 Université du Littoral-Côte d'Opale   | |
 Tel.  (33)-(0)3 28 23 76 12   | | Fax: 03 28 65 82 44
 189A, avenue Maurice Schumann | | 59140 Dunkerque, France
===

Re: crash

[Jürgen Spitzmüller]

Am Montag 22 September 2014, 17:37:16 schrieb Patrick Dupre:
> Hello,
> 
> I still have this continuous issue that if I have a first document
> .lyx file open and that I want to open another "complex" lyx file.
> It just crashes!
> 
> SIGSEGV signal caught!
> 
> It starting to really bother me!

In order to help, we need more information:

* a backtrace of the crash (http://wiki.lyx.org/FAQ/FurtherHelp#backtrace)
* an example document

Did you already file a bug report for this? If so, what is the ticket number? 
If not, please do and provide all necessary information there.

Thanks,
Jürgen

Fwd: Re: crash

[Jürgen Spitzmüller]

--  Weitergeleitete Nachricht  --

Betreff: Re: crash
Datum: Montag 22 September 2014, 18:00:17
Von: Patrick Dupre <pdu...@gmx.com>
An: Jürgen Spitzmüller <sp...@lyx.org>

Hello Jurgen,

Here a sort of trace back.

Unfortunately, right now, I do not have time to send you examples because
my files cannot be disseminated as is.

Sorry.
When I will have more time, I will try to do it!

Regards.

===
 Patrick DUPRÉ | | email: pdu...@gmx.com
 Laboratoire de Physico-Chimie de l'Atmosphère | |
 Université du Littoral-Côte d'Opale   | |
 Tel.  (33)-(0)3 28 23 76 12   | | Fax: 03 28 65 82 44
 189A, avenue Maurice Schumann | | 59140 Dunkerque, France
===


> Sent: Monday, September 22, 2014 at 5:45 PM
> From: "Jürgen Spitzmüller" <sp...@lyx.org>
> To: lyx-users@lists.lyx.org
> Subject: Re: crash
>
> Am Montag 22 September 2014, 17:37:16 schrieb Patrick Dupre:
> > Hello,
> > 
> > I still have this continuous issue that if I have a first document
> > .lyx file open and that I want to open another "complex" lyx file.
> > It just crashes!
> > 
> > SIGSEGV signal caught!
> > 
> > It starting to really bother me!
> 
> In order to help, we need more information:
> 
> * a backtrace of the crash (http://wiki.lyx.org/FAQ/FurtherHelp#backtrace)
> * an example document
> 
> Did you already file a bug report for this? If so, what is the ticket number? 
> If not, please do and provide all necessary information there.
> 
> Thanks,
> Jürgen
> 
> 
>
-gdb lyx 
GNU gdb (GDB) Fedora 7.7.1-18.fc20
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from lyx...Reading symbols from 
/home/pdupre/Dunkerque/Projects/ANR_2014/lyx...(no debugging symbols 
found)...done.
(no debugging symbols found)...done.
Missing separate debuginfos, use: debuginfo-install lyx-2.1.1-1.fc20.x86_64
(gdb) run
Starting program: /usr/bin/lyx 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Traceback (most recent call last):
  File "/usr/share/gdb/auto-load/usr/lib64/libgobject-2.0.so.0.3800.2-gdb.py", 
line 9, in 
from gobject import register
  File "/usr/share/glib-2.0/gdb/gobject.py", line 3, in 
import gdb.backtrace
ImportError: No module named backtrace
Traceback (most recent call last):
  File "/usr/share/gdb/auto-load/usr/lib64/libgobject-2.0.so.0.3800.2-gdb.py", 
line 9, in 
from gobject import register
  File "/usr/share/glib-2.0/gdb/gobject.py", line 3, in 
import gdb.backtrace
ImportError: No module named backtrace
Detaching after fork from child process 15726.
Detaching after fork from child process 15728.
Detaching after fork from child process 15729.
[New Thread 0x7fffec08d700 (LWP 15730)]
Detaching after fork from child process 15735.
Detaching after fork from child process 15736.
Detaching after fork from child process 15737.
Detaching after fork from child process 15738.
Detaching after fork from child process 15739.
Detaching after fork from child process 15740.
Detaching after fork from child process 15741.
Detaching after fork from child process 15742.
Detaching after fork from child process 15743.
Detaching after fork from child process 15744.
Detaching after fork from child process 15745.
Detaching after fork from child process 15746.
Detaching after fork from child process 15747.
Detaching after fork from child process 15748.
Detaching after fork from child process 15749.
Detaching after fork from child process 15750.
Detaching after fork from child process 15751.
Detaching after fork from child process 15752.
Detaching after fork from child process 15753.
Detaching after fork from child process 15754.
Detaching after fork from child process 15755.
Detaching after fork from child process 15756.
Detaching after fork from child process 15757.
Detachi

Re: Re: crash

[Scott Kostyshak]

On Mon, Sep 22, 2014 at 12:09 PM, Jürgen Spitzmüller <sp...@lyx.org> wrote:
>
> --  Weitergeleitete Nachricht  --
>
> Betreff: Re: crash
> Datum: Montag 22 September 2014, 18:00:17
> Von: Patrick Dupre <pdu...@gmx.com>
> An: Jürgen Spitzmüller <sp...@lyx.org>
>
> Hello Jurgen,
>
> Here a sort of trace back.
>
> Unfortunately, right now, I do not have time to send you examples because
> my files cannot be disseminated as is.
>
> Sorry.
> When I will have more time, I will try to do it!
>
> Regards.
>
> ===
>  Patrick DUPRÉ | | email: pdu...@gmx.com
>  Laboratoire de Physico-Chimie de l'Atmosphère | |
>  Université du Littoral-Côte d'Opale   | |
>  Tel.  (33)-(0)3 28 23 76 12   | | Fax: 03 28 65 82 44
>  189A, avenue Maurice Schumann | | 59140 Dunkerque, France
> ===

Hi Patrick,

It's useful if you respond to the list (don't worry if you forgot, I
forget also sometimes). Also, let's note for archival purposes
(someone might have the same problem you're having and find through
google this email thread, which is archived) that you opened at ticket
here: http://www.lyx.org/trac/ticket/9278

Best,

Scott

Re: LyX crash and cannot open file

[Wolfgang Engelmann]

Normally if you load your lyx file and there is an emergency file it 
tells you and if you agree it loads it. You are than asked whether you 
would like to keep the emergency file, and I would suggest to keep it.

Wolfgang
Am 15.05.2014 04:20, schrieb Steve Burnham:

Forum,

I was working on my thesis and tried to change some line spacing and fonts and 
LyX crashed on me and I cannot get the file to open up anymore (LyX freezes 
when I try to open it).  Under normal circumstances I have an online backup 
always running and I can just roll back to 15 minutes previously.  
Unfortunately I was doing this work in the airport and on the airplane so I had 
no internet access.  I have the following files:

Thesis 2.lyx and Thesis 2.lyx.emergency

I assume the emergency was made when LyX crashed on me as a means to restore 
any lost work.  I noticed that the .lyx file can be opened in a text editor and 
it appears as LaTeX code.  Because of these two files I am hoping there is a 
way to possibly de-corrupt the file that crashed and get it opened up again.

I am using LyX 2.1.0 on OSX 10.9.2.  I’m attaching the crash report in case it 
means something to anyone.  It’s beyond my understanding of coding.

When all is said and done it’s only about 6 hours worth of work and I have all 
of my thesis in an unformatted word document so if it cannot be fixed there’s 
no lost content, only time spent formatting.  Any help or insight is 
appreciated.



-Steve

Re: LyX crash and cannot open file

[Jürgen Spitzmüller]

2014-05-15 4:20 GMT+02:00 Steve Burnham:

 Forum,

 I was working on my thesis and tried to change some line spacing and fonts
 and LyX crashed on me and I cannot get the file to open up anymore (LyX
 freezes when I try to open it).  Under normal circumstances I have an
 online backup always running and I can just roll back to 15 minutes
 previously.  Unfortunately I was doing this work in the airport and on the
 airplane so I had no internet access.  I have the following files:

 Thesis 2.lyx and Thesis 2.lyx.emergency

 I assume the emergency was made when LyX crashed on me as a means to
 restore any lost work.  I noticed that the .lyx file can be opened in a
 text editor and it appears as LaTeX code.  Because of these two files I am
 hoping there is a way to possibly de-corrupt the file that crashed and get
 it opened up again.

 I am using LyX 2.1.0 on OSX 10.9.2.  I’m attaching the crash report in
 case it means something to anyone.  It’s beyond my understanding of coding.

 When all is said and done it’s only about 6 hours worth of work and I have
 all of my thesis in an unformatted word document so if it cannot be fixed
 there’s no lost content, only time spent formatting.  Any help or insight
 is appreciated.


Of course this should not happen.

In case the files are really corrupted, that is, if the .lyx and/or the
.lyx.emergency file do not end with
\end_body
\end_document

you can check if you have a working backup in your backups directory (see
Tools  Preferences  Paths).

HTH
Jürgen





 -Steve

Re: LyX crash and cannot open file

[aparsloe]

On 15/05/2014 6:37 p.m., Jürgen Spitzmüller wrote:

In case the files are really corrupted, that is, if the .lyx and/or the 
.lyx.emergency file do not end with

\end_body
\end_document

you can check if you have a working backup in your backups directory 
(see Tools  Preferences  Paths).


HTH
Jürgen

I've often thought that the backup files should be more accessible -- 
for instance through the normal File  Open dialog. At present the 
dialog has a combo box (is that the term?) at the lower right offering 
LyX Documents (*.lyx) and a triangular arrow suggesting there are more 
options below. But there aren't. It would be good to see *.lyx~ files 
there and to have the ability to open them. I realise naming conflicts 
would need to be sorted out, but the present accessibility of backup 
files is awkward (which may be a good thing of course).


Andrew

Re: LyX crash and cannot open file

[Steve Burnham]

On May 15, 2014 at 03:40:54 AM, aparsloe (apars...@clear.net.nz) wrote:

On 15/05/2014 6:37 p.m., Jürgen Spitzmüller wrote: 

In case the files are really corrupted, that is, if the .lyx and/or the 
.lyx.emergency file do not end with 
\end_body 
\end_document 

you can check if you have a working backup in your backups directory 
(see Tools  Preferences  Paths). 

HTH 
Jürgen 


I checked my backups directory and just my luck, there is no directory listed 
for backups.  I opened up the .lyx file and there is no \end_body or 
\end_document anywhere in the file.  The document ends with “\begin_inset 
Tabular”.  It actually looks like the entire document isn’t even there, 
possibly ending at chapter 5 (of 8 total plus appendix).  

I tried to add \end_body and \end_document to the end of the .lyx file but when 
I open it up now I just get that the file ended unexpectedly, which means that 
it is probably corrupted.



On May 15, 2014 at 24:29:12 AM, Wolfgang Engelmann (engelm...@uni-tuebingen.de) 
wrote:

Normally if you load your lyx file and there is an emergency file it 
tells you and if you agree it loads it. You are than asked whether you 
would like to keep the emergency file, and I would suggest to keep it. 
Wolfgang 


Unfortunately I cannot even get to the point where I am asked to keep the 
emergency file.  LyX just completely freezes as soon as I try to open up the 
file.  Any other file opens  up just fine, it’s only this one. 

I installed LyX and MikTeX on my Windows machine at school to see if this was a 
problem isolated to OSX, unfortunately LyX freezes when opening the file on 
Windows as well (Windows 8.1, LyX 2.1.0).  

-Steve