picom: the backend and damage tracking are each machine's settings (hq issue 345) #157

Merged
mesh-admin merged 2 commits from feat/picom-backend-and-damage-settings into main 2026-10-09 10:50:59 +00:00
Contributor

Part of hq issue 345. Do not merge without review; set no node value without the operator.

Why. The operator reports picom leaving a window stale after a workspace switch before (Telegram), and the empty calendar reminder on shanks may be the same failure: glx with damage tracking leaving a window unpainted on some drivers. Research 037 already lists backend as depending on each machine's driver.

What changes.

  • Two preferences: backend (default glx) and use-damage (default true, picom's own default). picom.conf asks for both; filled with the defaults it behaves as today (tested).
  • The file stays trusted (unmarked): both settings are set at the controller's terminal alone. Review found that "trusted": false let any settings caller inject options (xrender"; write-pid-path = "…); that general defect is hq issue 346 (hq PR #246). Commit ca1bd18 removes the marking and the test now refuses it.
  • README: a Settings section. A changed file is read at the next picom_restart or login.

What merging does. picom.conf on g14 and shanks gains the comment and use-damage = true;; behaviour unchanged. A node value is a later step, at the terminal, after the reminder test proves it.

Measured on shanks: AMD RX 6950 XT (Navi 21), amdgpu, xf86-video-amdgpu 25.0.0, X.Org 1.21.1.24, Mesa 26.2.4 radeonsi, kernel 7.2.8, picom 13.

Checks. merge-check.sh on the merge result with origin/main 7339ce8, controller from mesh-controller main 4d60628: pass (module check: picom: ok, with the expected warning that the configuration is unmarked and so trusted).

Part of hq issue 345. Do not merge without review; set no node value without the operator. **Why.** The operator reports picom leaving a window stale after a workspace switch before (Telegram), and the empty calendar reminder on shanks may be the same failure: glx with damage tracking leaving a window unpainted on some drivers. Research 037 already lists `backend` as depending on each machine's driver. **What changes.** - Two preferences: `backend` (default `glx`) and `use-damage` (default `true`, picom's own default). picom.conf asks for both; filled with the defaults it behaves as today (tested). - **The file stays trusted (unmarked): both settings are set at the controller's terminal alone.** Review found that `"trusted": false` let any settings caller inject options (`xrender"; write-pid-path = "…`); that general defect is hq issue 346 (hq PR #246). Commit `ca1bd18` removes the marking and the test now refuses it. - README: a Settings section. A changed file is read at the next `picom_restart` or login. **What merging does.** picom.conf on g14 and shanks gains the comment and `use-damage = true;`; behaviour unchanged. A node value is a later step, at the terminal, after the reminder test proves it. **Measured on shanks:** AMD RX 6950 XT (Navi 21), amdgpu, xf86-video-amdgpu 25.0.0, X.Org 1.21.1.24, Mesa 26.2.4 radeonsi, kernel 7.2.8, picom 13. **Checks.** `merge-check.sh` on the merge result with origin/main `7339ce8`, controller from mesh-controller main `4d60628`: pass (module check: `picom: ok`, with the expected warning that the configuration is unmarked and so trusted).
mesh-admin added 1 commit 2026-10-09 10:26:05 +00:00
picom: the backend and damage tracking are each machine's settings (hq issue 345)
mesh/merge-gate pass: builds picom → g14, shanks; no bus step; every machine composes with the change as it did without (4 of 4 compose)
mesh/repo-check pass: its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)
mesh/delivery superseded: a newer head of the same pull request
73f2962bab
A window mapped but left unpainted, or stale after a workspace switch, is a known failure of picom's glx
backend with damage tracking on some drivers, and the first suspect for the empty calendar reminder on
the workstation. Research 037 already found the backend to depend on the machine's driver. Both become
preferences whose defaults are today's (glx, use-damage true), so nothing changes until a machine is
given xrender or use-damage false to test it.
Author
Contributor

Delivery novox/mesh-catalog@ca1bd18de6db — superseded since 2026-10-09T10:51:01Z

