OPINIONATED OMARCHY
TROUBLESHOOTING CORPUS
790
RECORDS
790
AUDITED
0
UNCHECKED
2388
SOURCES
LIVE
wayland-compat low very-common DISPUTE

GTK4/libadwaita apps stay blinding white while everything else is dark

omarchyarchendeavouroscachyosmanjarohyprlanddesktoplaptop
CORRECTED An auditor found the fix wrong or incomplete and rewrote it.
AUDIT NOTE

Real problem, and the second half of the fix is right, but the cause's conclusion is disproven on the exact platform this corpus targets, and two specifics are fabricated. (a) The claim "With no backend serving Settings, the portal returns nothing" is false on a stock Hyprland/Omarchy install. Hyprland itself ships /usr/share/xdg-desktop-portal/hyprland-portals.conf containing [preferred] / default=hyprland;gtk (owned by package hyprland 0.56.2-1), so xdg-desktop-portal falls through to xdg-desktop-portal-gtk for any interface hyprland does not implement, including Settings, and Omarchy lists xdg-desktop-portal-gtk in /usr/share/omarchy/install/omarchy-base.packages. I verified this live on this machine, which has NO ~/.config/xdg-desktop-portal directory at all: busctl --user call ... org.freedesktop.portal.Settings Read ss "org.freedesktop.appearance" "color-scheme" answers correctly. So step 3 of the fix, creating a user hyprland-portals.conf, is unnecessary on a stock system, and it is the step the record's own danger field says can silently break FileChooser and ScreenCast. Telling every reader to write that file is the riskiest part of the record and it is usually not needed. (b) The enumeration of what xdg-desktop-portal-hyprland provides is wrong. /usr/share/xdg-desktop-portal/portals/hyprland.portal lists Screenshot;ScreenCast;GlobalShortcuts;InputCapture. There is no RemoteDesktop, and Screenshot is omitted. The true part (no Settings interface) is confirmed by that same file. (c) The verify's expected output is wrong: the real answer is v v u 1, a nested variant, not v u 1. (d) Correct-as-written: gtk-application-prefer-dark-theme is a GTK3 key that libadwaita ignores. xdg-desktop-portal-gtk is the Settings provider (ArchWiki Dark mode switching: "To query gsettings configuration, GTK requires the Settings XDG Desktop Portal, provided by xdg-desktop-portal-gtk, to be running"). color-scheme 'prefer-dark' is the right key/value (ArchWiki Dark mode switching). XDG_CURRENT_DESKTOP is Hyprland on Omarchy (set in /usr/share/omarchy/default/hypr/envs.lua) and portals.conf(5) confirms the filename is that value ASCII-lowercased, i.e. hyprland-portals.conf. All three systemd user units named exist. The real cause is simply that org.gnome.desktop.interface color-scheme sits at its schema default 'default' (= no preference), which libadwaita renders light. Omarchy sets it at first run in /usr/share/omarchy/install/user/first-run/gnome-theme.sh, so this only bites when that never ran, dconf was reset, or xdg-desktop-portal-gtk is absent on a non-Omarchy Hyprland box.

The cause above was rewritten on 2026-09-01 to match this note; the fix was corrected by the audit itself.
RISK

A malformed hyprland-portals.conf (a typo in an interface name, or pointing an interface at a backend that does not implement it) silently breaks whatever it names. Getting org.freedesktop.impl.portal.ScreenCast or FileChooser wrong will kill screen sharing or every file-open dialog. Keep default = hyprland;gtk and only add specific overrides you have verified with the busctl call above.

Symptom

Nautilus, GNOME Text Editor, Loupe, Fractal and other GTK4/libadwaita apps launch in bright white while my whole desktop is dark. Putting gtk-application-prefer-dark-theme=1 in ~/.config/gtk-4.0/settings.ini does nothing. GTK_THEME=Adwaita:dark only half-works. The headerbar is dark but the content is not.

Cause

