Skip to content

provide fonts for sandboxed Linux Chromium screenshots - #260

Merged
maxheld83 merged 4 commits into
mainfrom
maxheld83-sandboxed-linux-chromium-fonts
Oct 27, 2026
Merged

maxheld83 merged 4 commits into
mainfrom
maxheld83-sandboxed-linux-chromium-fonts

Conversation

@clowders

@clowders clowders Bot commented Oct 26, 2026 •

Copy link
Copy Markdown
Contributor

Wrap the default Linux Chromium browser with a Fontconfig configuration generated from pinned Nixpkgs Liberation and DejaVu fonts. Add a sandbox integration test that checks rasterized text and a fixed layout; it fails with plain Chromium and passes with the font wrapper.

Checks: nix build --no-link .#checks.x86_64-linux.r-shinytest2, nix build --no-link .#checks.aarch64-linux.r-shinytest2, nix develop --command tasks all, and nix develop --command nix flake check --print-build-logs.

Closes #256

Wrap the Linux default browser with Fontconfig built from Liberation and DejaVu fonts, and test rendered text in the Nix sandbox.

Co-authored-by: Copilot App <[email protected]>
@clowders
clowders Bot marked this pull request as ready for review October 26, 2026 23:42
@clowders

clowders Bot commented Oct 26, 2026

Copy link
Copy Markdown
Contributor Author

Investigated both failing consumer-contract checks:

Run Classification Decision
40421505655 (pull_request) Pre-existing Follow up in #261; no change in this PR.
40421485864 (push) Pre-existing Same root cause and follow-up.

Both stop during nix develop --command check-fixtures, before fixture execution,
when GitHub returns HTTP 404 for the pinned private dataheld/maxheld archive
at 83c05ac1282b2add9516117102c2a561d709b27e.
The identical error already occurs in main's run
40411158830

at this PR's base 76ddf79, after #254 changed the dev brand input.
This PR does not change that input, lock, dev configuration, or workflow.

No code changed, no commit/push required, and no CI re-run requested:
a re-run alone will not resolve private dependency access.
Full local validation was not repeated because there is no code change;
the matching main and PR logs establish this failure independently of the
Chromium change.
The checks remain blocked pending #261 and subsequent CI re-runs.

@maxheld83
maxheld83 merged commit f11eead into main Oct 27, 2026
20 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

provide fonts for sandboxed Linux Chromium screenshots

1 participant