.ifo files cause unplayable duplicates in movie libraries #7223

Open
opened 2025-12-22 05:25:25 +01:00 by backuprepo · 1 comment
Owner

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:

  • Something.ifo
  • Something.mkv
  • Something.sup

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

  1. Have a directory containing multiple AV files, some of which being accompanied by an .ifo and a .sup file
  2. In Jellyfin, add the directory to a library of type "Movies"

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

- OS: Arch Linux
- Linux Kernel: 6.12.41-1-lts
- Virtualization: None (bare metal systemd service)
- Clients: Various
- Browser: Firefox 141.0
- FFmpeg Version: 7.1.1p7 (jellyfin-ffmpeg-1:7.1.1p7-1 Arch Linux package)
- Playback Method: Does not apply
- Hardware Acceleration: Does not apply
- GPU Model: Intel ARC A380
- Plugins: None
- Reverse Proxy: Caddy 2.10.0 (caddy-2.10.0-3 Arch Linux package)
- Base URL: None, or / (has own subdomain)
- Networking: Through reverse proxy exclusively via Unix socket
- Jellyfin Data Storage: NVME SSD
- Media Storage: Linux Software RAID
- External Integrations: None

Jellyfin logs

Could not pinpoint the log area where the scanner picked up the .ifo file

FFmpeg logs


Client / Browser logs

No response

Relevant screenshots or videos

No response

Additional information

No response

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: - Something.ifo - Something.mkv - Something.sup 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 1. Have a directory containing multiple AV files, some of which being accompanied by an .ifo and a .sup file 2. In Jellyfin, add the directory to a library of type "Movies" ### 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 ```markdown - OS: Arch Linux - Linux Kernel: 6.12.41-1-lts - Virtualization: None (bare metal systemd service) - Clients: Various - Browser: Firefox 141.0 - FFmpeg Version: 7.1.1p7 (jellyfin-ffmpeg-1:7.1.1p7-1 Arch Linux package) - Playback Method: Does not apply - Hardware Acceleration: Does not apply - GPU Model: Intel ARC A380 - Plugins: None - Reverse Proxy: Caddy 2.10.0 (caddy-2.10.0-3 Arch Linux package) - Base URL: None, or / (has own subdomain) - Networking: Through reverse proxy exclusively via Unix socket - Jellyfin Data Storage: NVME SSD - Media Storage: Linux Software RAID - External Integrations: None ``` ### Jellyfin logs ```shell Could not pinpoint the log area where the scanner picked up the .ifo file ``` ### FFmpeg logs ```shell ``` ### Client / Browser logs _No response_ ### Relevant screenshots or videos _No response_ ### Additional information _No response_
backuprepo added the
stale
bug
labels 2025-12-22 05:25:25 +01:00
Author
Owner

@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.

@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](https://jellyfin.org/contact).
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: starred/jellyfin#7223
No description provided.