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.
Quickshell AppLibrary causes ~20% CPU usage at idle
Reported by sarniva · filed Aug 13, 2026Closed upstream on 2026-08-13 by the merge of PR #6815 (closed by dhh). GitHub close reason: completed.
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: 4.0.0rc2-1 Hyprland: 0.56.2 Quickshell: quickshell-git 0.3.0 OS: Arch Linux CPU: 8 cores RAM: 7.1 GiB
What's wrong?
When the system is idle, Quickshell consistently uses approximately 20% CPU.
The issue appears to be a feedback loop involving AppLibrary.qml, login-shell initialization, mise, and DesktopEntryMonitor.
Observed behavior
AppLibrary.qml runs the following scans using bash -lc:
- hidden-entries.sh
- icon-index
The scans repeatedly spawn approximately once per second. Each scan consumes around 0.67 seconds of CPU time.
Tracing the processes showed that the login shell runs mise activate bash, which updates the timestamp of:
~/.local/share/mise
Quickshell's DesktopEntryMonitor watches the parent directories of desktop-entry paths. The timestamp update inside ~/.local/share/mise therefore triggers a directory change event, which causes the application library to rescan. The rescan starts another bash -lc login shell, which runs mise activate bash again and updates the same directory.
This creates a self-sustaining loop:
AppLibrary scan
-> bash -lc
-> shell profile initialization
-> mise activate bash
-> ~/.local/share/mise timestamp changes
-> DesktopEntryMonitor directoryChanged
-> AppLibrary scan
Workaround
Changing these commands in:
/usr/share/omarchy/shell/services/AppLibrary.qml
from:
["bash", "-lc", command]
to:
["bash", "-c", command]
eliminated the CPU usage.
The plain non-login shell still produced the expected scan output, but did not source the login profile or trigger mise activate bash. An strace comparison also showed that bash -c no longer performed the repeated utimensat() calls on ~/.local/share/mise.
Possible fix
Use bash -c instead of bash -lc for the AppLibrary scan commands, since these commands do not appear to require login-shell initialization.
It may also be worth preventing scan re-entry or avoiding scans when the directory change originated from the scan's own process.
~Note: This issue was fixed and identified by an AI agent(opencode with deepseek v4 and gpt luna)~
~every text except this was generated by AI~
View raw text
### System details Omarchy: 4.0.0rc2-1 Hyprland: 0.56.2 Quickshell: quickshell-git 0.3.0 OS: Arch Linux CPU: 8 cores RAM: 7.1 GiB ### What's wrong? When the system is idle, Quickshell consistently uses approximately 20% CPU. The issue appears to be a feedback loop involving AppLibrary.qml, login-shell initialization, mise, and DesktopEntryMonitor. **Observed behavior** AppLibrary.qml runs the following scans using bash -lc: - hidden-entries.sh - icon-index The scans repeatedly spawn approximately once per second. Each scan consumes around 0.67 seconds of CPU time. Tracing the processes showed that the login shell runs mise activate bash, which updates the timestamp of: ~/.local/share/mise Quickshell's DesktopEntryMonitor watches the parent directories of desktop-entry paths. The timestamp update inside ~/.local/share/mise therefore triggers a directory change event, which causes the application library to rescan. The rescan starts another bash -lc login shell, which runs mise activate bash again and updates the same directory. This creates a self-sustaining loop: AppLibrary scan -> bash -lc -> shell profile initialization -> mise activate bash -> ~/.local/share/mise timestamp changes -> DesktopEntryMonitor directoryChanged -> AppLibrary scan **Workaround** Changing these commands in: /usr/share/omarchy/shell/services/AppLibrary.qml from: ["bash", "-lc", command] to: ["bash", "-c", command] eliminated the CPU usage. The plain non-login shell still produced the expected scan output, but did not source the login profile or trigger mise activate bash. An strace comparison also showed that bash -c no longer performed the repeated utimensat() calls on ~/.local/share/mise. **Possible fix** Use bash -c instead of bash -lc for the AppLibrary scan commands, since these commands do not appear to require login-shell initialization. It may also be worth preventing scan re-entry or avoiding scans when the directory change originated from the scan's own process. ~Note: This issue was fixed and identified by an AI agent(opencode with deepseek v4 and gpt luna)~ ~every text except this was generated by AI~
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.