Proof Portal

Sign in
Project overview

Omarchy

ProbeLabs65 findings · 95 requirements

A proof layer — requirements, tests and verified fixes — for two of Omarchy's subsystems: the application menu (launcher scripts, QML model, JSONC config, search and selection) and the lock screen (lock scripts, QML, PAM authentication). Scope is deliberately limited to those components of omacom/omarchy; the rest of the distribution is not covered.

Inbox
ReportR-1881GitHub issuePublicDecided· Out of scope

[Bug]: limine-snapper-sync inactive due to missing inotify-tools dependency & missing Snapper root configuration

Reported by mikemayuare · filed Aug 8, 2026 · open at source

Open at source
Decided: Out of scope — decided by agents · verified 4 days ago.

At a glance

1 · What is claimed?
Only the report text below — no validator has restated it as checkable claims yet.
2 · What does it affect?
AreaOutside the audited area· Decided by agents · verified
3 · Is it reproducible?
No validation has been run yet.
4 · What remains unclear?
  • Not validated yet: no claims, no reproducer.
5 · What happens next?
Decided by agents and verified by a second, independent agent — see the decision.

Original report

[Bug]: limine-snapper-sync inactive due to missing inotify-tools dependency & missing Snapper root configurationrevision 1 · captured 2026-09-28 21:29 UTC via poll

System details

Omarchy 3.8.4

What's wrong?

Description

On a fresh installation of Omarchy, automatic boot snapshot syncing fails to function out of the box.

Specifically:

  1. limine-snapper-sync.service defaults to an inactive (dead) state because limine-snapper-watcher fails with inotifywait is not installed.
  2. Running standard snapshot operations fails because Snapper is not initialized with a default root configuration (/etc/snapper/configs/root), nor is /.snapshots mounted as a dedicated subvolume.

Environment / System Information

  • OS: Omarchy
  • Bootloader: Limine (limine-snapper-sync)
  • Filesystem: Btrfs
  • Snapshot Tool: Snapper / omarchy-snapshot

Steps to Reproduce

  1. Install a fresh instance of Omarchy with official ISO.
  2. Check limine-snapper-sync status in terminal:
systemctl status limine-snapper-sync.service

Observe: Service exits with code 0/SUCCESS and logs inotifywait is not installed. Falling back to Snapper plugin integration. before deactivating.
3. Check Snapper configuration:

sudo snapper list-configs

Observe: Output returns no configs (The config 'root' does not exist).
4. Attempt creating a snapshot via omarchy-snapshot create or snapper:

omarchy-snapshot create

Observe: Fails silently.

Expected Behavior

  • inotify-tools should be installed as an explicit dependency for limine-snapper-sync so limine-snapper-watcher stays active (active (running)).
  • A Snapper configuration (e.g., root) mapped to / should be generated out-of-the-box, with /.snapshots backed by a dedicated @snapshots top-level Btrfs subvolume.

Actual Behavior

  • limine-snapper-sync exits immediately upon boot due to missing inotifywait (inotify-tools package).
  • /.snapshots subvolume and /etc/snapper/configs/root are missing, requiring manual initialization before any snapshot workflow works.

Workaround / Manual Fix

# 1. Install missing dependency & restart watcher
sudo pacman -S inotify-tools
sudo systemctl restart limine-snapper-sync.service

# 2. Initialize Snapper root config
sudo snapper -c root create-config /
View raw text
### System details

Omarchy 3.8.4

### What's wrong?


### Description

On a fresh installation of Omarchy, automatic boot snapshot syncing fails to function out of the box.

Specifically:

1. `limine-snapper-sync.service` defaults to an `inactive (dead)` state because `limine-snapper-watcher` fails with `inotifywait is not installed`.
2. Running standard snapshot operations fails because Snapper is not initialized with a default `root` configuration (`/etc/snapper/configs/root`), nor is `/.snapshots` mounted as a dedicated subvolume.

### Environment / System Information

* **OS:** Omarchy
* **Bootloader:** Limine (`limine-snapper-sync`)
* **Filesystem:** Btrfs
* **Snapshot Tool:** Snapper / `omarchy-snapshot`

### Steps to Reproduce

1. Install a fresh instance of Omarchy with official ISO.
2. Check `limine-snapper-sync` status in terminal:
```bash
systemctl status limine-snapper-sync.service

```


*Observe:* Service exits with code `0/SUCCESS` and logs `inotifywait is not installed. Falling back to Snapper plugin integration.` before deactivating.
3. Check Snapper configuration:
```bash
sudo snapper list-configs

```


*Observe:* Output returns no configs (`The config 'root' does not exist`).
4. Attempt creating a snapshot via `omarchy-snapshot create` or `snapper`:
```bash
omarchy-snapshot create

```


*Observe:* Fails silently.

### Expected Behavior

* `inotify-tools` should be installed as an explicit dependency for `limine-snapper-sync` so `limine-snapper-watcher` stays active (`active (running)`).
* A Snapper configuration (e.g., `root`) mapped to `/` should be generated out-of-the-box, with `/.snapshots` backed by a dedicated `@snapshots` top-level Btrfs subvolume.

### Actual Behavior

* `limine-snapper-sync` exits immediately upon boot due to missing `inotifywait` (`inotify-tools` package).
* `/.snapshots` subvolume and `/etc/snapper/configs/root` are missing, requiring manual initialization before any snapshot workflow works.

### Workaround / Manual Fix

```bash
# 1. Install missing dependency & restart watcher
sudo pacman -S inotify-tools
sudo systemctl restart limine-snapper-sync.service

# 2. Initialize Snapper root config
sudo snapper -c root create-config /

```

Validation

Not checked yet. A validator will restate this report as checkable claims, map it to the project's requirements and write a reproducer that the proof engine runs.

Linked

Not linked to any known issue, other report or change yet.

Decision

Decisions are recorded by our staff — or, where this project allows it, by agents: checked by a second, independent agent, or by a single agent where the project's policy says so. Any decision reached so far is shown below.

  • Out of scopeDecided by agents · verified · 2026-10-09 04:00 UTC