After undoing a "find & replace all" the cells with an automatic result are stuck with the result obtained after the find & replace whereas the undo action has been working.
Steps to Reproduce:
1. Enter 513 in cell A1
2. In cell B1 enter "=A1/12" (it will display 42.75)
3. Hit Ctrl+H
4. Find 513
5. Replace all by 625
6. The value of B1 is now 52.0833333
7. Hit Ctrl+Z
8. The value of B1 is still 52.0833333
8. B1 should have a value of 42.75
User Profile Reset: Yes
Build ID: a726b36747cf2001e06b58ad5db1aa3a9a1872d6
CPU threads: 8; OS: Linux 5.4; UI render: default; VCL: gtk3;
Locale: en-US (en_US.UTF-8); UI-Language: en-US
Created attachment 162761 [details]
Here is a file with some examples.
You can try with any value, the bug will always occur.
Also experimented on:
Build ID: 088b7f419f48f3390aac22587bbd92e9e027d5b1
CPU threads: 8; OS: Linux 5.4; UI render: default; VCL: gtk3
Locale: en-US (en_US.UTF-8); UI: en-US
Confirmed. It lacks one recalculation of the Undo value, entering a new value in A1 after that recalculates.
Found already in 5.3, don't know if earlier. Not in OOo3.3
Created attachment 163125 [details]
details of the strace command
After a quick bibisection, the bug seems to be introduced between LO 18.104.22.168 and LO 22.214.171.124.
I'm experiencing some issues while starting the versions between those mentioned above...
$> ./opt/program/soffice --version
LibreOfficeDev 126.96.36.199.beta1 3a2c2d2417101e45fe07cfd8358acf2204a98f3
[[ LO Loading splashscreen display ]]
javaldx: Could not find a Java Runtime Environment!
Warning: failed to read path from javaldx
** (soffice:27006): WARNING **: 16:53:04.815: Unknown type: GailWindow
[[ HERE the application stops and the progress bar isn't complete ]]
$> strace ./opt/program/soffice
... [see file attached to more details]
The bug was introduce in LO 188.8.131.52.beta1.
There is a patch for this issue.
It can be reviwed here:
Bibisect results in repo bibisect-42max, the following range is a single commit in the bibisect repo:
(In reply to Pierre Marty from comment #7)
> Hi all,
> There is a patch for this issue.
> It can be reviwed here:
Update at the same link