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-4138GitHub issuePublicReceived

ghostty causing > 15% iowait

Reported by bcookatpcsd · filed Feb 21, 2026Closed upstream on 2026-02-23 by dhh. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not evidence of a fix.

Received and recorded verbatim. Nothing has been checked yet.

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

ghostty causing > 15% iowaitrevision 1 · captured 2026-10-04 11:49 UTC via poll

System details

Omarchy 3.3.3

What's wrong?

I could only see this with glances.. I have two laptops identical (one for work at home and work at work.. )

both omarchy from 3.0.2, I got a new machine for someone at work and wanted to see how omarchy would run on a laptop with dedicated graphics and more ram.. and using glances.. I saw a crazy high iowait .. after updating bios and any other firmware I could.. still high iowait

assuming it was something with the HP ZBook (but not believing it and couldn't let it go) I reformatted my work at home laptop.. and had the same error..

long story short (too late)

.config/ghosttty/config:

iowait issues

async-backend = epoll

I found that epoll fixes the iowait:
https://github.com/ghostty-org/ghostty/discussions/3224

(or switching to alacritty) resolves the issue

but adding the async-backend fixes the issue

(at least for me)

but again I noticed it via glances and then confirmed on new install..

YMMV

Thank you for taking the time to read this.

View raw text
### System details

Omarchy 3.3.3

### What's wrong?

I could only see this with glances.. I have two laptops identical (one for work at home and work at work.. ) 

both omarchy from 3.0.2, I got a new machine for someone at work and wanted to see how omarchy would run on a laptop with dedicated graphics and more ram.. and using glances.. I saw a crazy high iowait .. after updating bios and any other firmware I could.. still high iowait

assuming it was something with the HP ZBook (but not believing it and couldn't let it go) I reformatted my work at home laptop.. and had the same error.. 

long story short (too late) 

.config/ghosttty/config: 

# iowait issues
async-backend = epoll

I found that epoll fixes the iowait: 
https://github.com/ghostty-org/ghostty/discussions/3224

(or switching to alacritty) resolves the issue

but adding the async-backend fixes the issue

(at least for me) 

but again I noticed it via glances and then confirmed on new install.. 

YMMV

Thank you for taking the time to read this. 

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.