https://bugs.freedesktop.org/show_bug.cgi?id=83263
--- Comment #13 from Lionel Elie Mamane <lio...@mamane.lu> --- I'm sorry your data file got corrupted. Since we don't know how to reproduce it, realistically I don't think much will happen. The corrupted file is not even recognised by "file" as a ZIP file anymore. I treated the corrupted file with "zip -F", and then it opened correctly, table and report. I'm not sure what to do QA-wise to this bug... I recognise it happened, but keeping it open without clear reproduction steps is not going to achieve anything. Robinson, what's your opinion? (In reply to robert from comment #8) > There should be a permanent backup from the *.odb-file to the backup-folder > of LibreOffice. There is an autosave every XX minutes; that's what the autorecovery uses; AFAIK one can "just" copy the autosave file before restarting LibreOffice; I think it is somewhere in ~/.config/libreoffice/4/. See "tools / options / load/save / general / save autorecovery information every XX minutes". (In reply to robert from comment #8) > (In reply to Alex Thurgood from comment #7) >> Thoughts on embedded hsqldb and known legendary instability ? > It isn't the instability of HSQLDB. Most of the problems appear while the > data were saved in the same packed file as all other things. It wouldn't be > better with an internal Firebird. I'm not so sure. Embedded HSQLDB does rather horrible tricks to "fake" that the database is saved to the odb after each transaction; I wouldn't be too surprised if the file corruption problems came from there. Embedded Firebird by design does not (and requires a "save" to save the data in the odb file). -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
