Bug 123921 - Fields (variables) auto update doesn't work at document opening (in some oldest documents)
Summary: Fields (variables) auto update doesn't work at document opening (in some olde...
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
6.2.0.3 release
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Fields
  Show dependency treegraph
 
Reported: 2019-03-07 09:33 UTC by Giovanni
Modified: 2019-10-19 02:43 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Sample file (16.44 KB, application/vnd.oasis.opendocument.text)
2019-03-07 09:34 UTC, Giovanni
Details
Result in 6.1.5 (23.86 KB, application/vnd.oasis.opendocument.text)
2019-03-07 15:10 UTC, Dieter
Details
Sample video (5.19 MB, video/mp4)
2019-03-18 06:43 UTC, Giovanni
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Giovanni 2019-03-07 09:33:07 UTC
Description:
After update to version 6.2 (6.2.0.3) the fields auto update doesn't work at document opening in some oldest documents (
I have to press the F9 key every time I open the document).

With previous versions the same files works.

New files, created with 6.2, works.  

Actual Results:
The fields doesn't auto updates

Expected Results:
The fields auto updates


Reproducible: Sometimes


User Profile Reset: Yes


OpenGL enabled: Yes

Additional Info:
Version: 6.2.0.3 (x64)
Build ID: 98c6a8a1c6c7b144ce3cc729e34964b47ce25d62
CPU threads: 4; OS: Windows 10.0; UI render: default; VCL: win; 
Locale: it-IT (it_IT); UI-Language: en-GB
Calc: CL
Comment 1 Giovanni 2019-03-07 09:34:05 UTC
Created attachment 149784 [details]
Sample file
Comment 2 Dieter 2019-03-07 13:27:56 UTC
(In reply to Giovanni from comment #0)
> With previous versions the same files works.

Which version did you use? I tried master, LO 6.1.5 and LO 5.4.7 and alwas got the same result: no update of second and fourth field
Comment 3 Giovanni 2019-03-07 13:51:12 UTC
Versione: 6.1.4.2 (x64)
Build ID: 9d0f32d1f0b509096fd65e0d4bec26ddd1938fd3
Thread CPU: 1; SO: Windows 10.0; Resa interfaccia: predefinito; 
Versione locale: it-IT (it_IT); Calc: group threaded

AND

Versione: 6.0.2.1 (x64)
Build ID: f7f06a8f319e4b62f9bc5095aa112a65d2f3ac89
Thread CPU: 1; SO: Windows 10.0; Resa interfaccia: predefinito; 
Versione locale: it-IT (it_IT); Calc: group

works
Comment 4 Dieter 2019-03-07 15:10:18 UTC
Created attachment 149801 [details]
Result in 6.1.5

Result in LO 6.1.5 (same result in 6.3.0.0). Giovanni, I'm not an expert with variables, so I'm not sure, if this ist the expected behaviour or not.
Comment 5 Giovanni 2019-03-07 15:50:52 UTC
Before version 2, when I opened the document, I saw all the fields filled in without having to press F9
Comment 6 Giovanni 2019-03-08 05:24:06 UTC
Sorry: Before version 6.2, when I opened the document, I saw all the fields filled in without having to press F9
Comment 7 Giovanni 2019-03-12 16:24:50 UTC
Same result with:

Versione: 6.2.1.2 (x64)
Build ID: 7bcb35dc3024a62dea0caee87020152d1ee96e71
Thread CPU: 4; SO: Windows 10.0; Resa interfaccia: predefinito; VCL: win; 
Versione locale: it-IT (it_IT); Lingua interfaccia: it-IT
Calc: CL
Comment 8 Giovanni 2019-03-13 06:38:53 UTC
Other test: open the sample file, go to the end of the first field, press the space key: the other fields are displayed!
Comment 9 Xisco Faulí 2019-03-14 18:39:03 UTC
Hi Giovanni,
I get the same result even with 

Version: 5.2.0.0.alpha1+
Build ID: 5b168b3fa568e48e795234dc5fa454bf24c9805e
CPU Threads: 4; OS Version: Linux 4.15; UI Render: default; 
Locale: ca-ES (ca_ES.UTF-8)

Are you use the *same* file attached was autoupdated with older versions? Please share the help info of that version...
Comment 10 Giovanni 2019-03-18 06:43:00 UTC
Created attachment 150041 [details]
Sample video
Comment 11 Giovanni 2019-03-18 06:44:10 UTC
Attached a sample video
Comment 12 Xisco Faulí 2019-03-20 18:25:35 UTC
This is really weird. The result with

Versió: 6.1.4.2
ID de la construcció: 1:6.1.4-0ubuntu0.16.04.1~lo2
Fils de CPU: 4; SO: Linux 4.15; Renderitzador de la IU: per defecte; VCL: gtk3; 
Configuració local: ca-ES (ca_ES.UTF-8); Calc: group threaded

and

Versión: 5.3.7.2
Id. de compilación: 6b8ed514a9f8b44d37a1b96673cbbdd077e24059
Subprocs. CPU: 1; SO: Windows 6.1; Repres. IU: predet.; Motor de trazado: HarfBuzz; 
Configuración regional: es-ES (es_ES); Calc: group

What happens if you try with a clean profile with the windows version ?
Comment 13 Giovanni 2019-03-21 08:07:04 UTC
Same result. But does it work correctly in your tests (without the need to press F9 when opening)?
Comment 14 Xisco Faulí 2019-03-21 09:48:57 UTC
(In reply to Giovanni from comment #13)
> Same result. But does it work correctly in your tests (without the need to
> press F9 when opening)?

For my tests, I've never pressed F9 and I could never see the fields autoupdated. It doesn't matter whether I do it on windows, linux, new versions or old versions...
Comment 15 QA Administrators 2019-09-18 02:55:40 UTC Comment hidden (obsolete)
Comment 16 QA Administrators 2019-10-19 02:43:25 UTC
Dear Giovanni,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp