Diagnose Stale or Incorrect Formula Results in Gnumeric

A formula can display the wrong result because it has not recalculated, references the wrong cell, or receives text where you expected a number. Work through these cases separately in a disposable Gnumeric workbook. Recalculating cannot fix an incorrect formula, and changing display precision cannot fix an incorrect value.

Scope and exact controls

The online manual and official Gnumeric 1.12.62 source were reviewed on 2026-10-19. The source defines File → Document Properties → Calculation, with Automatic and Manual recalculation, and Edit → Recalculate, with shortcut F9. These are English desktop labels; distributions and translations may differ. A desktop may intercept F9, so the menu command is the fallback.

No fresh native run was available. The deliberately stale scenario below is a source-supported exercise with independently calculated expected results, not an observed native failure. The change tests are intended to verify the behavior on your installation. Do not change calculation mode in an important workbook just to reproduce a problem.

The sample entries use a decimal point. If your worksheet locale uses a decimal comma, enter the equivalent numeric values in that convention and verify their types before continuing.

Build a controlled reference case

Start a new workbook and enter this complete fixture in A1:F4:

Row	A: Item	B: Quantity	C: Price	D: Expected logic	E: Wrong reference	F: Total check
1	Item	Quantity	Price	Correct amount	Wrong amount	Check
2	Folder	4	2.50	=B2*C2	=B2*C3	=SUM(D2:D3)
3	Pen	3	1.20	=B3*C3	leave blank	leave blank
4	leave blank	leave blank	leave blank	leave blank	leave blank	leave blank

D2 should be 10, D3 3.6, E2 4.8, and F2 13.6. Set Automatic calculation in Document Properties → Calculation, then use Edit → Recalculate to establish a fresh baseline. Save diagnostic-practice.gnumeric.

Select each formula cell and inspect the formula entry area. D2 references the Folder quantity and price. E2 deliberately combines the Folder quantity with the Pen price. Both calculate valid numbers, but only D2 represents the intended transaction.

Case 1: expose and recover a stale result

1. Open File → Document Properties → Calculation and select Manual recalculation. Close the dialog. This changes a workbook setting; do not assume Undo will restore it.
2. Change B2 from 4 to 6. The new mathematical expectations are D2 15, E2 7.2, and F2 18.6. Before requesting recalculation, dependent results may still show the old 10, 4.8 and 13.6. Record what your installation shows; do not retype the result cells.
3. Choose Edit → Recalculate or press F9. Confirm 15, 7.2 and 18.6. A change after this command identifies calculation freshness as one issue; E2 is still logically wrong.
4. Return to Document Properties → Calculation and explicitly select Automatic. Restore B2 to 4. D2 should return to 10 and F2 to 13.6 without another manual recalculation.
5. Save, close and reopen the native practice file. Check that Automatic is selected and repeat a 4 → 6 → 4 input change. This checks the saved workbook state as well as the displayed values.

If results updated immediately in the supposed Manual test, revisit the setting before concluding you reproduced a stale state. If F9 does nothing, use the menu command, check that cell entry has been committed, and inspect the actual formula text. Do not apply remembered Excel key combinations as though they were verified Gnumeric controls.

Case 2: repair a valid calculation with the wrong dependency

With B2 restored to 4, select E2. Its expression is =B2*C3, so 4.8 is mathematically correct for the references it actually uses. Recalculation should not turn that expression into 10.

Replace E2 with =B2*C2. It should return 10. Change C2 to 3.00: D2 and E2 should both become 12, and F2 15.6. Restore C2 to 2.50 and check D2 = E2 = 10 and F2 = 13.6. This tests the repaired dependency rather than merely matching a single saved number.

For a copied column of formulas, inspect the first, middle and last rows. An unintended absolute reference or one shifted row may produce plausible numbers. Repair the reference pattern deliberately and test an input that affects only one row.

Case 3: distinguish text from numeric input

Use H1:I4, leaving the amount model intact:

Cell	Entry
H1	Input
H2	type '12.50 with a leading apostrophe
H3	type numeric 7.50
I1	Check
I2	=COUNT(H2:H3)
I3	=SUM(H2:H3)
I4	=ISTEXT(H2)

The apostrophe deliberately makes H2 text. Expected checks are 1, 7.5, and TRUE, despite H2 looking like an amount. SUM over this range excludes the text entry. A two-decimal Number format alone does not establish conversion.

Repair this known synthetic value by setting H2 to General through Format → Cells → Format, replacing its entry with numeric 12.50 without the apostrophe, and committing the edit. Expected checks become 2, 20, and FALSE. For real imported data, return to the original file and correct import locale/type settings instead of blindly removing punctuation from unknown values.

Case 4: distinguish precision from formatting

Enter =1/16 in K2 and apply a Number format with two decimal places. It should display 0.06, while =K2*16 in K3 should be 1. The stored value is 0.0625. Merely increasing displayed decimal places reveals more of it; it does not change the calculation.

If a calculation genuinely requires rounding each intermediate result, state that policy explicitly and use a rounding formula. Do not switch calculation settings or overwrite values merely to make a displayed total look familiar. See ROUND for the distinction.

Finish with a reproducible check

Leave Automatic enabled, B2 = 4, C2 = 2.50, E2 repaired, and H2 numeric. Final expected checks are D2 10, D3 3.6, E2 10, F2 13.6, I2 2, I3 20, I4 FALSE, and K3 1. Save a separate repaired copy if applying this method to a real workbook.

If those checks fail, isolate a small copy and record the formula, its direct inputs, calculation mode and expected result. Do not enable iterative calculation as a generic fix for a circular reference; that changes the model’s behavior. A formula error such as a missing reference is a different finding from a stale numeric result.

See COUNT, ISTEXT, SUM and CSV import typing.

Primary references

Reviewed 2026-10-19: Gnumeric menus, Data Types, Formatting Cells, and official Gnumeric 1.12.62 source, src/dialogs/doc-meta-data.ui, src/dialogs/dialog-doc-metadata.c, src/wbc-gtk-actions.c and src/GNOME_Gnumeric-gtk.xml.