Track: 0.21.0 on Linux (desktop build, WebKitGTK, VAAPI, ffmpeg) #787

What this tracks

Nothing in 0.21.0 has been built or run on Linux desktop. The Docker image and the Linux tarball each carry a different ffmpeg, and the shipped Linux desktop ffmpeg has no GPU encoder.

To check

• The tarball builds (scripts/linux/make-portable.sh) and starts, with the 0.21.0 shell.
• Save dialog and Show in folder (a file manager that can select a file, and a fallback that opens the folder).
• Camera and microphone access in WebKitGTK. The GStreamer plugin hint (capture.hint.linuxPlugins) shows when plugins are missing.
• Which recording container WebKitGTK produces for a Performance take, and whether the render accepts it.
• scripts/encoder_matrix.py with VAAPI on Intel and AMD, and the CPU fallback on a machine without a GPU encoder.
• The encoder test takes about two minutes on Linux. Confirm that cancel works during it (see the export cancel issue).
• The Wayland launch error reported in [Bug]: Wayland protocol error on launch (Missing acquire timeline) #780.
• The CPU-only package and the torchvision wheel (CPU-only Linux package ships the cu124 torchvision wheel: warmup fails with "operator torchvision::nms does not exist" #778).
• Docker image: a Performance export with the image's ffmpeg. The :edge tag is published when the pull request merges, so test on :edge first.

Constraints

• Shell changes change the binary (desktop-update-gate), and uv.lock changes force a full download.
• Anything visible needs a Guide entry and ten language tables.

Verified by

Not verified. No Linux machine was available in the pass that wrote this list.

Related

#778 and #780 (open). #550 and #531 (closed) describe earlier Linux build problems.