aboutsummaryrefslogtreecommitdiff
path: root/todo.org
diff options
context:
space:
mode:
Diffstat (limited to 'todo.org')
-rw-r--r--todo.org8
1 files changed, 7 insertions, 1 deletions
diff --git a/todo.org b/todo.org
index 0ac5b1f..124406b 100644
--- a/todo.org
+++ b/todo.org
@@ -743,7 +743,13 @@ CLOSED: [2026-06-24 Wed]
:PROPERTIES:
:LAST_REVIEWED: 2026-06-24
:END:
-nautilus rendered blindingly white (Craig, 2026-06-24). As a GTK4/libadwaita app it ignores the GTK theme name and follows =org.gnome.desktop.interface color-scheme=. Root cause: velox had no system-wide dconf db at all — no =/etc/dconf/profile/user=, no =/etc/dconf/db/site.d/00-archsetup-defaults=, no compiled =site= db — so archsetup's declared default (=color-scheme='prefer-dark'=, already at =archsetup:1109-1119=) never reached the machine. velox predates that block. Fix (velox, live): created the profile + site defaults exactly as archsetup writes them and ran =dconf update=. =gsettings get= now returns =prefer-dark= / =Adwaita-dark=, and a restarted nautilus renders dark (screenshot-verified). No archsetup change needed — fresh installs already get this. ratio may have the same gap (couldn't check from velox) — see the Active Reminder.
+nautilus rendered blindingly white (Craig, 2026-06-24). As a GTK4/libadwaita app it follows the appearance portal's =org.freedesktop.appearance color-scheme=, which mirrors =org.gnome.desktop.interface color-scheme=. Two stacked causes:
+
+1. velox had no system-wide dconf db at all — no =/etc/dconf/profile/user=, no =/etc/dconf/db/site.d/00-archsetup-defaults=, no compiled =site= db — so archsetup's declared default (=color-scheme='prefer-dark'=, =archsetup:1109-1119=) never reached the machine (velox predates that block). Created the profile + site defaults as archsetup writes them and ran =dconf update=. =gsettings get= then returned =prefer-dark=.
+
+2. That alone did NOT fix the running session: a system-db default emits no GSettings change signal, so the appearance portal kept reporting =0= (no-preference → light), and libadwaita reads the portal, not =GTK_THEME=. (An early screenshot looked dark only because the shell env carries =GTK_THEME=Adwaita:dark=, which Hyprland-launched apps don't inherit — masking the real state.) Fix: a user-level =gsettings set org.gnome.desktop.interface color-scheme prefer-dark=, which signals the portal live. It now reports =1=, and a portal-driven nautilus (GTK_THEME unset) renders dark — screenshot-verified.
+
+Durable: the user value persists in =~/.config/dconf/user=; archsetup's system-db handles fresh installs (the portal reads the default fresh at login, so no signal is needed there). No archsetup change. ratio may need the same one-two — see the Active Reminder.
** TODO [#C] Review current tool pain points annually
:PROPERTIES: