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.
Performance power profile runs fans at 100% while idle on Alienware
Reported by floriancheval · filed Aug 19, 2026 · open at source
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
What happened
On an Alienware 16 Aurora AC16250, Omarchy's Performance power profile runs both fans at 100% even when the machine is idle.
There is no load to justify it. CPU package is ~40–55°C, load average ~0.4, GPU ~9W / ~35°C. Fans still sit at ~6500 RPM with fan*_boost at 100 and dell-smm PWM at 255.
This is the profile Omarchy applies on AC after a fresh install (omarchy-powerprofiles-init → omarchy-powerprofiles-set, which defaults AC to performance). Selecting Performance later does the same thing.
powerprofilesctl get is performance. /sys/firmware/acpi/platform_profile is performance. The alienware-wmi platform profile for performance is G-Mode (thermal profile 0xAB), which locks the fans at full speed instead of following temperature.
What I expected
Performance should not pin the fans at 100%. At idle they should follow a temperature curve, as they do in Balanced on this machine (fans stop around 44°C).
Steps to reproduce
- Install Omarchy on an Alienware 16 Aurora AC16250 (plugged in).
- Boot to the desktop and leave the machine idle.
- Fans are at full speed.
- Confirm:
powerprofilesctl get→performancecat /sys/firmware/acpi/platform_profile→performance- sensors /
alienware_wmihwmon: CPU ~40°C, fans ~6500 RPM,fan*_boost100
System
- Omarchy 4.0.0-1
- Kernel 7.1.8-arch1-3
- Alienware 16 Aurora AC16250, BIOS 1.15.0
- Intel Core 7 240H + NVIDIA GeForce RTX 5060 Max-Q
- Hyprland 0.56.2
omarchy-debug --no-sudo --print log is at /tmp/omarchy-debug.log.
Filed by Grok 4.6 via Grok Build.
View raw text
## What happened On an Alienware 16 Aurora AC16250, Omarchy's Performance power profile runs both fans at 100% even when the machine is idle. There is no load to justify it. CPU package is ~40–55°C, load average ~0.4, GPU ~9W / ~35°C. Fans still sit at ~6500 RPM with `fan*_boost` at 100 and dell-smm PWM at 255. This is the profile Omarchy applies on AC after a fresh install (`omarchy-powerprofiles-init` → `omarchy-powerprofiles-set`, which defaults AC to `performance`). Selecting Performance later does the same thing. `powerprofilesctl get` is `performance`. `/sys/firmware/acpi/platform_profile` is `performance`. The `alienware-wmi` platform profile for `performance` is G-Mode (thermal profile `0xAB`), which locks the fans at full speed instead of following temperature. ## What I expected Performance should not pin the fans at 100%. At idle they should follow a temperature curve, as they do in Balanced on this machine (fans stop around 44°C). ## Steps to reproduce 1. Install Omarchy on an Alienware 16 Aurora AC16250 (plugged in). 2. Boot to the desktop and leave the machine idle. 3. Fans are at full speed. 4. Confirm: - `powerprofilesctl get` → `performance` - `cat /sys/firmware/acpi/platform_profile` → `performance` - sensors / `alienware_wmi` hwmon: CPU ~40°C, fans ~6500 RPM, `fan*_boost` 100 ## System - Omarchy 4.0.0-1 - Kernel 7.1.8-arch1-3 - Alienware 16 Aurora AC16250, BIOS 1.15.0 - Intel Core 7 240H + NVIDIA GeForce RTX 5060 Max-Q - Hyprland 0.56.2 `omarchy-debug --no-sudo --print` log is at `/tmp/omarchy-debug.log`. Filed by Grok 4.6 via Grok Build.
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 04:47 UTC