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.
Soft-Bricked My Laptop After System Update
Reported by RomanoCodes · filed Oct 20, 2025Closed upstream on 2026-02-01 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
System details
Dell Alienware m51 R13
What's wrong?
Today I tried Omarchy... it was great until I pulled the latest system update and installed it. My laptop did not come back (or even POST) after the reboot.
My main drive had Windows 10 on it, so I cleared a spare 256Gb m2 drive I had available. After installing Omarchy without issue, even rebooting once normally, I grabbed the latest system update (prompted by the system toast notification). The laptop was in UEFI with secure boot turned off.
Upon restarting the machine simply dances through the post-POST keyboard lightshow, but never gets any further.
I have tried pulling all drives and booting with only one drive at a time. No luck.
I have tried doing static clear/memory wipe by removing battery/CMOS/cables and letting it sit for 1hr. No luck.
I have tried loading a previous bios from a fat32-formatted drive with a BIOS_IMG.rcv file in the root. No luck.
I have tried weeping uncontrollably... Still, no luck.
After bouncing some ideas off of AI, it has come to believe that perhaps... well, I can cut-n-paste it for you:
The utility fwupd (Firmware Updater Daemon) is a service used in Linux to update firmware on various components (like the system BIOS, SSDs, etc.) from Linux. When included in a system-wide update like $ pacman -Syu, it can sometimes automatically detect and apply new firmware updates using data from the Linux Vendor Firmware Service (LVFS).
If an update to the system's firmware (BIOS/UEFI) is applied and fails, or if the new firmware is incompatible, it can corrupt the BIOS chip, resulting in a "brick" scenario where the laptop won't POST. The symptoms you describe—keyboard lights pulsing but no POST or display—are consistent with a failed or interrupted BIOS/firmware update.
I suppose this bug is perhaps a two-parter... I'd love to get my machine working again (it was my personal machine), but perhaps it could serve as a warning to others, and perhaps if this is truly a bug perhaps it can be guarded against.
View raw text
### System details Dell Alienware m51 R13 ### What's wrong? Today I tried Omarchy... it was great until I pulled the latest system update and installed it. My laptop did not come back (or even POST) after the reboot. My main drive had Windows 10 on it, so I cleared a spare 256Gb m2 drive I had available. After installing Omarchy without issue, even rebooting once normally, I grabbed the latest system update (prompted by the system toast notification). The laptop was in UEFI with secure boot turned off. Upon restarting the machine simply dances through the post-POST keyboard lightshow, but never gets any further. I have tried pulling all drives and booting with only one drive at a time. No luck. I have tried doing static clear/memory wipe by removing battery/CMOS/cables and letting it sit for 1hr. No luck. I have tried loading a previous bios from a fat32-formatted drive with a BIOS_IMG.rcv file in the root. No luck. I have tried weeping uncontrollably... Still, no luck. After bouncing some ideas off of AI, it has come to believe that perhaps... well, I can cut-n-paste it for you: ----------- The utility fwupd (Firmware Updater Daemon) is a service used in Linux to update firmware on various components (like the system BIOS, SSDs, etc.) from Linux. When included in a system-wide update like $ pacman -Syu, it can sometimes automatically detect and apply new firmware updates using data from the Linux Vendor Firmware Service (LVFS). If an update to the system's firmware (BIOS/UEFI) is applied and fails, or if the new firmware is incompatible, it can corrupt the BIOS chip, resulting in a "brick" scenario where the laptop won't POST. The symptoms you describe—keyboard lights pulsing but no POST or display—are consistent with a failed or interrupted BIOS/firmware update. ----------- I suppose this bug is perhaps a two-parter... I'd love to get my machine working again (it was my personal machine), but perhaps it could serve as a warning to others, and perhaps if this is truly a bug perhaps it can be guarded against.
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.