Problem description: I have a very large spreadsheet {question terminology here - workbook} with a lot of sheets {spreadsheets} (FILE1.xls) which had caused a crash ("Block position not found" - during a row insert - bug to be reported separately). In order to try to remove sensitive information and submit the spreadsheet to report the bug I saved the spreadsheet as FILE2.xls The Title Bar showed correctly FILE2.xls The error condition occurred again now in FILE2.xls and LO-calc closed. When I started LO-calc again it showed FILE1.xls needed to be recovered - not FILE2.xls If I close all instances of LO-calc and then open File2.xls, cause the crash and restart LO-calc then FILE2.xls is (correctly) shown as needing to be recovered, Steps to reproduce: 1. .... 2. .... 3. .... Current behavior: Expected behavior: Operating System: Ubuntu Version: 4.2.0.4 rc
Can you replicate this without the complicated document by just killing the process with blank sheets or nearly blank sheets? Marking as NEEDINFO - with the given instructions it's really hard to try to reproduce so try to simplify the cause and then report in easy to read reproducible steps: 1. Open spreadsheet 2. Write ;kjas;kfjsdf in A1 3 . . . Thank you for your understanding - we have nearly a thousand bugs to get through and the simpler the instructions are the more we can move through. Once you provide easy steps mark as UNCONFIRMED and we'll go from there. Thanks!
Dear Bug Submitter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/FDO/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team
Dear Bug Submitter, Please read this message in its entirety before proceeding. Your bug report is being closed as INVALID due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of FDO