From 42542334e85a35df17f13c5b75f37b9ff97042b9 Mon Sep 17 00:00:00 2001 From: Bernardo Magri Date: Sat, 11 Jul 2026 15:35:07 +0100 Subject: [PATCH] docs: backfill 05bab55 journal entry; real cause in MIGRATION browser note MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The migration session crashed before journaling. Follow-up diagnosis: extensions vanished because programs.chromium.extensions wasn't carried into the downstream flake — Chromium external-uninstall deletes the extensions AND their Local Extension Settings. Rewrite the browser migration note with the mechanism and the snapshot recovery path. Co-Authored-By: Claude Fable 5 --- agent/JOURNAL.md | 18 ++++++++++++++++++ docs/MIGRATION.md | 15 ++++++++++++--- 2 files changed, 30 insertions(+), 3 deletions(-) diff --git a/agent/JOURNAL.md b/agent/JOURNAL.md index 54bc6d2..2899472 100644 --- a/agent/JOURNAL.md +++ b/agent/JOURNAL.md @@ -19,6 +19,24 @@ Template: --- +## 2026-07-11 — post-migration fix batch (05bab55; entry backfilled) +- **Task:** Escalation — first real-hardware migration (TuringMachine → + Nomarchy) surfaced a batch of annoyances; session crashed before + journaling, entry written by the follow-up session. +- **Did:** Force fprintAuth off unless `fingerprint.pam`; first-boot toast + waits for swaync + retries; night-light handles masked units; VPN menu + `rofi_menu` no-op fixed; ← = Back in list menus; GTK menu contrast; + mic-mute LED udev rule + sync; EasyEffects after tray; MIGRATION.md notes. +- **Verified:** V0 flake check; checks.first-boot; checks.hardware-toggles. +- **Pending:** V3 on the migrated machine. Follow-up found the downstream + `~/.nomarchy` lock still pinned the *previous* commit — the user's rebuild + excluded this batch (mic LED "regression" was just that). Also: HM + `programs.chromium.extensions` from the old config wasn't carried over, so + Chromium externally-uninstalled all extensions **and their data** (wallets + included); recovered from the `pre-nomarchy-home` btrfs snapshot. + MIGRATION.md browser note rewritten with the real mechanism. +- **Next suggestion:** V3 sweep of the 05bab55 items after a locked rebuild. + ## 2026-07-11 — #88 neon-glass polish / finish - **Task:** NEXT #88 — finish neon-glass (`VISION § D`), not quarantine. - **Did:** Rewrote `themes/neon-glass/rofi.rasi` (was invalid `var()` CSS; diff --git a/docs/MIGRATION.md b/docs/MIGRATION.md index a647d87..cc9f275 100644 --- a/docs/MIGRATION.md +++ b/docs/MIGRATION.md @@ -267,9 +267,18 @@ default yet. - **Browser profiles:** Nomarchy does not manage Chromium/Firefox state. Bookmarks/extensions live under `~/.config/chromium` (or `~/.config/google-chrome` / ungoogled paths if that was your previous - browser). A package name change can look like "extensions vanished" - while bookmarks remain — point the new browser at the old profile dir - or re-install extensions; nothing was wiped by the activation. + browser). **If your old Home Manager config declared + `programs.chromium.extensions`, carry that block into `home.nix` + *before* first launch** — HM installs those via + `External Extensions/*.json`, and when the JSONs vanish Chromium + treats every extension as externally uninstalled and deletes it + **together with its stored data** (`Local Extension Settings` — + wallet vaults, password-manager pairings). Bookmarks survive, which + makes it look minor; it isn't. Recovery: re-declare the extension + ids, close the browser, and copy `Default/Local Extension + Settings/` (plus any `Default/IndexedDB/chrome-extension__*`) + back from your Phase-0 `pre-nomarchy-home` snapshot before + relaunching. - **VPN:** NetworkManager connections survive under `/etc/NetworkManager` and your home. System › VPN lists NM `vpn`/`wireguard` profiles; import any that lived outside NM.