| 1 |
# Alloy user-service presets |
| 2 |
# |
| 3 |
# Applied on first user login for services that run under the user |
| 4 |
# session (not system-wide). |
| 5 |
# |
| 6 |
# This file is load-bearing because user units really do run here, which is not |
| 7 |
# obvious from Alloy's own config: greetd exec's the session directly |
| 8 |
# (alloy-session, then sway), and nothing Alloy writes starts a session target. |
| 9 |
# The sway-systemd package does it. Its |
| 10 |
# /etc/sway/config.d/10-systemd-session.conf exec's |
| 11 |
# /usr/libexec/sway-systemd/session.sh, which starts sway-session.target; |
| 12 |
# that target BindsTo=graphical-session.target and wants |
| 13 |
# graphical-session-pre.target, so anything ordered against those activates the |
| 14 |
# ordinary way. Proven on 2026-07-21 on an install booted in QEMU, by reading |
| 15 |
# the uid 1000 manager's journal: all three targets reached, |
| 16 |
# xdg-user-dirs.service ran, pipewire and wireplumber ran as the user. |
| 17 |
# Reproduced on the fw12 install on 2026-07-29 from its own session journal, so |
| 18 |
# this is not a QEMU artifact. Twice |
| 19 |
# now that has been assumed false and worked around with an `exec` line in the |
| 20 |
# sway config; do not add a third. |
| 21 |
# |
| 22 |
# Rationale for each entry: |
| 23 |
# |
| 24 |
# - syncthing: opt-in only. Enrollment via `alloy sync` |
| 25 |
# (see docs/CONTINUITY.md). |
| 26 |
# - gammastep: opt-in only. User needs to set their location |
| 27 |
# before enabling makes sense. |
| 28 |
# |
| 29 |
# Both units above exist in the image; checked, because two lines here |
| 30 |
# have named units that do not. |
| 31 |
# |
| 32 |
# alloy-hinged was enabled here until 2026-07-19. The fold-to-notes |
| 33 |
# daemon was shelved in the 2026-07-17 pivot (see |
| 34 |
# docs/HARDWARE-FW12.md#fold-to-notes-shelved) and no unit was ever |
| 35 |
# shipped, so the line only produced a failed enable at first login. |
| 36 |
# |
| 37 |
# swayosd.service was enabled here until 2026-07-21 and was the same |
| 38 |
# mistake. Fedora's SwayOSD 0.3.2 ships three binaries, one SYSTEM unit |
| 39 |
# (swayosd-libinput-backend.service, now in the system preset) and a |
| 40 |
# D-Bus service file. There is no user unit, so this line named nothing. |
| 41 |
# The server is started by `exec swayosd-server` in the sway config, |
| 42 |
# which is the mechanism rather than a workaround for this line failing. |
| 43 |
|
| 44 |
disable syncthing.service |
| 45 |
disable gammastep.service |
| 46 |
|