mirror of
https://github.com/jellyfin/jellyfin.git
synced 2026-01-23 23:20:51 +01:00
Content duplicated in playlist #7925
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#7925
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 @ipascv on GitHub (Dec 17, 2025).
Description of the bug
Content duplicates in playlist after adding new items from a different library and change playlist image updating missing metadata.
Reproduction steps
What is the current bug behavior?
It seems to be a problem with rebuilding/searching metadata when (¿sql?) querying from 2 different libraries without appropiate grouping.
Removing one of the duplicated items from the playlist remove all occurrences of that item.
What is the expected correct behavior?
After updating the metadata, the playlist content elements shouldn't be duplicated.
Also removing one of the duplicated items should remove only that occurrence of the item.
Jellyfin Server version
10.11.5
Specify commit id
No response
Specify unstable release number
No response
Specify version number
No response
Specify the build version
10.11.5
Environment
Jellyfin logs
FFmpeg logs
Client / Browser logs
No response
Relevant screenshots or videos
No response
Additional information
No response
@Collin-Swish commented on GitHub (Dec 19, 2025):
If no one else is working on this I'd like to take a look.