Failed to load user configuration file – Inkscape configuration loader

Problem Context

When upgrading to a new major release of Inkscape, the application may abort with the message "Failed to load user configuration file". The loader searches for the legacy configuration directory (e.g., ~/.config/inkscape on Linux or %APPDATA%\Inkscape on Windows) and cannot locate it, causing the launch to fail.

Recovery Path

Documentation recommends simply deleting the old configuration directory so that the installer can recreate a fresh defaults set. This restores the core UI and preferences but discards any custom UI themes or user‑defined settings.

Unresolved Decision

During this upgrade path the loader does not back up or migrate user‑installed extensions located in the extensions sub‑folder. Users lose custom functionality unless they manually copy the files before upgrading.

Questions

• Should Inkscape automatically back up and migrate user extensions during a major release upgrade?
• What configuration flag or installer option could preserve legacy config files without requiring manual deletion?
• Is there an official roadmap to address extension migration in future releases?