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.
Bitwarden Chrome Extension popup locked to 875x600 since 2026.5.1 update
Reported by dfmknz · filed Jun 11, 2026Closed upstream on 2026-10-09 by its own reporter dfmknz, as a duplicate (target not recorded). 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?
- 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 3.8.2, Hyprland 0.55.2, Chromium 148.0.7778.96, Bitwarden Chrome Extension 2026.5.1
What's wrong?
Description:
The Bitwarden Chrome Extension popup window is being forced to 875x600 and cannot be corrected via windowrules. The correct size the extension accepts is 480x650. This started after Bitwarden updated to 2026.5.1 on approximately June 2, 2026.
Suspected causes:
Three existing changes combined with the Bitwarden 2026.5.1 update to produce this bug:
- system.conf applies size 875 600 to all windows tagged floating-window (introduced in commit 4c97a31c, November 2025)
- bitwarden.conf tags the Chrome extension class with +floating-window (introduced in 3.4.0, February 2026), causing it to inherit the 875x600 size rule from system.conf
- Bitwarden 2026.5.1 changed how the popup requests its window size, making the forced 875x600 visibly incorrect — prior to this update the mismatch was not noticeable
Workaround:
- First, find your Bitwarden Chrome extension class by opening the popup and running:
hyprctl clients | grep -A3 "Bitwarden"- Look for the class and initialClass fields. For Chromium, this will be chrome-nngceckbapebfimnlniiiahkandclblb-Default.
- Then add to your personal windowrules config, substituting your class if different:
windowrule = tag -floating-window, size 480 650, match:class chrome-nngceckbapebfimnlniiiahkandclblb-DefaultThis removes the floating-window tag before the size rule is applied, bypassing the 875x600 override in system.conf.
Possible fix:
Add an explicit size rule for the Chrome extension class directly in bitwarden.conf to override the generic floating-window size, or exempt it from the size 875 600 rule in system.conf.
View raw text
### System details Omarchy 3.8.2, Hyprland 0.55.2, Chromium 148.0.7778.96, Bitwarden Chrome Extension 2026.5.1 ### What's wrong? Description: The Bitwarden Chrome Extension popup window is being forced to 875x600 and cannot be corrected via windowrules. The correct size the extension accepts is 480x650. This started after Bitwarden updated to 2026.5.1 on approximately June 2, 2026. Suspected causes: Three existing changes combined with the Bitwarden 2026.5.1 update to produce this bug: - system.conf applies size 875 600 to all windows tagged floating-window (introduced in commit 4c97a31c, November 2025) - bitwarden.conf tags the Chrome extension class with +floating-window (introduced in 3.4.0, February 2026), causing it to inherit the 875x600 size rule from system.conf - Bitwarden 2026.5.1 changed how the popup requests its window size, making the forced 875x600 visibly incorrect — prior to this update the mismatch was not noticeable Workaround: - First, find your Bitwarden Chrome extension class by opening the popup and running: ``` hyprctl clients | grep -A3 "Bitwarden" ``` - Look for the class and initialClass fields. For Chromium, this will be chrome-nngceckbapebfimnlniiiahkandclblb-Default. - Then add to your personal windowrules config, substituting your class if different: ``` windowrule = tag -floating-window, size 480 650, match:class chrome-nngceckbapebfimnlniiiahkandclblb-Default ``` This removes the floating-window tag before the size rule is applied, bypassing the 875x600 override in system.conf. Possible fix: Add an explicit size rule for the Chrome extension class directly in bitwarden.conf to override the generic floating-window size, or exempt it from the size 875 600 rule in system.conf.
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 03:52 UTC