[DISCLAIMER: I used Claude Code to debug this and write the report. The analysis of the problem is its own, and the proposed fix worked. I’ve read the report and it looks good to me, but there might still be inaccuracies].
This happened because of a damaged Local Storage file, so I can’t give clean repro steps from a fresh install. Here’s what happened and what I found:
- A vault uses Settings → Files and links → Override config folder, set to a custom folder (e.g. .obsidian-myhost).
- At some point (likely an unclean shutdown or crash while switching from the Snap build to the .deb), Obsidian’s Local Storage LevelDB write-ahead log (~/.config/obsidian/Local Storage/leveldb/000003.log) got a block of 19 zero bytes partway through.
- On every startup, LevelDB reads up to the zeros, treats them as padding, and silently drops everything after them. Its LOG file shows no corruption warning.
- The -config key therefore reverts to the last value before the zeros, which was an old folder name from months ago.
- Changing “Override config folder” and relaunching works while the app is running. The new value is appended after the zeros, so it’s discarded again at the next startup.
Expected result
The override setting persists across restarts. If Obsidian can’t read back the stored value, it should warn rather than silently open the vault with a different config folder.
Actual result
After every restart, the vault opened with an old, unused config folder. Obsidian created a fresh default config in it (app.json = {}), so all plugins, theme and hotkeys appeared lost. Setting the override again in the UI had no lasting effect, no matter how many times I did it.
While troubleshooting, I looked in obsidian.json first, since that’s where the vault is registered, and added a config-folder key to the vault entry by hand. Obsidian ignores it, since the override is stored only in Local Storage. That made the problem very hard to diagnose.
Environment
SYSTEM INFO:
Obsidian version: 1.14.4
Installer version: 1.14.4
Operating system: #147-Ubuntu SMP PREEMPT_DYNAMIC Thu Sep 24 11:33:16 UTC 2026 6.8.0-147-generic
Login status: logged in
Language: en
Catalyst license: none
Insider build toggle: off
Live preview: on
Base theme: adapt to system
Community theme: none
Snippets enabled: 0
Restricted mode: off
Plugins installed: 7
Plugins enabled: 5
1: Zotero Integration v2.2.35
2: Dataview v0.5.54
3: File Cleaner v0.1.5
4: Templater v1.16.0
5: Emoji Toolbar v1.0.0
- Obsidian 1.14.4 (.deb, /opt/Obsidian), Ubuntu (X11/GNOME)
- Previously installed via Snap and AppImage. Config migrated from the Snap location.
- Vault synced with Synology Drive. ~/.config/obsidian is not synced.
Additional information
Workaround: with Obsidian closed, truncate 000003.log at the start of the zero-filled region (keeping only the valid records before it). Then set the override again and relaunch. After that it persists.
Suggestion: the root cause was file damage, not Obsidian code, but Obsidian makes it much worse. A setting that decides which config folder a vault loads is kept only in Chromium Local Storage, which fails silently and can’t be inspected or edited. Please consider:
- storing the config-folder override in obsidian.json alongside the vault entry (e.g. “configDir”: “.obsidian-myhost”). Today it lives only in Local Storage under -config. I tried adding such a key to obsidian.json by hand while troubleshooting, and Obsidian (understandably) ignores it, but that’s where I expected the setting to be.
- warning when the override value read at startup differs from the last one the user set.
Note: I no longer have the damaged file to attach. If this happens again, I’ll keep a copy of the leveldb folder.