Jellyfin 10.8.13 or 10.9.1?

[Jinxovarrio]

I upgraded my Jellyfin from 10.8.13 to 10.9.1 and since then I have had some bugs appearing on Github like the application suddenly crashes and I have to restart the container, apart from many other problems.

Many of them were corrected by testing from scratch version 10.9.1 in another container.

The thing is that after looking at Github I don't know if it is advisable to continue with an installation of Jellyfin 10.9.1 from scratch or go back to a clean install of 10.8.13 from scratch.

What do you recommend?

[TeaTotaled]

In general, you should use 10.9.1 (or whatever is latest). It has bug fixes, new features, and as of the 10.9.x branch, a very revamped testing framework that should make it easier to find bugs before they are released.

Go with Jellyfin 10.9.1.

[Machiela]

> Go with Jellyfin 10.9.1.

I did that, and I've gone from a completely crash-free problem-free environment to an empty screen with no movies; crashes, lost preferences, complete PC freeze, subtitles appearing scrambled. That was in the first 30 minutes. I've just downgraded client and server back to stable releases again. I'll wait for the bugs to die first.

[rsd-jelly]

I upgraded my Jellyfin from 10.8.13 to 10.9.1 and since then I have had some bugs appearing on Github like the application suddenly crashes and I have to restart the container, apart from many other problems.

Many of them were corrected by testing from scratch version 10.9.1 in another container.

The thing is that after looking at Github I don't know if it is advisable to continue with an installation of Jellyfin 10.9.1 from scratch or go back to a clean install of 10.8.13 from scratch.

What do you recommend?

I also had issues after apt on Ubuntu upgraded without knowing issues would result.  I ended up switching to 10.8.13 based docker install to prevent further issues and have had smooth zero issue results. I will keep this version until the major 10.9.x bugs have been resolved with confidence.

[jellyforphotos]

As for me, I cannot compile 10.9.1 from source, using "python3 ./build.py auto ubuntu amd64 noble"
It was working fine on 10.8.13 and 10.9.0
Do you know how to force compiling 10.8.13 ? (I tried ./checkout.py v10.8.13 but I still cant compile..)

[MisterMcDuck]

As for me, I cannot compile 10.9.1 from source, using "python3 ./build.py auto ubuntu amd64 noble"
It was working fine on 10.8.13 and 10.9.0
Do you know how to force compiling 10.8.13 ? (I tried ./checkout.py v10.8.13 but I still cant compile..)

What errors are you seeing? Also, I always need the --local flag when I do my docker compile.
my buildline: ./build.py 10.9.1 docker amd64 --local

[jellyforphotos]

I do a native compilation (ubuntu noble)
I see .net related errors , it was not the case with previous versions of jellyfin :
#7 14.21 Some packages could not be installed.
#7 14.21 The following packages have unmet dependencies:
#7 14.27 dotnet-sdk-8.0 : Depends: dotnet-runtime-8.0 (>= 8.0.5) but it is not going to be installed
#7 14.27 Depends: netstandard-targeting-pack-2.1 (>= 2.1.0)
#7 14.27 Depends: aspnetcore-runtime-8.0 (>= 8.0.5) but it is not going to be installed
#7 14.27 E: Unable to correct problems, you have held broken packages.
#7 ERROR: process "/bin/sh -c wget https://packages.microsoft.com/config/${PACKAGE_TYPE}/${PACKAGE_VERSION}/packages-microsoft-prod.deb -O packages-microsoft-prod.deb && dpkg -i packages-microsoft-prod.deb && apt-get -f install && apt-get update && apt-get install -y dotnet-sdk-${DOTNET_VERSION}" did not complete successfully: exit code: 100

[TheDreadPirate]

Why are you compiling and not installing the deb package?

For those of you with crashes, can you share your full jellyfin logs via pastebin?

[lolish]

I got 10.9.1 on Windows runs like a champ 0 issues everything jsut works

[MisterMcDuck]

@jellyforphotos FWIW, I have the same error when compiling for a native debpkg.

This may have something to do with Microsoft switching how they handle dotnet packages for .NET8