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

linux-omarchy 7.2.5-3: PoE 2 freezes and stutters; standard Arch 7.2.3 resolves it

Reported by WolfOfSesameSt · filed Oct 1, 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

linux-omarchy 7.2.5-3: PoE 2 freezes and stutters; standard Arch 7.2.3 resolves itrevision 1 · captured 2026-10-01 16:14 UTC via poll

System details

  • Omarchy 4.0.4-1, x86_64
  • Intel Core i7-11700K; NVIDIA RTX 3070 8 GB
  • Failing kernel: linux-omarchy 7.2.5-3 (uname: 7.2.5-3-omarchy)
  • Working comparison: standard Arch linux 7.2.3.arch1-3 (uname: 7.2.3-arch1-3)
  • NVIDIA open kernel module and userspace driver: 610.57.04 in both tests
  • Path of Exile 2, Steam app 2694490, build 25568465; Proton Experimental build 25502719; Vulkan renderer

What's wrong?

After upgrading from Omarchy 4.0.3 to 4.0.4 and rebooting into the newly defaulted linux-omarchy kernel, Path of Exile 2 suffered severe stuttering and repeated freezes/disconnections. Rebooting into the already-installed standard Arch kernel resolved the symptoms in the user's gameplay test, without changing the NVIDIA driver, game settings, Proton version, or game installation between those two tests.

Reproduction / comparison

  1. Upgrade to Omarchy 4.0.4, which installs and prioritizes linux-omarchy.
  2. Boot 7.2.5-3-omarchy and play PoE 2 using Proton Experimental and Vulkan.
  3. Observe severe stuttering and freezes during gameplay/area transitions.
  4. Reboot into standard Arch 7.2.3-arch1-3, keeping the same installation and settings.
  5. The user reports that gameplay is working normally again.

This is one machine's failing-to-working kernel comparison, not a bisect. The specific kernel change responsible is unknown.

Relevant diagnostics

The failing run's game log included:

error X3663: thread sync operation found in varying flow control, consider reformulating your algorithm so all threads will hit the sync simultaneously
Deadlock detected with timeout 15000ms; running graph nodes: Present
Recovered from deadlock
Deadlock detected with timeout 15000ms; running graph nodes: RecordMetaPasses
Abnormal disconnect: An unexpected disconnection occurred.

These are correlated game diagnostics, not proof that the kernel directly caused shader compilation errors. No NVIDIA Xid, OOM kill, or local-disk I/O error was found during the failing internal-SSD run.

An earlier attempt ran from external USB storage and had real USB resets/read failures. To remove that variable, the game, prefix, Proton, and Steam runtime were moved to internal NVMe and passed Steam integrity checks. The severe stutter/freeze then reproduced on linux-omarchy from the verified internal installation. The successful standard-kernel test used that same internal installation.

The previously running kernel before the update/reboot was 7.1.9-arch1-2, but the successful comparison above is specifically 7.2.3-arch1-3.

omarchy debug --no-sudo --print returned "Unknown Omarchy command" on this installation; relevant versions and observations are included here instead. Full game logs are omitted because they contain chat/account information.

Workaround

Prefer the standard linux entry in /etc/default/limine BOOT_ORDER and set the Limine default to Omarchy/linux. Both kernel packages remain installed. No full-system rollback was required.

Filed by GPT-6 via Codex, with user-provided gameplay confirmation.

View raw text
### System details

- Omarchy 4.0.4-1, x86_64
- Intel Core i7-11700K; NVIDIA RTX 3070 8 GB
- Failing kernel: linux-omarchy 7.2.5-3 (uname: 7.2.5-3-omarchy)
- Working comparison: standard Arch linux 7.2.3.arch1-3 (uname: 7.2.3-arch1-3)
- NVIDIA open kernel module and userspace driver: 610.57.04 in both tests
- Path of Exile 2, Steam app 2694490, build 25568465; Proton Experimental build 25502719; Vulkan renderer

### What's wrong?

After upgrading from Omarchy 4.0.3 to 4.0.4 and rebooting into the newly defaulted linux-omarchy kernel, Path of Exile 2 suffered severe stuttering and repeated freezes/disconnections. Rebooting into the already-installed standard Arch kernel resolved the symptoms in the user's gameplay test, without changing the NVIDIA driver, game settings, Proton version, or game installation between those two tests.

### Reproduction / comparison

1. Upgrade to Omarchy 4.0.4, which installs and prioritizes linux-omarchy.
2. Boot 7.2.5-3-omarchy and play PoE 2 using Proton Experimental and Vulkan.
3. Observe severe stuttering and freezes during gameplay/area transitions.
4. Reboot into standard Arch 7.2.3-arch1-3, keeping the same installation and settings.
5. The user reports that gameplay is working normally again.

This is one machine's failing-to-working kernel comparison, not a bisect. The specific kernel change responsible is unknown.

### Relevant diagnostics

The failing run's game log included:

```text
error X3663: thread sync operation found in varying flow control, consider reformulating your algorithm so all threads will hit the sync simultaneously
Deadlock detected with timeout 15000ms; running graph nodes: Present
Recovered from deadlock
Deadlock detected with timeout 15000ms; running graph nodes: RecordMetaPasses
Abnormal disconnect: An unexpected disconnection occurred.
```

These are correlated game diagnostics, not proof that the kernel directly caused shader compilation errors. No NVIDIA Xid, OOM kill, or local-disk I/O error was found during the failing internal-SSD run.

An earlier attempt ran from external USB storage and had real USB resets/read failures. To remove that variable, the game, prefix, Proton, and Steam runtime were moved to internal NVMe and passed Steam integrity checks. The severe stutter/freeze then reproduced on linux-omarchy from the verified internal installation. The successful standard-kernel test used that same internal installation.

The previously running kernel before the update/reboot was 7.1.9-arch1-2, but the successful comparison above is specifically 7.2.3-arch1-3.

`omarchy debug --no-sudo --print` returned "Unknown Omarchy command" on this installation; relevant versions and observations are included here instead. Full game logs are omitted because they contain chat/account information.

### Workaround

Prefer the standard `linux` entry in `/etc/default/limine` BOOT_ORDER and set the Limine default to `Omarchy/linux`. Both kernel packages remain installed. No full-system rollback was required.

Filed by GPT-6 via Codex, with user-provided gameplay confirmation.

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 20:26 UTC