Description: FILEOPEN DOCX: File marked as changed after opening Steps to Reproduce: 1. Open the attached file 2. Save to DOCX 3. File reload 4. Look at the save icon -> Marked changed Actual Results: Changed Expected Results: There shouldn't be a change registered Reproducible: Always User Profile Reset: No Additional Info: Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 36efb384a66b6dd645e0ae80fd7df68370a9dc8b CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: nl-NL (nl_NL); UI: en-US Calc: CL
Created attachment 174239 [details] Example file
Created attachment 174240 [details] DOCX 7.3 Master
Also in Version: 6.0.6.0.0+ Build ID: c30963b8b4bbbe42a24b97aafa161eff9d7ccdd4 CPU threads: 4; OS: Windows 6.3; UI render: default; Locale: nl-NL (nl_NL); Calc: CL and in Versie: 4.4.7.2 Build ID: f3153a8b245191196a4b6b9abd1d0da16eead600 Locale: nl_NL and in Versie 4.0.0.3 (Bouw-id: 7545bee9c2a0782548772a21bc84a9dcc583b89) not in LibreOffice 3.5.7.2 Build ID: 3215f89-f603614-ab984f2-7348103-1225a5b
If on the save icon red point that means marked changed, true?
(In reply to Nina_Shtygailo from comment #4) > If on the save icon red point that means marked changed, true? Yes, you can also simply close the file.. there is a save dialog popup's if a change being registered
confirm in Version: 7.1.5.2 (x64) / LibreOffice Community Build ID: 85f04e9f809797b8199d13c421bd8a2b025d52b5 CPU threads: 4; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win Locale: en-US (ru_RU); UI: en-US Calc: CL
Seen in 43all-oldest so I set notBibisectable. Also in 7.3+.
*** This bug has been marked as a duplicate of bug 140491 ***
*** This bug has been marked as a duplicate of bug 112797 ***
Not a dup. It is triggered from this sequence of calls that comes after sfx2/source/doc/objmisc.cxx's finishedLoading()'s SetModified(false): #0 sw::DocumentStateManager::SetModified() (this=0x5555571d7500) at sw/source/core/doc/DocumentStateManager.cxx:46 #1 0x00007fffb96984fd in SwDoc::MakeFrameFormat(rtl::OUString const&, SwFrameFormat*, bool, bool) (this=0x55555bff7720, rFormatName="Root", pDerivedFrom= 0x55555a75fe20, bBroadcast=false, bAuto=true) at sw/source/core/doc/docfmt.cxx:827 #2 0x00007fffb9c13046 in SwRootFrame::SwRootFrame(SwFrameFormat*, SwViewShell*) (this=0x55555b4e79e0, pFormat=0x55555a75fe20, pSh=0x55555b0a5e10) at sw/source/core/layout/newfrm.cxx:428 #3 0x00007fffba2b37df in SwViewShell::Init(SwViewOption const*) (this=0x55555b0a5e10, pNewOpt=0x7fffffffbca0) at sw/source/core/view/vnew.cxx:126 #4 0x00007fffba2b3dd1 in SwViewShell::SwViewShell(SwDoc&, vcl::Window*, SwViewOption const*, OutputDevice*, long) (this=0x55555b0a5e10, rDocument=..., pWindow= 0x55555b9e6800, pNewOpt=0x7fffffffbca0, pOutput=0x0, nFlags=0) at sw/source/core/view/vnew.cxx:180 #5 0x00007fffb950e139 in SwCursorShell::SwCursorShell(SwDoc&, vcl::Window*, SwViewOption const*) (this=0x55555b0a5e10, rDoc=..., pInitWin=0x55555b9e6800, pInitOpt=0x7fffffffbca0) atsw/source/core/crsr/crsrsh.cxx:2995 #6 0x00007fffb9a7a36b in SwEditShell::SwEditShell(SwDoc&, vcl::Window*, SwViewOption const*) (this=0x55555b0a5e10, rDoc=..., pWindow=0x55555b9e6800, pOptions=0x7fffffffbca0) at sw/source/core/edit/edws.cxx:50 #7 0x00007fffb9b2ef11 in SwFEShell::SwFEShell(SwDoc&, vcl::Window*, SwViewOption const*) (this=0x55555b0a5e10, rDoc=..., pWindow=0x55555b9e6800, pOptions=0x7fffffffbca0) at sw/source/core/frmedt/fews.cxx:667 #8 0x00007fffba9f4035 in SwWrtShell::SwWrtShell(SwDoc&, vcl::Window*, SwView&, SwViewOption const*) (this=0x55555b0a5e10, rDoc=..., _pWin=0x55555b9e6800, rShell=..., pViewOpt=0x7fffffffbca0) at sw/source/uibase/wrtsh/wrtsh1.cxx:1990 #9 0x00007fffc19b1d6e in SwView::SwView(SfxViewFrame*, SfxViewShell*) (this=0x55555b3f8a70, _pFrame=0x55555b7aecd0, pOldSh=0x0) at sw/source/uibase/uiview/view.cxx:888 This view.cxx has a bunch of code related to SetModified, and it clearly wants changes here to be kept. So the problem doesn't seem to be with SetModified itself I don't think. The fix would have to be from finding out why the frame format is changing at this point after loading has finished.
Dear Telesto, 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