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.
Add the ability to install in multi-boot situations
Reported by ryanrhughes · filed Oct 27, 2025Closed upstream on 2026-07-18. 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
Within the configurator, we currently only support selecting and wiping a full disk.
This leaves a fair number of users who have a legitimate need for dual booting out in the cold and stuck going through a manual install process. This is less than ideal, for many reasons; not the least of which are user experience and just generally being more error prone.
We should add a simple way for users to install Omarchy using the ISO. There are effectively 2 ways I think this could be accomplished easily.
1.) Use Free Space
Require the user to effectively make room for Omarchy on disk. From there, we analyze the disk and establish partition details to utilize the free space only that gets passed over to our archinstall JSON.
We could offer a utility as well at the screen where you're able to perform this like gparted or otherwise so the user could adjust their partitions there but most likely, they will have done that already in preparation from within a GUI.
This method ensures the partitions are created correctly as we don't leave that to the user to control.
2.) Require User Partitioning
Require the user to do all of the partitioning changes themselves, using an included utility or otherwise.
From there, we just offer an option to choose partitions instead of disks, at which point the user is prompted to select their boot partition, as well as their data partition.
This is likely the less complex option on one side but probably results in a change to the archinstall json output since we're not creating partitions, we're using them and need to provide that instruction properly.
In this instance, there are still circumstances we need to check for to ensure the user has partitioned correctly and / or selected the right ones. We need to ensure both size and format are correct at a minimum.
View raw text
Within the [configurator](https://github.com/omacom-io/omarchy-iso/blob/main/configs/airootfs/root/configurator), we currently only support selecting and wiping a full disk. This leaves a fair number of users who have a legitimate need for dual booting out in the cold and stuck going through a manual install process. This is less than ideal, for many reasons; not the least of which are user experience and just generally being more error prone. We should add a **simple** way for users to install Omarchy using the ISO. There are effectively 2 ways I think this could be accomplished easily. ### 1.) Use Free Space Require the user to effectively make room for Omarchy on disk. From there, we analyze the disk and establish partition details to utilize the free space only that gets passed over to our archinstall JSON. We could offer a utility as well at the screen where you're able to perform this like gparted or otherwise so the user could adjust their partitions there but most likely, they will have done that already in preparation from within a GUI. This method ensures the partitions are created correctly as we don't leave that to the user to control. ### 2.) Require User Partitioning Require the user to do all of the partitioning changes themselves, using an included utility or otherwise. From there, we just offer an option to choose partitions instead of disks, at which point the user is prompted to select their boot partition, as well as their data partition. This is likely the less complex option on one side but probably results in a change to the archinstall json output since we're not creating partitions, we're using them and need to provide that instruction properly. In this instance, there are still circumstances we need to check for to ensure the user has partitioned correctly and / or selected the right ones. We need to ensure both size and format are correct at a minimum.
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.