Description: Writer shows immediately after opening this file the 'There are changes to be saved' icon with the star. If you save the file as a docx, close Writer and open the docx with Writer again, the "changes to be saved" icon shows up again. This icon disappears if you save the document as a odt file and open that odt file. I prefer ODT anyway, but in my opinion this issue is an interesting behaviour, that is worth a report. Steps to Reproduce: 1. Open File Actual Results: In the menu bar should be the "normal" save icon (floppy disk icon). Expected Results: In the menu bar is the "there are changes to be saved icon (floppy disk icon with star"- Reproducible: Always User Profile Reset: No Additional Info: Searched via "file open save changes icon" for dupes, but did not found one Version: 5.4.1.2 (x64) Build-ID: ea7cb86e6eeb2bf3a5af73a8f7777ac570321527 CPU-Threads: 4; Betriebssystem:Windows 6.19; UI-Render: Standard; Gebietsschema: de-DE (de_DE); Calc: group User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:56.0) Gecko/20100101 Firefox/56.0
Created attachment 136660 [details] test case
Created attachment 136661 [details] Image of issue
Fished it from the net via google: https://www.hdm-stuttgart.de/~riekert/theses/thesis.docx
The test case seems to be saved with M$ Word 2016 (if I interpret the properties of the docx right). I opened the testcase with 'ThinkFree Office Word' and 'TextMaker 2016' and saved the file under a different name. The issue stays. I attached those files. Maybe it helps your great coders to figure out, what the common thing in those three files is, that makes Writer show the 'modified state' icon. :-)
Created attachment 136662 [details] Test case opened and saved with 'ThinkFree Office Word'
Created attachment 136663 [details] Test case opened and saved with 'TextMaker 2016'
Comment on attachment 136662 [details] Test case opened and saved with 'ThinkFree Office Word' I was wrong, Writer works with the docx, that I created with ThinkFree. I'm sorry to confuse you. :-(
I was wrong, Writer works with the docx, that I created with ThinkFree. I'm sorry to confuse you. :-( But the docx that I saved with TextMaker shows the issue, if you open it with Writer.
I opened attachments from comment 1, 5, 6 and 7 => no "changes to be saved" icon Version: 5.4.2.2 (x64) Build-ID: 22b09f6418e8c2d508a9eaf86b2399209b0990f4 CPU-Threads: 4; Betriebssystem:Windows 6.19; UI-Render: Standard; Gebietsschema: de-DE (de_DE); Calc: group
Thank you for reporting the bug. Unfortunately without clear steps to reproduce it, we cannot track down the origin of the problem. Please provide a clearer set of step-by-step instructions on how to reproduce the problem. I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the steps are provided
Created attachment 137437 [details] Minimum test case
Created attachment 137438 [details] Screenshots and description
The issue with “thesis.docx” could not be confirmed by another member. Out of curiosity I mailed the test case to a Linux user, who could confirm the issue. He uses Ubuntu 17.02 and LO 5.3.1.2. Then I created and tested this minimum test case. Would someone be so nice and open the attached file “FILEOPEN DOCX - file in modified state directly after opening of file.docx”? This is a minimum test case (5 kb) of the original file, that I attached to this report (“thesis.docx”) I had the issue in Version: 6.0.0.0.alpha1+ (x64) Build ID: 9ea8686d3573540b697b51d1e2e00bfe2d57d872 CPU threads: 4; OS: Windows 10.0; UI render: default; TinderBox: Win-x86_64@42, Branch:master, Time: 2017-10-29_07:23:44 Locale: de-DE (de_DE); Calc: CL And Version 3.6.4.3 (Build ID: 2ef5aff) I did not have the issue in LO 3.3.0, so it is not inherited. LibreOffice 3.3.0 OOO330m19 (Build:6) tag libreoffice-3.3.0.4 Can someone confirm this issue? I attached a PDF with screenshots. Many thanks in advance! :-) P. S. MS’s ‘Open XML Productivity Tool’ found no error.
I also tried with the test case from comment 11, but I couldn't reproduce it. Do you get any informations about the cahnge if you enable tracking changes? Version: 6.0.0.0.alpha1 (x64) Build ID: c1d1f859b268f650143d48f294999cda0fa57350 CPU threads: 4; OS: Windows 10.0; UI render: default; Locale: de-DE (de_DE); Calc: group
(In reply to Mike from comment #11) > Created attachment 137437 [details] > Minimum test case I confirm the problem with the file. Version: 6.0.0.0.alpha1+ (x64) Build ID: 4058d85963e371be657f531d8f30e31381a9ccab CPU threads: 4; OS: Windows 10.0; UI render: default; TinderBox: Win-x86_64@42, Branch:master, Time: 2017-11-05_22:51:05 Locale: fi-FI (fi_FI); Calc: group Arch Linux 64-bit, KDE Plasma 5 Version: 6.0.0.0.alpha1+ Build ID: 1aba1955f161cc112dab80b6b3e78ec7761616fc CPU threads: 8; OS: Linux 4.13; UI render: default; VCL: kde4; Locale: fi-FI (fi_FI.UTF-8); Calc: group Built on November 10th 2017
Created attachment 137846 [details] Manually fixed Minimum test case I have NOT a coder, but I did some trial-and-error with the minimum test case and found a hint: 1. Open minimum test case ("FILEOPEN DOCX - file in modified state directly after opening of file.docx", 5kb only) 2. Open word\document.xml in the DOCX 3. Delete the lines <w:r> <w:instrText> PAGEREF \h </w:instrText> </w:r> 4. Save the test case again as a DOCX 5. Open the new DOCX 6. New DOCX is not opened in "modified state". P.S. I opened the lines in Open XML Productivity tool and they mean: Run run2 = new Run(); FieldCode fieldCode1 = new FieldCode(); fieldCode1.Text = " PAGEREF \\h "; (Can't understand it, I'm not a coder)
Hello Dieter, :-) I tried the tracker, but it did not record anything. Maybe because the issue is before doing anything "real". It's just about opening. (Just a guess. I don't know theres things.) Regards, Mike Version: 6.0.0.0.alpha1+ (x64) Build ID: a5af0fd9f27af42cf2e8571f659cdad6e606215b CPU threads: 4; OS: Windows 10.0; UI render: default; TinderBox: Win-x86_64@42, Branch:master, Time: 2017-11-07_00:30:02 Locale: de-DE (de_DE); Calc: CL
So the issue is inherited from OOo, though earlier versions didnt have the changed saved icon, but closing the document will then ask to save changes. Assume the issue boys down to fields being update on opening. @Dieter: The DOCX-Opening meta tag is for docx files that arent able to open, not bugs that have a bug in them after opening.
** 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 with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. 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) from 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: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Still a problem in: Version: 7.2.0.0.alpha0+ (x64) Build ID: cb084f475db33a2cfc62bc9c8de37b8c3c87b3c7 CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: hu-HU (hu_HU); UI: en-US Calc: CL
*** Bug 140491 has been marked as a duplicate of this bug. ***
*** Bug 143845 has been marked as a duplicate of this bug. ***
It's about missing reference. I'm not sure this should be fixed, my take is WontFix.
The code being called is sw/source/core/doc/DocumentStateManager.cxx DocumentStateManager::SetModified() which can run if IsEnableSetModified(). This is triggered by DocumentFieldsManager::UpdateFields which ALWAYS marks as modified every time it is run. UpdateFields is called by writerfilter/source/dmapper/ModelEventListener.cxx via a rather generic uno "refresh()" call. The only way around this that I can imagine is to extend the uno call to accept "bEnableSetModified". Unless we can get away with doing this (it passes a make check): + IDocumentState& rIDS = GetDoc()->getIDocumentState(); + const bool bOldSetModified = rIDS.IsEnableSetModified(); + if (bOldSetModified) + rIDS.SetEnableSetModified(false); GetDoc()->getIDocumentStatistics().UpdateDocStat( false, true ); GetDoc()->getIDocumentFieldsAccess().UpdateFields(false); + if (bOldSetModified) + rIDS.SetEnableSetModified(true);
Dear Mike, 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 with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. 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) from https://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: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Can replicate the issue with the lastest release Version: 24.8.2.1 (X86_64) / LibreOffice Community Build ID: 0f794b6e29741098670a3b95d60478a65d05ef13 CPU threads: 12; OS: Windows 11 X86_64 (10.0 build 22631); UI render: Skia/Vulkan; VCL: win Locale: de-DE (de_DE); UI: de-DE Calc: CL threaded