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-2716GitHub issuePublicReceived

I somehow managed to destroy my OS during an update

Reported by fitzzz · filed Aug 29, 2025Closed upstream on 2025-09-16 by dhh. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not evidence of a fix.

Open at source
Received and recorded verbatim. Nothing has been checked yet.

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

I somehow managed to destroy my OS during an updaterevision 1 · captured 2026-10-04 11:35 UTC via poll

Hi all! Not sure how much of an issue this is but I wanted to share my experience.

I had just completed the finishing touches on all my apps, monitor configs, key bindings, etc. I think I accidentally pressed a hot key or something because a terminal with the OMARCHY logo popped up asking for my password seemingly randomly right while I was configuring NVM.

I didn’t think much of it and I just didn’t want to deal with it at that exact moment. I reflexively pressed CTRL+C a few times to close it out. Then I realized it was SUPER+W (still getting used to it).

Seconds later an error on the top bar of my active screen showed up that a bunch of lines in my hyprland.conf couldn’t be parsed. I had a terminal open and navigated to it… my entire ~/.local/share/omarchy directory was gone.

I couldn’t open new terminals, use hotkeys, open the launcher, or access even the top bar because waybar disappeared to make way for the error messages. I tried to run omarchy-update thinking that might help but it said file not found.

I tried whatever I could and then just quickly made peace with it as part of the learning curve. I backed up my local configs and just reinstalled Omarchy instead of sulking.

To be frank I’m pretty new to running Linux as my personal desktop (though I’ve ran Ubuntu servers for quite a long time). I’m not sure exactly what chain of events my actions caused, but I think the messy way I cancelled the update process caused me to get into some weird edge case.

I’m not writing to complain or ask for a fix, but I’m. A huge fan of Omarchy and wanted to let you guys know what happened.

Thanks for taking the time to read this.

View raw text
Hi all! Not sure how much of an issue this is but I wanted to share my experience. 

I had just completed the finishing touches on all my apps, monitor configs, key bindings, etc.  I think I accidentally pressed a hot key or something because a terminal with the OMARCHY logo popped up asking for my password seemingly randomly right while I was configuring NVM.  

I didn’t think much of it and I just didn’t want to deal with it at that exact moment.  I reflexively pressed CTRL+C a few times to close it out.  Then I realized it was SUPER+W (still getting used to it).  

Seconds later an error on the top bar of my active screen showed up that a bunch of lines in my hyprland.conf couldn’t be parsed.  I had a terminal open and navigated to it… my entire ~/.local/share/omarchy directory was gone. 

I couldn’t open new terminals, use hotkeys, open the launcher, or access even the top bar because waybar disappeared to make way for the error messages. I tried to run omarchy-update thinking that might help but it said file not found. 

I tried whatever I could and then just quickly made peace with it as part of the learning curve. I backed up my local configs and just reinstalled Omarchy instead of sulking. 

To be frank I’m pretty new to running Linux as my personal desktop (though I’ve ran Ubuntu servers for quite a long time).  I’m not sure exactly what chain of events my actions caused, but I think the messy way I cancelled the update process caused me to get into some weird edge case. 

I’m not writing to complain or ask for a fix, but I’m. A huge fan of Omarchy and wanted to let you guys know what happened. 

Thanks for taking the time to read this.

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.