LyX 2.1.0 on Mac incorrectly saves a file

[Paweł Doligalski]

Hello,

I encountered the following bug. While working on a document "temp
notes.lyx", LyX froze. I closed LyX and opened again, but then I couldn't
open the file anymore. It turns out that the file was saved in an incorrect
way: a few hundred bottom lines were missing, includng my content and latex
code. I enclose the incorrectly saved file (temp notes bugged.lyx) as well
as the original file I recovered (temp notes original.lyx). As far as I can
tell, the original file shows well how the file looked like just before the
crash.

I was using LyX 2.1.0. on Mac OS 10.9.4. Let me know if I can give you any
more information about my configuration.

Since I was using obsolete version of LyX, it's possible that the bug has
already been corrected. However, I couldn't find bugs reported for LyX
2.1.0 on your bug report website, so I was not able to check that.

Best,
Paweł

[Stephan Witt]

Post by Paweł Doligalski
Hello,
I encountered the following bug. While working on a document "temp notes.lyx", LyX froze. I closed LyX and opened again, but then I couldn't open the file anymore. It turns out that the file was saved in an incorrect way: a few hundred bottom lines were missing, includng my content and latex code. I enclose the incorrectly saved file (temp notes bugged.lyx) as well as the original file I recovered (temp notes original.lyx). As far as I can tell, the original file shows well how the file looked like just before the crash.
I was using LyX 2.1.0. on Mac OS 10.9.4. Let me know if I can give you any more information about my configuration.
Since I was using obsolete version of LyX, it's possible that the bug has already been corrected. However, I couldn't find bugs reported for LyX 2.1.0 on your bug report website, so I was not able to check that.

Look at bug #9049, I may fit.

If it matches (I think so), please attach your Crash Log protocol or send it to the list.

Stephan

Post by Paweł Doligalski
Best,
Paweł
<temp notes bugged.lyx><temp notes original.lyx>

[Scott Kostyshak]

Post by Stephan Witt
Look at bug #9049, I may fit.
If it matches (I think so), please attach your Crash Log protocol or send it to the list.

Yes please do so. If you want a quick recap (from what I understand),
LyX 2.1.1 improves on the bug in the sense that there should not be
data loss, although you will still get the crash; LyX 2.1.2 I believe
will not have the crash.

Scott

[Paweł Doligalski]

Thanks! What do you mean by Crash Log protocol?

If you mean running LyX via terminal and sending you the output, then there
is the same problem as you encountered while solving the bug: I do not know
what triggers the crash.

Post by Stephan Witt
Crash Log protocol

[Stephan Witt]

Post by Paweł Doligalski
Thanks! What do you mean by Crash Log protocol?

If a program on a Mac crashes normally you see the Crash Log and get asked if it should be send to Apple.

The Crash Log itself is stored somewhere in your user directory.

One possibility to locate it is with the Console program. Start it with the help of Spotlight (type console in the upper right most search field). The there should be the list of the Crash or Diagnostic Reports. The LyX ones are named "lyx_2014-08 …". There is an menu item "E-Mail" or similar to send it.

Stephan

Post by Paweł Doligalski
If you mean running LyX via terminal and sending you the output, then there is the same problem as you encountered while solving the bug: I do not know what triggers the crash.
Crash Log protocol

[Paweł Doligalski]

Thanks for instructions, here it goes.

Post by Stephan Witt

Post by Paweł Doligalski
Thanks! What do you mean by Crash Log protocol?

If a program on a Mac crashes normally you see the Crash Log and get asked
if it should be send to Apple.
The Crash Log itself is stored somewhere in your user directory.
One possibility to locate it is with the Console program. Start it with
the help of Spotlight (type console in the upper right most search field).
The there should be the list of the Crash or Diagnostic Reports. The LyX
ones are named "lyx_2014-08 
". There is an menu item "E-Mail" or similar
to send it.
Stephan

Post by Paweł Doligalski
If you mean running LyX via terminal and sending you the output, then

there is the same problem as you encountered while solving the bug: I do
not know what triggers the crash.

Post by Paweł Doligalski
Crash Log protocol

[Paweł Doligalski]

Hello everybody,

Unfortunately, very simmilar crash just happened to me again, this time on
LyX 2.1.1. Just as in the previous case, LyX crashed and there was a data
loss. However, this time the corrupted file does not end with "\begin_inset
Tabular".

I enclose a crash report and the file before and after the data loss.

Best,
Paweł

Post by Paweł Doligalski
Thanks for instructions, here it goes.

Post by Stephan Witt

Post by Paweł Doligalski
Thanks! What do you mean by Crash Log protocol?

If a program on a Mac crashes normally you see the Crash Log and get
asked if it should be send to Apple.
The Crash Log itself is stored somewhere in your user directory.
One possibility to locate it is with the Console program. Start it with
the help of Spotlight (type console in the upper right most search field).
The there should be the list of the Crash or Diagnostic Reports. The LyX
ones are named "lyx_2014-08 
". There is an menu item "E-Mail" or similar
to send it.
Stephan

Post by Paweł Doligalski
If you mean running LyX via terminal and sending you the output, then

