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.
Update: Additional Reproduction Details and Diagnostic Findings
Reported by Rambo176 · filed Oct 11, 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
System details
Ryzen 5600x with 32gb of ram and 3060 12gb varient
What's wrong?
Hi, I’ve reproduced the issue again and collected additional diagnostic information that may help narrow down the root cause.
Reproduction Steps
Start Omarchy normally with the top bar in its default position.
Launch Discord.
Quit Discord through the system task manager.
Observe the right-side status bar widgets.
Observed Behaviour
After quitting Discord, the following widgets become unresponsive to mouse interaction:
Dropbox
Tailscale
Agents
Speaker/Audio
The pointing-hand cursor no longer appears when hovering over these affected widgets. Meanwhile, the Display and Ethernet widgets continue to behave normally.
The issue persists until the shell is restarted or the bar is repositioned.
Additional Observation: Repositioning the Bar Fixes the Issue
I noticed that moving the status bar to a different position, such as the left or right side of the screen, makes the issue disappear.
This is an important detail because changing the bar's position appears to restore normal interaction without requiring the same troubleshooting steps. It may indicate a relationship with the bar's geometry, layout recalculation, or input handling after the tray state changes, although I cannot confirm the exact cause.
Diagnostic Findings
- hyprctl layers
The output shows a single monitor (HDMI-A-2, 1920×1080) and the Omarchy bar at 1920×24. No additional top or overlay layer was visible in the captured output.
- Journal logs
Around Discord startup, the following Quickshell warnings appeared:
Error updating property StatusNotifierItem:IconName
QDBusError("org.freedesktop.DBus.Error.Failed", "error occurred in Get")
I cannot confirm whether these warnings are directly responsible, but they may be worth investigating in relation to system tray updates.
Request for Further Investigation
Given that the issue is reproducible after quitting Discord and appears to disappear when the bar is repositioned, could the investigation look more closely at:
Right-side widget layout recalculation after a tray item disappears.
Pointer input regions and hit-testing after the bar's geometry changes.
Widget registration and unregistration during tray item lifecycle changes.
Whether repositioning the bar triggers a layout or input-state refresh that restores normal behaviour.
I understand that the exact root cause has not yet been established, and I do not want to assume that the observed warnings are necessarily responsible.
However, the reproducible trigger, the affected widgets, the missing pointing-hand cursor, and the fact that repositioning the bar resolves the issue provide additional evidence that may help isolate the problem.
I hope these findings can help move the investigation forward toward a reliable fix in a future Omarchy update, rather than requiring users to restart the shell or reposition the bar as a workaround.
Thanks for continuing to investigate this issue.
View raw text
### System details
Ryzen 5600x with 32gb of ram and 3060 12gb varient
### What's wrong?
Hi, I’ve reproduced the issue again and collected additional diagnostic information that may help narrow down the root cause.
Reproduction Steps
Start Omarchy normally with the top bar in its default position.
Launch Discord.
Quit Discord through the system task manager.
Observe the right-side status bar widgets.
Observed Behaviour
After quitting Discord, the following widgets become unresponsive to mouse interaction:
Dropbox
Tailscale
Agents
Speaker/Audio
The pointing-hand cursor no longer appears when hovering over these affected widgets. Meanwhile, the Display and Ethernet widgets continue to behave normally.
The issue persists until the shell is restarted or the bar is repositioned.
Additional Observation: Repositioning the Bar Fixes the Issue
I noticed that moving the status bar to a different position, such as the left or right side of the screen, makes the issue disappear.
This is an important detail because changing the bar's position appears to restore normal interaction without requiring the same troubleshooting steps. It may indicate a relationship with the bar's geometry, layout recalculation, or input handling after the tray state changes, although I cannot confirm the exact cause.
Diagnostic Findings
1. hyprctl layers
The output shows a single monitor (HDMI-A-2, 1920×1080) and the Omarchy bar at 1920×24. No additional top or overlay layer was visible in the captured output.
2. Journal logs
Around Discord startup, the following Quickshell warnings appeared:
Error updating property StatusNotifierItem:IconName
QDBusError("org.freedesktop.DBus.Error.Failed", "error occurred in Get")
I cannot confirm whether these warnings are directly responsible, but they may be worth investigating in relation to system tray updates.
Request for Further Investigation
Given that the issue is reproducible after quitting Discord and appears to disappear when the bar is repositioned, could the investigation look more closely at:
Right-side widget layout recalculation after a tray item disappears.
Pointer input regions and hit-testing after the bar's geometry changes.
Widget registration and unregistration during tray item lifecycle changes.
Whether repositioning the bar triggers a layout or input-state refresh that restores normal behaviour.
I understand that the exact root cause has not yet been established, and I do not want to assume that the observed warnings are necessarily responsible.
However, the reproducible trigger, the affected widgets, the missing pointing-hand cursor, and the fact that repositioning the bar resolves the issue provide additional evidence that may help isolate the problem.
I hope these findings can help move the investigation forward toward a reliable fix in a future Omarchy update, rather than requiring users to restart the shell or reposition the bar as a workaround.
Thanks for continuing to investigate this issue.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-11 10:54 UTC