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.
Enable hibernation bug: resume.conf missing the resume_offset
Reported by NicolasDorier · filed Mar 11, 2026Closed upstream on 2026-04-01 by its own reporter NicolasDorier. GitHub close reason: completed. Closed by its own reporter — not by itself 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
Omarchy 3.4.2
What's wrong?
After enabling hibernation via the menu, my laptop blue screen when waking up.
Upon investigation I remember seeing a "Permission Denied" error while enabling hibernation in omarchy.
I am sorry, but I don't have the logs about it anymore.
However, after I noticed this
cat /etc/limine-entry-tool.d/resume.conf
KERNEL_CMDLINE[default]+=" resume=/dev/mapper/root resume_offset="Notice that the resume_offset= is missing a value.
So I tried to follow what the enable script does on
Suspiciously, this line RESUME_OFFSET=$(btrfs inspect-internal map-swapfile -r "$SWAP_FILE") returns "Permission Denied" when not running as root.
So I believe the setup silently failed.
I've tried to fix it and run
sudo limine-mkinitcpio
sudo limine-updateI am still blue screening, but one thing is sure: resume_offset wasn't set properly before.
EDIT, the resume.conf doesn't seem applied
cat /proc/cmdline
quiet splash cryptdevice=PARTUUID=7cd32dfd-7a98-4743-a74b-386a4abed4cb:root root=/dev/mapper/root zswap.enabled=0 rootflags=subvol=@ rw rootfstype=btrfsEDIT, /proc/cmdline didn't show resume because /etc/default/limine have KERNEL_CMDLINE[default]="cry.. instead of KERNEL_CMDLINE[default]+="cry....
Once fixed, and running limine-mkinitcpio again, the resume= show in /proc/cmdline.
However I still blue screen.
View raw text
### System details Omarchy 3.4.2 ### What's wrong? After enabling hibernation via the menu, my laptop blue screen when waking up. Upon investigation I remember seeing a "Permission Denied" error while enabling hibernation in omarchy. I am sorry, but I don't have the logs about it anymore. However, after I noticed this ```bash cat /etc/limine-entry-tool.d/resume.conf KERNEL_CMDLINE[default]+=" resume=/dev/mapper/root resume_offset=" ``` Notice that the `resume_offset=` is missing a value. So I tried to follow what the enable script does on https://github.com/basecamp/omarchy/blob/2acc2ebfea41255d2cbe6e1204025235dfb166a9/bin/omarchy-hibernation-setup#L76 Suspiciously, this line `RESUME_OFFSET=$(btrfs inspect-internal map-swapfile -r "$SWAP_FILE")` returns "Permission Denied" when not running as `root`. So I believe the setup silently failed. I've tried to fix it and run ```bash sudo limine-mkinitcpio sudo limine-update ``` I am still blue screening, but one thing is sure: resume_offset wasn't set properly before. --- EDIT, the `resume.conf` doesn't seem applied `cat /proc/cmdline` ``` quiet splash cryptdevice=PARTUUID=7cd32dfd-7a98-4743-a74b-386a4abed4cb:root root=/dev/mapper/root zswap.enabled=0 rootflags=subvol=@ rw rootfstype=btrfs ``` --- EDIT, `/proc/cmdline` didn't show resume because `/etc/default/limine` have `KERNEL_CMDLINE[default]="cry..` instead of `KERNEL_CMDLINE[default]+="cry...`. Once fixed, and running `limine-mkinitcpio` again, the `resume=` show in `/proc/cmdline`. However I still blue screen. Related to https://github.com/basecamp/omarchy/issues/4158
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.