be1fa77c6e
The niri 'environment' block only affects processes niri spawns directly. Apps launched via dbus activation or systemd-user (most .desktop launches go through one of these) get systemd-user's env, which still has bare 'niri' — set by niri-session BEFORE niri itself runs. Adding a one-shot spawn-at-startup that re-imports XDG_CURRENT_DESKTOP from niri's env into both systemd-user and dbus-activation, after niri starts. Future dbus-activated apps will see niri:GNOME. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>