Bug Hunting Session
Bug 125597 - File-Properties-General: Dissension between documentation and behaviour of saving without modification
Summary: File-Properties-General: Dissension between documentation and behaviour of sa...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
6.1.3.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: File-Properties
  Show dependency treegraph
 
Reported: 2019-05-30 17:55 UTC by Topaz Englander
Modified: 2019-06-01 07:25 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Topaz Englander 2019-05-30 17:55:09 UTC
Description:
You open "LibreOffice" and after saving a blank file, the "Modified" field in the "General" tab is not updated and remain blanked. 

Setup:
Windows 10
LibreOffice 6.1.3.2
 
Scenario:
Open "Writer"
Save the file (blank file-no content)
Open General

Steps to Reproduce:
1.Open "Writer" 
2."Save" the file (blank file-no content)
3.Open "General"

Actual Results:
Only the "Created" field changed, the "Modified" field remains blank. 

Expected Results:
Both "Created" & "Modified" fields should be updated according to when file was saved.



Reproducible: Always


User Profile Reset: Yes


OpenGL enabled: Yes

Additional Info:
Note:
-This happened with "LibreOffice" version 6.1.6 as well.
-Workaround: if you "Save" the file again, the "Modified" field do change.
-if you "Save" the file & replace it with a file with the same name (which is also blank file), the "Modified" field does change.
-If you add content to the file before saving, for example, "Character(s)", the "Modified" field does change, even if you delete all the content you added before saving.  
-Happened with "Save as" and "CTRL+S" as well
-I did try to resetting "UserProfile", the same result.

-This is the information from "Help"-"About LibreOffice":
Version: 6.2.4.2 (x64)
Build ID: 2412653d852ce75f65fbfa83fb7e7b669a126d64
CPU threads: 8; OS: Windows 10.0; UI render: GL; VCL: win; 
Locale: en-US (he_IL); UI-Language: en-GB
Calc: CL
Comment 1 raal 2019-05-31 03:53:38 UTC
Confirm with Version: 6.3.0.0.alpha1+
Build ID: 53325b40b557cc84d8d21c1baa0ef8d3bfc00ab8
CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; 

doesn't confirm > -Workaround: if you "Save" the file again, the "Modified" field do change.

not sure if it's a bug, leaving unconfirmed.
Comment 2 Topaz Englander 2019-05-31 07:00:12 UTC
(In reply to raal from comment #1)
> Confirm with Version: 6.3.0.0.alpha1+
> Build ID: 53325b40b557cc84d8d21c1baa0ef8d3bfc00ab8
> CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; 
> 
> doesn't confirm > -Workaround: if you "Save" the file again, the "Modified"
> field do change.
> 
> not sure if it's a bug, leaving unconfirmed.

If we check the file after the first saving in "Windows Properties" (Locating the file->"Right Click"->"Properties") the Modified field does change accordingly to when the file was saved  

Another thing to note is the "Help" description in the General tab and I quote :

"Modified":
Displays the date and time and author when the file was last saved in a LibreOffice file format.

So according to this description, the file "Modified" field should be updated when saving the blank file.
Comment 3 Dieter Praas 2019-05-31 08:28:27 UTC
You get the same result with a document with content inside: If you save it without any change the modified entry is not updated. So I'm not sure, that this is a bug, but I agree, that this not in line with the documentation: https://help.libreoffice.org/6.3/en-US/text/shared/01/01100200.html?System=WIN&DbPAR=WRITER&HID=sfx/ui/documentinfopage/signature#bm_id3149284

So changed bug summary and added Design Team for input. While not change the entry "Modified" to "Last Save" (but it should be clear, if this includes AutoSave or not)
Comment 4 Topaz Englander 2019-05-31 08:42:33 UTC
I noticed after some more testing that the workaround which I mentioned working in a random way, sometimes I just need to press it once (like I mentioned in the bug report) and "Modified" updated, but sometimes it still remains blank and maybe 2-3 more press on "Save" the "Modified" field changes correctly to what expected so this workaround isn't reliable enough.
Comment 5 Heiko Tietze 2019-06-01 07:25:59 UTC
Don't see any reason to not remove the flag after saving. So definitely a bug.