Skip to content

[META] Road to v2.0.0 Release #227

Closed

Description

@ehfd

Will be consistently updated. Entries without assignees are all open to pull requests. Vibe coding is welcome as long as functional validation is correct.

Checkmarked entries are currently in Pull Requests. Will be unchecked if it gets closed without merging, and will be struck out and moved to the bottom if merged.

Tier 1: High Priority, blockers for v2.0.0

Tier 2: Moderate, preferred to land in v2.0.0

Tier 3: Roadmap, but not necessarily for v2.0.0

Done

Activity

  1. added
    documentationDocumentation improvements or additions
    CI/CDCI/CD procedures or container usage
    encodingAudio or video encoders but not the OS interfaces
    transportUnderlying media or data transport protocols
    performancePerformance or latency issues, not critical but impacts usage
    webWeb components including gst-web
    interfaceOS input, display, or audio interfaces
    on Mar 27, 2026
  2. ehfd commented on Mar 27, 2026

    @ehfd
    MemberAuthor

    Details for NVENC encoder dropping a lot of frames with Windows Chromium D3D11VideoDecoder - Consult settings in https://github.com/selkies-project/selkies/blob/7dd6a93065332e5b3fe48fe5e5eb911a91f82746/src/selkies/legacy/gstwebrtc_app.py#L257-L938. The decoder initially starts from baseline profile and changes to high.

    Details
    Timestamp	Property	Value
    00:00:00.000	created	
    "2026-03-25 10:21:43.784039 UTC"
    00:00:00.000	url	
    "WebCodecs::VideoDecoder"
    00:00:00.000	kFrameTitle	
    "Fedora KDE"
    00:00:00.000	kFrameUrl	
    "https://ehf-xgl-test.nrp-nautilus.io/"
    00:00:00.007	info	
    "Use D3D11VideoDecoder"
    00:00:00.007	info	
    "D3D11VideoDecoder is using h264 baseline / 4:2:0"
    00:00:00.007	info	
    "D3D11VideoDecoder producing NV12"
    00:00:00.007	info	
    "D3D11VideoDecoder: Selected NV12"
    00:00:00.007	info	
    "D3D11VideoDecoder is binding textures"
    00:00:00.007	info	
    "D3D11VideoDecoder is using D3D11 backend"
    00:00:00.011	info	
    "D3D11VideoDecoder is using array texture"
    00:00:00.011	info	
    "Selected D3D11VideoDecoder adapter LUID:{0, 64263}"
    00:00:00.011	info	
    "Video is supported by D3D11VideoDecoder"
    00:00:00.011	kVideoDecoderName	
    "D3D11VideoDecoder"
    00:00:00.011	kIsPlatformVideoDecoder	
    true
    00:00:00.011	kVideoTracks	
    [
      {
        "alpha mode": "is_opaque",
        "codec": "h264",
        "coded size": "1920x1080",
        "color space": {
          "matrix": "BT709",
          "primaries": "BT709",
          "range": "LIMITED",
          "transfer": "BT709"
        },
        "encryption scheme": "Unencrypted",
        "has extra data": false,
        "hdr metadata": {},
        "natural size": "1920x1080",
        "orientation": "0°",
        "profile": "h264 baseline",
        "visible rect": "0,0 1920x1080"
      }
    ]
    00:00:00.011	info	
    "Initialized VideoDecoder: codec: h264, profile: h264 baseline, level: not available, alpha_mode: is_opaque, coded size: [1920,1080], visible rect: [0,0,1920,1080], natural size: [1920,1080], has extra data: false, encryption scheme: Unencrypted, rotation: 0°, flipped: 0, color space: {primaries:BT709, transfer:BT709, matrix:BT709, range:LIMITED}"
    00:00:00.013	info	
    "D3D11VideoDecoder config change: profile: h264 high, chroma_sampling_format: 4:2:0, coded_size: 1920x1088, bit_depth: 8, color_space: {primary=1, transfer=1, matrix=1, range=1}"
    00:00:00.013	info	
    "D3D11VideoDecoder is using h264 high / 4:2:0"
    00:00:00.013	info	
    "D3D11VideoDecoder producing NV12"
    00:00:00.013	info	
    "D3D11VideoDecoder: Selected NV12"
    00:00:00.013	info	
    "D3D11VideoDecoder is binding textures"
    00:00:00.013	info	
    "D3D11VideoDecoder is using D3D11 backend"
    00:00:00.016	info	
    "D3D11VideoDecoder is using array texture"
    00:03:22.846	event	
    "kWebMediaPlayerDestroyed"
    Use D3D11VideoDecoder
    D3D11VideoDecoder is using h264 baseline / 4:2:0
    D3D11VideoDecoder producing NV12
    D3D11VideoDecoder: Selected NV12
    D3D11VideoDecoder is binding textures
    D3D11VideoDecoder is using D3D11 backend
    D3D11VideoDecoder is using array texture
    Selected D3D11VideoDecoder adapter LUID:{0, 64263}
    Video is supported by D3D11VideoDecoder
    Initialized VideoDecoder: codec: h264, profile: h264 baseline, level: not available, alpha_mode: is_opaque, coded size: [1920,1080], visible rect: [0,0,1920,1080], natural size: [1920,1080], has extra data: false, encryption scheme: Unencrypted, rotation: 0°, flipped: 0, color space: {primaries:BT709, transfer:BT709, matrix:BT709, range:LIMITED}
    D3D11VideoDecoder config change: profile: h264 high, chroma_sampling_format: 4:2:0, coded_size: 1920x1088, bit_depth: 8, color_space: {primary=1, transfer=1, matrix=1, range=1}
    D3D11VideoDecoder is using h264 high / 4:2:0
    D3D11VideoDecoder producing NV12
    D3D11VideoDecoder: Selected NV12
    D3D11VideoDecoder is binding textures
    D3D11VideoDecoder is using D3D11 backend
    D3D11VideoDecoder is using array texture
    
  3. ehfd commented on Jul 14, 2026

    @ehfd
    MemberAuthor

    Example image is ready in ghcr.io/selkies-project/selkies/example:main-ubuntu26.04.

  4. huoxingdawang commented on Aug 6, 2026

    @huoxingdawang

    Hi there! I was just wondering if there's any rough estimate for when v2.0.0 might be released?

  5. ehfd commented on Aug 6, 2026

    @ehfd
    MemberAuthor

    We can get a release candidate out very soon. CI/CD has been wired up. We do have to get a couple PRs sorted out from pixelflux and pcmflux.

  6. ztsyx commented on Aug 13, 2026

    @ztsyx

    Hi, planning to build desktop images across multiple Ubuntu bases. Could you confirm the officially supported/tested distros for the 2.0 line?

    Specifically:

    Ubuntu Supported? Known limitations?
    24.04 (noble) ?
    22.04 (jammy) ?
    20.04 (focal) ?
    18.04 (bionic) ?

    Context: I've hit these on 22.04:

    • pixelflux / pcmflux need GLIBC_2.34 (jammy has 2.35, focal only 2.31 — blocks 20.04?)
    • selkies_joystick_interposer.so needs GLIBC_2.38 (jammy 2.35 too old)
    • libavcodec.so.60 / libx264.so.164 not in jammy apt

    Questions:

    1. What's the minimum GLIBC / Python / FFmpeg the 2.0 native modules require?
    2. Any plan to ship a wheel built against older glibc (e.g. manylinux_2_28)?
    3. For distros without official support, is source-build the only path?

    A minimal dependency list per Ubuntu version (or a link to one) would be great. Thanks!

  7. 16 remaining items

  8. junkerderprovinz commented on Sep 1, 2026

    @junkerderprovinz

    v2.0.0rc0 QA, second pass

    Re-ran the sweep against today's images, NVIDIA path, both bases, X11 and Wayland. All eight matrix cells passed. Five findings, line numbers are dbc9787. Happy to expand on any of them.

    1. A viewer can drive player 1's gamepad. js, is in VIEWER_ALLOWED_PREFIXES (input_handler.py:161) and the target slot is toks[2], straight from the client's message. The check that would bind a client to its own slot is gated on secure mode (selkies.py:4107, is_secure_mode = bool(master_token) at 1231; same in rtc.py:1371), but the sharing fragments only apply when there is no master token, so it is off exactly where the feature lives. Connecting as ?role=viewer&slot=-1 and sending js,c,0,... gives:

    INFO:data_websocket:Legacy client connected. Role: viewer, Slot: None
    INFO:webrtc_input:Client controller 'PROBE' is now associated with persistent virtual gamepad slot 0.
    

    So a #shared viewer holding no slot drives player 1, against usage.md:53 ("no keyboard, mouse or gamepad"). Index 99 is rejected, so the range check is the only one that fires. It also allows taking over (js,c,0, input_handler.py:4011-4021) and resetting (js,d,0, 4050-4060) that pad.

    2. The generated certificate cannot validate anywhere it is used. _make_self_signed_cert (stream_server.py:1207-1220) sets one SAN, DNSName("localhost"), no IPAddress, subject = issuer = CN=localhost. Stock images hit this by default: addons/base/Dockerfile:595 enables HTTPS and 600 deletes the snakeoil pair.

    3. A failed start looks healthy. When _require_configured_credentials (stream_server.py:1662-1683) exits, docker still reports running restarts=0 while the port returns 000. addons/base/services/selkies/run is a plain exec under s6-supervise with no restart ceiling, so it respawns forever. A ceiling or a port health check would surface it.

    4. Cursor callback outlives the websockets app on a mode switch. selkies.py:5344 dereferences self.app unchecked; that attribute is set to None in shutdown() at 5634, and no unregister for the callback exists (set_cursor_callback appears twice, both registrations). Result, swallowed at 5345:

    ERROR:data_websocket:Error handling pixelflux cursor: 'NoneType' object has no attribute 'send_ws_cursor_data'
    

    A race window, not a certainty. Switching to WebRTC on Wayland gave 8 occurrences on ubuntu26.04 and 7 on debiantrixie; X11 and plain WebSockets give zero.

    5. The apps panel only remembers installs in the browser. State lives in localStorage under prootInstalledApps (selkies-web-core/lib/app-commands.js:14), both dashboards initialise from it, and there is no query command, so nothing asks the server. Another browser or a cleared cache shows installed apps as missing.

    Also worth noting: the "JPEG Striped Frame freezes" I mentioned earlier was my own artifact (a second browser evicting the first) and is withdrawn. Wayland is clean now, zero swapchain and zero No free output buffer slot on both bases, with SELKIES_WAYLAND_X11_FALLBACK=false and the compositor verified up first. The second screen I could not test: "Add Screen +" does nothing here and gives no feedback, but I never entered the code path, so treat it as untested rather than working.

    Two questions:

    1. For the gamepad issue, do you want the slot derived from the connection and the existing check run unconditionally, or js, refused from viewers without a master token? I will send the PR either way.
    2. Is the localhost-only certificate deliberate, or should it carry the container's addresses?
  9. ztsyx commented on Sep 9, 2026

    @ztsyx

    Hi, after the second QA pass, do you have a rough plan for v2.0.0 stable release? Which issues are blocking stable?

  10. ehfd commented on Sep 9, 2026

    @ehfd
    MemberAuthor

    We have the whole test suite passing, and then we get a pre-release out.

  11. ztsyx commented on Sep 10, 2026

    @ztsyx

    Hi, is there a CI-built AppImage artifact available for testing before v2.0 is officially released?

  12. ehfd commented on Sep 10, 2026

    @ehfd
    MemberAuthor

    @ztsyx Artifacts are in each CI job under https://github.com/selkies-project/selkies/actions/workflows/ci.yaml. Appreciate if you could give it a go.

  13. ztsyx commented on Sep 10, 2026

    @ztsyx

    @ehfd Thanks, I'll test the AppImage from CI and report back if I find any issues.

  14. ztsyx commented on Sep 10, 2026

    @ztsyx

    @ztsyx Artifacts are in each CI job under https://github.com/selkies-project/selkies/actions/workflows/ci.yaml. Appreciate if you could give it a go.

    Hi @ehfd, integrated selkies-0.0.0.dev0-x86_64.AppImage from ci.yaml run 34343605118. One blocker:

    After --appimage-extract, ~1992 executables under usr/conda/bin/ have shebangs pointing to /home/runner/work/selkies/selkies/AppDir/usr/conda/bin/python. Both AppRun and direct invocation fail
    with exec: /home/runner/work/selkies/selkies/AppDir/usr/conda/bin/python: not found. No conda-unpack script is bundled to rewrite these on first run.

    Workaround: mkdir -p /home/runner/work/selkies/selkies && ln -sfn /home/runner/work/selkies/selkies/AppDir.

  15. ehfd commented on Sep 10, 2026

    @ehfd
    MemberAuthor

    @ztsyx Fixed in 5977f29; Please try again.

  16. ztsyx commented on Sep 10, 2026

    @ztsyx

    @ehfd Confirmed, --appimage-extract + direct AppRun invocation both work out-of-the-box on the CI build post-5977f29. Thanks for the quick turnaround.

  17. ehfd commented on Sep 12, 2026

    @ehfd
    MemberAuthor

    2.0.0rc0 is out. The role of this issue thread has been fulfilled.

  18. jhony-asanuma-oxb commented on Sep 16, 2026

    @jhony-asanuma-oxb

    hey guys, why were all 'v1.x' releases/packages deleted from https://github.com/selkies-project/selkies/releases and https://sourceforge.net/projects/selkies-gstreamer.mirror/files/?

    We're still using v1.6.2, and this has broken our CI:

    #7 195.9 + curl -fsSL https://github.com/selkies-project/selkies-gstreamer/releases/download/v1.6.2/gstreamer-selkies_gpl_v1.6.2_ubuntu22.04_amd64.tar.gz
    #7 195.9 + tar -xzf -
    #7 196.3 curl: (22) The requested URL returned error: 404
    
  19. ehfd commented on Sep 16, 2026

    @ehfd
    MemberAuthor

    @jhony-asanuma-oxb Sorry about that, but they were deleted because they were unsafe and had probably several security vulnerabilities (at least one at the very least). It's very trivial to change from v1.6.2 to v2.0.0rc0 (consider using any coding AI; it will do it), so please bear with us.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

CI/CDCI/CD procedures or container usagedocumentationDocumentation improvements or additionsencodingAudio or video encoders but not the OS interfacesinterfaceOS input, display, or audio interfacesperformancePerformance or latency issues, not critical but impacts usagetransportUnderlying media or data transport protocolswebWeb components including gst-web

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions