Re: Compiling causes LyX to crash [UPDATE]

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.

Re: Compiling causes LyX to crash [UPDATE]

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

Re: Compiling causes LyX to crash [UPDATE]

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

Re: Compiling causes LyX to crash [UPDATE]

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

Re: Compiling causes LyX to crash [UPDATE]

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

Re: Compiling causes LyX to crash [UPDATE]

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

Re: Compiling causes LyX to crash [UPDATE]

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

Compiling causes LyX to crash

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

Re: 2.4 crash report

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

Re: 2.4 crash report

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

Re: 2.4 crash report

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

Re: 2.4 crash report

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-

Re: 2.4 crash report

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

Re: 2.4 crash report

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

Re: 2.4 crash report

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): D

2.4 crash report

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

Re: how to report crash recorded with gdb

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

Re: how to report crash recorded with gdb

"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

how to report crash recorded with gdb

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

Re: lyx 2.4.0 crash

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

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

Lyx 2.3.6 crash on opening file

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 n

lyx crash on latex export

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

Re: lyx crash 2.3.3.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Just kidding, by pointing out that there are crashes and crashes :-)-O el On 2019-07-24 12:00 , Kornel Benko wrote: > Am Mittwoch, 24. Juli 2019, 11:30:01 CEST schrieb Dr Eberhard > Lisse: >> Then it wasn't really a crash :-)

Re: lyx crash 2.3.3.

tps://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 go

Re: lyx crash 2.3.3.

Le 24/07/2019 à 12:00, Kornel Benko a écrit : It was a real crash, and we definitely are interested in the cause. The fact, that lyx was able to create the emergency file means that lyx could catch some (probably also unexpected) exception. It looks like an assertion, but I might be wrong

Re: lyx crash 2.3.3.

Am Mittwoch, 24. Juli 2019, 11:30:01 CEST schrieb Dr Eberhard Lisse: > Then it wasn't really a crash :-)-O > > el > > > On 23/07/2019 17:38, Wolfgang Engelmann wrote: > [...] > > p.s. I could recover the document from the emergency file > > > > W

Re: lyx crash 2.3.3.

Then it wasn't really a crash :-)-O el On 23/07/2019 17:38, Wolfgang Engelmann wrote: [...] > p.s. I could recover the document from the emergency file > > Wolfgang

Re: lyx crash 2.3.3.

Le 23/07/2019 à 19:01, Wolfgang Engelmann a écrit : On 23.07.19 18:36, Jean-Marc Lasgouttes wrote: Le 23/07/2019 à 18:24, Wolfgang Engelmann a écrit : Being able to reproduce the issue would be the best. JMarc which means I should next time run lyx with -dbg, right? Or can I still find a

Re: lyx crash 2.3.3.

On 23.07.19 18:36, Jean-Marc Lasgouttes wrote: Le 23/07/2019 à 18:24, Wolfgang Engelmann a écrit : Being able to reproduce the issue would be the best. JMarc which means I should next time run lyx with -dbg, right? Or can I still find a file with error messages now? Or trying to

Re: lyx crash 2.3.3.

Le 23/07/2019 à 18:24, Wolfgang Engelmann a écrit : Being able to reproduce the issue would be the best. JMarc which means I should next time run lyx with -dbg, right? Or can I still find a file with error messages now? Or trying to reproduce the situation if you remember it a bit. How

Re: lyx crash 2.3.3.

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

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

Re: lyx crash 2.3.3.

ument from the emergency file Wolfgang p.p.s. I think, I tried to dissolve a note in a note, which led to the crash. W.

Re: lyx crash 2.3.3.

On 23.07.19 17:35, Wolfgang Engelmann wrote: Its the second time today that lyx crashed suddenly. I was trying to insert a reference via jabref. I am including the lines from the terminal, perhaps it gives some clue of what happened. Wolfgang ] (  8) lyx: lyx() [0xcb20c8] (  9)

lyx crash 2.3.3.

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:

Re: crash

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

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

Re: crash

ached 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 me

Re: crash

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

Re: crash

=== > 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 wrot

Re: crash

This code crash immediately when I try to open the inlet. === Patrick DUPRÉ | | email: pdu...@gmx.com === > S

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 t

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

Re: crash when spell checking

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

Re: crash when spell checking

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,

crash when spell checking

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,

Re: Crash

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

Crash

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

Re: Is this crash a bug?

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

Re: Is this crash a bug?

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

Re: Is this crash a bug?

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?

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

Is this crash a bug?

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)

Re: crash

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 activ

crash

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)

Re: lyx-2.3.0alpha1-1 crash

/ 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

Re: lyx-2.3.0alpha1-1 crash

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

Re: lyx-2.3.0alpha1-1 crash

-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

lyx-2.3.0alpha1-1 crash

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

Re: crash

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

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

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

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

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

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? &g

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

("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

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

LyX 2.2.0 crash from command line

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

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

Re: Crash when quitting on OS X

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

crash

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

Re: crash

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

crash

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

Re: crash

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

crash

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 cras

Re: crash

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!

Re: crash

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

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

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

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

Re: crash

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

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

Re: crash

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

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

Re: crash

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

crash

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.

Re: crash

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

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

Re: Re: crash

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

crash

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.

Re: crash

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

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

Re: Re: crash

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

crash

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.

Re: crash

> 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

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

Re: Re: crash

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

Re: LyX crash and cannot open file

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

Re: LyX crash and cannot open file

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

Re: LyX crash and cannot open file

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

Re: LyX crash and cannot open file

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

  1   2   3   4   5   6   7   8   9   10   >