https://bugs.freedesktop.org/show_bug.cgi?id=83263
--- Comment #3 from Rainer Rillke <rainerril...@hotmail.com> --- (In reply to comment #2) > Please understand that our goal is to reproduce problems so that we can > diagnose what went wrong - just saying "this happened" doesn't give us > anything to reproduce by. For this reason, I attached the corrupted odb file. I guess someone with sufficient knowledge of this file format can very easily find out the reason it opens now with writer instead of base. So what does it mean if it starts with writer? That the zip file was not fully written or that some file inside the archive is corrupt. Note that the more information you I have, I will me more likely to get an idea how to reproduce it. Apart from that, I still suggest to add a warning to the UI on first use that base is not stable/ and or always create backups of the whole odb file *by default*. This seems to be justified as a query for corrupt base files https://bugs.freedesktop.org/buglist.cgi?order=Importance&list_id=462365&short_desc=corrupt&query_format=advanced&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&bug_status=NEEDINFO&bug_status=PLEASETEST&short_desc_type=allwordssubstr&component=Database&component=Libreoffice&product=LibreOffice returned 36 bugs, the majority of them created less than 12 months ago. Given that base is certainly less extensively used than writer or calc, I bet this is enough evidence. Please note that some bugs are inherently hard to reproduce (see bug 75717 for example), if they for example need a complex chain of actions in advance to enter in corrupt state, or time-dependent bugs, e.g. only happening on high CPU load by other programs, etc. Joel, considering the bug's description, can you recommend me a tool assisting me detecting whether libre office enters into a broken state (e.g. buffer overflows, other debugging tools and information)? BTW, reading Bug 60880#c10 it seems to me that this message could be improved linking to those tools able to assist debugging LO for newcomers. Do you recommend me filing bugs like that in future, even if I am unable to reproduce? I just wonder whether it's worth the efforts, OTH I think it's important to somehow track the occurrences of issues like that? Seeing other bug reports about corrupted files, I'd like to mention that my file system otherwise works well. The file was located on a local ntfs system; the drive is a relatively new SSD. -- 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
