Registers issue 345 (status: diagnosing). Do not merge without review.
Symptom (operator, 2026-10-09): on the workstation, Betterbird's meeting reminder appears as a transparent window with no content. i3 + picom (glx). No module owned Betterbird.
Measured: the reminder is class Calendar/eu.betterbird.Betterbird, role AlarmWindow, type DIALOG, 600x300, depth 32 (like every Betterbird window there). Four reminders raised from a throw-away profile (--no-remote, one local .ics event) were drawn every time it was captured, with defaults and with the operator's theme and use_system_colors. mozilla.widget.use-argb-visuals=false does not change the depth. The long-running Betterbird (5 days) prints to the session's dead pipe; hardware WebRender; no suspend, no GPU reset.
Guess, said as one: a depth-32 window its program never painted looks transparent under picom; so the window is very likely mapped but not painted. Candidates left: the long-running process, Owl's reminders, the moment (full-screen window, other monitor).
Next: at the next real reminder, xorg_windows class=Calendar, xorg_screenshot window=… inline, betterbird_status; then betterbird_restart + betterbird_reminder_test.
Code: mesh-catalog fix/xorg-windows-and-window-screenshot (window list, screenshot cut from the screen) and feat/betterbird-module.
merge-check.sh passes locally (records, index, cycle, words with the catalogue's list).
Registers issue 345 (status: diagnosing). Do not merge without review.
- **Symptom (operator, 2026-10-09):** on the workstation, Betterbird's meeting reminder appears as a transparent window with no content. i3 + picom (glx). No module owned Betterbird.
- **Measured:** the reminder is class `Calendar`/`eu.betterbird.Betterbird`, role `AlarmWindow`, type DIALOG, 600x300, **depth 32** (like every Betterbird window there). Four reminders raised from a throw-away profile (`--no-remote`, one local .ics event) were **drawn** every time it was captured, with defaults and with the operator's theme and `use_system_colors`. `mozilla.widget.use-argb-visuals=false` does not change the depth. The long-running Betterbird (5 days) prints to the session's dead pipe; hardware WebRender; no suspend, no GPU reset.
- **Guess, said as one:** a depth-32 window its program never painted looks transparent under picom; so the window is very likely mapped but not painted. Candidates left: the long-running process, Owl's reminders, the moment (full-screen window, other monitor).
- **Next:** at the next real reminder, `xorg_windows class=Calendar`, `xorg_screenshot window=… inline`, `betterbird_status`; then `betterbird_restart` + `betterbird_reminder_test`.
- **Code:** mesh-catalog `fix/xorg-windows-and-window-screenshot` (window list, screenshot cut from the screen) and `feat/betterbird-module`.
`merge-check.sh` passes locally (records, index, cycle, words with the catalogue's list).
Records the symptom, what four reminders raised from a throw-away profile showed (drawn every time, at
depth 32), what that rules out, the candidates left, and what to measure at the next real reminder.
Status diagnosing: the cause is not known.
Deliverynovox/hq@a4e132e47be0 — delivered since 2026-10-09T10:51:00Z
Delivery plan — builds nothing: the change touches no module of the mesh's graph
Transitions
2026-10-09 10:25 (new) → proposed (announced): novox/hq#245's head announced
2026-10-09 10:26 proposed → checked (checked): the verdict names this commit
2026-10-09 10:26 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-09 10:51 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-09 10:51 published → delivered (done): nothing for a walk to move
The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.
<!-- mesh-delivery:view -->
**Delivery** `novox/hq@a4e132e47be0` — **delivered** since 2026-10-09T10:51:00Z
**Delivery plan** — builds nothing: the change touches no module of the mesh's graph
**Transitions**
- 2026-10-09 10:25 (new) → proposed (announced): novox/hq#245's head announced
- 2026-10-09 10:26 proposed → checked (checked): the verdict names this commit
- 2026-10-09 10:26 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-09 10:51 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
- 2026-10-09 10:51 published → delivered (done): nothing for a walk to move
The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.
The operator reports picom leaving a chat window stale after a workspace switch before, never recorded.
The diagnosis now names the graphics stack, puts picom first among the candidates, and makes the first
step at the next empty reminder turning compositing off, which loses nothing; a Betterbird restart comes
after, refused while a message is being written unless the operator says yes.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Registers issue 345 (status: diagnosing). Do not merge without review.
Calendar/eu.betterbird.Betterbird, roleAlarmWindow, type DIALOG, 600x300, depth 32 (like every Betterbird window there). Four reminders raised from a throw-away profile (--no-remote, one local .ics event) were drawn every time it was captured, with defaults and with the operator's theme anduse_system_colors.mozilla.widget.use-argb-visuals=falsedoes not change the depth. The long-running Betterbird (5 days) prints to the session's dead pipe; hardware WebRender; no suspend, no GPU reset.xorg_windows class=Calendar,xorg_screenshot window=… inline,betterbird_status; thenbetterbird_restart+betterbird_reminder_test.fix/xorg-windows-and-window-screenshot(window list, screenshot cut from the screen) andfeat/betterbird-module.merge-check.shpasses locally (records, index, cycle, words with the catalogue's list).Delivery
novox/hq@a4e132e47be0— delivered since 2026-10-09T10:51:00ZDelivery plan — builds nothing: the change touches no module of the mesh's graph
Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.