mirror of
https://github.com/jellyfin/jellyfin.git
synced 2026-01-24 07:30:57 +01:00
📺 Metadata bug: Episode titles containing “2002” trigger creation of phantom “Season 20” #7420
Labels
No labels
area:database
awaiting-feedback
backend
blocked
breaking change: web api
bug
build
ci
confirmed
discussion needed
dotnet future
downstream
duplicate
EFjellyfin.db
enhancement
feature
future
github-actions
good first issue
hdr
help wanted
invalid
investigation
librarydb
live-tv
lyrics
media playback
music
needs testing
nuget
performance
platform
pull-request
question
regression
release critical
requires-web
roadmap
security
security
stale
support
syncplay
ui & ux
upstream
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: starred/jellyfin#7420
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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 @YamRider1991 on GitHub (Oct 16, 2025).
Description of the bug
Description:
I encountered an issue where Jellyfin automatically creates a “Season 20” folder/entry for a single-season series whenever the episode filenames contain the year 2002 in their titles.
Reproduction steps
Example file naming pattern:
ShowName - S01E01 - Pilot (2002).mkv
ShowName - S01E02 - Episode Two (2002).mkv
What is the current bug behavior?
Even though there’s only one season, Jellyfin generated a phantom “Season 20” containing the same episodes.
What is the expected correct behavior?
Workaround:
Removing the “2002” text from the filenames stops the issue. After renaming the files, Jellyfin no longer creates the phantom season.
Jellyfin Server version
10.10.0+
Specify commit id
No response
Specify unstable release number
No response
Specify version number
No response
Specify the build version
10.10.7
Environment
Jellyfin logs
FFmpeg logs
Client / Browser logs
No response
Relevant screenshots or videos
No response
Additional information
No response
@marrobHD commented on GitHub (Oct 19, 2025):
I can confirm this issue on 10.10.7