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

Intel Iris Xe on Arch feels laggy

Reported by atiqullahsadeqi · filed Sep 11, 2025Closed upstream on 2025-09-11. 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

Intel Iris Xe on Arch feels laggyrevision 1 · captured 2026-10-04 11:35 UTC via poll

System details

Dell Latitude 7420, CPU: Intel Core i7 11th Gen, RAM: 32 GB, GPU: Intel Iris Xe (integrated) + 16 GB built-in Intel graphics memory, torage: 1 TB SSD

What's wrong?

Sorry if this is not relatable

Hey everyone, I’m trying to get the best performance out of my Intel Iris Xe on Arch Linux and wanted to see if anyone has ideas or suggestions. Here’s my setup:

Dell Latitude 7420

CPU: Intel Core i7 11th Gen

RAM: 32 GB

GPU: Intel Iris Xe (integrated) + 16 GB built-in Intel graphics memory

Storage: 1 TB SSD

Some context on my experience:

I installed Arch with Hyprland previously, and back then even just two Chrome tabs could push CPU and RAM usage up to 90%.

Now, with Omarchy, memory usage shows only 10–15% even with Android Studio emulator open, but it’s still laggy.

If I open btop SUPER + T with one or two Chrome tabs, I can really feel the heaviness.

I also use two monitors, and performance drops a lot with both. With just my laptop display, it feels much smoother.

Things I already tried:

Installed latest Mesa and Vulkan Intel drivers:

sudo pacman -S mesa vulkan-intel libva-intel-driver intel-media-driver

If anyone has tips for better Iris Xe performance on Linux, or configs I should check, I’d really appreciate the help! 🙏

View raw text
### System details

Dell Latitude 7420, CPU: Intel Core i7 11th Gen, RAM: 32 GB, GPU: Intel Iris Xe (integrated) + 16 GB built-in Intel graphics memory, torage: 1 TB SSD

### What's wrong?

Sorry if this is not relatable 

Hey everyone, I’m trying to get the best performance out of my Intel Iris Xe on Arch Linux and wanted to see if anyone has ideas or suggestions. Here’s my setup:

Dell Latitude 7420

CPU: Intel Core i7 11th Gen

RAM: 32 GB

GPU: Intel Iris Xe (integrated) + 16 GB built-in Intel graphics memory

Storage: 1 TB SSD


Some context on my experience:

I installed Arch with Hyprland previously, and back then even just two Chrome tabs could push CPU and RAM usage up to 90%.

Now, with Omarchy, memory usage shows only 10–15% even with Android Studio emulator open, but it’s still laggy.

If I open btop SUPER + T with one or two Chrome tabs, I can really feel the heaviness.

I also use two monitors, and performance drops a lot with both. With just my laptop display, it feels much smoother.

Things I already tried:

Installed latest Mesa and Vulkan Intel drivers:

`sudo pacman -S mesa vulkan-intel libva-intel-driver intel-media-driver`

If anyone has tips for better Iris Xe performance on Linux, or configs I should check, I’d really appreciate the help! 🙏

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.