Description: The entire program randomly freezes and often crashes, he's to be forced to quit and restarted, and loses all new data when I switch to another window then back again, even if the other window is also a Libre document. I have lost countless hours attempting to recreate lost data due to these crashes. This is an unacceptable error. Steps to Reproduce: 1.Open a document in Libre. Type for some period of time. 2.Switch to another window. 3.Switch back to the original Libre window. Actual Results: Sometimes the bug doesn't occur, but it often does and with increasing frequency. Every update has made the problem worse. It's the only program on my computer that doesn't function properly or bugs in this manner. Expected Results: I should have been able to switch to my research material then returned to the document to continue typing. Reproducible: Sometimes User Profile Reset: No. That is a complicated process that I don't expect to have to tackle in order to make a program function as designed. Additional Info: In older versions of this software, I have typed literally thousands of pages without incident. I don't know what was altered in recent versions, but it needs to be fixed. Stop fiddling with a program when it works. User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_2) AppleWebKit/602.3.12 (KHTML, like Gecko) Version/10.0.2 Safari/602.3.12
2 things you can do: 1) update to 5.2.4 2) take a look to https://wiki.documentfoundation.org/QA/FirstSteps which talks about reset LO profile. Please don't tell me it's a complicate process to rename a folder.
@cjpresson : if the freeze is random, how are we supposed to even attempt to reproduce it ? The details you give are insufficient. I regularly type long Writer documents, with several other LibreOffice windows open at the same time (Draw, Database, etc) - I don't experience the crashes you seem to. I am also using LibreOffice 5.2.x (although the latest iteration thereof) on OSX 10.12.2. If you aren't prepared to even try resetting your user profile, or provide us with more precise detail on how and when the crashes occur and how to reproduce them, then we are going to be unable to help move this report anywhere except to the RESOLVED INSUFFICIENTDATA flag. For all we know, it could be a problem with OSX - there have already been at least two different bug reports of crashes which were linked to changes that Apple introduced in OSX 10.12 in the way it manages graphics cards. These were fixed, or partly fixed in later Apple updates.
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 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-20170830
Dear Bug Submitter, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA 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 our bug tracker Warm Regards, QA Team MassPing-NeedInfo-20170929