Contact
12 programs
Explore the site

Gnumeric · Saving and recovery · Beginner

Set Up Auto Save Safely in Gnumeric

Configure Gnumeric Auto Save, keep an independent checkpoint, and verify saved changes without mistaking timed saves for crash recovery or version history.

Gnumeric 1.12.62 source reviewed; starter checked with headless ssconvert; Auto Save GUI and timer untested · Editorial standards

Gnumeric’s Tools → Auto Save can save a changed workbook at an interval you choose. In the reviewed 1.12.62 implementation, it calls the normal save operation. For a named, writable native workbook, that means updating the working file, not keeping a separate history of every edit.

Keep a known-good copy before enabling it on important work. An incorrect edit can be saved automatically too, and closing without saving cannot undo a save that already happened.

Scope and practice download

This guide uses Gnumeric 1.12.62 GTK desktop source and its bundled manual, with English control labels. The downloadable starter’s contents and formula were checked using the 1.12.62 headless ssconvert engine. The Auto Save dialog, elapsed-time behavior, prompts, desktop reopen procedure and crash recovery were not run or photographed. The steps below are a source-supported acceptance test to perform on your installation.

Download the native Auto Save practice workbook. It contains one Practice sheet with synthetic data and one SUM formula. It does not enable Auto Save for you.

Use a new practice folder that you can write to. Avoid testing against your only report, a shared original or a synchronized production file. If any suggested filename already exists, choose a fresh name rather than overwrite it.

Keep a checkpoint before making changes

Open the download. Alternatively, create a new workbook with these cells:

Cells Contents
A2 Auto Save practice
A4 / B4 Stage / CHECKPOINT
A6 / B6 Item / Units
A7 / B7 Batch A / 12
A8 / B8 Batch B / 18
A9 / B9 Batch C / 20
A11 / B11 Total units / =SUM(B7:B9)

The total should be 50, because 12 + 18 + 20 = 50. Inspect B11’s formula, not just its displayed number. Gnumeric may display the function name in lowercase: =sum(B7:B9) is equivalent to =SUM(B7:B9).

  1. Choose File → Save As, select the native Gnumeric format and save autosave-checkpoint.gnumeric in your practice folder. This is your deliberately retained checkpoint.
  2. Close it and reopen that exact file. Verify CHECKPOINT, 20 in B9 and 50 in B11 before proceeding.
  3. Immediately choose File → Save As again and save autosave-working.gnumeric in the same folder. Confirm that the active file is the working copy before entering any new data.

These are two different files. Auto Save is not the step that creates the checkpoint. The workbook-template guide explains the same separate-master principle for reusable reports.

Enable Auto Save for the working copy

With autosave-working.gnumeric active:

  1. Open Tools → Auto Save. Record whether Automatically save every is selected, the displayed minutes and the Prompt Before Saving setting.
  2. Select Automatically save every and enter 1 in the minutes field for this short test.
  3. Select Prompt Before Saving, then choose OK.
  4. Change B4 to AUTOSAVE-CHECK and B9 to 35. Commit both entries. B11 should now be 65: 12 + 18 + 35 = 65.
  5. Leave Gnumeric open, with no cell entry or other dialog in progress, for longer than the selected interval. When the save question appears, check that it identifies the working file before choosing Yes. Do not approve a save to the checkpoint by mistake.

The setting uses a positive whole number of minutes, not seconds. With automatic saving enabled, the reviewed dialog disables OK for an invalid value or a value at or below zero. To turn the feature off, clear Automatically save every and choose OK instead of trying to use zero minutes.

If you choose No at a save question, the reviewed code skips that save attempt but keeps the timer active. No is not the same as disabling Auto Save. With no unsaved changes, the timer does not need to ask or save anything.

Verify the file, not just the elapsed time

Waiting one minute proves neither a successful write nor the contents of the saved file. Use a reopen check without accidentally replacing the evidence with a manual Save:

  1. After accepting a timed save that reports no error, reopen Tools → Auto Save, clear Automatically save every, and choose OK. This prevents another timer attempt during the check. Do not edit worksheet cells or press Save. If saving failed, preserve the open work as described under Troubleshooting and record this test as inconclusive.
  2. Close the working file. If Gnumeric still asks to save changes, cancel the close. Preserve the current work with Save As under a third filename, such as autosave-rescue.gnumeric, and record the timed-save check as inconclusive. Do not discard changes merely to complete the exercise.
  3. If it closes without asking, reopen autosave-working.gnumeric from your practice folder. Check all four items: B4 is AUTOSAVE-CHECK, B9 is 35, B11 displays 65, and B11 still contains =SUM(B7:B9).
  4. Open autosave-checkpoint.gnumeric separately. It must still contain CHECKPOINT, 20 and the formula result 50. Do not save changes to it.

The working-file check establishes what was written; the checkpoint check establishes that the earlier version remains available. If you manually save the working file before reopening it, the result verifies an ordinary save, not the timed-save path.

Restore a known-good copy safely

To practice returning to the earlier state, open the verified checkpoint and immediately Save As autosave-restored.gnumeric. Verify its stage, input, total and formula again. Keep both the current working file and the original checkpoint until you have compared their contents.

For a real interrupted session, preserve any existing workbook or identifiable backup before experimenting. Work on copies, open each candidate, inspect its latest meaningful inputs and formulas, and save a usable result under a new filename. Do not deliberately crash Gnumeric to test recovery.

This guide does not establish a crash-recovery folder, an automatic version history, or a way to recover a never-saved workbook. The Auto Save command’s normal-save path is not evidence that a separate recovery copy exists. Without an actual retained file or backup, do not assume unsaved edits can be reconstructed.

Current-window settings versus application defaults

Tools → Auto Save changes the timer and prompt properties of the current workbook window in the reviewed source. Recheck its settings after reopening a workbook or working in another window; do not assume the practice download carries your chosen interval or prompt preference.

Edit → Preferences → Files also has an autosave-frequency preference. That setting is in seconds, whereas Tools → Auto Save uses minutes: 5 minutes = 300 seconds. New window initialization reads the application preference. This exercise does not change it, so there is no need to alter an application-wide default just to test one working copy.

After practice, leave Auto Save off in disposable files you no longer need, or restore the recorded current-window settings if you continue using that window. Choose a sensible interval for real work only after verifying your installation. Keep deliberate checkpoints or an independent backup as well.

Troubleshooting

  • No prompt appears: check that automatic saving and prompting are both enabled in the active working window, commit a real cell change, and allow longer than the interval. An unchanged workbook does not trigger this path. Do not treat silence as confirmation of a save.
  • The minutes field is disabled: select Automatically save every. If OK remains disabled, enter a positive whole number such as 1, not 0.5 or 0.
  • A Save As dialog appears: the normal save path can require a destination, including for a new workbook or a read-only/unsuitable save format. Establish a writable native working copy first. Do not bypass an access restriction.
  • A warning says the file changed elsewhere: stop and compare the other version. Auto Save uses the ordinary save path and does not make overwriting somebody else’s changes safe.
  • Saving reports a permission, disk or location error: preserve the open work under a new filename in a permitted writable location, then reopen that file to verify it. A timer does not repair a storage failure.
  • The checkpoint now contains 65: the files were not kept separate, or the checkpoint was edited and saved. Stop using that checkpoint as an earlier version; recover a verified older backup rather than just relabeling the changed file.
  • An incorrect edit was already saved: do not expect closing without saving to remove it. Use a verified checkpoint or an appropriate still-available Undo operation, inspect the correction, then save a new result.