there is the same problem as you encountered while solving the bug: I do
not know what triggers the crash.

Post by Paweł Doligalski
Crash Log protocol

[Richard Heck]

Post by Paweł Doligalski
Hello everybody,
Unfortunately, very simmilar crash just happened to me again, this
time on LyX 2.1.1. Just as in the previous case, LyX crashed and there
was a data loss. However, this time the corrupted file does not end
with "\begin_inset Tabular".
I enclose a crash report and the file before and after the data loss.

Thanks for this. We believe this crash has been solved for 2.1.2, and
your file suggests that our diagnosis was correct: It ends with a
multicolumn cell. The crash is also in to_utf8, which is where we
eventually were led. See
http://www.lyx.org/trac/ticket/9049
for the details.

We should be releasing 2.1.2 in early September, but of course you can
compile it now if you wish.

Richard

Post by Paweł Doligalski
Best,
Paweł
Thanks for instructions, here it goes.
Am 22.08.2014 um 16:32 schrieb Paweł Doligalski

Post by Paweł Doligalski
Thanks! What do you mean by Crash Log protocol?

If a program on a Mac crashes normally you see the Crash Log
and get asked if it should be send to Apple.
The Crash Log itself is stored somewhere in your user directory.
One possibility to locate it is with the Console program.
Start it with the help of Spotlight (type console in the upper
right most search field). The there should be the list of the
Crash or Diagnostic Reports. The LyX ones are named
"lyx_2014-08 
". There is an menu item "E-Mail" or similar to
send it.
Stephan

Post by Paweł Doligalski
If you mean running LyX via terminal and sending you the

output, then there is the same problem as you encountered
while solving the bug: I do not know what triggers the crash.

Post by Paweł Doligalski
Crash Log protocol

[Stephan Witt]

Post by Paweł Doligalski
Hello everybody,
Unfortunately, very simmilar crash just happened to me again, this time on LyX 2.1.1. Just as in the previous case, LyX crashed and there was a data loss. However, this time the corrupted file does not end with "\begin_inset Tabular".
I enclose a crash report and the file before and after the data loss.

Thanks for this. We believe this crash has been solved for 2.1.2, and your file suggests that our diagnosis was correct: It ends with a multicolumn cell. The crash is also in to_utf8, which is where we eventually were led. See
http://www.lyx.org/trac/ticket/9049
for the details.
We should be releasing 2.1.2 in early September, but of course you can compile it now if you wish.
Richard

I'll make a Disk Image for Mac ASAP

Stephan

Post by Paweł Doligalski
Best,
Paweł

Post by Paweł Doligalski
Thanks for instructions, here it goes.

Post by Stephan Witt

Post by Paweł Doligalski
Thanks! What do you mean by Crash Log protocol?

If a program on a Mac crashes normally you see the Crash Log and get asked if it should be send to Apple.
The Crash Log itself is stored somewhere in your user directory.
One possibility to locate it is with the Console program. Start it with the help of Spotlight (type console in the upper right most search field). The there should be the list of the Crash or Diagnostic Reports. The LyX ones are named "lyx_2014-08 
". There is an menu item "E-Mail" or similar to send it.
Stephan

Post by Paweł Doligalski
If you mean running LyX via terminal and sending you the output, then there is the same problem as you encountered while solving the bug: I do not know what triggers the crash.
Crash Log protocol

[Stephan Witt]

Post by Stephan Witt

Post by Paweł Doligalski
Hello everybody,
Unfortunately, very simmilar crash just happened to me again, this time on LyX 2.1.1. Just as in the previous case, LyX crashed and there was a data loss. However, this time the corrupted file does not end with "\begin_inset Tabular".
I enclose a crash report and the file before and after the data loss.

Thanks for this. We believe this crash has been solved for 2.1.2, and your file suggests that our diagnosis was correct: It ends with a multicolumn cell. The crash is also in to_utf8, which is where we eventually were led. See
http://www.lyx.org/trac/ticket/9049
for the details.
We should be releasing 2.1.2 in early September, but of course you can compile it now if you wish.
Richard

I'll make a Disk Image for Mac ASAP

This is the location for an "snapshot release" of LyX-2.1.2dev as of git hash fa82d6b327990cf7e6a67f9ecdb1915583f928a9.

https://dl.dropboxusercontent.com/u/27842660/LyX-2.1.2dev-fa82d6b%2Bqt4-cocoa.dmg
https://dl.dropboxusercontent.com/u/27842660/LyX-2.1.2dev-fa82d6b%2Bqt4-cocoa.dmg.sig

Here is the tar ball produced by make dist with this git checkout of 2.1.x. Just for the record...

https://dl.dropboxusercontent.com/u/27842660/LyX-2.1.2dev-fa82d6b.tar.gz
https://dl.dropboxusercontent.com/u/27842660/LyX-2.1.2dev-fa82d6b.tar.gz.sig

Stephan

[Paweł Doligalski]

Thanks!

Post by Paweł Doligalski

Post by Stephan Witt

Post by Richard Heck

