mirror of
https://github.com/jellyfin/jellyfin.git
synced 2026-01-23 23:20:51 +01:00
10.11.x dotNet SkiaSharp Platform Problem, Needs Upgrade #7681
Labels
No labels
area:database
awaiting-feedback
backend
blocked
breaking change: web api
bug
build
ci
confirmed
discussion needed
dotnet future
downstream
duplicate
EFjellyfin.db
enhancement
feature
future
github-actions
good first issue
hdr
help wanted
invalid
investigation
librarydb
live-tv
lyrics
media playback
music
needs testing
nuget
performance
platform
pull-request
question
regression
release critical
requires-web
roadmap
security
security
stale
support
syncplay
ui & ux
upstream
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: starred/jellyfin#7681
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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
Jellyfin logs
FFmpeg logs
Client / Browser logs
Doesn't get that far
Relevant screenshots or videos
N/A
Additional information
No response
@crobibero commented on GitHub (Nov 3, 2025):
See https://github.com/jellyfin/jellyfin/pull/14862
@gandihar commented on GitHub (Nov 3, 2025):
If the developer team wants to roll back to old SkiaSharp, I'm fine with that.