https://bugs.documentfoundation.org/show_bug.cgi?id=174274
Bug ID: 174274
Summary: Endless document recovery loop after GTK crash caused
by exhausted /tmp storage on Ubuntu
Product: LibreOffice
Version: 26.2.6.3 release
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: UNCONFIRMED
Severity: normal
Priority: medium
Component: Writer
Assignee: [email protected]
Reporter: [email protected]
Description:
LibreOffice enters a repeated document recovery cycle during startup when GTK
fails to load an SVG icon because a temporary-file write returns EDQUOT (Disk
quota exceeded).
Instead of terminating cleanly and explaining the storage problem, LibreOffice
repeatedly offers to recover documents and fails again.
Steps to Reproduce:
1. Run LibreOffice with /tmp near or above its (user) storage or quota limit.
Encounter a GTK icon-loading failure returning EDQUOT.
Attempt to restart LibreOffice by killing the splash in loop.
Observe repeated document recovery prompts and unsuccessful startup in endless
loop.
Actual Results:
LibreOffice repeatedly attempts document recovery. GTK crashes during startup
with:
Gtk:ERROR:gtkiconhelper.c:495:
ensure_surface_for_gicon:
assertion failed (error == NULL):
Failed to load
/usr/share/icons/breeze/status/64/image-missing.svg:
Disk quota exceeded
The problem also occurs with a fresh LibreOffice user profile.
Expected Results:
LibreOffice should detect or gracefully handle the failed startup, avoid an
endless recovery cycle, and present a useful error message identifying the
temporary-storage problem.
Freeing space in /tmp immediately restored normal LibreOffice operation. User
should at very least being made aware.
Reproducible: Always
User Profile Reset: Yes
Additional Info:
LibreOffice started successfully once when launched under strace, suggesting
timing-dependent behavior. Normal startup subsequently continued to fail until
space was freed in /tmp.
The exact quota threshold and the mechanism causing the recovery loop have not
yet been established.
--
You are receiving this mail because:
You are the assignee for the bug.
