I have the documents that I use all stored on Microsoft's OneDrive in the cloud. Every time I go to open them, it goes through the recovery process. I make a one letter change, save, close writer, reopen, and have to recover. It seems to be recovering OK, but it should not be doing this. I have just downloaded the latest version and am running on Windows 10, 64 bit along with the 64 bit version of OfficeLibre. The properties on the desktop Icon uses C:\Users\user\OneDrive\!Documents\filename.odt
This has been going on for months. Does anyone have a suggestion? Else, I guess I am going to have to pull my data back to the PC. I just lost data because of this.
OK. Has nothing to do with the cloud. It Recovers EVERY TIME. This is getting to be a real pain in the behind. Not only that, it doesn't recover just the file I am editing. Seems to be every file I have, only tow now. Sometimes there are multiple recover files out there for a single document. That last one was how I lost data. I am also now starting to get regular crashes during the recover process. There are probably at least 10 crash reports sent in over the last couple of days. This is 5.2.0.4 release. I hate to do this, but I'm afraid its time to start looking for something else. Its having too many bugs. I am also having problems with toc and the navigator window.
Hello Sccrow, Sorry for the delayed reply. How were you accessing your OneDrive? When it was crashing with 5.2, were you able to send in the crash report to us?
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-20170502
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-20170531
I finally managed to get this resolved. Its been a while, and I do not recall what I did to fix it. Sorry