Quick Start
Running Manually
For testing purposes, you can run Stasis directly from the command line. Make sure you're in a running Wayland session, then simply run:
stasisThis is useful for testing your configuration, but for daily use we strongly recommend setting up the systemd service below for automatic startup.
Systemd Service (Recommended)
The recommended way to run Stasis is as a systemd user service. This ensures Stasis starts automatically with your graphical session and restarts if it crashes.
Provided Service File
Stasis already provides a service file if you installed it via the AUR on Arch Linux To start the service file with your desired compositor first enable it using:
systemctl --user enable stasis.serviceThen you can start Stasis via your compositors autostart section using the following:
systemctl --user start stasisCreate the Service File
If you installed Stasis manually and want to create a user only service file in your home directory,
Create a service file at ~/.config/systemd/user/stasis.service with this content:
[Unit]
Description=Stasis Wayland Idle Manager
PartOf=graphical-session.target
After=graphical-session.target
ConditionEnvironment=WAYLAND_DISPLAY
[Service]
Type=simple
ExecStart=/usr/bin/stasis
Restart=on-failure
[Install]
WantedBy=graphical-session.target$HOME/.local/bin/stasis.
If you installed Stasis to a different location (e.g., ~/.cargo/bin/stasis),
update the ExecStart= line accordingly.Enable and Start
Enable and start the service with these commands:
# Reload systemd to recognize the new service
systemctl --user daemon-reload
# Enable and start the service
systemctl --user enable --now stasis.serviceNow start Stasis from your compositors autostart section e.g. for Hyprland:
exec-once = systemctl --user start stasis