Skip to content

docs(roadmap): capture 2026-05-07 ozone-platform default reset session#2509

Merged
IsmaelMartinez merged 2 commits into
mainfrom
claude/roadmap-ozone-2026-05-07
May 7, 2026
Merged

docs(roadmap): capture 2026-05-07 ozone-platform default reset session#2509
IsmaelMartinez merged 2 commits into
mainfrom
claude/roadmap-ozone-2026-05-07

Conversation

@IsmaelMartinez
Copy link
Copy Markdown
Owner

Summary

Documentation only. No code changes.

Test plan

  • CI green
  • Roadmap renders correctly on the docs site preview (no broken links, headings nest as expected).

claude and others added 2 commits May 6, 2026 16:13
Let Chromium pick the rendering backend per session (Wayland on
Wayland, X11 elsewhere) rather than forcing XWayland everywhere.
Users hitting Wayland regressions can still override with
--ozone-platform=x11 on the command line or in their .desktop file.

Updates the deb/rpm/AppImage and snap executableArgs in package.json
and refreshes the troubleshooting + configuration docs to match the
new default. The XWayland runtime detection in commandLine.js is
unchanged: it still triggers when the user explicitly passes
--ozone-platform=x11.
Bump the Last Updated date and status line, extend the Wayland
Compatibility section with PR #2506 and tracking issue #2508 context,
and add a session outcomes block summarising today's PR open, tracker
creation, and the four targeted pings (#2486, #2345, #2383, #2094).

Closes nothing; the actual default change ships in #2506.
@sonarqubecloud
Copy link
Copy Markdown

sonarqubecloud Bot commented May 7, 2026

Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates the default --ozone-platform flag from x11 to auto in the package.json configurations and across the project's documentation. This change enables Chromium to automatically detect the appropriate display backend for the session, while documentation updates in configuration.md, roadmap.md, and troubleshooting.md provide guidance on the new behavior and how to manually override it if regressions occur. I have no feedback to provide.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 7, 2026

📦 PR Snap Build Artifacts

Snap builds successful! Download artifacts:

🐧 Linux Snap Packages

x86_64 (110.28 MB)

arm64 (107.10 MB)

armv7l (101.13 MB)


📝 Note: Other package formats (.deb, .rpm, .AppImage, .dmg, .exe) are built in the main workflow

View workflow run

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 7, 2026

📦 PR Build Artifacts

Build successful! Download artifacts:

🐧 Linux

x86_64 (446.51 MB) - Contains: .deb, .rpm, .tar.gz, .AppImage

arm64 (436.75 MB) - Contains: .deb, .rpm, .tar.gz, .AppImage

armv7l (414.58 MB) - Contains: .deb, .rpm, .tar.gz, .AppImage

🍎 macOS

x86_64 (128.75 MB) - Contains: .dmg

🪟 Windows

x86_64 (109.26 MB) - Contains: .exe installer


📝 Note: Snap packages (.snap) are built in a separate workflow

View workflow run

🕐 Last updated: 2026-05-07 15:33 UTC

@IsmaelMartinez IsmaelMartinez merged commit e1826ef into main May 7, 2026
19 checks passed
@IsmaelMartinez IsmaelMartinez deleted the claude/roadmap-ozone-2026-05-07 branch May 7, 2026 16:03
IsmaelMartinez added a commit that referenced this pull request May 8, 2026
PR #2509 ("docs(roadmap): capture 2026-05-07 ozone-platform default reset
session") accidentally bundled a package.json change that flipped the flag
from =x11 to =auto. =auto is not a valid value for --ozone-platform —
Chromium aborts with `FATAL:ui/ozone/platform_selection.cc:46 Invalid ozone
platform: auto`, making every build cut from main since 2026-05-07
unlaunchable on every distro and packaging format.

Restore the working =x11 default. The proper "remove the flag entirely and
let Chromium auto-detect per session" direction is being handled separately
on #2506; this is the minimum patch to keep main releasable until that lands.

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Geek0x0 pushed a commit to Geek0x0/teams-for-linux that referenced this pull request May 19, 2026
…inez#2511)

PR IsmaelMartinez#2509 ("docs(roadmap): capture 2026-05-07 ozone-platform default reset
session") accidentally bundled a package.json change that flipped the flag
from =x11 to =auto. =auto is not a valid value for --ozone-platform —
Chromium aborts with `FATAL:ui/ozone/platform_selection.cc:46 Invalid ozone
platform: auto`, making every build cut from main since 2026-05-07
unlaunchable on every distro and packaging format.

Restore the working =x11 default. The proper "remove the flag entirely and
let Chromium auto-detect per session" direction is being handled separately
on IsmaelMartinez#2506; this is the minimum patch to keep main releasable until that lands.

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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.

2 participants