Proof Portal

Project overview

Omarchy

ProbeLabs65 findings · 95 requirements

A 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.

Inbox
ReportR-4794GitHub issuePublicReceived

Thunderbird leaves dwindle tiles stuck at stale sizes after another window closes

Reported by gigerIT · filed Aug 31, 2026Closed upstream on 2026-09-01 by its own reporter gigerIT. GitHub close reason: completed. Closed by its own reporter — not by itself evidence of a fix.

Received and recorded verbatim. Nothing has been checked yet.

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

Thunderbird leaves dwindle tiles stuck at stale sizes after another window closesrevision 1 · captured 2026-10-04 12:03 UTC via poll

System details

  • Omarchy 4.0.2-1
  • Hyprland 0.56.2-1 (efb50993780079460b0cbed1363e2166a2de1d9f)
  • Thunderbird 153.0.2-2
  • AMD Ryzen 9 5950X; NVIDIA GeForce RTX 5080, driver 610.57.04
  • Affected output: 5120x2160 at 165 Hz, scale 1.3333334 (3840x1620 logical)
  • Thunderbird is native Wayland (xwayland: false); Omarchy's default environment sets MOZ_ENABLE_WAYLAND=1

What's wrong?

With Thunderbird tiled in Hyprland's dwindle layout, closing another tiled window can leave the remaining layout at its previous dimensions instead of expanding it into the freed space. Repeating the open/close cycle progressively shrinks Thunderbird and the other surviving tiles. Large regions of the workspace become empty. The layout recovers only after Thunderbird is completely closed.

This reproduces every time on this machine.

Steps to reproduce

  1. Open Thunderbird on a workspace.
  2. Open another tiled window beside it. The workspace initially splits as expected.
  3. Close the other window.
  4. Observe that Thunderbird remains at the old half-workspace size instead of expanding.
  5. Open another tiled window and close it.
  6. Observe that the layout subdivides the already-stale region, leaving progressively smaller tiles and more unused workspace.

The same behavior was captured in a controlled cycle with ChatGPT, Thunderbird, and Ghostty on workspace 1:

  • Before closing Ghostty, Hyprland reported three clients: ChatGPT at 960x1594, Thunderbird at 960x797, and Ghostty at 960x797.
  • After exiting Ghostty, the workspace correctly reported only two clients, but neither surviving tile was recalculated:
workspace 1: windows=2, layout=dwindle, fullscreen=false
output DP-3: 3840x1620 logical, usable height 1594

ChatGPT:
  at:   [2560, 26]
  size: [960, 1594]

Thunderbird:
  at:   [3520, 26]
  size: [960, 797]
  mapped: true
  hidden: false
  floating: false
  pseudo: null
  fullscreen: 0
  grouped: []
  xwayland: false

For two tiled clients on this 3840-logical-pixel-wide output, the expected 50/50 geometry is approximately 1920x1594 per client. Instead, the old 960-pixel widths remain and Thunderbird also retains its old half-height of 797, leaving most of the workspace blank. hyprctl clients reports these stale dimensions, so this is not only a rendering artifact.

Configuration checks

  • hyprctl configerrors is empty.
  • Active layout is stock Omarchy dwindle with preserve_split=true and force_split=2.
  • layout:single_window_aspect_ratio is disabled.
  • There is no user layout/dwindle override and no Thunderbird-specific Omarchy window rule.

Because Hyprland itself reports the stale geometry and the other surviving client also fails to expand, this appears to be a dwindle reflow/configure interaction triggered by native-Wayland Thunderbird, rather than Thunderbird merely drawing at the wrong size. That attribution is an inference; I have not isolated whether the underlying defect belongs to Hyprland or Gecko.

A fully redacted screenshot showing the post-close geometry is available. The unredacted capture is intentionally not attached because it contains private mail and calendar data.

View raw text
### System details

- Omarchy `4.0.2-1`
- Hyprland `0.56.2-1` (`efb50993780079460b0cbed1363e2166a2de1d9f`)
- Thunderbird `153.0.2-2`
- AMD Ryzen 9 5950X; NVIDIA GeForce RTX 5080, driver `610.57.04`
- Affected output: 5120x2160 at 165 Hz, scale `1.3333334` (3840x1620 logical)
- Thunderbird is native Wayland (`xwayland: false`); Omarchy's default environment sets `MOZ_ENABLE_WAYLAND=1`

### What's wrong?

With Thunderbird tiled in Hyprland's `dwindle` layout, closing another tiled window can leave the remaining layout at its previous dimensions instead of expanding it into the freed space. Repeating the open/close cycle progressively shrinks Thunderbird and the other surviving tiles. Large regions of the workspace become empty. The layout recovers only after Thunderbird is completely closed.

This reproduces every time on this machine.

#### Steps to reproduce

1. Open Thunderbird on a workspace.
2. Open another tiled window beside it. The workspace initially splits as expected.
3. Close the other window.
4. Observe that Thunderbird remains at the old half-workspace size instead of expanding.
5. Open another tiled window and close it.
6. Observe that the layout subdivides the already-stale region, leaving progressively smaller tiles and more unused workspace.

The same behavior was captured in a controlled cycle with ChatGPT, Thunderbird, and Ghostty on workspace 1:

- Before closing Ghostty, Hyprland reported three clients: ChatGPT at `960x1594`, Thunderbird at `960x797`, and Ghostty at `960x797`.
- After exiting Ghostty, the workspace correctly reported only two clients, but neither surviving tile was recalculated:

```text
workspace 1: windows=2, layout=dwindle, fullscreen=false
output DP-3: 3840x1620 logical, usable height 1594

ChatGPT:
  at:   [2560, 26]
  size: [960, 1594]

Thunderbird:
  at:   [3520, 26]
  size: [960, 797]
  mapped: true
  hidden: false
  floating: false
  pseudo: null
  fullscreen: 0
  grouped: []
  xwayland: false
```

For two tiled clients on this 3840-logical-pixel-wide output, the expected 50/50 geometry is approximately `1920x1594` per client. Instead, the old `960`-pixel widths remain and Thunderbird also retains its old half-height of `797`, leaving most of the workspace blank. `hyprctl clients` reports these stale dimensions, so this is not only a rendering artifact.

#### Configuration checks

- `hyprctl configerrors` is empty.
- Active layout is stock Omarchy `dwindle` with `preserve_split=true` and `force_split=2`.
- `layout:single_window_aspect_ratio` is disabled.
- There is no user layout/dwindle override and no Thunderbird-specific Omarchy window rule.

Because Hyprland itself reports the stale geometry and the other surviving client also fails to expand, this appears to be a dwindle reflow/configure interaction triggered by native-Wayland Thunderbird, rather than Thunderbird merely drawing at the wrong size. That attribution is an inference; I have not isolated whether the underlying defect belongs to Hyprland or Gecko.

A fully redacted screenshot showing the post-close geometry is available. The unredacted capture is intentionally not attached because it contains private mail and calendar data.

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.