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.
Bazaar Flatpak opens two windows from a single application-menu launch
Reported by JosephM0on · filed Oct 8, 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
Omarchy 4.0.4-1; Hyprland 0.56.2-2; UWSM 0.26.7-1; Flatpak 1.18.2-1; Bazaar 0.9.7 (Flathub stable, system installation).
What's wrong?
Launching Bazaar once from the Omarchy application menu opens two Bazaar windows. The problem has been happening for some time and was reproduced during diagnosis.
Expected: one launch opens one window.
Actual: two windows appear, both belonging to the same Bazaar process.
Steps to reproduce
- Start with Bazaar closed.
- Select Bazaar once in the Omarchy application menu.
- Observe two Bazaar windows.
The issue was also reproduced with a single invocation:
uwsm app -- gtk-launch io.github.kolunmi.Bazaar.desktopDiagnostic evidence
The application emitted the following messages during one launch:
(bazaar-daemon): Application starting
(bazaar-daemon): Relaunch requested via D-Bus
(bazaar-daemon): Application starting
(bazaar-daemon): Application exited (status 0)hyprctl clients -j confirmed two windows with class io.github.kolunmi.Bazaar and the same PID.
The installed desktop entry uses:
Exec=/usr/bin/flatpak run --branch=stable --arch=x86_64 --command=bazaar-daemon --file-forwarding io.github.kolunmi.Bazaar @@u %U @@No user-local Bazaar desktop override or Bazaar autostart entry was found before testing. Temporary workarounds did not consistently prevent duplication; all experimental overrides were removed.
Scope
The repeated daemon start and D-Bus relaunch suggest an activation/forwarding interaction, but this is not a confirmed root cause.
The symptom is confirmed on Omarchy. It has not been established whether the defect is in Omarchy's launch integration, GTK/Flatpak activation, or Bazaar itself. No comparison on another desktop has been performed. If this belongs upstream in Bazaar, please redirect accordingly.
omarchy-debug --no-sudo --print was collected locally. The full diagnostic log is not included because it contains unrelated machine/session information.
View raw text
### System details Omarchy 4.0.4-1; Hyprland 0.56.2-2; UWSM 0.26.7-1; Flatpak 1.18.2-1; Bazaar 0.9.7 (Flathub stable, system installation). ### What's wrong? Launching Bazaar once from the Omarchy application menu opens two Bazaar windows. The problem has been happening for some time and was reproduced during diagnosis. Expected: one launch opens one window. Actual: two windows appear, both belonging to the same Bazaar process. ### Steps to reproduce 1. Start with Bazaar closed. 2. Select Bazaar once in the Omarchy application menu. 3. Observe two Bazaar windows. The issue was also reproduced with a single invocation: ```sh uwsm app -- gtk-launch io.github.kolunmi.Bazaar.desktop ``` ### Diagnostic evidence The application emitted the following messages during one launch: ```text (bazaar-daemon): Application starting (bazaar-daemon): Relaunch requested via D-Bus (bazaar-daemon): Application starting (bazaar-daemon): Application exited (status 0) ``` `hyprctl clients -j` confirmed two windows with class `io.github.kolunmi.Bazaar` and the same PID. The installed desktop entry uses: ```text Exec=/usr/bin/flatpak run --branch=stable --arch=x86_64 --command=bazaar-daemon --file-forwarding io.github.kolunmi.Bazaar @@u %U @@ ``` No user-local Bazaar desktop override or Bazaar autostart entry was found before testing. Temporary workarounds did not consistently prevent duplication; all experimental overrides were removed. ### Scope The repeated daemon start and D-Bus relaunch suggest an activation/forwarding interaction, but this is not a confirmed root cause. The symptom is confirmed on Omarchy. It has not been established whether the defect is in Omarchy's launch integration, GTK/Flatpak activation, or Bazaar itself. No comparison on another desktop has been performed. If this belongs upstream in Bazaar, please redirect accordingly. `omarchy-debug --no-sudo --print` was collected locally. The full diagnostic log is not included because it contains unrelated machine/session information.
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 23:03 UTC