mirror of
https://github.com/jellyfin/jellyfin.git
synced 2026-07-16 05:43:54 +03:00
[Issue]: Jellyfin not starting / DotNet issue #5302
Reference in New Issue
Block a user
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 @ztardik on GitHub (Dec 10, 2023).
Please describe your bug
After update it sopped working. After reinstall it's the same.
Complaining about dotnet version.
`It was not possible to find any compatible framework version
The framework 'Microsoft.NETCore.App', version '6.0.0' (x64) was not found.
6.0.0-rc.2.21470.23 at [/usr/lib64/dotnet/shared/Microsoft.NETCore.App]`
Jellyfin Version
10.8.z
if other:
No response
Environment
Jellyfin logs
FFmpeg logs
No response
Please attach any browser or client logs here
No response
Please attach any screenshots here
No response
Code of Conduct
@joshuaboniface commented on GitHub (Dec 11, 2023):
How was this installed, was it from our packages on repo.jellyfin.org or from dnf?
@ztardik commented on GitHub (Dec 12, 2023):
For a long time (over a year) it was installed from jellyfin rpm. When it stopped working I've tried installing from jellyfin and dnf sources (the above log).
@lolomin commented on GitHub (Apr 10, 2024):
Hi,
Same problem here on Fedora 39 with RPMFusion packages, it was an older installation with jellyfin RPM but even if I drop the /var/lib/jellyfin full directory and reinstall the packages I have the exact same problem, so maybe there is a problem with RPMFusion packages ? Did not yet try to run with jellyfin "official" Fedora 36 rpms ...
@lolomin commented on GitHub (Apr 10, 2024):
just tried a few minutes ago to uninstall all jellyfin-* RPMfusion 10.8.13 packages and installed all the 3 jellyfin/jellyfin-server and jellyfin-web Fedora packages from official Jellyfin repository here : https://repo.jellyfin.org/?path=/server/fedora/latest-stable/amd64
Everything is working properly at startup so it seems for me that the package at RPMFusion are broken for some reasons ...
Hope that it will serve for others people having the same problem.
@felix920506 commented on GitHub (Apr 11, 2024):
RPMFusion packages are maintained by a 3rd party, not us. Report the issue to them instead.