Bug 137599 - cells calculated value not recalculated until window refocus
Summary: cells calculated value not recalculated until window refocus
Status: CLOSED DUPLICATE of bug 137248
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
(earliest affected) release
Hardware: All All
: medium normal
Assignee: Not Assigned
Depends on:
Reported: 2020-10-19 17:24 UTC by Heather Ellsworth
Modified: 2020-10-19 17:54 UTC (History)
0 users

See Also:
Crash report or crash signature:


Note You need to log in before you can comment on or make changes to this bug.
Description Heather Ellsworth 2020-10-19 17:24:58 UTC
This was reported by a user on launchpad: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1900454

The problem is better explained via steps to reproduce (see steps below) but basically if a cell in calc is a *calculated value* based off of another cell, and the original cell's value changes, then that change is not reflected in the calculated cell's value until the cursor focus goes to another application and comes back to libreoffice.

Steps to Reproduce:
1. Start calc; you'll get a new spreadsheet.
2. Fill in the following in cells A1-A3:

  A1: 1
  A2: =A1+1
  A3: =A1-1
As expected: A2 is calculated as 2, A3 is calculated as 0.

3. Change A1 to 2 and press enter. A2 is autocalculated to 3, but A3 remains at 0 (wrong!).
4. Now for the fun part: switch to a different application so LibreOffice window loses focus, the put it back in focus. A3 is now recalculated to 1.

Actual Results:
The cell's values are updated only if the cursor focus goes to another application and then back to libreoffice.

Expected Results:
The cell's values should be updated immediately.

Reproducible: Always

User Profile Reset: No

Additional Info:
This was first reported by a user running Ubuntu 20.10 with libreoffice 7.0.2-0ubuntu1 (repackaged release).

I've also reproduced this on a debian testing system with the TDF LibreOffice_7.0.2_Linux_x86-64_deb.tar.gz
Comment 1 Eike Rathke 2020-10-19 17:54:01 UTC

*** This bug has been marked as a duplicate of bug 137248 ***