Created attachment 113852 [details] styles.xml with obfuscated private data While trying to reproduce another bug, I deleted all text from my document to publish here in order to reproduce the bug. I noticed there is still private data left in the styles.xml. I can't find a way to delete that private data, that was used in the document some time ago. I don't get why private data has arrived in the styles anyway. I can't reproduce that issue by creating an empty document with user data arriving in the styles, so I just attach the obfuscated styles.xml. It will be interesting to find out, how data of an (for the user/author) appearantly empty file is still hidden in the meta-data, just for the case of publishing .odt files instead of PDF.
Hi Massimo B - I am going to toss this into NEEDINFO status. We need the following: 1. Instructions on how to reproduce this from scratch - while it is awesome that you provided your styles file - we really need to know how to reproduce from a blank document. Enumerated is best: 1. Open writer; 2. Type multiple lines of test; 3. Set style.... Etc... Be explicit about every step and keep it simple. 2. Tell us what exactly we're looking for in that styles.xml sheet - while it says that there is private data, the text is quite long so it's best to point out exactly what you expect not to be there; 3. A simpler example (styles.xml) would be helpful as the current on is pretty complex Once you do the above please set the bug to UNCONFIRMED. Thanks for your understanding, patience, and support!
Created attachment 114021 [details] Document with header in custom page style When a page style is created, the header is included. 1. Open testpagestyleheader.odt. 2. Change page style to default. 3. Save document. Result: Header disappears. The information is still there because you can switch the page style and the header comes back. Check the document for unused custom page styles and see if the information reappears. If so, you can either delete the style or amend the header.
Following Gordo's comment, could it be "NOTABUG"?
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 INVALID due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/FDO/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 This NEEDINFO message was generated on: 2015-10-14
Dear Bug Submitter, Please read this message in its entirety before proceeding. Your bug report is being closed as INVALID 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 This INVALID Message was generated on: 2016-05-09