10.11.x dotNet SkiaSharp Platform Problem, Needs Upgrade #7682

New Issue

OVERLORD · 2026-02-07T05:19:36+03:00

OVERLORD commented

2026-02-07 05:19:36 +03:00

Originally created by @gandihar on GitHub (Nov 3, 2025).

Description of the bug

Jellyfin 10.11.x fails to compile on Enterprise Linux systems older than EL9 due to a SkiaSharp platform issue.

Reproduction steps

Attempt to build Jellyfin 10.11.x with dotNet 9 on an EL8 (Rocky, Alma, CentOS Stream, Oracle, etc). Do the whole build and test process. During the test, the system will throw numerous errors about SkiaSharp (Or one of its components) not being able to load.

The exact same steps work fine on EL9 (Any variant).

What is the current bug behavior?

Jellyfin 10.11.x brings in SkiaSharp 3.116.1. Jellyfin 10.10.x used SkiaSharp 2.88.

After dissecting the problem for a while, one discovered that SkiaSharp 3.x has a bug in that the binaries provided link against GLIBC 2.29, which is only available in EL 9. EL 8 uses GLIBC 2.28.

This is not mentioned anywhere on the SkiaSharp website, but was discovered in the Github issues list. Here's the issue: https://github.com/mono/SkiaSharp/issues/3201 And they list it as fixed in 3.119-alpha, which has been replaced with a stable release since then.

What is the expected correct behavior?

The system should build on EL9 the same as EL8, since they both have dotNet 9 available. I am aware this is not a Jellyfin problem per se, but since SkiaSharp is required by Jellyfin, could we get it upgraded to SkiaSharp to v3.119.1? Assuming the version upgrade doesn't break something else.

Jellyfin Server version

10.10.0+

Specify commit id

No response

Specify unstable release number

No response

Specify version number

No response

Specify the build version

10.11.*

Environment

- OS: Enterprise Linux below 9
- Linux Kernel: 4.18.0-553.76.1.el8_10
- Virtualization: N/A
- Clients: N/A
- Browser: Firefox
- FFmpeg Version: Any
- Playback Method: Any
- Hardware Acceleration: N/A
- GPU Model: N/A
- Plugins: N/A
- Reverse Proxy: N/A
- Base URL: N/A
- Networking: N/A
- Jellyfin Data Storage: N/A
- Media Storage: N/A
- External Integrations: N/A

Jellyfin logs

Doesn't get that far

FFmpeg logs

Doesn't get that far

Client / Browser logs

Doesn't get that far

Relevant screenshots or videos

N/A

Additional information

No response

Originally created by @gandihar on GitHub (Nov 3, 2025). ### Description of the bug Jellyfin 10.11.x fails to compile on Enterprise Linux systems older than EL9 due to a SkiaSharp platform issue. ### Reproduction steps Attempt to build Jellyfin 10.11.x with dotNet 9 on an EL8 (Rocky, Alma, CentOS Stream, Oracle, etc). Do the whole build and test process. During the test, the system will throw numerous errors about SkiaSharp (Or one of its components) not being able to load. The exact same steps work fine on EL9 (Any variant). ### What is the current _bug_ behavior? Jellyfin 10.11.x brings in SkiaSharp 3.116.1. Jellyfin 10.10.x used SkiaSharp 2.88. After dissecting the problem for a while, one discovered that SkiaSharp 3.x has a bug in that the binaries provided link against GLIBC 2.29, which is only available in EL 9. EL 8 uses GLIBC 2.28. This is not mentioned anywhere on the SkiaSharp website, but was discovered in the Github issues list. Here's the issue: https://github.com/mono/SkiaSharp/issues/3201 And they list it as fixed in 3.119-alpha, which has been replaced with a stable release since then. ### What is the expected _correct_ behavior? The system should build on EL9 the same as EL8, since they both have dotNet 9 available. I am aware this is not a Jellyfin problem per se, but since SkiaSharp is required by Jellyfin, could we get it upgraded to SkiaSharp to v3.119.1? Assuming the version upgrade doesn't break something else. ### Jellyfin Server version 10.10.0+ ### Specify commit id _No response_ ### Specify unstable release number _No response_ ### Specify version number _No response_ ### Specify the build version 10.11.* ### Environment ```markdown - OS: Enterprise Linux below 9 - Linux Kernel: 4.18.0-553.76.1.el8_10 - Virtualization: N/A - Clients: N/A - Browser: Firefox - FFmpeg Version: Any - Playback Method: Any - Hardware Acceleration: N/A - GPU Model: N/A - Plugins: N/A - Reverse Proxy: N/A - Base URL: N/A - Networking: N/A - Jellyfin Data Storage: N/A - Media Storage: N/A - External Integrations: N/A ``` ### Jellyfin logs ```shell Doesn't get that far ``` ### FFmpeg logs ```shell Doesn't get that far ``` ### Client / Browser logs Doesn't get that far ### Relevant screenshots or videos N/A ### Additional information _No response_

OVERLORD added the bug upstream labels 2026-02-07 05:19:36 +03:00

OVERLORD commented

2026-02-07 05:19:38 +03:00

@crobibero commented on GitHub (Nov 4, 2025):

See https://github.com/jellyfin/jellyfin/pull/14862

@crobibero commented on GitHub (Nov 4, 2025): See https://github.com/jellyfin/jellyfin/pull/14862

OVERLORD commented

2026-02-07 05:19:39 +03:00

@gandihar commented on GitHub (Nov 4, 2025):

If the developer team wants to roll back to old SkiaSharp, I'm fine with that.

@gandihar commented on GitHub (Nov 4, 2025): If the developer team wants to roll back to old SkiaSharp, I'm fine with that.

OVERLORD referenced this issue