Lyx 2.1.1 can not open file after crash

Bug #1364271 reported by Maurice Clerc
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
lyx (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Ubuntu 14.10.
I was working on paper.lyx (about 120 Ko).

LyX crashed without any error message. After that both paper.lyx and paper.lyx.emergency were corrupted (only 12 Ko), and LyX could not open them (trying for "infinite" time, I had to use Force Quit).

The only workaround I found it that there were also a hidden file paper.lyx~ whose size was correct. I renamed it paper2.lyx, and LyX has been able to open it. Only my very last update before the crash was missing.

Revision history for this message
Scott Kostyshak (scott-kostyshak) wrote :

The only corruption bug that I'm aware of is
http://www.lyx.org/trac/ticket/9049
But yX 2.1.1 should have improved on that (although 2.1.2 will have a better fix), so perhaps this is different. However, without a backtrace or a way to reproduce, unfortunately there's nothing we can do.

Revision history for this message
Maurice Clerc (maurice-clerc) wrote : Re: [Bug 1364271] Re: Lyx 2.1.1 can not open file after crash

If it crashes again, which files do you need I send to you?

Maurice Clerc

Le 02/09/2014 19:58, Scott Kostyshak a écrit :
> The only corruption bug that I'm aware of is
> http://www.lyx.org/trac/ticket/9049
> But yX 2.1.1 should have improved on that (although 2.1.2 will have a better fix), so perhaps this is different. However, without a backtrace or a way to reproduce, unfortunately there's nothing we can do.
>
> ** Bug watch added: www.lyx.org/trac/ #9049
> http://www.lyx.org/trac/ticket/9049
>

Revision history for this message
Scott Kostyshak (scott-kostyshak) wrote :

The best would be if you could send a .lyx file (hopefully as small and anonymous as possible) and a set of detailed instructions that when followed reproduce the crash. If you cannot do that, then a backtrace would still be useful. There are a few different ways to get it (e.g. you could enable core dumping in Ubuntu), but the easiest might be to run LyX with gdb. Then if it crashes, in gdb you can type "bt" (google for more information if you're interested in this option). If none of these options sounds feasible to you, you might get more information if you run LyX from the terminal.

Thanks for your interest in helping find the problem.

Revision history for this message
Juhani Numminen (jsonic) wrote :

Did you encounter a crash like that again?

Changed in lyx (Ubuntu):
status: New → Incomplete
Revision history for this message
Maurice Clerc (maurice-clerc) wrote :

No (I am now using 2.2.3)

Le 07/09/2018 à 15:43, Juhani Numminen a écrit :
> Did you encounter a crash like that again?
>
> ** Changed in: lyx (Ubuntu)
> Status: New => Incomplete
>

Revision history for this message
Juhani Numminen (jsonic) wrote :

Thank you Maurice, let's close this bug.

Changed in lyx (Ubuntu):
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.