Everytime I save the document the track changes setting changes and has to be reset manually. Also, on my computer using both Ubuntu 12.04 and 14.04 one can not see what the setting is/are in track changes - only way to know is to test by making a change and seeing if you can see it or not.
Not reproduced. You mean "Show changes" or which setting? Did you try this yet: https://wiki.documentfoundation.org/UserProfile#Resolving_corruption_in_the_user_profile Set to NEEDINFO. Change back to UNCONFIRMED after you have provided the information. Arch Linux 64-bit, KDE Plasma 5 Version: 5.2.0.0.alpha0+ Build ID: 4bf2b6b2e6641c82e2b714e394482f1a1620b436 CPU Threads: 8; OS Version: Linux 4.4; UI Render: default; Locale: fi-FI (fi_FI.UTF-8) Built on March 21st 2016
MS Word documents in LIbre Office Writer do not work properly with 'track changes'. One can NOT see what it is set at [red light, green light doesn't change - stays red]. Everytime a document is saved it reverts to show changes if set on do not show changes. Everything one closes a document even though it was saved, it prompts for 'Save Changes?' and reverts to show changes when it is set on do not show changes. I do professional editing and always edit with do not show changes, but this is now almost impossible. One has to endlessly switch back to do not show changes, as the program finds every reason to show changes.
Could you attach test file? Thanks
Thanks, I can reproduce with DOCX. Arch Linux 64-bit, KDE Plasma 5 Version: 5.2.0.0.alpha0+ Build ID: 011e65c93053c88eb752e50ef47c69872608cbcd CPU Threads: 8; OS Version: Linux 4.4; UI Render: default; Locale: fi-FI (fi_FI.UTF-8) Built on March 22nd 2016
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.2.7 or 5.3.3 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170522
*** This bug has been marked as a duplicate of bug 89991 ***