Created attachment 161213 [details] Backup of LibreOffice file I was working on when it crashed. Mostly copied text. This bug was filed from the crash reporting server and is br-a7aaebef-6577-4584-9d88-377673a4906a. ========================================= I copied some text from a web page to my open document. It had a frame around it that I didn't want, so I decided to delete it and start again. I typed ctrl-z, but nothing happened. Then I typed ctrl-z two or three more times and Libre Office crashed. I had two other documents open. I have tried to restart in safe mode twice with no success. Thank you for your help.
2 things you can try: - upgrade to LO 6.4.4 - apply what https://wiki.documentfoundation.org/QA/FirstSteps indicates If you still reproduce this, please provide a bit more detailed procedure to reproduce this (which web page, what part did you copy paste, etc.)
Thanks for the report. It's indeed probably related to the frame + undo. There already few bugs around in that area
Dear brad_voltmer, 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
Yes. I was using version 5.7. I have since upgraded to version 7. I am not experiencing any problems at this time. Thank you for your help. Brad
(In reply to brad_voltmer from comment #4) > Yes. I was using version 5.7. I have since upgraded to version 7. I am not > experiencing any problems at this time. Thank you for your help. Brad Thanks for retesting the issue with the latest version. Setting to RESOLVED WORKSFORME since the commit fixing this issue hasn't been identified.