Epsilon_02/niri
1
0
Fork 0
mirror of https://github.com/YaLTeR/niri.git synced 2025-10-06 00:23:14 +02:00
Code Issues Packages Projects Releases Wiki Activity
Page: Example systemd Setup
Pages
Accessibility Animation Timing Application Issues Configuration: Animations Configuration: Debug Options Configuration: Gestures Configuration: Include Configuration: Input Configuration: Introduction Configuration: Key Bindings Configuration: Layer Rules Configuration: Layout Configuration: Miscellaneous Configuration: Named Workspaces Configuration: Outputs Configuration: Overview Configuration: Switch Events Configuration: Window Rules Design Principles Developing niri Development: Animation Timing Development: Design Principles Development: Developing niri Development: Documenting niri Development: Fractional Layout Development: Redraw Loop Example systemd Setup FAQ Floating Windows Fractional Layout Gestures Getting Started Home IPC Important Software Integrating niri Layer‐Shell Components Name and Logo Nvidia Overview Packaging niri Redraw Loop Screencasting Tabs Workspaces Xwayland index
Clone
10
Example systemd Setup
github-actions[bot] edited this page 2025-08-17 14:29:43 +00:00
Table of Contents

When starting niri from a display manager like GDM, or otherwise through the niri-session binary, it runs as a systemd service. This provides the necessary systemd integration to run programs like mako and services like xdg-desktop-portal bound to the graphical session.

Here's an example on how you might set up mako, waybar, swaybg and swayidle to run as systemd services with niri. Unlike spawn-at-startup, this lets you easily monitor their status and output, and restart or reload them.

  1. Install them, i.e. sudo dnf install mako waybar swaybg swayidle

  2. mako and waybar provide systemd units out of the box, so you can simply add them to the niri session:

    systemctl --user add-wants niri.service mako.service
systemctl --user add-wants niri.service waybar.service

    This will create links in ~/.config/systemd/user/niri.service.wants/, a special systemd folder for services that need to start together with niri.service.

  3. swaybg does not provide a systemd unit, since you need to pass the background image as a command-line argument. So we will make our own. Create ~/.config/systemd/user/swaybg.service with the following contents:

    [Unit]
PartOf=graphical-session.target
After=graphical-session.target
Requisite=graphical-session.target

[Service]
ExecStart=/usr/bin/swaybg -m fill -i "%h/Pictures/LakeSide.png"
Restart=on-failure

    Replace the image path with the one you want. %h is expanded to your home directory.

    After editing swaybg.service, run systemctl --user daemon-reload so systemd picks up the changes in the file.

    Now, add it to the niri session:

    systemctl --user add-wants niri.service swaybg.service

  4. swayidle similarly does not provide a service, so we will also make our own. Create ~/.config/systemd/user/swayidle.service with the following contents:

    [Unit]
PartOf=graphical-session.target
After=graphical-session.target
Requisite=graphical-session.target

[Service]
ExecStart=/usr/bin/swayidle -w timeout 601 'niri msg action power-off-monitors' timeout 600 'swaylock -f' before-sleep 'swaylock -f'
Restart=on-failure

    Then, run systemctl --user daemon-reload and add it to the niri session:

    systemctl --user add-wants niri.service swayidle.service

That's it! Now these three utilities will be started together with the niri session and stopped when it exits. You can also restart them with a command like systemctl --user restart waybar.service, for example after editing their config files.

To remove a service from niri startup, remove its symbolic link from ~/.config/systemd/user/niri.service.wants/. Then, run systemctl --user daemon-reload.

Running Programs Across Logout

When running niri as a session, exiting it (logging out) will kill all programs that you've started within. However, sometimes you want a program, like tmux, dtach or similar, to persist in this case. To do this, run it in a transient systemd scope:

systemd-run --user --scope tmux new-session
This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

Usage

Configuration

Development