mirror of
https://github.com/jellyfin/jellyfin.git
synced 2026-05-04 18:09:12 +03:00
Playlist collision when using the same name as a playlist created by root #4187
Reference in New Issue
Block a user
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 @Andrew-sCode on GitHub (Sep 8, 2022).
Running Jellyfin version
10.8.3indocker.I was logged in using the web client.
I created three playlists as the
rootuser, let's saylist 1,list 2,list 3.I wanted to recreate these playlists as my main user, let's call this user,
user.I logged out of
rootand logged in asuser, on the web client.I created the first list, by adding a show to a
New...playlist and named itlist 1.I went to check if the
Playlistsoption was on the Home screen, because this was my first playlist for this user.The
Playlistsoption was available, I clicked on it, and my newly created playlist was available, along with the three playlists created asroot. So the Playlists listed were:list 1,list 1,list 2, andlist 3. Notice,list 1was listed twice. One version had the one show that I had just added.I deleted the
list 1playlist with the single show, thinking that I misunderstood playlists, and the maybe the playlists created byrootwere available to all users. But when I went back toPlaylistsafter deleting the newly created playlist, there were no playlists listed/available.There is some undefined behavior when playlists between a user and root have the same name. This might also extend to any two arbitrary users, but I did not investigate that possibility.
@jellyfin-bot commented on GitHub (Jan 13, 2023):
This issue has gone 120 days without comment. To avoid abandoned issues, it will be closed in 21 days if there are no new comments.
If you're the original submitter of this issue, please comment confirming if this issue still affects you in the latest release or master branch, or close the issue if it has been fixed. If you're another user also affected by this bug, please comment confirming so. Either action will remove the stale label.
This bot exists to prevent issues from becoming stale and forgotten. Jellyfin is always moving forward, and bugs are often fixed as side effects of other changes. We therefore ask that bug report authors remain vigilant about their issues to ensure they are closed if fixed, or re-confirmed - perhaps with fresh logs or reproduction examples - regularly. If you have any questions you can reach us on Matrix or Social Media.