Proof Portal

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-374GitHub issuePublicDecided· Out of scope

Random hard crashes (instant power-off) on ThinkPad X220 since linux-omarchy 7.2.5-3; stock linux 7.2.3 is stable

Reported by tami1A84 · filed Sep 18, 2026 · open at source

Decided: Out of scope — decided by agents · verified 4 days ago.

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?
AreaOutside the audited area· Decided by agents · verified
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?
Decided by agents and verified by a second, independent agent — see the decision.

Original report

Random hard crashes (instant power-off) on ThinkPad X220 since linux-omarchy 7.2.5-3; stock linux 7.2.3 is stablerevision 1 · captured 2026-09-28 21:23 UTC via poll

Random hard crashes on ThinkPad X220 since linux-omarchy 7.2.5-3; stock linux 7.2.3 is stable

Summary

After Omarchy 4.0.4 installed linux-omarchy 7.2.5-3, the machine started crashing randomly (power loss without reboot — power button needed). Rolling back to the stock Arch linux 7.2.3.arch1-3 kernel completely stopped the crashes, so the linux-omarchy 7.2.5-3 kernel appears to be the cause.

System

  • ThinkPad X220 (4286PH9), BIOS 8DET55WW (1.25)
  • Intel Core i7-2640M (Sandy Bridge), i915 Gen-6 graphics
  • Omarchy 4.0.4, Hyprland 0.56.2
  • Faulty/degraded battery (BAT0 at ~4% of design capacity), normally on AC power

Timeline (from last -x / journalctl)

Crashes are unclean terminations — the previous boot ends with no shutdown record and normal log activity (last messages are routine UFW BLOCK lines), i.e. the machine just lost power instantly. No oops, no panic, no MCE, no pstore entry, no coredump from the kernel.

BootKernelStartEndOutcome
-47.2.5-3-omarchySep 16 11:18Sep 16 15:35crash (~4h20m uptime)
-37.2.5-3-omarchySep 16 16:38Sep 16 16:45crash (~8m uptime)
-27.2.5-3-omarchySep 16 16:53Sep 16 17:53crash (~1h uptime)
-17.2.5-3-omarchySep 16 17:55Sep 16 18:14clean shutdown (I rolled back to stock)
07.2.3-arch1-3Sep 16 18:14—stable, 2 days and counting, no crash

Before Sep 16 (stock linux 7.2.3), the machine had 21 clean boots back to Sep 9 with uptimes up to ~23h and zero crashes.

pacman -Qi shows linux-omarchy 7.2.5-3 installed 2026-09-16 11:15 JST — the first crash boot started at 11:18 the same morning.

What was ruled out

  • No kernel panic / oops / MCE anywhere in the journals of the crashed boots.
  • /sys/fs/pstore empty; no kernel coredumps.
  • Journal of each crashed boot ends mid-stream with routine traffic (UFW BLOCK lines every ~2 min), consistent with an instant power loss rather than a software hang.
  • The only somewhat relevant hardware note is a badly degraded battery (4.2% design capacity) — possibly relevant to power-rail behavior under load, but the crash correlation with the kernel switch (4 crashes in ~5 hours on 7.2.5-3, zero crashes in 9 days on 7.2.3 before and 2 days after) is very strong.

Expected behavior

No crashes on stock linux 7.2.3.arch1-3 — reproduced over ~11 days of usage on either side of the linux-omarchy 7.2.5-3 window.

Workaround

Booting the stock linux kernel instead of linux-omarchy avoids the crashes entirely.

View raw text
# Random hard crashes on ThinkPad X220 since linux-omarchy 7.2.5-3; stock `linux` 7.2.3 is stable

## Summary

After Omarchy 4.0.4 installed `linux-omarchy 7.2.5-3`, the machine started crashing randomly (power loss without reboot — power button needed). Rolling back to the stock Arch `linux 7.2.3.arch1-3` kernel completely stopped the crashes, so the `linux-omarchy 7.2.5-3` kernel appears to be the cause.

## System

- ThinkPad X220 (4286PH9), BIOS 8DET55WW (1.25)
- Intel Core i7-2640M (Sandy Bridge), i915 Gen-6 graphics
- Omarchy 4.0.4, Hyprland 0.56.2
- Faulty/degraded battery (BAT0 at ~4% of design capacity), normally on AC power

## Timeline (from `last -x` / journalctl)

Crashes are unclean terminations — the previous boot ends with no shutdown record and normal log activity (last messages are routine UFW BLOCK lines), i.e. the machine just lost power instantly. No oops, no panic, no MCE, no pstore entry, no coredump from the kernel.

| Boot | Kernel | Start | End | Outcome |
|---|---|---|---|---|
| -4 | 7.2.5-3-omarchy | Sep 16 11:18 | Sep 16 15:35 | **crash** (~4h20m uptime) |
| -3 | 7.2.5-3-omarchy | Sep 16 16:38 | Sep 16 16:45 | **crash** (~8m uptime) |
| -2 | 7.2.5-3-omarchy | Sep 16 16:53 | Sep 16 17:53 | **crash** (~1h uptime) |
| -1 | 7.2.5-3-omarchy | Sep 16 17:55 | Sep 16 18:14 | clean shutdown (I rolled back to stock) |
| 0 | 7.2.3-arch1-3 | Sep 16 18:14 | — | stable, 2 days and counting, no crash |

Before Sep 16 (stock `linux 7.2.3`), the machine had 21 clean boots back to Sep 9 with uptimes up to ~23h and **zero** crashes.

`pacman -Qi` shows `linux-omarchy 7.2.5-3` installed 2026-09-16 11:15 JST — the first crash boot started at 11:18 the same morning.

## What was ruled out

- No kernel panic / oops / MCE anywhere in the journals of the crashed boots.
- `/sys/fs/pstore` empty; no kernel coredumps.
- Journal of each crashed boot ends mid-stream with routine traffic (UFW BLOCK lines every ~2 min), consistent with an instant power loss rather than a software hang.
- The only somewhat relevant hardware note is a badly degraded battery (4.2% design capacity) — possibly relevant to power-rail behavior under load, but the crash correlation with the kernel switch (4 crashes in ~5 hours on 7.2.5-3, zero crashes in 9 days on 7.2.3 before and 2 days after) is very strong.

## Expected behavior

No crashes on stock `linux 7.2.3.arch1-3` — reproduced over ~11 days of usage on either side of the `linux-omarchy 7.2.5-3` window.

## Workaround

Booting the stock `linux` kernel instead of `linux-omarchy` avoids the crashes entirely.

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.

  • Out of scopeDecided by agents · verified · 2026-10-09 15:15 UTC