Skip to content

Linux builds report runtimeVersion 1.6.0 (CMake VERSION is not synced from the tag) #1790

Open

Description

@byungjul

What happens

On Linux, xrGetInstanceProperties returns runtimeVersion = 1.6.0 for runtime v2.21.11, both from the installed .deb (displayxr-runtime 2.21.11) and from a local build. The tag only shows up in the name: runtimeName = "DisplayXR Runtime (based on Monado/XRT) 'v2.21.11'".

Why

build-windows.yml has a "Sync CMake VERSION from latest vX.Y.Z tag" step that patches project(VERSION ...) before building. build-linux.yml has no such step. It uses git describe only to name the tarball and the .deb. So the Linux runtime reports the placeholder VERSION 1.6.0 from CMakeLists.txt.

Why it matters

Apps gate on runtimeVersion. DisplayXR/displayxr-unity#348 (the #347 colour fix) turns on _SRGB swapchains only when the runtime is format-honest, and it decides that from runtimeVersion (Vulkan ≥ 2.21.7). On Linux it reads 1.6.0, so the fix never engages, and Unity apps stay washed out on a runtime that logs Color (#1589) [vk_native]: format-honest.

Suggested fix

Add the same version-sync step to the Linux jobs that build the runtime (at least Deb and Package, which ship it), so runtimeVersion matches the tag on every platform.

Found while testing displayxr-unity#348 on a Leia DS1 (Ubuntu 26.04, NVIDIA).

🤖 Generated with Claude Code

Activity

  1. added 2 commits that reference this issue on Oct 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions