starred/jellyfin

Fork 0

mirror of https://github.com/jellyfin/jellyfin.git synced 2026-01-23 23:20:51 +01:00

[10.11.0] Changes to Artist metadata for music does not save #7603

New issue

Closed

opened 2025-12-22 06:08:54 +01:00 by backuprepo · 3 comments

backuprepo commented

2025-12-22 06:08:54 +01:00

Owner

Originally created by @Casuallynoted on GitHub (Oct 28, 2025).

Description of the bug

After upgrading to 10.11.1, I've found that I can't get changes made in the UI to artist metadata to save - specifically when it comes to adding new artist names. One time, I got it to save - but when I refreshed, the Artist field was just empty.

Reproduction steps

Sign into Jellyfin on the web
Navigate to a music library, and into an album
Select a track and edit metadata
Change the artist name to a different artist and save it
Refresh the page to see the unchanged metadata

What is the current bug behavior?

It says that it saves, but if you refresh, the artist metadata does not change

What is the expected correct behavior?

It should change the artist metadata upon saving.

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

Environment

- OS: TrueNAS SCALE
- Linux Kernel: 6.12
- Virtualization: Docker
- Clients: Browser
- Browser: Firefox 144
- Jellyfin Data Storage: Local SATA SSD
- Media Storage: Local HDD
- External Integrations: Jellyseerr

Jellyfin logs

Nothing relevant in the logs, just a lot of spam, like this:

2025-10-27 23:12:24.453 -04:00] [INF] [150] Jellyfin.Api.Auth.CustomAuthenticationHandler: AuthenticationScheme: "CustomAuthentication" was challenged.
[2025-10-27 23:12:24.454 -04:00] [INF] [150] Jellyfin.Api.Auth.CustomAuthenticationHandler: "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[2025-10-27 23:12:24.455 -04:00] [INF] [156] Jellyfin.Api.Auth.CustomAuthenticationHandler: "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[2025-10-27 23:12:24.455 -04:00] [INF] [156] Jellyfin.Api.Auth.CustomAuthenticationHandler: "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[2025-10-27 23:12:24.455 -04:00] [INF] [150] Jellyfin.Api.Auth.CustomAuthenticationHandler: "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[2025-10-27 23:12:24.455 -04:00] [INF] [157] Jellyfin.Api.Auth.CustomAuthenticationHandler: "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[2025-10-27 23:12:24.455 -04:00] [INF] [156] Jellyfin.Api.Auth.CustomAuthenticationHandler: AuthenticationScheme: "CustomAuthentication" was challenged.
[2025-10-27 23:12:24.455 -04:00] [INF] [150] Jellyfin.Api.Auth.CustomAuthenticationHandler: AuthenticationScheme: "CustomAuthentication" was challenged.
[2025-10-27 23:12:24.455 -04:00] [INF] [157] Jellyfin.Api.Auth.CustomAuthenticationHandler: "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[2025-10-27 23:12:24.455 -04:00] [INF] [157] Jellyfin.Api.Auth.CustomAuthenticationHandler: AuthenticationScheme: "CustomAuthentication" was challenged.
[2025-10-27 23:12:24.455 -04:00] [INF] [163] Jellyfin.Api.Auth.CustomAuthenticationHandler: "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[2025-10-27 23:12:24.455 -04:00] [INF] [157] Jellyfin.Api.Auth.CustomAuthenticationHandler: "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[2025-10-27 23:12:24.455 -04:00] [INF] [163] Jellyfin.Api.Auth.CustomAuthenticationHandler: "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[2025-10-27 23:12:24.455 -04:00] [INF] [157] Jellyfin.Api.Auth.CustomAuthenticationHandler: "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[2025-10-27 23:12:24.456 -04:00] [INF] [163] Jellyfin.Api.Auth.CustomAuthenticationHandler: AuthenticationScheme: "CustomAuthentication" was challenged.
[2025-10-27 23:12:24.456 -04:00] [INF] [157] Jellyfin.Api.Auth.CustomAuthenticationHandler: AuthenticationScheme: "CustomAuthentication" was challenged.
[2025-10-27 23:12:24.813 -04:00] [INF] [163] Jellyfin.Api.Auth.CustomAuthenticationHandler: "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[2025-10-27 23:12:24.813 -04:00] [INF] [163] Jellyfin.Api.Auth.CustomAuthenticationHandler: "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[2025-10-27 23:12:24.813 -04:00] [INF] [163] Jellyfin.Api.Auth.CustomAuthenticationHandler: AuthenticationScheme: "CustomAuthentication" was challenged.

