Jellyfin error when using dietpi-update

Troubleshooting
1

Creating a bug report/issue

I have searched the existing open and closed issues

Required Information

  • DietPi version Trixie
  • Distro version | echo $G_DISTRO_NAME $G_RASPBIAN
  • Kernel version | uname --all
  • Architecture | dpkg --print-architecture
  • SBC model | echo $G_HW_MODEL_NAME or (EG: RPi3)
  • Power supply used | (EG: 5V 1A RAVpower)
  • SD card used | (EG: SanDisk ultra)

Additional Information (if applicable)

PRETTY_NAME=“Debian GNU/Linux 13 (trixie)”
NAME=“Debian GNU/Linux”
VERSION_ID=“13”
VERSION=“13 (trixie)”
VERSION_CODENAME=trixie
DEBIAN_VERSION_FULL=13.1
ID=debian
HOME_URL=“https://www.debian.org/”
SUPPORT_URL=“https://www.debian.org/support”
BUG_REPORT_URL=“https://bugs.debian.org/”

  • Software title | (EG: Nextcloud)
  • Was the software title installed freshly or updated/migrated?
  • Can this issue be replicated on a fresh installation of DietPi?
    ← If you sent a “dietpi-bugreport”, please paste the ID here →
  • Bug report ID | echo $G_HW_UUID

Steps to reproduce

  1. …
  2. …

Expected behaviour

  • …

Actual behaviour

