Skip to content

Report Omarchy to Steam instead of Arch Linux - #284

Open
spaceXrace wants to merge 1 commit into
omacom:masterfrom
spaceXrace:fix/omarchy-steam-survey-name
Open

Report Omarchy to Steam instead of Arch Linux#284
spaceXrace wants to merge 1 commit into
omacom:masterfrom
spaceXrace:fix/omarchy-steam-survey-name

Conversation

@spaceXrace

Copy link
Copy Markdown

Summary

  • ship an Omarchy-specific /etc/lsb-release override
  • apply it from both stable and development omarchy-settings packages
  • keep the release value as rolling so reporting is not split across Omarchy patch versions

Why

Omarchy already identifies itself correctly in /etc/os-release:

ID=omarchy
ID_LIKE=arch
NAME="Omarchy"

However, Arch's steam package depends on lsb-release, whose /etc/lsb-release currently says:

DISTRIB_ID="Arch"
DISTRIB_RELEASE="rolling"
DISTRIB_DESCRIPTION="Arch Linux"

Steam's launcher checks /etc/lsb-release before /etc/os-release. On a stock Omarchy 4.0.2 installation this is visible in ~/.local/share/Steam/logs/console-linux.txt:

Running Steam on arch rolling 64-bit

Steam's public hardware survey does not currently list Omarchy as a distinct Linux version. Although the public table only exposes entries above its reporting cutoff, the client-side value shows that native Steam installations submit/use the Arch identity at this detection point.

With this override, the same Steam detection path resolves to:

omarchy rolling 64-bit

Verification

  • bash -n passes for both PKGBUILDs and install scripts
  • all repository self-tests pass:
    • ./bin/sync-upstream self-test
    • ./bin/omarchy-pkgs self-test
    • ./bin/omarchy-release self-test
  • omarchy-settings builds successfully with makepkg
  • inspected the built archive to verify the new override and install-script copy are present

@spaceXrace
spaceXrace marked this pull request as ready for review September 3, 2026 09:29
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.

1 participant