Post by Paweł Doligalski
Hello everybody,
Unfortunately, very simmilar crash just happened to me again, this

time on LyX 2.1.1. Just as in the previous case, LyX crashed and there was
a data loss. However, this time the corrupted file does not end with
"\begin_inset Tabular".

Post by Stephan Witt

Post by Richard Heck

Post by Paweł Doligalski
I enclose a crash report and the file before and after the data loss.

Thanks for this. We believe this crash has been solved for 2.1.2, and

your file suggests that our diagnosis was correct: It ends with a
multicolumn cell. The crash is also in to_utf8, which is where we
eventually were led. See

Post by Stephan Witt

Post by Richard Heck
http://www.lyx.org/trac/ticket/9049
for the details.
We should be releasing 2.1.2 in early September, but of course you can

compile it now if you wish.

Post by Stephan Witt

Post by Richard Heck
Richard

I'll make a Disk Image for Mac ASAP

This is the location for an "snapshot release" of LyX-2.1.2dev as of git
hash fa82d6b327990cf7e6a67f9ecdb1915583f928a9.
https://dl.dropboxusercontent.com/u/27842660/LyX-2.1.2dev-fa82d6b%2Bqt4-cocoa.dmg
https://dl.dropboxusercontent.com/u/27842660/LyX-2.1.2dev-fa82d6b%2Bqt4-cocoa.dmg.sig
Here is the tar ball produced by make dist with this git checkout of
2.1.x. Just for the record...
https://dl.dropboxusercontent.com/u/27842660/LyX-2.1.2dev-fa82d6b.tar.gz
https://dl.dropboxusercontent.com/u/27842660/LyX-2.1.2dev-fa82d6b.tar.gz.sig
Stephan

[Richard Heck]

Post by Stephan Witt

Post by Paweł Doligalski
Hello,
I encountered the following bug. While working on a document "temp notes.lyx", LyX froze. I closed LyX and opened again, but then I couldn't open the file anymore. It turns out that the file was saved in an incorrect way: a few hundred bottom lines were missing, includng my content and latex code. I enclose the incorrectly saved file (temp notes bugged.lyx) as well as the original file I recovered (temp notes original.lyx). As far as I can tell, the original file shows well how the file looked like just before the crash.
I was using LyX 2.1.0. on Mac OS 10.9.4. Let me know if I can give you any more information about my configuration.
Since I was using obsolete version of LyX, it's possible that the bug has already been corrected. However, I couldn't find bugs reported for LyX 2.1.0 on your bug report website, so I was not able to check that.

Look at bug #9049, I may fit.
If it matches (I think so), please attach your Crash Log protocol or send it to the list.

Yes, this is definitely #9049: The file ends with "\begin_inset Tabular".

I also note that the table in question contains a multi-column cell,
which we believe to be the source of the crash.

Richard

[Will Furnass]

I encountered what appears to be a similar problem to bug #9049 over
the weekend where copying a table with some multi-column cells from a
UTF-8 encoded file in one instance of LyX to another instance of LyX
caused file corruption when the file pasted into was then saved (LyX
crashes when writing the part of the file corresponding to the table).
This happened when using LyX 2.1.1.1 and the table in this LyX file:

http://pastebin.com/VzrXVP3G

Tried and thankfully failed to reproduce the problem today using the
tip of the master branch so it looks like commit 54c2ab2 has fixed my
problem!

Cheers,

Will

Post by Richard Heck

Post by Stephan Witt

Post by Paweł Doligalski
Hello,
I encountered the following bug. While working on a document "temp
notes.lyx", LyX froze. I closed LyX and opened again, but then I couldn't
open the file anymore. It turns out that the file was saved in an incorrect
way: a few hundred bottom lines were missing, includng my content and latex
code. I enclose the incorrectly saved file (temp notes bugged.lyx) as well
as the original file I recovered (temp notes original.lyx). As far as I can
tell, the original file shows well how the file looked like just before the
crash.
I was using LyX 2.1.0. on Mac OS 10.9.4. Let me know if I can give you
any more information about my configuration.
Since I was using obsolete version of LyX, it's possible that the bug has
already been corrected. However, I couldn't find bugs reported for LyX 2.1.0
on your bug report website, so I was not able to check that.

Look at bug #9049, I may fit.
If it matches (I think so), please attach your Crash Log protocol or send it to the list.

Yes, this is definitely #9049: The file ends with "\begin_inset Tabular".
I also note that the table in question contains a multi-column cell, which
we believe to be the source of the crash.
Richard

[Richard Heck]

Post by Will Furnass
I encountered what appears to be a similar problem to bug #9049 over
the weekend where copying a table with some multi-column cells from a
UTF-8 encoded file in one instance of LyX to another instance of LyX
caused file corruption when the file pasted into was then saved (LyX
crashes when writing the part of the file corresponding to the table).

Yes, this is exactly what we think causes #9049.

Post by Will Furnass
http://pastebin.com/VzrXVP3G
Tried and thankfully failed to reproduce the problem today using the
tip of the master branch so it looks like commit 54c2ab2 has fixed my
problem!

Excellent. Thanks for letting us know.

Richard