Description: 1. Load a file using Webdav (eg XLSX file) 2. Edit it, do not save 3. Crash Libreoffice so that it freezes and has to be SIGKILLed 4. Restart Libreoffice 5. It will ask whether to recover file and claim success in doing so (before that, it'll ask for the master password to unlock the WebDAV location) Expected: It'll then show me my file as it was before I SIGKILLed it Actual: It showed the file as it was on the WebDAV share when last saving it Result: the autorecovery procedure is not usable with files on WebDAV shares. Steps to Reproduce: see above Actual Results: see above Expected Results: see above Reproducible: Always User Profile Reset: No Additional Info: [Information automatically included from LibreOffice] Locale: de Module: SpreadsheetDocument [Information guessed from browser] OS is 64bit: yes NB: The OS was autofilled by Libreoffice as "Mac OS X (All)", which this form claims doesn't exist. I removed it.
Thank you Jens. 7.4 has reached end of life, and autoSave / autoRecovery improvements are coming to LibreOffice 24.2. Could you please: - test the same thing with a daily build and report if anything has changed? https://dev-builds.libreoffice.org/daily/master/current.html (it will install alongside a stable installation – which I also recommend updating in any case) - share the full information copied from LibreOffice > About. There is also bug 98576 and bug 151708 that might be relevant. Thank you!
Dear Jens, 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
Dear Jens, 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-FollowUp