libadwaita does not read GTK theme files for light/dark, and gtk-application-prefer-dark-theme is a GTK3 key it ignores entirely. It asks the org.freedesktop.impl.portal.Settings portal for org.freedesktop.appearance / color-scheme and renders light for anything other than prefer-dark. xdg-desktop-portal-hyprland genuinely does not implement Settings (/usr/share/xdg-desktop-portal/portals/hyprland.portal declares only Screenshot;ScreenCast;GlobalShortcuts;InputCapture), but on its own that breaks nothing, because Hyprland ships /usr/share/xdg-desktop-portal/hyprland-portals.conf containing default=hyprland;gtk, so xdg-desktop-portal falls through to xdg-desktop-portal-gtk for Settings, and Omarchy installs that package in its base set. So on a stock Omarchy the portal chain already works and the actual cause is that org.gnome.desktop.interface color-scheme is still at its schema default of 'default' (no preference). Omarchy sets it to prefer-dark at first run via /usr/share/omarchy/install/user/first-run/gnome-theme.sh, so this appears when that script never ran, when dconf was reset, or on a non-Omarchy Hyprland install where xdg-desktop-portal-gtk is simply not installed and nothing serves Settings at all.

Fix

**1. Ask the portal what it currently answers, before changing anything.** The reply is a nested variant, v v u N, where 0 = no preference, 1 = prefer-dark, 2 = prefer-light:


busctl --user call org.freedesktop.portal.Desktop /org/freedesktop/portal/desktop \
  org.freedesktop.portal.Settings Read ss "org.freedesktop.appearance" "color-scheme"
  • Answers v v u 0 → the portal works, you just have no preference set. Skip to step 3.
  • Answers v v u 1 → the portal already says dark. Your problem is elsewhere (a GTK theme with no dark variant, or GTK_THEME forced in the environment, so check systemctl --user show-environment | grep GTK).
  • Errors, or reports no such backend → do step 2.

**2. Only if step 1 found no Settings backend: install one.** Hyprland does not implement the Settings portal, but it ships a fall-through to gtk, so installing the gtk backend is normally all that is required. On Omarchy it is already in the base package set:


sudo pacman -S --needed xdg-desktop-portal-gtk
cat /usr/share/xdg-desktop-portal/hyprland-portals.conf   # expect: [preferred] / default=hyprland;gtk

**3. Set the preference.** This is the actual fix in the common case:


gsettings set org.gnome.desktop.interface color-scheme 'prefer-dark'
gsettings set org.gnome.desktop.interface gtk-theme 'Adwaita-dark'

Without gsettings schemas available:


dconf write /org/gnome/desktop/interface/color-scheme "'prefer-dark'"

On Omarchy you can simply re-run the first-run script that does exactly this:


bash /usr/share/omarchy/install/user/first-run/gnome-theme.sh

**4. Restart the portal stack, then the apps.**


systemctl --user restart xdg-desktop-portal-gtk xdg-desktop-portal-hyprland xdg-desktop-portal

libadwaita queries the portal at startup and then follows live changes, but an app started before any backend existed never got a first answer, so restart the affected apps once.

**5. Pin the backend explicitly only if steps 1 to 4 did not fix it.** A user file at this path *shadows Hyprland's shipped one*, so you take over responsibility for every interface it names. XDG_CURRENT_DESKTOP is Hyprland on Omarchy and portals.conf(5) says the filename is that value with ASCII upper case folded to lower, hence hyprland-portals.conf:


# ~/.config/xdg-desktop-portal/hyprland-portals.conf
[preferred]
default = hyprland;gtk
org.freedesktop.impl.portal.Settings = gtk

Keep default = hyprland;gtk and add nothing you have not verified with the busctl call in step 1. Do **not** add org.freedesktop.impl.portal.FileChooser or ScreenCast overrides speculatively. Pointing either at a backend that does not implement it kills every file dialog or all screen sharing, silently. Delete the file to go back to the shipped default.

To flip back to light: gsettings set org.gnome.desktop.interface color-scheme 'prefer-light'.

Verify

Ask the portal directly. It should answer v u 1 (1 = prefer-dark, 2 = prefer-light, 0 = no preference):


busctl --user call org.freedesktop.portal.Desktop /org/freedesktop/portal/desktop \
  org.freedesktop.portal.Settings Read ss "org.freedesktop.appearance" "color-scheme"

Then open Nautilus or GNOME Text Editor. It should be dark, and should follow a live gsettings set ... color-scheme change without restarting.

Sources

gtk4-libadwaita-apps-stuck-in-light-theme