Duplicate music albums shown in music library on the artist page if this artist already was in another library

[densilent]

This issue respects the following points:

• This is a bug, not a question or a configuration issue; Please visit our forum or chat rooms first to troubleshoot with volunteers, before creating a report. The links can be found here.
• This issue is not already reported on GitHub (I've searched it).
• I'm using an up to date version of Jellyfin Server stable, unstable or master; We generally do not support previous older versions. If possible, please update to the latest version before opening an issue.
• I agree to follow Jellyfin's Code of Conduct.
• This report addresses only a single issue; If you encounter multiple issues, kindly create separate reports for each one.

Description of the bug

I have multiple music libraries (for different users).

Let's say there is an artist "Artist A" in music library "Library A". And a bunch of other different artists.
Path to media files is /mnt/MusicA/

I create a separate music library "Library B" with almost completely different artists BUT it also has "Artist A"
Path to media files is /mnt/MusicB/

There is only one path to media files in each library. And they are different.

Yes, there are two different folders with ArtistA's music. Albums and tracks are obviously the same, id tags in files are the same. Paths are different. No hardlinks, two different folders in different places but with the same content.

If we open "Library B", page Artists, page "Artist A" we will see that all Artist A albums shown twice. If we open «media info» - paths to media files are different. One copy of an album has paths to /mnt/MusicA another copy of the album to /mnt/MusicB/
But there is no /mnt/MusicA in "Library B" config.

There is more to it. If we open "Library B", page Artists, page "Artist A" and "Library A", page Artists, page "Artist A" - URLs of these pages are the same. Basically, no matter where we start (what music library), we end on the same page. And this page belongs to whatever library created first. This has another consequences - if "Library B" was created later then "Library A" and userA has only access to "Library A" and userB has access only to "Library B" then userB cannot open the artist page at all (empty page with never-ending load animation). Once we gave userB access to music "Library A" he starts seeing the same page as userA with duplicate albums.

I tried to rename track files. So both libraries still have Artist A music but path to files and filenames are different. Then I delete "Library B" and create it again. No difference. Still two copies of the same albums with different paths.
I reinstalled the server from scratch. No difference.

For example, brother and sister have two separate music libraries and separate folders with media files. Brother created his library first. Brother has Avril Lavigne and Canibal Corpse. Sister has Madonna and Avril Lavigne. Sister cannot open her Avril Lavigne artist page unless she has access to her brothers' library. And in brothers' library he see duplicate albums for Avrile Lavigne. One album from his folder and the second from his sister's fоlder (this folder is NOT added in his library settings). If they both have access to brothers' library they will see the same Avril Lavigne page with duplicate albums.

more context with screenshots here
https://forum.jellyfin.org/t-duplicate-music-albums

Reproduction steps

1. Create folder /whatever/MusicA/
2. Create folder /whatever/MusicB/
3. Add to folder "MusicA" music artists "ArtistA", "ArtistB"
4. Add to folder "MusicB" music artists "ArtistA", "ArtistC"
5. Open web jellyfin web interface
6. Create music library "MusicA" with only one path to media files /whatever/MusicA/
7. Create music library "MusicB" with only one path to media files /whatever/MusicB/
8. Wait until metadata scan is completed
9. Go to library "MusicB" -> artists -> "ArtistA" page

What is the current bug behavior?

1. all "ArtistA" albums are shown twice. If we open «media info» - paths to media files are different. One copy of an album has paths to /whatever/MusicA/ another copy of the album to /whatever/MusicB/
2. URLs of the "ArtistA" pages from music library "MusicA" and music library "MusicB" are the same.
3. User can open "ArtistA" page from music library "MusicB" ONLY if he has access to music library "MusicA"

What is the expected correct behavior?

1. all "ArtistA" albums are shown only once (because there is only one path to media files in the library config)
2. URLs of the "ArtistA" pages from music library "MusicA" and music library "MusicB" are different (because these are different libraries)
3. User can open "ArtistA" page from music library "MusicB" without having access to music library "MusicA" (because he has ArtistA media files in his music library "MusicB")

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

Environment

- OS: Ubuntu server 24.04
- Linux Kernel: 6.8.0-48-generic 
- Virtualization: esxi
- Clients: any
- Browser: any supported
- FFmpeg Version: ffmpeg 7:6.1.1-3ubuntu5  jellyfin-ffmpeg7 7.0.2-5-noble
- Playback Method: any (irrelevant)
- Hardware Acceleration: none
- GPU Model: none
- Plugins: none (only preinstalled AudioDB;MusicBrainz;OMDb;Studio Images;TMDb)
- Reverse Proxy: Nginx Proxy Manager
- Base URL: none
- Networking: connection to LAN - bridge (esxi), connection to WAN - NAT
- Storage: NFS (for media files); local for jellyfin itself

Jellyfin logs

I didn't see anything relevant in the logs :(

FFmpeg logs

No response

Client / Browser logs

No response

Relevant screenshots or videos

Additional information

I use proxy for blocked domains. So jellyfin service is started with settings override:
sudo systemctl edit jellyfin.service

[Service]
Environment=http_proxy=http://127.0.0.1:10181
Environment=https_proxy=http://127.0.0.1:10181

[farfalleflickan]

Exact same on a bare metal install on Debian.

[densilent]

Updated to server 10.10.0 - no changes. Same bug.

[Dan-613]

I think the answer to this is the same as #12976 (comment)

[densilent]

I think the answer to this is the same as #12976 (comment)

Looks to me like two different problems.
There - one library. Two folders with same artist. Two artist in web interface - looks like this is "by design", not a bug.
Here - many libraries. only one folder with artist in each. One artist in web interface. But many identical albums (from each other library, everybody can see content from this artist from all other libraries at once) - this can not be intended behavior, looks like a bug

[densilent]

Another consequence of this bug:
"Various Artist" is a "artist" too. So all albums with "various artist" tag mixes together on one page in every library.
For example, brother has OST from HotLine Miami in his separate library and sister has OST from Repo in her separate library. But because of the bug they both see in their libraries both OSTs
Screenshots from my server:

[densilent]

Also, notice both libraries MusicM and MusicS from previous screenshots have Korn in them?
Guess how Korn page looks in both of this libraries. Yes, with duplicate albums.

[farfalleflickan]

Even if this isn't a bug (and I wholeheartedly agree with densilent that it is ) this part would still be at play:

if "Library B" was created later then "Library A" and userA has only access to "Library A" and userB has access only to "Library B" then userB cannot open the artist page at all (empty page with never-ending load animation).

At the very least that behavior cannot be as intended.

[densilent]

Even if this isn't a bug (and I wholeheartedly agree with densilent that it is ) this part would still be at play:

if "Library B" was created later then "Library A" and userA has only access to "Library A" and userB has access only to "Library B" then userB cannot open the artist page at all (empty page with never-ending load animation).

At the very least that behavior cannot be as intended.

Yes and it is really annoying.
Again, real life example from previous screenshots:
I can not give User1 access only to lib MusicM and User2 only to lib MusicS (that was my original intention) because User2 then loses access to Korn while he obviously has Korn in his media folder. That makes zero sense.