both were installed but never launched. they ship their own units, but in
$out/share/systemd/user - not $out/lib/systemd/user - and that distinction
is why they need redeclaring rather than merely enabling:
* systemd.packages would collect nothing, since nixpkgs' generateUnits
globs only $pkg/etc/systemd/user and $pkg/lib/systemd/user.
* the units are nonetheless visible to the user manager, via
environment.pathsToLink -> /run/current-system/sw/share/systemd/user,
which is on the search path because XDG_DATA_DIRS ends with
/run/current-system/sw/share. but visible is not enabled - nothing
creates the WantedBy symlink, so they sit unstarted.
* wantedBy alone would not help either: with no other keys nixos
synthesises a replacement unit with an empty [Service] section, and it
shadows upstream's because /etc/systemd/user takes precedence over
$XDG_DATA_DIRS.
binding them to graphical-session.target, which uwsm manages properly,
means they start and stop with the session instead of leaking across
logins - same reasoning as udiskie, so that moves into the same attrset.
close to upstream's definitions but not identical: hyprsunset's
Requires=graphical-session.target is dropped, because PartOf already
propagates the stop while Requires would additionally make starting
hyprsunset by hand pull up the whole session target. the Slice=session.slice
asymmetry is upstream's own - hyprsunset sets it, hypridle does not - and is
noted inline so it does not get "fixed" later.
hypridle gets an explicit path because its config shells out to hyprlock,
pidof, brightnessctl, hyprctl, loginctl, systemctl and notify-send. that
config lives in the dotfiles repo, so this list can silently drift out of
sync with it: a binary used there but missing here fails as a bare "command
not found" inside hypridle, and Restart=on-failure will not catch it because
hypridle itself stays up. flagged in a comment at both ends.
ahmza
f8552bc7bb