| Summary: | When LO saves a file, it changes "created", "modified" and "accesed" date properties. | ||
|---|---|---|---|
| Product: | LibreOffice | Reporter: | MarioMey <mariomey> |
| Component: | LibreOffice | Assignee: | Not Assigned <libreoffice-bugs> |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | CC: | jcsanz |
| Priority: | medium | ||
| Version: | 7.6.7.2 release | ||
| Hardware: | x86-64 (AMD64) | ||
| OS: | Linux (All) | ||
| See Also: | https://bugs.documentfoundation.org/show_bug.cgi?id=161831 | ||
| Whiteboard: | |||
| Crash report or crash signature: | Regression By: | ||
| Attachments: |
Dates changes correctly
Bug not reproducible |
||
|
Description
MarioMey
2024-06-28 14:21:53 UTC
Here is the other report: https://bugs.documentfoundation.org/show_bug.cgi?id=161831 Please paste here the information on Menu/Help/About LibreOffice (There is an icon to copy) Version: 7.6.7.2 (X86_64) / LibreOffice Community Build ID: dd47e4b30cb7dab30588d6c79c651f218165e3c5 CPU threads: 8; OS: Linux 6.1; UI render: default; VCL: gtk3 Locale: es-AR (es_AR.UTF-8); UI: es-ES Calc: threaded Created attachment 195043 [details] Dates changes correctly The bug is NOT reproducible, as shown in the image. It seems it is dependent on OS Version: 24.2.4.2 (X86_64) / LibreOffice Community Build ID: 51a6219feb6075d9a4c46691dcfe0cd9c4fff3c2 CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: Skia/Vulkan; VCL: win Locale: es-ES (es_ES); UI: es-ES Calc: CL threaded Created attachment 195044 [details] Bug not reproducible The bug is NOT reprducible, as can see in the image all dates, "Created" (Creado), "modified" (Modificado) and "accessed" (Último acceso) are as expected. I think it is not our bug but is an OS dependent one. Version: 24.2.4.2 (X86_64) / LibreOffice Community Build ID: 51a6219feb6075d9a4c46691dcfe0cd9c4fff3c2 CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: Skia/Vulkan; VCL: win Locale: es-ES (es_ES); UI: es-ES Calc: CL threaded (In reply to jcsanz from comment #5) > Created attachment 195044 [details] > Bug not reproducible > > The bug is NOT reprducible, as can see in the image all dates, "Created" > (Creado), "modified" (Modificado) and "accessed" (Último acceso) are as > expected. > I think it is not our bug but is an OS dependent one. Yes, you are right about "created date". There were some stuff and maybe one or both was causing the confusion (on me): - If you duplicate a file, the created date is the moment you duplicate it... but modified and accessed are not touched. So, paradoxically, it was modified before its creation! 😱 Well... I think this is the correct behavior of any OS. So, nothing to say about it. But, the most important and relevant thing is... - MY BAD! I realized that I'm using Syncthing in the folder where I have these files. So, when it sincronizes, Syncthing creates the files in my computer, not LO. I'm not really sure that Syncthing works like this, but I think it is a good hypothesis. Ok, LO doesn't change "created date" property. But why LO in you OS doesn't change "modified date" and in my and Robert's computers, it does? (Robert said in the other bug '"Created" is also untouched here. But "modified" and "accessed" are almost the same when LO has been closed (Connection to the database has been closed).'). I mean, this is a very unimportant issue... but it is the not correct behavior of managing files. As I say in my country: "te dejo la inquietud" - "I leave the restlessness" (?) Again, as this last behavior (modified/accessed date) is not serious at all, I close this report. Thanks! (In reply to MarioMey from comment #6) > Ok, LO doesn't change "created date" property. But why LO in you OS doesn't > change "modified date" and in my and Robert's computers, it does? I don´t understand the question, as you can see en both attached images, the modified data is different of creation data, and of course it is the date when was modified. further more, in "Dates changes correctly" the modification data is higlited by a red arrow. >(Robert > said in the other bug '"Created" is also untouched here. But "modified" and > "accessed" are almost the same when LO has been closed (Connection to the > database has been closed).'). I mean, this is a very unimportant issue... > but it is the not correct behavior of managing files. > In the "Bug not reproducible" image it is possible to see that the three dates are different, Creation, modification y the third one accesed is different because I've opened the file, *I haven't done any modification* even in the records, and I've close the file so the only date modified is the date of access. > As I say in my country: "te dejo la inquietud" - "I leave the restlessness" > (?) That's a challenge? we are here to report/solve software problems, not to challenge each other. > > Again, as this last behavior (modified/accessed date) is not serious at all, > I close this report. Thanks! It seems perfect to me in my OS, any case is not a LibreOffice fault For now, this report is close, so devs have nothing to do. But there are some doubts that I think I will understand (or not) when new LO version (with bug https://bugs.documentfoundation.org/show_bug.cgi?id=117118 fixed) is realeased and I will know how Firebird will work and if it will work as macro works. This is why: LO 7.6.7.2 WITHOUT macro: - I open a file and inmediatly close it: "accessed date" is the only property modified. LO 7.6.7.2 WITH macro: - I open a file and inmediatly close it: "accessed date" and "modified date" are modified because macro saves file when "View is going to be closed". It's not my intention to challenge anyone. I apologize if I expressed myself in the wrong way. What I tried to say is that, as I explained above, in current version or in next version, with macro or without macro... there are different behaviors with file properties modifications. Ok, it is my "inquietud" and it is not your responsability to solve it. And again, this "inquietud" is just that and it is not important. |