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

Hibernate image not restored with linux-omarchy 7.2.5 on MacBookAir6,2

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

Open at source
Decided: Out of scope — decided by agents · verified 3 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

Hibernate image not restored with linux-omarchy 7.2.5 on MacBookAir6,2revision 1 · captured 2026-09-28 21:23 UTC via poll

System details

  • Omarchy 4.0.4-1
  • Apple MacBookAir6,2 (Haswell), Intel integrated graphics
  • systemd 261.2-1, Limine 12.8.0-1
  • Encrypted Btrfs root with a disk swapfile and zram
  • Previously working kernel: linux 7.2.3.arch1-3
  • Kernel where the failure was observed: linux-omarchy 7.2.5-3

What's wrong?

After an Omarchy update switched the default boot from the regular Arch kernel to linux-omarchy, a suspend-then-hibernate cycle powered the laptop off but the next power-on performed a cold boot instead of restoring the session.

This looks like a possible linux-omarchy 7.2.5-3 hibernation-resume regression on this MacBook model. I have one failed cycle on the new kernel, so the kernel is strongly correlated but not yet proven to be the root cause.

The hibernation configuration appears valid:

  • The kernel command line contains both resume= and resume_offset=.
  • The configured resume offset matches the current Btrfs swapfile offset.
  • The active UKI contains both hooks/resume and usr/bin/resume.
  • The same swapfile and resume configuration successfully restored hibernation under linux 7.2.3.arch1-3.

Failed cycle with linux-omarchy 7.2.5-3

Relevant events, with timestamps removed:

systemd-logind: Lid closed.
systemd-logind: Suspending, then hibernating...
systemd-sleep: Performing sleep operation 'suspend'...
kernel: PM: suspend entry (deep)
systemd-sleep: System returned from sleep operation 'suspend-then-hibernate'.
kernel: PM: suspend exit
systemd-sleep: Performing sleep operation 'hibernate'...
kernel: PM: hibernation: hibernation entry

The next power-on has a new boot ID and reports:

kernel: PM: Image not found (code -22)

Successful cycle with linux 7.2.3.arch1-3

Before the kernel switch, the same setup transitioned to hibernation and later restored the session while retaining the same boot ID:

kernel: PM: suspend entry (deep)
systemd-sleep: System returned from sleep operation 'suspend-then-hibernate'.
kernel: PM: suspend exit
systemd-sleep: Performing sleep operation 'hibernate'...
kernel: PM: hibernation: hibernation entry
kernel: PM: hibernation: Basic memory bitmaps created
kernel: PM: hibernation: hibernation exit
systemd-sleep: System returned from sleep operation 'suspend-then-hibernate'.

Steps to reproduce

  1. Boot linux-omarchy 7.2.5-3 on a MacBookAir6,2 with hibernation configured.
  2. Enter hibernation, either directly or through suspend-then-hibernate.
  3. Power the machine back on.
  4. Observe a normal cold boot instead of the previous session being restored.

Expected result

The kernel restores the hibernation image and continues the previous session, as linux 7.2.3.arch1-3 did.

I disabled automatic hibernation after the incident to avoid further session loss, so I have not repeated a destructive confirmation test.

Related but apparently different reports: #5265 (missing/incorrect resume offset) and #6125 (cold boot after hibernate on different hardware).

View raw text
### System details

- Omarchy `4.0.4-1`
- Apple MacBookAir6,2 (Haswell), Intel integrated graphics
- systemd `261.2-1`, Limine `12.8.0-1`
- Encrypted Btrfs root with a disk swapfile and zram
- Previously working kernel: `linux 7.2.3.arch1-3`
- Kernel where the failure was observed: `linux-omarchy 7.2.5-3`

### What's wrong?

After an Omarchy update switched the default boot from the regular Arch kernel to `linux-omarchy`, a suspend-then-hibernate cycle powered the laptop off but the next power-on performed a cold boot instead of restoring the session.

This looks like a possible `linux-omarchy 7.2.5-3` hibernation-resume regression on this MacBook model. I have one failed cycle on the new kernel, so the kernel is strongly correlated but not yet proven to be the root cause.

The hibernation configuration appears valid:

- The kernel command line contains both `resume=` and `resume_offset=`.
- The configured resume offset matches the current Btrfs swapfile offset.
- The active UKI contains both `hooks/resume` and `usr/bin/resume`.
- The same swapfile and resume configuration successfully restored hibernation under `linux 7.2.3.arch1-3`.

#### Failed cycle with `linux-omarchy 7.2.5-3`

Relevant events, with timestamps removed:

```text
systemd-logind: Lid closed.
systemd-logind: Suspending, then hibernating...
systemd-sleep: Performing sleep operation 'suspend'...
kernel: PM: suspend entry (deep)
systemd-sleep: System returned from sleep operation 'suspend-then-hibernate'.
kernel: PM: suspend exit
systemd-sleep: Performing sleep operation 'hibernate'...
kernel: PM: hibernation: hibernation entry
```

The next power-on has a new boot ID and reports:

```text
kernel: PM: Image not found (code -22)
```

#### Successful cycle with `linux 7.2.3.arch1-3`

Before the kernel switch, the same setup transitioned to hibernation and later restored the session while retaining the same boot ID:

```text
kernel: PM: suspend entry (deep)
systemd-sleep: System returned from sleep operation 'suspend-then-hibernate'.
kernel: PM: suspend exit
systemd-sleep: Performing sleep operation 'hibernate'...
kernel: PM: hibernation: hibernation entry
kernel: PM: hibernation: Basic memory bitmaps created
kernel: PM: hibernation: hibernation exit
systemd-sleep: System returned from sleep operation 'suspend-then-hibernate'.
```

#### Steps to reproduce

1. Boot `linux-omarchy 7.2.5-3` on a MacBookAir6,2 with hibernation configured.
2. Enter hibernation, either directly or through `suspend-then-hibernate`.
3. Power the machine back on.
4. Observe a normal cold boot instead of the previous session being restored.

#### Expected result

The kernel restores the hibernation image and continues the previous session, as `linux 7.2.3.arch1-3` did.

I disabled automatic hibernation after the incident to avoid further session loss, so I have not repeated a destructive confirmation test.

Related but apparently different reports: #5265 (missing/incorrect resume offset) and #6125 (cold boot after hibernate on different hardware).

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:42 UTC