FFmpeg logs

Client / Browser logs

No response

Relevant screenshots or videos

No response

Additional information

No response

Originally created by @Casuallynoted on GitHub (Oct 28, 2025). ### Description of the bug After upgrading to 10.11.1, I've found that I can't get changes made in the UI to artist metadata to save - specifically when it comes to adding new artist names. One time, I got it to save - but when I refreshed, the Artist field was just empty. ### Reproduction steps 1. Sign into Jellyfin on the web 2. Navigate to a music library, and into an album 3. Select a track and edit metadata 4. Change the artist name to a different artist and save it 5. Refresh the page to see the unchanged metadata ### What is the current _bug_ behavior? It says that it saves, but if you refresh, the artist metadata does not change ### What is the expected _correct_ behavior? It should change the artist metadata upon saving. ### 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.11.1 ### Environment ```markdown - OS: TrueNAS SCALE - Linux Kernel: 6.12 - Virtualization: Docker - Clients: Browser - Browser: Firefox 144 - Jellyfin Data Storage: Local SATA SSD - Media Storage: Local HDD - External Integrations: Jellyseerr ``` ### Jellyfin logs ```shell Nothing relevant in the logs, just a lot of spam, like this: 2025-10-27 23:12:24.453 -04:00] [INF] [150] Jellyfin.Api.Auth.CustomAuthenticationHandler: AuthenticationScheme: "CustomAuthentication" was challenged. [2025-10-27 23:12:24.454 -04:00] [INF] [150] Jellyfin.Api.Auth.CustomAuthenticationHandler: "CustomAuthentication" was not authenticated. Failure message: "Invalid token." [2025-10-27 23:12:24.455 -04:00] [INF] [156] Jellyfin.Api.Auth.CustomAuthenticationHandler: "CustomAuthentication" was not authenticated. Failure message: "Invalid token." [2025-10-27 23:12:24.455 -04:00] [INF] [156] Jellyfin.Api.Auth.CustomAuthenticationHandler: "CustomAuthentication" was not authenticated. Failure message: "Invalid token." [2025-10-27 23:12:24.455 -04:00] [INF] [150] Jellyfin.Api.Auth.CustomAuthenticationHandler: "CustomAuthentication" was not authenticated. Failure message: "Invalid token." [2025-10-27 23:12:24.455 -04:00] [INF] [157] Jellyfin.Api.Auth.CustomAuthenticationHandler: "CustomAuthentication" was not authenticated. Failure message: "Invalid token." [2025-10-27 23:12:24.455 -04:00] [INF] [156] Jellyfin.Api.Auth.CustomAuthenticationHandler: AuthenticationScheme: "CustomAuthentication" was challenged. [2025-10-27 23:12:24.455 -04:00] [INF] [150] Jellyfin.Api.Auth.CustomAuthenticationHandler: AuthenticationScheme: "CustomAuthentication" was challenged. [2025-10-27 23:12:24.455 -04:00] [INF] [157] Jellyfin.Api.Auth.CustomAuthenticationHandler: "CustomAuthentication" was not authenticated. Failure message: "Invalid token." [2025-10-27 23:12:24.455 -04:00] [INF] [157] Jellyfin.Api.Auth.CustomAuthenticationHandler: AuthenticationScheme: "CustomAuthentication" was challenged. [2025-10-27 23:12:24.455 -04:00] [INF] [163] Jellyfin.Api.Auth.CustomAuthenticationHandler: "CustomAuthentication" was not authenticated. Failure message: "Invalid token." [2025-10-27 23:12:24.455 -04:00] [INF] [157] Jellyfin.Api.Auth.CustomAuthenticationHandler: "CustomAuthentication" was not authenticated. Failure message: "Invalid token." [2025-10-27 23:12:24.455 -04:00] [INF] [163] Jellyfin.Api.Auth.CustomAuthenticationHandler: "CustomAuthentication" was not authenticated. Failure message: "Invalid token." [2025-10-27 23:12:24.455 -04:00] [INF] [157] Jellyfin.Api.Auth.CustomAuthenticationHandler: "CustomAuthentication" was not authenticated. Failure message: "Invalid token." [2025-10-27 23:12:24.456 -04:00] [INF] [163] Jellyfin.Api.Auth.CustomAuthenticationHandler: AuthenticationScheme: "CustomAuthentication" was challenged. [2025-10-27 23:12:24.456 -04:00] [INF] [157] Jellyfin.Api.Auth.CustomAuthenticationHandler: AuthenticationScheme: "CustomAuthentication" was challenged. [2025-10-27 23:12:24.813 -04:00] [INF] [163] Jellyfin.Api.Auth.CustomAuthenticationHandler: "CustomAuthentication" was not authenticated. Failure message: "Invalid token." [2025-10-27 23:12:24.813 -04:00] [INF] [163] Jellyfin.Api.Auth.CustomAuthenticationHandler: "CustomAuthentication" was not authenticated. Failure message: "Invalid token." [2025-10-27 23:12:24.813 -04:00] [INF] [163] Jellyfin.Api.Auth.CustomAuthenticationHandler: AuthenticationScheme: "CustomAuthentication" was challenged. ``` ### FFmpeg logs ```shell ``` ### Client / Browser logs _No response_ ### Relevant screenshots or videos _No response_ ### Additional information _No response_

