Proof Portal
Omarchy
ProbeLabs65 findings · 95 requirementsA 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.
Docs Addition: Limine + Snapper
Reported by ryanrhughes · filed Aug 25, 2025Closed upstream on 2025-10-25 by dhh. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not evidence of a fix.
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?
- Not yet mapped to any requirement or component.
- 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?
- Our staff decide whether the report is valid. Where this project allows it, agents decide whether it duplicates another report or a known issue. No decision has been recorded yet.
Original report
Limine + Snapper
Limine is the bootloader of choice in Omarchy chosen for its universal, robust, but easy configuration abilities and integrations. With it, we unlock the ability to have a really great boot experience along with bootable snapshots.
EFI
For systems with EFI support, Limine helps us build a Unified Kernel Image (UKI) that can be booted directly and we add an entry to your EFI boot menu. What this means is that when you boot; you don't see a bootloader on bootup, you just go straight into Omarchy.
The Limine bootloader is still configured as an additional entry. To access it in the event you need to boot a snapshot or enter recovery, just hit your BIOS boot menu button on startup and choose "Limine" from the menu. This is usually esc or del but can vary based on hardware manufacturers.
Limine is also configured as the EFI fallback so that even in the event your NVRAM gets totally wiped, you can still boot in just fine.
Snapshots
Utilizing [Snapper](), we're able to take snapshots before every Omarchy update to allow easy restoration if something goes wrong.
The snapshots for the root subvolume are bootable and automatically added as entries to Limine.
Creating Snapshots
We create snapshots automatically on every Omarchy update but should you want to create your own, you can use omarchy-snapshot create. This will snapshot both the /root and /home mountpoints at the time you create the snapshot.
Booting and Restoring a Snapshot
To boot and restore a snapshot, boot to Limine by selecting it from your EFI boot menu.
From that screen, choose the snapshot you'd like to boot into based on the date and version. The version of Omarchy at the time of the snapshot can be seen at the bottom left corner.
<img width="2832" height="1760" alt="Image" src="https://github.com/user-attachments/assets/a690b61c-16ff-4379-b426-e30d8762f438" />
When you arrive inside, a notification will popup notifying you that you're in a bootable snapshot and if you click it, will start the restoration process. Alternatively, you can utilize omarchy-snapshot restore
<img width="2824" height="1758" alt="Image" src="https://github.com/user-attachments/assets/d1e348db-68c4-4b26-b008-5f2e07935ac2" />
Note: This restoration process will only restore the /root mountpoint. Any changes that would live inside of /home are not restored and need a little bit of extra work to restore, though they do exist.
Restoring /home
This post from Snapper does a good job of outlining the details of some of the intricacies of why the home subvolume isn't just restored with root but it's also difficult for us to tell which pair go together.
We'll have some better tooling to facilitate this process in the future but for now, you can follow the workflow in the post as a way to restore the home subvolume.
View raw text
# Limine + Snapper Limine is the bootloader of choice in Omarchy chosen for its universal, robust, but easy configuration abilities and integrations. With it, we unlock the ability to have a really great boot experience along with bootable snapshots. ## EFI For systems with EFI support, Limine helps us build a Unified Kernel Image (UKI) that can be booted directly and we add an entry to your EFI boot menu. What this means is that when you boot; you don't see a bootloader on bootup, you just go straight into Omarchy. The Limine bootloader is still configured as an additional entry. To access it in the event you need to boot a snapshot or enter recovery, just hit your BIOS boot menu button on startup and choose "Limine" from the menu. This is usually `esc` or `del` but can vary based on hardware manufacturers. Limine is also configured as the EFI fallback so that even in the event your NVRAM gets totally wiped, you can still boot in just fine. ## Snapshots Utilizing [Snapper](), we're able to take snapshots before every Omarchy update to allow easy restoration if something goes wrong. The snapshots for the `root` subvolume are bootable and automatically added as entries to Limine. ## Creating Snapshots We create snapshots automatically on every Omarchy update but should you want to create your own, you can use `omarchy-snapshot create`. This will snapshot both the `/root` and `/home` mountpoints at the time you create the snapshot. ### Booting and Restoring a Snapshot To boot and restore a snapshot, boot to Limine by selecting it from your EFI boot menu. From that screen, choose the snapshot you'd like to boot into based on the date and version. The version of Omarchy at the time of the snapshot can be seen at the bottom left corner. <img width="2832" height="1760" alt="Image" src="https://github.com/user-attachments/assets/a690b61c-16ff-4379-b426-e30d8762f438" /> When you arrive inside, a notification will popup notifying you that you're in a bootable snapshot and if you click it, will start the restoration process. Alternatively, you can utilize `omarchy-snapshot restore` <img width="2824" height="1758" alt="Image" src="https://github.com/user-attachments/assets/d1e348db-68c4-4b26-b008-5f2e07935ac2" /> **Note**: This restoration process will only restore the `/root` mountpoint. Any changes that would live inside of `/home` are not restored and need a little bit of extra work to restore, though they do exist. ### Restoring /home [This post](http://snapper.io/2025/05/16/rollback-any.html) from Snapper does a good job of outlining the details of some of the intricacies of why the `home` subvolume isn't just restored with `root` but it's also difficult for us to tell which pair go together. We'll have some better tooling to facilitate this process in the future but for now, you can follow the workflow in the post as a way to restore the `home` subvolume.
- a690b61c-16ff-4379-b426-e30d8762f438
- d1e348db-68c4-4b26-b008-5f2e07935ac2
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.
No decision has been recorded yet.