Description: test files saved in word(.docx) format sometime give corrupted error and non-recoverable. Steps to Reproduce: 1. create a new document in writer and save as ms word format. 2. continue making regular changes as required. 3. after editing, close the application completely and then try to reopen the document for editing later. Actual Results: 1. couple of files were corrupted and I wasn't able to reopen or recover the file. 2. didn't happen with all the files I tried with but once in which it happened was completely random. 3. in one file the issue was first noticed after a restart of computer was done and in another when trying to open it later after closing the application. Expected Results: 1. the file should've opened every time without error no matter the format in which it is saved. Reproducible: Couldn't Reproduce User Profile Reset: No Additional Info: Version: 7.0.0.3 (x64) Build ID: 8061b3e9204bef6b321a21033174034a5e2ea88e CPU threads: 12; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win Locale: en-IN (en_IN); UI: en-US Calc: CL
Is it possible to add one or two corrupted files.. or give some more specific steps.. might be related to content of the DOCX
Created attachment 168303 [details] this file was originally saved in docx format, but later was corrupted.
Attached .txt file is giving corrupted error But when I saved it in .docx format, it does not show corrupted error after opening Version: 7.2.0.0.alpha0+ (x64) Build ID: 761a672d62df1891b9f4f367a499b220ab2b33fa CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL Version: 7.0.3.1 (x64) Build ID: d7547858d014d4cf69878db179d326fc3483e082 CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL
You attached an .odt renamed as .txt. I saved it to docx and there was no problem. You need to specify what exactly is the state that causes the corruption. Set to NEEDINFO. Change back to UNCONFIRMED, if the problem persists. Change to RESOLVED WORKSFORME, if the problem went away. Arch Linux 64-bit Version: 7.4.0.0.alpha0+ / LibreOffice Community Build ID: b18c2a0024c6d33cdf142ed2adf0d127483411e8 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: kf5 (cairo+xcb) Locale: fi-FI (fi_FI.UTF-8); UI: en-US Calc: threaded Built on 26 November 2021
Dear 180010028, 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 180010028, 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