Talk:Niri
Using systemd services instead of spawn-at-startup
I personally believe using systemd services over spawn-at-startup for long-running programs such as the ones provided in Niri#Spawn_at_startup makes for a more sensible setup. Example: Reloading waybar with the current recommended way needs kind of "scary" killall-commands: [1]https://github.com/Alexays/Waybar/wiki/FAQ#how-can-i-reload-the-configuration-without-restarting-waybar. Using systemd services, the equivalent feels more sensible
$ systemd --user restart waybar
---
All of the recommended programs listed in the Spawn at startup section are also described in the project wiki: [2]https://github.com/YaLTeR/niri/wiki/Example-systemd-Setup.
Now, I feel like a section about systemd doesn't fit in the Configuration-section, since it's not about the Niri configuration file. I see sections like Sway#Manage_Sway-specific_daemons_with_systemd on other pages. Is it already time to add a "Tips and Tricks" section on Niri's page? Chinatsu (talk) 15:50, 12 March 2025 (UTC)
- In principle I agree but some programs do not ship with systemd services (like swayidle) which makes it a bit error prone. But feel free to add a clarifying section about systemd services Aarroyoc (talk) 21:41, 13 March 2025 (UTC)
- You make some good points --- however, as @Aarroyoc pointed out, some programs don't include services and they need to be manually written by the user. So instead of recommending it as the default, a clarifying section would be great. I'm happy to review any contribution. Ficd (talk) 14:25, 11 August 2025 (UTC)
built-in xwayland satellite integration
Next update, Niri will be gaining built-in integration with Xwayland satellite. The Xwayland section will have to be overhauled to represent that to not mislead users. Iwuvkittens (talk) 19:02, 9 August 2025 (UTC)
[Starting] exec wayland (niri-session) via getty autologin for a 'seamless' experience
> "Additionally you can start Niri from a getty by executing: `niri-session` This can be paired with auto login to have a seamless boot experience."
Having to manually exec 'niri-session' after the getty-autologin barely 'seamless'. Is there a way for a seamless (getty-autologin+niri-session) combination of these both so the blanks here are filled please? Thanks for the tips. Muthuh (talk) 08:25, 8 September 2025 (UTC)
- you can add that line to your shells profile for it to be automatically executed once after auto login has occurred System72 (talk) 07:05, 18 December 2025 (UTC)
Issues with wayvnc
I recently encountered the following issue: https://github.com/niri-wm/niri/issues/3595. It deserves a mention. A possible workaround is https://github.com/niri-wm/niri/discussions/680. Topcat01 (talk) 18:25, 4 August 2026 (UTC)
Add troubleshooting section for Java applications
See Special:Diff/883872.
I recently ran into an issue where a Java based application (josm) would only show a blank window. Specifically, a splash screen would first display (correctly), but the main application window was blank.
This is a known issue in several tiling WMs, and also mentioned in the Niri docs; see e.g.
The fix remains the same for Niri (set _JAVA_AWT_WM_NONREPARENTING=1).
I think it could make a nice addition to the troubleshooting section, in a similar style as Sway's page. Lstngr (talk) 09:42, 23 August 2026 (UTC)
- You're welcome to add an item. If the Sway#Java applications instructions apply, referring to and crosslinking them is ideal. --Indigo (talk) 16:24, 23 August 2026 (UTC)
- Thank you for the encouragement, my account being recent, I was wondering if there was an etiquette to respect before making the first edit. I hope the new paragraph is okay! Lstngr (talk) 08:03, 25 August 2026 (UTC)
- It's particularly good to open a talk item prior to involved/complex changes. Welcome to the wiki. --Indigo (talk) 16:25, 25 August 2026 (UTC)
- Thank you for the encouragement, my account being recent, I was wondering if there was an etiquette to respect before making the first edit. I hope the new paragraph is okay! Lstngr (talk) 08:03, 25 August 2026 (UTC)