Delivery plan — builds picom → g14, shanks; no bus step

  • tier 0: picom
  • g14: receives picom
  • shanks: receives picom

Transitions

  • 2026-10-09 10:35 (new) → proposed (announced): novox/mesh-catalog#157's head announced
  • 2026-10-09 10:37 proposed → checked (checked): the verdict names this commit
  • 2026-10-09 10:37 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 → superseded (superseded): a newer delivery to the same trunk took over its walk

The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.

<!-- mesh-delivery:view --> **Delivery** `novox/mesh-catalog@ca1bd18de6db` — **superseded** since 2026-10-09T10:51:01Z **Delivery plan** — builds picom → g14, shanks; no bus step - tier 0: picom - g14: receives picom - shanks: receives picom **Transitions** - 2026-10-09 10:35 (new) → proposed (announced): novox/mesh-catalog#157's head announced - 2026-10-09 10:37 proposed → checked (checked): the verdict names this commit - 2026-10-09 10:37 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 → superseded (superseded): a newer delivery to the same trunk took over its walk The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.
Author
Contributor

Merge check at 73f2962b

  • mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: picom)
  • mesh/repo-check: PASS — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)

Delivery plan — builds picom → g14, shanks; no bus step

  • tier 0: picom
  • g14: receives picom
  • shanks: receives picom

Run by the build seat on novox as build-1791541592128330153 (builds --log build-1791541592128330153).

--- the gate: picom
picom: ok, 4 tool(s)
long-running resources without health: 0
files asking for a setting without saying whether it is trusted: 0
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 1 module(s) changed against 4 machine(s), as the snapshot of 2026-10-09T08:07:39Z says they run
composing every machine as the mesh is
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
composing every machine with the change
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-09T08:07:39Z

modules the change moves:
  - picom (changed)

machines:
  - a machine (f35): composes
  - holds mesh-dns-resolver (idt): composes
  - holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
  - a machine (yvbpsm): composes

a merge would rebuild 1 module(s) in 1 tier(s): picom
--- its merge-check.sh (go toolchain)
ok  	git.novox.be/novox/mesh-catalog/checks/words	0.002s
words: 12 retired words, none in the 34109 strings of 603 files
ok  	git.novox.be/novox/mesh-catalog/checks/paths	0.006s
paths: no module names another's state on its machine (3 known, listed to go)
long-running resources without health: 70, as kept
testing modules/picom
ok  	picom/cmd/picom-tools	1.241s
--- its merge-check-typescript.sh (typescript toolchain)
**Merge check** at `73f2962b` - `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: picom) - `mesh/repo-check`: **PASS** — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript) **Delivery plan** — builds picom → g14, shanks; no bus step - tier 0: picom - g14: receives picom - shanks: receives picom Run by the build seat on novox as `build-1791541592128330153` (`builds --log build-1791541592128330153`). ``` --- the gate: picom picom: ok, 4 tool(s) long-running resources without health: 0 files asking for a setting without saying whether it is trusted: 0 1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here judging 1 module(s) changed against 4 machine(s), as the snapshot of 2026-10-09T08:07:39Z says they run composing every machine as the mesh is the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued composing every machine with the change the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose) judged by controller development build against the facts of 2026-10-09T08:07:39Z modules the change moves: - picom (changed) machines: - a machine (f35): composes - holds mesh-dns-resolver (idt): composes - holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes - a machine (yvbpsm): composes a merge would rebuild 1 module(s) in 1 tier(s): picom --- its merge-check.sh (go toolchain) ok git.novox.be/novox/mesh-catalog/checks/words 0.002s words: 12 retired words, none in the 34109 strings of 603 files ok git.novox.be/novox/mesh-catalog/checks/paths 0.006s paths: no module names another's state on its machine (3 known, listed to go) long-running resources without health: 70, as kept testing modules/picom ok picom/cmd/picom-tools 1.241s --- its merge-check-typescript.sh (typescript toolchain) ```
jschoubben added 1 commit 2026-10-09 10:35:38 +00:00
picom: keep the configuration trusted, so only the terminal sets the backend (review of #157)
mesh/merge-gate pass: builds picom → g14, shanks; no bus step; every machine composes with the change as it did without (4 of 4 compose)
mesh/repo-check pass: its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)
mesh/delivery superseded: a newer delivery to the same trunk took over its walk
ca1bd18de6
A setting is pasted into picom.conf as it is, so a backend of xrender"; write-pid-path = "… adds an
option of the caller's: picom would then overwrite any file the operator can write. With the file
trusted, both settings are set at the controller's terminal alone until settings are typed and quoted
(hq issue 346).
Author
Contributor

