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.
System Configuration Override Issue After Waybar Customization Attempt
Reported by zenhooms123321-stack · filed Oct 25, 2025Closed upstream on 2025-10-25 by ryanrhughes. 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
System details
Omarchy
What's wrong?
I am experiencing a critical system configuration issue with my Omarchy distribution installation. The system was functioning correctly until I attempted to modify the Waybar configuration.
Timeline of Events
1. Initial State: Omarchy distribution was running perfectly with all components functioning as expected.
2. Configuration Attempt: While attempting to customize Waybar settings, I navigated to a GitHub repository and executed a command that I believed would help with the configuration.
3. Unintended Installation: The command unexpectedly installed(Kool Arch) distribution components, which overrode my file manager and other system components.
The repo: https://github.com/JaKooLit/Arch-Hyprland
4. Current State: Despite the override, the Omarchy login screen continues to appear upon system reboot, indicating that Omarchy is still partially installed.
Actions Taken
In an attempt to resolve the issue, I tried to remove the kool Arch components that were running on Hyprland. However, this action resulted in the system switching to a Sway desktop environment instead, further complicating the situation.
Current System State
• Login screen displays Omarchy branding
• File manager and other applications have been overridden
• System appears to be running a mixture of Omarchy, Cool Arch, and Sway components
• The original Omarchy configuration and functionality have been lost
Requested Assistance
I would like to restore my system to its original Omarchy configuration prior to these modifications. Specifically, I need guidance on:
1. How to properly remove the Cool Arch and Sway components without damaging the Omarchy installation
2. Steps to restore the original Omarchy file manager and system applications
3. Methods to verify system integrity and ensure all Omarchy components are functioning correctly
4. Best practices for safely customizing Waybar configuration in the future to prevent similar issues
System Information
• Distribution: Omarchy
• Desktop Environment: Originally Hyprland (now mixed with Sway components)
• Display Manager: [Displays Omarchy login screen]
• Issue Origin: Waybar configuration modification attempt
Any assistance in restoring my system to its original Omarchy state would be greatly appreciated. Thank you for your time and support.
View raw text
### System details Omarchy ### What's wrong? I am experiencing a critical system configuration issue with my Omarchy distribution installation. The system was functioning correctly until I attempted to modify the Waybar configuration. Timeline of Events 1. Initial State: Omarchy distribution was running perfectly with all components functioning as expected. 2. Configuration Attempt: While attempting to customize Waybar settings, I navigated to a GitHub repository and executed a command that I believed would help with the configuration. 3. Unintended Installation: The command unexpectedly installed(Kool Arch) distribution components, which overrode my file manager and other system components. The repo: https://github.com/JaKooLit/Arch-Hyprland 4. Current State: Despite the override, the Omarchy login screen continues to appear upon system reboot, indicating that Omarchy is still partially installed. Actions Taken In an attempt to resolve the issue, I tried to remove the kool Arch components that were running on Hyprland. However, this action resulted in the system switching to a Sway desktop environment instead, further complicating the situation. Current System State • Login screen displays Omarchy branding • File manager and other applications have been overridden • System appears to be running a mixture of Omarchy, Cool Arch, and Sway components • The original Omarchy configuration and functionality have been lost Requested Assistance I would like to restore my system to its original Omarchy configuration prior to these modifications. Specifically, I need guidance on: 1. How to properly remove the Cool Arch and Sway components without damaging the Omarchy installation 2. Steps to restore the original Omarchy file manager and system applications 3. Methods to verify system integrity and ensure all Omarchy components are functioning correctly 4. Best practices for safely customizing Waybar configuration in the future to prevent similar issues System Information • Distribution: Omarchy • Desktop Environment: Originally Hyprland (now mixed with Sway components) • Display Manager: [Displays Omarchy login screen] • Issue Origin: Waybar configuration modification attempt Any assistance in restoring my system to its original Omarchy state would be greatly appreciated. Thank you for your time and support.
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.