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.
Hibernate on pre-T2 Intel Macs reboots instead of powering off
Reported by animadito · filed Sep 3, 2026 · open at source
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
Summary
Hibernate on pre-T2 Intel MacBook models reboots instead of powering off, but resume works correctly.
Environment
- Machine: MacBookPro11,1 (2014, Intel Haswell)
- Omarchy: 4.x
- GPU: Intel integrated only (no dGPU)
- Kernel: 7.x
What happens
- User triggers hibernate from Omarchy menu (\
systemctl hibernate\) - Machine writes hibernation image ✓
- Machine reboots instead of powering off ✗
- After cold boot, session resumes correctly ✓
Root cause
\/sys/power/disk\ shows \[platform] shutdown\ — systemd tries platform mode first (ACPI S4), which fails on this hardware, triggering an unexpected reboot.
Regular shutdown (\systemctl poweroff\) works correctly because it uses the shutdown power-off path directly.
Workaround
Creating \/etc/systemd/sleep.conf.d/hibernatemode.conf\ with \HibernateMode=shutdown\ fixes the issue. This makes hibernate use the same shutdown code path as regular shutdown (see \bin/omarchy-system-shutdown\ which calls \systemctl poweroff\).
Questions for the community
- Does this affect other pre-T2 Intel Macs (MacBookPro11,x, MacBookAir6,x, etc.)?
- Does this affect non-Apple hardware with broken ACPI S4?
- Should this be applied universally to all systems, or gated on hardware detection?
Related
- kernel PM debugging docs recommend shutdown mode for "systems with broken BIOSes"
- ArchWiki documents the same symptom under "System does not power off when hibernating"
- PR #8017 uses the same fix for ThinkBook X IMH which has broken ACPI
View raw text
## Summary Hibernate on pre-T2 Intel MacBook models reboots instead of powering off, but resume works correctly. ## Environment - Machine: MacBookPro11,1 (2014, Intel Haswell) - Omarchy: 4.x - GPU: Intel integrated only (no dGPU) - Kernel: 7.x ## What happens 1. User triggers hibernate from Omarchy menu (\`systemctl hibernate\`) 2. Machine writes hibernation image ✓ 3. Machine reboots instead of powering off ✗ 4. After cold boot, session resumes correctly ✓ ## Root cause \`/sys/power/disk\` shows \`[platform] shutdown\` — systemd tries platform mode first (ACPI S4), which fails on this hardware, triggering an unexpected reboot. Regular shutdown (\`systemctl poweroff\`) works correctly because it uses the shutdown power-off path directly. ## Workaround Creating \`/etc/systemd/sleep.conf.d/hibernatemode.conf\` with \`HibernateMode=shutdown\` fixes the issue. This makes hibernate use the same shutdown code path as regular shutdown (see \`bin/omarchy-system-shutdown\` which calls \`systemctl poweroff\`). ## Questions for the community 1. Does this affect other pre-T2 Intel Macs (MacBookPro11,x, MacBookAir6,x, etc.)? 2. Does this affect non-Apple hardware with broken ACPI S4? 3. Should this be applied universally to all systems, or gated on hardware detection? ## Related - [kernel PM debugging docs](https://docs.kernel.org/power/basic-pm-debugging.html) recommend shutdown mode for "systems with broken BIOSes" - ArchWiki documents the same symptom under "System does not power off when hibernating" - PR #8017 uses the same fix for ThinkBook X IMH which has broken ACPI
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 10:40 UTC