backuprepo

2025-12-22 06:08:54 +01:00

closed this issue
added the
bug
label

backuprepo commented

2025-12-22 06:08:58 +01:00

Author

Owner

@sproutsberry commented on GitHub (Oct 28, 2025):

Dealing with this on my server and it's a pretty significant usability issue. Affects a fresh install with no migrated data. After poking around a bit, I believe it may be 2-3 separate bugs.

When editing the Artists field, if an artist is not already in the database of artists, they will be excluded. This only applies to the UI, as the unknown artist is still saved to the relevant field in jellyfin.db. I believe this is why Artists blank out after being edited as well.
When editing the Artists field, the order of semicolon-delimited entries in the Artist field is not properly preserved, nor is it sorted in any discernible way (alphabetical UUID or Name). This does not apply when loading delimited artists from file tags.
Editing any kind of metadata on a track does not update in the Album or Edit Track view; only the Now Playing window. This is an in-memory state desync, as it fixes itself after a restart.

Custom delimiters only affect the file tag parser, they do not affect direct edits of the Artists field. This is not a bug, but may be relevant to anyone stumbling upon this issue.

@sproutsberry commented on GitHub (Oct 28, 2025): Dealing with this on my server and it's a pretty significant usability issue. Affects a fresh install with no migrated data. After poking around a bit, I believe it may be 2-3 separate bugs. - When editing the Artists field, if an artist is not already in the database of artists, they will be excluded. This only applies to the UI, as the unknown artist is still saved to the relevant field in jellyfin.db. I believe this is why Artists blank out after being edited as well. - When editing the Artists field, the order of semicolon-delimited entries in the Artist field is not properly preserved, nor is it sorted in any discernible way (alphabetical UUID or Name). This does not apply when loading delimited artists from file tags. - Editing any kind of metadata on a track does not update in the Album or Edit Track view; only the Now Playing window. This is an in-memory state desync, as it fixes itself after a restart. Custom delimiters only affect the file tag parser, they do not affect direct edits of the Artists field. This is not a bug, but may be relevant to anyone stumbling upon this issue.

backuprepo commented

2025-12-22 06:08:59 +01:00

Author

Owner

@liebestod77-netizen commented on GitHub (Nov 6, 2025):

10.11.2 has made my whole music listening experience miserable. Artists no longer show albums for many of them, I get "Server unavailable" after selecting Artist and seeing no albums. I spent hours changing metadata to correctly display albums and refreshing metadata after each metadata change on each album. That cured things for less than a day. Now back to frustration.

@liebestod77-netizen commented on GitHub (Nov 6, 2025): 10.11.2 has made my whole music listening experience miserable. Artists no longer show albums for many of them, I get "Server unavailable" after selecting Artist and seeing no albums. I spent hours changing metadata to correctly display albums and refreshing metadata after each metadata change on each album. That cured things for less than a day. Now back to frustration.

backuprepo commented

2025-12-22 06:09:02 +01:00

Author

Owner

@theguymadmax commented on GitHub (Nov 16, 2025):

Fixed by: #15423

@theguymadmax commented on GitHub (Nov 16, 2025): Fixed by: #15423

backuprepo referenced this issue

2025-12-22 08:39:29 +01:00

[PR #7603] [MERGED] Migrate MusicBrainz plugin to MetaBrainz.MusicBrainz #11288

backuprepo referenced this issue

2025-12-22 09:00:16 +01:00