Merge check at ca1bd18d

  • mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: picom)
  • mesh/repo-check: PASS — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)

Delivery plan — builds picom → g14, shanks; no bus step

  • tier 0: picom
  • g14: receives picom
  • shanks: receives picom

Run by the build seat on g14 as build-1791542142100578874 (builds --log build-1791542142100578874).

--- the gate: picom
picom: ok, 4 tool(s); WARNING: configuration ask(s) for a setting and do(es) not say whether it is trusted, so it counts as trusted: set at the terminal alone; say "trusted" false where nothing trusts it (novox/hq issue 339)
long-running resources without health: 0
files asking for a setting without saying whether it is trusted: 1
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 1 module(s) changed against 4 machine(s), as the snapshot of 2026-10-09T08:07:39Z says they run
composing every machine as the mesh is
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
composing every machine with the change
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-09T08:07:39Z

modules the change moves:
  - picom (changed)

machines:
  - a machine (f35): composes
  - holds mesh-dns-resolver (idt): composes
  - holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
  - a machine (yvbpsm): composes

a merge would rebuild 1 module(s) in 1 tier(s): picom
--- its merge-check.sh (go toolchain)
ok  	git.novox.be/novox/mesh-catalog/checks/words	0.002s
words: 12 retired words, none in the 34109 strings of 603 files
ok  	git.novox.be/novox/mesh-catalog/checks/paths	0.005s
paths: no module names another's state on its machine (3 known, listed to go)
long-running resources without health: 70, as kept
testing modules/picom
ok  	picom/cmd/picom-tools	1.231s
--- its merge-check-typescript.sh (typescript toolchain)
**Merge check** at `ca1bd18d` - `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: picom) - `mesh/repo-check`: **PASS** — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript) **Delivery plan** — builds picom → g14, shanks; no bus step - tier 0: picom - g14: receives picom - shanks: receives picom Run by the build seat on g14 as `build-1791542142100578874` (`builds --log build-1791542142100578874`). ``` --- the gate: picom picom: ok, 4 tool(s); WARNING: configuration ask(s) for a setting and do(es) not say whether it is trusted, so it counts as trusted: set at the terminal alone; say "trusted" false where nothing trusts it (novox/hq issue 339) long-running resources without health: 0 files asking for a setting without saying whether it is trusted: 1 1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here judging 1 module(s) changed against 4 machine(s), as the snapshot of 2026-10-09T08:07:39Z says they run composing every machine as the mesh is the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued composing every machine with the change the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose) judged by controller development build against the facts of 2026-10-09T08:07:39Z modules the change moves: - picom (changed) machines: - a machine (f35): composes - holds mesh-dns-resolver (idt): composes - holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes - a machine (yvbpsm): composes a merge would rebuild 1 module(s) in 1 tier(s): picom --- its merge-check.sh (go toolchain) ok git.novox.be/novox/mesh-catalog/checks/words 0.002s words: 12 retired words, none in the 34109 strings of 603 files ok git.novox.be/novox/mesh-catalog/checks/paths 0.005s paths: no module names another's state on its machine (3 known, listed to go) long-running resources without health: 70, as kept testing modules/picom ok picom/cmd/picom-tools 1.231s --- its merge-check-typescript.sh (typescript toolchain) ```
mesh-admin merged commit 1833045c33 into main 2026-10-09 10:50:59 +00:00
mesh-admin deleted branch feat/picom-backend-and-damage-settings 2026-10-09 10:50:59 +00:00
Sign in to join this conversation.
No Reviewers
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/mesh-catalog#157