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.
Severe CPU degradation on MacBook Air 2015 caused by broadcom-wl (BCM4360) IRQ storm on kernel 6.19
Reported by dwotV · filed Apr 23, 2026Closed upstream on 2026-04-29 by its own reporter dwotV. 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.5.1, Linux 6.19.12-arch1-1, MacBook Air 2015
What's wrong?
After a clean installation, the system runs with normal CPU performance. However, after updating the system (which includes the update to Limine 11.4.0 intended to fix keyboard/trackpad issues), CPU performance becomes severely degraded.
What works (before update)
- CPU scales normally (up to ~2.7 GHz)
- System is responsive
- Browsers (Chromium/Firefox) run smoothly
- No abnormal fan behavior
What breaks (after update)
- CPU frequency drops to ~500 MHz under load
- All CPU cores stay near ~99% usage
- System becomes slow and unresponsive
- Browsers (Chromium and Firefox) become laggy (e.g., video playback)
- Fan runs constantly at high speed (~6500 RPM)
- CPU temperatures remain normal (~40–45°C)
Steps to reproduce
- Perform a clean installation
- Verify normal system performance
- Update the system (includes Limine 11.4.0)
- Reboot
- Open a browser and play a video
- Monitor CPU frequency
Context
This update was applied after seeing the following note from the maintainer:
“I’m bumping the stable mirror now. Then we’ll have Limine 11.4.0 available when you go to update. That should fix this.”
The update successfully resolved the keyboard and trackpad issue affecting MacBook models (2015–2017), but introduced this CPU performance problem.
View raw text
### System details Omarchy 3.5.1, Linux 6.19.12-arch1-1, MacBook Air 2015 ### What's wrong? After a clean installation, the system runs with normal CPU performance. However, after updating the system (which includes the update to Limine 11.4.0 intended to fix keyboard/trackpad issues), CPU performance becomes severely degraded. #### What works (before update) - CPU scales normally (up to ~2.7 GHz) - System is responsive - Browsers (Chromium/Firefox) run smoothly - No abnormal fan behavior #### What breaks (after update) - CPU frequency drops to ~500 MHz under load - All CPU cores stay near ~99% usage - System becomes slow and unresponsive - Browsers (Chromium and Firefox) become laggy (e.g., video playback) - Fan runs constantly at high speed (~6500 RPM) - CPU temperatures remain normal (~40–45°C) #### Steps to reproduce 1. Perform a clean installation 2. Verify normal system performance 3. Update the system (includes Limine 11.4.0) 4. Reboot 5. Open a browser and play a video 6. Monitor CPU frequency #### Context This update was applied after seeing the following note from the maintainer: >“I’m bumping the stable mirror now. Then we’ll have Limine 11.4.0 available when you go to update. That should fix this.” The update successfully resolved the keyboard and trackpad issue affecting MacBook models (2015–2017), but introduced this CPU performance problem.
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.