[Issue]: Can't install Jellyfin if dotnet is already installed #4416

Closed
opened 2026-02-07 00:49:50 +03:00 by OVERLORD · 4 comments
Owner

Originally created by @ImanolFotia on GitHub (Dec 8, 2022).

Can't install Jellyfin if dotnet is already installed

I'm using the latest Fedora 37 and neither package will install alongside the other, i.e. can't install jellyfin if dotnet is installed, and can't install dotnet if jellyfin is installed

What I'm doing:

sudo dnf install jellyfin

What I'm getting:
Error: Transaction test error: file /usr/lib/.build-id/68/73960cdb17942ebcbf54311816fe30b0ae2292 from install of jellyfin-server-10.8.8-1.fc37.x86_64 conflicts with file from package dotnet-sdk-6.0-6.0.111-1.fc37.x86_64

I'm using Jellyfin 10.8.8

My system:

OS: Fedora Linux 37 (Workstation Edition) x86_64
Kernel: 6.0.11-300.fc37.x86_64
Shell: bash 5.2.9
DE: GNOME 43.1

Jellyfin Version

10.8.0

Environment

- OS: Fedora Linux 37 (Workstation Edition) x86_64 
- Virtualization: No
- Clients:
- Browser:
- FFmpeg Version:
- Playback Method:
- Hardware Acceleration:
- Plugins:
- Reverse Proxy:
- Base URL:
- Networking:
- Storage:
Originally created by @ImanolFotia on GitHub (Dec 8, 2022). ### Can't install Jellyfin if dotnet is already installed I'm using the latest Fedora 37 and neither package will install alongside the other, i.e. can't install jellyfin if dotnet is installed, and can't install dotnet if jellyfin is installed What I'm doing: `sudo dnf install jellyfin` What I'm getting: `Error: Transaction test error: file /usr/lib/.build-id/68/73960cdb17942ebcbf54311816fe30b0ae2292 from install of jellyfin-server-10.8.8-1.fc37.x86_64 conflicts with file from package dotnet-sdk-6.0-6.0.111-1.fc37.x86_64 ` I'm using Jellyfin 10.8.8 ### My system: OS: Fedora Linux 37 (Workstation Edition) x86_64 Kernel: 6.0.11-300.fc37.x86_64 Shell: bash 5.2.9 DE: GNOME 43.1 ### Jellyfin Version 10.8.0 ### Environment ```markdown - OS: Fedora Linux 37 (Workstation Edition) x86_64 - Virtualization: No - Clients: - Browser: - FFmpeg Version: - Playback Method: - Hardware Acceleration: - Plugins: - Reverse Proxy: - Base URL: - Networking: - Storage: ```
OVERLORD added the bugstale labels 2026-02-07 00:49:50 +03:00
Author
Owner

@Seeings commented on GitHub (Dec 8, 2022):

I'm having the same issue when updating from jellyfin-server-10.8.7-2.fc36 to 10.8.8-1.fc37 (I recently upgraded from Fedora 36 to Fedora 37 so it's using the old fc36 install of 10.8.7-2)

I tried uninstalling dotnet-sdk but then I just get that it can't open the jellyfin-server*.rpm.
Otherwise I'm getting the same error as ImanolFotia.

@Seeings commented on GitHub (Dec 8, 2022): I'm having the same issue when updating from jellyfin-server-10.8.7-2.fc36 to 10.8.8-1.fc37 (I recently upgraded from Fedora 36 to Fedora 37 so it's using the old fc36 install of 10.8.7-2) I tried uninstalling dotnet-sdk but then I just get that it can't open the jellyfin-server*.rpm. Otherwise I'm getting the same error as ImanolFotia.
Author
Owner

@Seeings commented on GitHub (Jan 29, 2023):

This problem persist with the latest 10.8.9 update.

@Seeings commented on GitHub (Jan 29, 2023): This problem persist with the latest 10.8.9 update.
Author
Owner

@Seeings commented on GitHub (Jan 29, 2023):

I seem to have been able to install the 10.8.9 update now after removing dotnet (uninstalling the old jellyfin-server-10.8.7-2.fc36 with it) and renaming the folder /usr/lib64/jellyfin-web to jellyfin-web.backup. Seeing as the new version seems to be using a symlink to /usr/share/jellyfin-web instead. So it had problem with the old jellyfin-web folder existing.

@Seeings commented on GitHub (Jan 29, 2023): I seem to have been able to install the 10.8.9 update now after removing dotnet (uninstalling the old jellyfin-server-10.8.7-2.fc36 with it) and renaming the folder /usr/lib64/jellyfin-web to jellyfin-web.backup. Seeing as the new version seems to be using a symlink to /usr/share/jellyfin-web instead. So it had problem with the old jellyfin-web folder existing.
Author
Owner

@jellyfin-bot commented on GitHub (May 30, 2023):

This issue has gone 120 days without comment. To avoid abandoned issues, it will be closed in 21 days if there are no new comments.

If you're the original submitter of this issue, please comment confirming if this issue still affects you in the latest release or master branch, or close the issue if it has been fixed. If you're another user also affected by this bug, please comment confirming so. Either action will remove the stale label.

This bot exists to prevent issues from becoming stale and forgotten. Jellyfin is always moving forward, and bugs are often fixed as side effects of other changes. We therefore ask that bug report authors remain vigilant about their issues to ensure they are closed if fixed, or re-confirmed - perhaps with fresh logs or reproduction examples - regularly. If you have any questions you can reach us on Matrix or Social Media.

@jellyfin-bot commented on GitHub (May 30, 2023): This issue has gone 120 days without comment. To avoid abandoned issues, it will be closed in 21 days if there are no new comments. If you're the original submitter of this issue, please comment confirming if this issue still affects you in the latest release or master branch, or close the issue if it has been fixed. If you're another user also affected by this bug, please comment confirming so. Either action will remove the stale label. This bot exists to prevent issues from becoming stale and forgotten. Jellyfin is always moving forward, and bugs are often fixed as side effects of other changes. We therefore ask that bug report authors remain vigilant about their issues to ensure they are closed if fixed, or re-confirmed - perhaps with fresh logs or reproduction examples - regularly. If you have any questions you can reach us on [Matrix or Social Media](https://docs.jellyfin.org/general/getting-help.html).
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/jellyfin#4416