-
-
Notifications
You must be signed in to change notification settings - Fork 522
Open
Labels
External bug 🐞For bugs which are not caused by DietPi.For bugs which are not caused by DietPi.Waiting for external fix ⏳Workaround available 🆗Workaround is available/has been implemented, but a definite solution should be found when possible.Workaround is available/has been implemented, but a definite solution should be found when possible.
Milestone
Description
Creating a bug report/issue
- I have searched the existing open and closed issues
Required Information
- DietPi version |
cat /boot/dietpi/.version
G_DIETPI_VERSION_CORE=9
G_DIETPI_VERSION_SUB=12
G_DIETPI_VERSION_RC=1
G_GITBRANCH='master'
G_GITOWNER='MichaIng'
- Distro version |
echo $G_DISTRO_NAME $G_RASPBIAN
bookworm
- Kernel version |
uname -a
Linux DietPi 6.1.0-34-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.135-1 (2025-04-25) x86_64 GNU/Linux
- SBC model |
echo $G_HW_MODEL_NAME
or (EG: RPi3)
Native PC (x86_64) - Power supply used | (EG: 5V 1A RAVpower)
Generic Power Supply - SD card used | (EG: SanDisk ultra)
Generic NVMe
Additional Information (if applicable)
- Software title | (EG: Nextcloud)
Jellyfin - Was the software title installed freshly or updated/migrated?
Yes, installed freshly. - Can this issue be replicated on a fresh installation of DietPi?
Yes.
Steps to reproduce
- Install Jellyfin the official way by using DietPi Software List.
Expected behaviour
Jellyfin should be installed properly.
Actual behaviour
Jellyfin is installed a very wrong/obsolete way.
For example, it does not even install the packages, which are shown in the documentation.
Then, it needs ancient fixes, like this one.
Extra details
Most basic DietPi installation. Only installed software from official DietPi Software List, like Jellyfin, Docker and OpenSSH.
Metadata
Metadata
Assignees
Labels
External bug 🐞For bugs which are not caused by DietPi.For bugs which are not caused by DietPi.Waiting for external fix ⏳Workaround available 🆗Workaround is available/has been implemented, but a definite solution should be found when possible.Workaround is available/has been implemented, but a definite solution should be found when possible.