10.11.1 New Library adds incorrect PhysicalLocationsList #7602

Open
opened 2026-02-07 05:13:51 +03:00 by OVERLORD · 4 comments
Owner

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

Description of the bug

When creating a new library in 10.11.1 an extra item is injected into the PhysicalLocationsList of /config/root/default/$libraryName. Example:

❯ sqlite3 jellyfin/config/data/jellyfin.db "SELECT data FROM BaseItems WHERE Path='/config/root/default/Concerts';" | python3 -m json.tool 2>/dev/null || sqlite3 jellyfin/config/data/jellyfin.db "SELECT data FROM BaseItems WHERE Path='/config/root/default/Concerts';"
{
    "PhysicalLocationsList": [
        "/config/root/default/Concerts",
        "/media/video/concerts"
    ],
...

The new library does not work until:

  1. Jellyfin is stopped.
  2. The extra location is removed, for example:
❯ sqlite3 jellyfin/config/data/jellyfin.db <<EOF
UPDATE BaseItems
SET data = json_set(data, '$.PhysicalLocationsList', json('["\/media\/video\/concerts"]'))
WHERE Path='/config/root/default/Concerts';
EOF
  1. Jellyfin is restarted.

Reproduction steps

  1. Be on 10.11.1
  2. Create a new library. I was using type of "Movie". Point it at a working physical path where content lives.
  3. Attempt to scan the library to no avail. Attempt to edit it and see:
Image

What is the current bug behavior?

The library is not visible in the dashboard and cannot be scanned or edited (managed). jellyfin.db shows an errant extra item in PhysicalLocationsList for the library.

What is the expected correct behavior?

The PhysicalLocationsList just has the physical location specified, and the library works.

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: Debian
- Linux Kernel: 6.1.0-40-amd64
- Virtualization: Docker
- Clients: NA
- Browser:NA
- FFmpeg Version: Default to container
- Playback Method: NA
- Hardware Acceleration: NA
- GPU Model:
- Plugins:
- Reverse Proxy:
- Base URL:
- Networking:
- Jellyfin Data Storage:
- Media Storage:
- External Integrations:

Jellyfin logs

There are no relevant logs (that I can see from `docker logs` about newly created libraries encountering this issue.

FFmpeg logs


Client / Browser logs

No response

Relevant screenshots or videos

No response

Additional information

No response

Originally created by @alexfornuto on GitHub (Oct 28, 2025). ### Description of the bug When creating a new library in 10.11.1 an extra item is injected into the `PhysicalLocationsList` of `/config/root/default/$libraryName`. Example: ``` ❯ sqlite3 jellyfin/config/data/jellyfin.db "SELECT data FROM BaseItems WHERE Path='/config/root/default/Concerts';" | python3 -m json.tool 2>/dev/null || sqlite3 jellyfin/config/data/jellyfin.db "SELECT data FROM BaseItems WHERE Path='/config/root/default/Concerts';" { "PhysicalLocationsList": [ "/config/root/default/Concerts", "/media/video/concerts" ], ... ``` The new library does not work until: 1. Jellyfin is stopped. 2. The extra location is removed, for example: ``` ❯ sqlite3 jellyfin/config/data/jellyfin.db <<EOF UPDATE BaseItems SET data = json_set(data, '$.PhysicalLocationsList', json('["\/media\/video\/concerts"]')) WHERE Path='/config/root/default/Concerts'; EOF ``` 3. Jellyfin is restarted. ### Reproduction steps 1. Be on 10.11.1 2. Create a new library. I was using type of "Movie". Point it at a working physical path where content lives. 3. Attempt to scan the library to no avail. Attempt to edit it and see: <img width="333" height="222" alt="Image" src="https://github.com/user-attachments/assets/bdeca5c5-5268-4fa8-abff-9aabbe4d62cb" /> ### What is the current _bug_ behavior? The library is not visible in the dashboard and cannot be scanned or edited (managed). `jellyfin.db` shows an errant extra item in `PhysicalLocationsList` for the library. ### What is the expected _correct_ behavior? The `PhysicalLocationsList` just has the physical location specified, and the library works. ### 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: Debian - Linux Kernel: 6.1.0-40-amd64 - Virtualization: Docker - Clients: NA - Browser:NA - FFmpeg Version: Default to container - Playback Method: NA - Hardware Acceleration: NA - GPU Model: - Plugins: - Reverse Proxy: - Base URL: - Networking: - Jellyfin Data Storage: - Media Storage: - External Integrations: ``` ### Jellyfin logs ```shell There are no relevant logs (that I can see from `docker logs` about newly created libraries encountering this issue. ``` ### FFmpeg logs ```shell ``` ### Client / Browser logs _No response_ ### Relevant screenshots or videos _No response_ ### Additional information _No response_
OVERLORD added the bug label 2026-02-07 05:13:51 +03:00
Author
Owner

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

I have the same issue. On Ubuntu 24.04.3 and Jellyfin 10.11.1

@peef2 commented on GitHub (Oct 28, 2025): I have the same issue. On Ubuntu 24.04.3 and Jellyfin 10.11.1
Author
Owner

@waazaa-fr commented on GitHub (Oct 31, 2025):

Same problems here too with docker container.

@waazaa-fr commented on GitHub (Oct 31, 2025): Same problems here too with docker container.
Author
Owner

@deepfriedbutter commented on GitHub (Nov 3, 2025):

same issue here. i think this might be related to some of the performance issues

@deepfriedbutter commented on GitHub (Nov 3, 2025): same issue here. i think this might be related to some of the performance issues
Author
Owner

@alexfornuto commented on GitHub (Nov 28, 2025):

This issue persists in 10.11.3.0, and also affects adding new paths to existing libraries. I plead for triage, as this issue is making things much harder as I transition to serving content from a new path.

@alexfornuto commented on GitHub (Nov 28, 2025): This issue persists in 10.11.3.0, and also affects adding new paths to existing libraries. I plead for triage, as this issue is making things much harder as I transition to serving content from a new path.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/jellyfin#7602