This bug was filed from the crash reporting server and is br-d518197b-858e-458a-a565-c76a80cf0f43. ========================================= The file with which it happened cannot be provided as it contains private data. I cannot even reproduce the crash, but the steps involved: - copying cell (or its formula, to have the data returned based on correct cells), - pasting it above some other cells with other formulas (this probably isn't relevant), - writing one-word-text in the cell to the left of the aformentioned one, - moving vertically the 2x3 array of cells while holding the left-Alt button to move them correctly, - maybe changing the formatting of some cells to be centered, either here or before the previous step, or both, - going back and forth with ctrl-z, ctrl-y and moving the cells in between. At some action in the last step it crashed. Or it was during ctrl-s saving, but I can't be sure. I know it was saved like this a few moments before and it was fine. There was another calc document opened in the background, and both were closed due to the crash (don't know if calc always does this or if it indicates some kind of problem that's going on here). I don't think I will be able to provide any further info.
Can you update your LibreOffice to 6.2.8 or 6.3.3 version and try retest your problem?
Dear trawa92, 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
As I said before, I couldn't reproduce it even on the version that it crashed on, let alone after updating it, since I don't know the exact steps. I can't or don't know how to reproduce it. This will probably not be resolved alone, but I think may be of some help in the future if similar bug occurs, in knowing which actions to try.
[Automated Action] NeedInfo-To-Unconfirmed
Setting to Resolved WFM.. Anyway thanks for reporting