Plex Flatpak using EOL libraries error

Server Version#: 1.42.2.10156
Player Version#: 1.112.0.359-0d79a49f
Flatpak is giving a warning that it is using end of life libraries, listed below.

Info: runtime org.freedesktop.Platformbranch23.08is end-of-life, with reason:
org.freedesktop.Platform 23.08 is no longer receiving fixes and security updates. Please update to a supported runtime version.
Info: applications using this runtime:
tv.plex.PlexDesktop

Info: runtime org.freedesktop.Platform.GL.defaultbranch23.08-extrais end-of-life, with reason:
org.freedesktop.Platform 23.08 is no longer receiving fixes and security updates. Please update to a supported runtime version.
Info: applications using this extension:
tv.plex.PlexDesktop

Info: runtime org.freedesktop.Platform.GL.defaultbranch23.08is end-of-life, with reason:
org.freedesktop.Platform 23.08 is no longer receiving fixes and security updates. Please update to a supported runtime version.
Info: applications using this extension:
tv.plex.PlexDesktop

1 Like

I have attempted bumping the platform to 25.08, and building locally, however, one of the resources cannot be fetched as it seems the endpoint is either being mapped to an internal IP that no longer exists or it is denying public access.

I think that this means, that either Plex have to conduct the necessary updates themselves internally and push the release, or fix the endpoint failure.

Changes I had made locally to test:

flathub.json

...
    "runtime": "org.freedesktop.Platform",
    "runtime-version": "25.08",
    "sdk": "org.freedesktop.Sdk"
...

tv.plex.PlexDesktop.yml

...
runtime-version: "25.08"
...
  - --share=network
  - --device=dri
  - --env=ELECTRON_OZONE_PLATFORM_HINT=auto
  - --filesystem=xdg-run/pipewire-0
  - --socket=wayland
  - --socket=fallback-x11
...

The tail from build log shows;

Downloading https://artifacts.plex.tv/plex-desktop-stable/1.112.0.359-0d79a49f/linux/Plex-1.112.0.359-0d79a49f-linux-x86_64.tar.bz2

Failed to download sources: module plex-binaries: The requested URL returned error: 403

There is a branch & PR that has been in play for several months regarding this matter, but it is “thick milky”…

I guess we just have to wait. Time will tell.

/shrug