However, it can be launched within Weston, and it gives 2 results depending on what command i use:
1 (niri, dbus-run-session niri) - Niri launches as a window, with a huge input delay
2 (niri --session, dbus-run-session niri --session) - Niri doesn't launch, giving the following message:
Code: Select all
2026-03-18T21:33:06.669874Z WARN niri: running as a session but WAYLAND_DISPLAY
is set, removing it
2026-03-18T21:33:06.669919Z INFO niri: starting version 25.11 (b35bcae)
2026-03-18T21:33:06.698406Z DEBUG niri_config: loaded config from "/home/user/.
config/niri/config.kdl"
thread 'main' (4705) panicked at src/main.rs:181:6:
called `Result::unwrap()` on an `Err` value: error initializing the TTY backend
Caused by:
0: Error creating a session. This might mean that you're trying to run niri
on a TTY that is already busy, for example if you're running this inside tmux th
at had been originally started on a different TTY
1: Failed to open session: Function not implemented (os error 38)
