mirror of
https://github.com/jellyfin/jellyfin.git
synced 2026-01-23 23:20:51 +01:00
.ifo files cause unplayable duplicates in movie libraries #7223
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#7223
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 @eomanis on GitHub (Aug 6, 2025).
Description of the bug
Sometimes AV files are accompanied by an .ifo and a .sup file:
I understand that the .sup file is a "BluRay Subtitle Presentation" type of file, and that the .ifo file is some sort of index file that possibly contains metadata about the contents of the .sup file.
When Jellyfin encounters such a file group, not only the .mkv is added to the movie library, but also a library entry is created for the .ifo file; a broken duplicate that cannot be played back.
The .ifo file can be seen when bringing up the broken entry's media information in the Jellyfin web frontend.
Reproduction steps
What is the current bug behavior?
In addition to the actual AV file, the accompanying .ifo file is added to the library as its own, unplayable entry
What is the expected correct behavior?
Jellyfin should not identify .ifo files as files that should be added to movie libraries
Jellyfin Server version
10.10.0+
Specify commit id
No response
Specify unstable release number
No response
Specify version number
10.10.7
Specify the build version
Release
Environment
Jellyfin logs
FFmpeg logs
Client / Browser logs
No response
Relevant screenshots or videos
No response
Additional information
No response
@jellyfin-bot commented on GitHub (Dec 5, 2025):
This issue has gone 120 days without an update and will be closed within 21 days if there is no new activity. To prevent this issue from being closed, please confirm the issue has not already been fixed by providing updated examples or logs.
If you have any questions you can use one of several ways to contact us.