Calc crashes when updating link to another spreadsheet
Please attach a short sample file and the one linked, to test.
The attachments would be two .ods spreadsheets but the system will only allow me to attach text or image files.
(In reply to Michael Dewsbury from comment #2) > The attachments would be two .ods spreadsheets but the system will only > allow me to attach text or image files. Look for the "Add an attachment" link in the page of the report bug 156288. Once you click on that link, you will see a button to add one file, which can be an ods file, with some additional text for the comment. After you click "submit", the file will be attached to the report and a new comment will be added. Repeat the steps for the second file. Please eliminate any non-essential data in the files, making the file as minimal as possible, just to replicate the problem. https://wiki.documentfoundation.org/QA/Bugzilla/Sanitizing_Files_Before_Submission I wonder whether there is some crash information generated by LO or by your OS that you could add to the report.
Dear Michael Dewsbury, 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 INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/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 MassPing-NeedInfo-Ping
I have not been able to replicate the error.
Ok, let's close. Hopefully, if you get a crash, you will be offered to submit a crash report. This will allow developers to attempt a fix even just by reading the code (although a test case is always better).