Created attachment 150915 [details] file with corrupted <w:rPrChange> While saving DOCX file, LibreOffice saves <w:rPrChange> element without inner <w:rPr> element. OXML schema: <xsd:complexType name="CT_RPrChange"> <xsd:complexContent> <xsd:extension base="CT_TrackChange"> <xsd:sequence> <xsd:element name="rPr" type="CT_RPrOriginal" minOccurs="1"/> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType> This means that <w:rPr> element MUST BE present, even if it is empty. Corrupted file (LibreOffice save result) is in attach.
@Leonid : LO6042 (the version you reported the bug against) is EOL. Does this still happen with a current GA release of LO (6152 / 6222) ? Setting NEEDINFO.
Confirmed in LibreOffice 6.2.3.0 for MacOS X
You can't confirm your own bugs. Moving it back to UNCONFIRMED until someone else confirms it.
Please attach uncorrupted file so we can test the bug Please attach an example document. Set to NEEDINFO. Change back to UNCONFIRMED after you have provided the document.
Dear leonid.melkozerov, 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 leonid.melkozerov, 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