* …APT update │
  │ - Command: apt-get -y -eany update │
  │ - Exit code: 100 │
  │ - DietPi version: v9.18.1 (MichaIng/master) | HW_MODEL: 5 | HW_ARCH: 3 | DISTRO: 8 │
  │ - Error log: │
  │ Hit:1 https://deb.debian.org/debian trixie InRelease │
  │ Hit:2 https://deb.debian.org/debian trixie-updates InRelease │
  │ Hit:3 https://archive.raspberrypi.com/debian trixie InRelease │
  │ Hit:4 https://dietpi.com/apt trixie InRelease │
  │ Hit:5 [https://deb.debian.org/debian-security](https://deb.debian.org/debian-security) trixie-security InRelease │
  │ Hit:6 https://deb.debian.org/debian trixie-backports InRelease │
  │ Hit:7 https://dietpi.com/apt all InRelease │
  │ Get:8 [https://repo.jellyfin.org/debian](https://repo.jellyfin.org/debian) trixie InRelease \[8126 B\] │
  │ Err:8 [https://repo.jellyfin.org/debian](https://repo.jellyfin.org/debian) trixie InRelease │
  │ Sub-process /usr/bin/sqv returned an error code (1), error message is: Signature by │
  │ 4918AABC486CA052358D778D49023CD01DE21A7B was created after the --not-after date. │
  │ Reading package lists… │
  │ W: OpenPGP signature verification failed: [https://repo.jellyfin.org/debian](https://repo.jellyfin.org/debian) trixie InRelease: Sub-process │
  │ /usr/bin/sqv returned an error code (1), error message is: Signature by 4918AABC486CA052358D778D49023CD01DE21A7B was │
  │ created after the --not-after date. │
  │ E: The repository ‘[https://repo.jellyfin.org/debian](https://repo.jellyfin.org/debian) trixie InRelease’ is not signed. │

Extra details

  • …
2

Hmm on a new installation its working, maybe the PGP key depreciated on your system.

try following

eval curl -sSfL 'https://repo.jellyfin.org/jellyfin_team.gpg.key' | gpg --dearmor -o /etc/apt/trusted.gpg.d/dietpi-jellyfin.gpg --yes
apt update
3

Can you also check that your system time is correct?

date
4

I have checked the hardware clock time it says 2025-10-29 14:28:56.667053+00:00 ut my PC says it is 2:33

5

If I issue the command hwclock -w the hwclock -r the RPi is still about 4 minutes different from my PC

6 
root@DietPi:\~# eval curl -sSfL ‘https://repo.jellyfin.org/jellyfin_team.gpg.key’ | gpg --dearmor -o /etc/apt/trusted.gpg.d/dietpi-jellyfin.gpg --yes

apt update
Hit:1 https://deb.debian.org/debian trixie InRelease
Get:2 https://deb.debian.org/debian trixie-updates InRelease \[47.3 kB\]
Hit:3 https://dietpi.com/apt trixie InRelease
Get:4 https://archive.raspberrypi.com/debian trixie InRelease \[54.8 kB\]
Get:5 https://deb.debian.org/debian-security trixie-security InRelease \[43.4 kB\]
Get:6 https://archive.raspberrypi.com/debian trixie/main arm64 Packages \[352 kB\]
Get:7 https://deb.debian.org/debian trixie-backports InRelease \[54.0 kB\]
Get:8 https://dietpi.com/apt all InRelease \[30.3 kB\]
Get:9 https://repo.jellyfin.org/debian trixie InRelease \[8126 B\]
Fetched 590 kB in 1s (523 kB/s)
1 package can be upgraded. Run ‘apt list --upgradable’ to see it.

root@DietPi:\~# apt list --upgradable
raspberrypi-sys-mods/all 2:20251027-dietpi1 all \[upgradable from: 2:20230510-dietpi2\]
Notice: There are 2 additional versions. Please use the ‘-a’ switch to see them.

root@DietPi:\~# apt list --upgradable -a
raspberrypi-sys-mods/all 2:20251027-dietpi1 all \[upgradable from: 2:20230510-dietpi2\]
raspberrypi-sys-mods/all,now 2:20230510-dietpi2 all \[installed,upgradable to: 2:20251027-dietpi1\]
raspberrypi-sys-mods/testing 1:20251028+1 all

root@DietPi:\~# apt upgrade
Upgrading:
raspberrypi-sys-mods

Summary:
Upgrading: 1, Installing: 0, Removing: 0, Not Upgrading: 0
Download size: 3616 B
Space needed: 65.5 kB / 406 GB available

Continue? \[Y/n\] y
Get:1 https://dietpi.com/apt all/rpi all raspberrypi-sys-mods all 2:20251027-dietpi1 \[3616 B\]
Fetched 3616 B in 1s (5473 B/s)
(Reading database … 24645 files and directories currently installed.)
Preparing to unpack …/raspberrypi-sys-mods_2%3a20251027-dietpi1_all.deb …
Unpacking raspberrypi-sys-mods (2:20251027-dietpi1) over (2:20230510-dietpi2) ..
.
dpkg: warning: unable to delete old directory ‘/lib/udev/rules.d’: Directory not
empty
dpkg: warning: unable to delete old directory ‘/lib/udev’: Directory not empty
Setting up raspberrypi-sys-mods (2:20251027-dietpi1) …
root@DietPi:\~#
7

That’s now a different message not related to jellyfin. But all seems to be fine

8

After that new update jellyfin is working again

9

Btw system clock can be set manually as follows, if needed

/boot/dietpi/func/run_ntpd 1
10

Am I supposed to delete manually :-1: dpkg: warning:

unable to delete old directory ‘/lib/udev/rules.d’: Directory not empty
dpkg: warning: unable to delete old directory ‘/lib/udev’: Directory not empty
Setting up raspberrypi-sys-mods (2:20251027-dietpi1) …
root@DietPi:\~#
11

Nope

12

It’s very odd that the RPi time is about 5 minutes less than my laptop and they are both using NPT

13

Maybe this is a new feature ‘Time Dilation’ very useful for aliens

14

You would need to get your time in sync as describe above and see it it drift again.

15
  1. doesn’t hwclock -w set the time and hwclock-r reads it.
  2. Is that correct?
16 
oot@DietPi:\~# /boot/dietpi/func/run_ntpd 1
\[ INFO \] DietPi-TimeSync | Manual mode detected, skipping time sync
root@DietPi:\~#
17 
root@DietPi:\~# /boot/dietpi/func/run_ntpd 1
\[  OK  \] DietPi-TimeSync | rm /run/systemd/timesync/synchronized
\[  OK  \] DietPi-TimeSync | systemctl restart systemd-timesyncd
\[ INFO \] DietPi-TimeSync | Waiting for time sync (1/60)
\[  OK  \] DietPi-TimeSync | Time sync completed
\[  OK  \] DietPi-TimeSync | systemctl stop systemd-timesyncd
\[  OK  \] DietPi-TimeSync | mkdir -p /run/systemd/timesync
root@DietPi:\~#skipping time sync

I read somewhere if you use the hwclock then you ought to set time syncing to custom but that looks like it stops the RPi syncing the NTP time.

root@DietPi:\~# /boot/dietpi/func/run_ntpd 1
\[  OK  \] DietPi-TimeSync | rm /run/systemd/timesync/synchronized
\[  OK  \] DietPi-TimeSync | systemctl restart systemd-timesyncd
\[ INFO \] DietPi-TimeSync | Waiting for time sync (1/60)
\[  OK  \] DietPi-TimeSync | Time sync completed
\[  OK  \] DietPi-TimeSync | systemctl stop systemd-timesyncd
\[  OK  \] DietPi-TimeSync | mkdir -p /run/systemd/timesync
root@DietPi:\~#
18

correct

That’s incorrect. The Pi does not have its own time module. Where would it get the time from if it is offline and being restarted?

19

would it not get the time from the hardware clock

20

None of the RPi models have a hardware clock, it get’s the time from the internet via NTP.