Skip to content
iNiR

Setup, updates and rollback

Your family

These commands keep an installed iNiR healthy. Run them in a terminal. inir update works from anywhere. ./setup commands need the folder you cloned iNiR into.

Update

Section titled “Update”
inir update

The update checks for new changes, takes a snapshot so you can roll back, pulls the changes, copies the new shell files and restarts the shell. Your settings are not overwritten. It also installs what the shell needs and is missing, such as plasma-integration, a colour emoji font and the shell’s fonts. It asks first, since that needs your password. With --skip-deps, or when you manage the packages yourself, it leaves them to you. What an older version left in your config that no longer fits, the update sets right on its own, after the snapshot.

inir update in a terminal, or the update notification, brings everything: the base, the families your config uses from the hub, the prebuilt runtime and the inir command. Your config and edits stay, and a version that won’t load is rolled back. If it stops because the checkout has local changes or commits of its own, it prints the command to run.

The hub moves on its own: when iNiR itself has nothing new, inir update still brings new versions of the families, themes, widgets and web apps you installed. Where systemd runs the shell, a new family, component or Design that won’t load goes back to the version you had; on Void the shell restarts on the new version without that check. The update check also posts “Hub updates ready” when there are new versions: run inir update, or update them on the Hub page.

If iNiR came from your distro’s package manager, update the shell through that package manager instead.

Coming from 2.33 without an update

Section titled “Coming from 2.33 without an update”

An install without .git (copied, not cloned), or one still on 2.33 after the first 3.x fix, gets a fresh clone and installs over itself. Your config is kept, and the line works in fish 3 or newer too:

git clone https://github.com/snowarch/iNiR ~/iNiR-3 && cd ~/iNiR-3 && ./setup install

The runtime and the helpers

Section titled “The runtime and the helpers”

Setup and inir update also download two parts built for you: qs-rs, which draws the shell, with its own Qt (on x86_64), and inir-accel, the native helpers (on x86_64 and aarch64). Each download is checked against the checksum the release pins, and nothing compiles on your machine. On ARM the shell runs on Quickshell.

  • A download that fails stops the update before anything changes. On a fresh install the shell runs on Quickshell instead, and the next inir update gets them.
  • If qs-rs doesn’t start on your system, the update moves the shell to Quickshell and says so; inir doctor does the same if it stops starting later. The next inir update tries qs-rs again.
  • The version before stays beside the new one, so a rollback brings both back.
  • INIR_PREBUILT=0 inir update skips the downloads and keeps the shell on Quickshell.
  • Without inir-accel (another architecture, INIR_PREBUILT=0 or a failed download) the shell still runs, and Material’s colours from the wallpaper and the app and terminal themes still work. iRiS keeps its default palette and the VSCode, OpenCode and Zed themes are skipped; an install updated from 2.33 keeps the ones it compiled back then.
  • While Material’s Web Apps tab is on, setup and the update also get Qt WebEngine for qs-rs (about 110 MB, once, always the one for the qs-rs you have). inir webengine gets it at any time and restarts the shell. On Quickshell it comes from your distribution’s Qt 6 WebEngine package instead.

Repair

Section titled “Repair”
inir doctor

Checks the install and fixes what it can: missing folders, script permissions, YT Music’s yt-dlp and Deno, and version tracking. It also checks that qs-rs starts on its own Qt (if it doesn’t, the shell moves to Quickshell until the next update), that password prompts get answered (by the shell, or by your own agent), and that inir-accel’s helpers match what is installed. It checks plasma-integration, a colour emoji font, niri-session (not on Void), a power profiles daemon and the fonts the shell and each installed family use, and tries to install the missing ones. With the Web Apps tab on, it gets Qt WebEngine if it is missing.

If you also want a restart and a check of the logs, run inir repair.

Rollback

Section titled “Rollback”
./setup rollback

Lists the snapshots taken before each update, by date. Pick one to restore it.

My changes

Section titled “My changes”
./setup my-changes

Shows the files you changed from the defaults. You can look at the differences, restore the originals, or keep your changes.

Uninstall

Section titled “Uninstall”
./setup uninstall

Removes iNiR and asks before each shared file, such as your Niri config, GTK and Kvantum settings. Your iNiR settings are removed too, so copy them first if you want to keep them. Before it removes anything, it backs them up to ~/.local/share/inir-uninstall-backup- followed by the date and time.

The runtime, the helpers and the inir command that iNiR downloaded go too, and so does the inir launcher.

Packages are not removed. The command prints the commands to remove them, so you can run those yourself.

Use ./setup uninstall -y to take the recommended answer to every question.

Backups

Section titled “Backups”
  • Before a first install, your existing configs are backed up to ~/inir-backup/.
  • Update backups go to ~/.local/state/quickshell/backups/.