[Issue]: Changing backdrop order fails if backdrop on ro file system #5852

Open
opened 2025-12-22 02:59:01 +01:00 by backuprepo · 3 comments
Owner

Originally created by @Shadowghost on GitHub (May 24, 2024).

Please describe your bug

Changing backdrop order fails if backdrop on ro file system

Reproduction Steps

  1. Have a series folder with backdrops in it on a readonly file system
  2. Scan
  3. Add backdrop manually or by external metadata source
  4. try chaning backdrop order

Jellyfin Version

Master branch

if other:

No response

Environment

- OS: Linux
- Linux Kernel: -
- Virtualization: -
- Clients: -
- Browser: -
- FFmpeg Version: -
- Playback Method: -
- Hardware Acceleration: -
- GPU Model: -
- Plugins:
- Reverse Proxy:
- Base URL:
- Networking:
- Storage:

Jellyfin logs

Error processing request: "Read-only file system : '<read-only-path>/fanart.jpg'". URL "POST" "/Items/<id>/Images/Backdrop/1/Index".

FFmpeg logs

No response

Please attach any browser or client logs here

No response

Please attach any screenshots here

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct
Originally created by @Shadowghost on GitHub (May 24, 2024). ### Please describe your bug Changing backdrop order fails if backdrop on ro file system ### Reproduction Steps 1. Have a series folder with backdrops in it on a readonly file system 2. Scan 3. Add backdrop manually or by external metadata source 4. try chaning backdrop order ### Jellyfin Version Master branch ### if other: _No response_ ### Environment ```markdown - OS: Linux - Linux Kernel: - - Virtualization: - - Clients: - - Browser: - - FFmpeg Version: - - Playback Method: - - Hardware Acceleration: - - GPU Model: - - Plugins: - Reverse Proxy: - Base URL: - Networking: - Storage: ``` ### Jellyfin logs ```shell Error processing request: "Read-only file system : '<read-only-path>/fanart.jpg'". URL "POST" "/Items/<id>/Images/Backdrop/1/Index". ``` ### FFmpeg logs _No response_ ### Please attach any browser or client logs here _No response_ ### Please attach any screenshots here _No response_ ### Code of Conduct - [X] I agree to follow this project's Code of Conduct
backuprepo added the
bug
confirmed
labels 2025-12-22 02:59:01 +01:00
Author
Owner

@jellyfin-bot commented on GitHub (May 24, 2024):

Hi, it seems like your issue report has the following item(s) that need to be addressed:

  • You are not running an up-to-date version of Jellyfin. Please update to the latest release.
  • You have not filled in the environment completely.

This is an automated message, currently under testing. Please file an issue here if you encounter any problems.

@jellyfin-bot commented on GitHub (May 24, 2024): Hi, it seems like your issue report has the following item(s) that need to be addressed: - You are not running an up-to-date version of Jellyfin. Please update to the latest release. - You have not filled in the environment completely. This is an automated message, currently under testing. Please file an issue [here](https://github.com/jellyfin/jellyfin-triage-scripts/issues) if you encounter any problems.
Author
Owner

@jellyfin-bot commented on GitHub (Sep 22, 2024):

This issue has gone 120 days without an update and will be closed within 21 days if there is no new activity. To prevent this issue from being closed, please confirm the issue has not already been fixed by providing updated examples or logs.

If you have any questions you can use one of several ways to contact us.

@jellyfin-bot commented on GitHub (Sep 22, 2024): This issue has gone 120 days without an update and will be closed within 21 days if there is no new activity. To prevent this issue from being closed, please confirm the issue has not already been fixed by providing updated examples or logs. If you have any questions you can use one of several ways to [contact us](https://jellyfin.org/contact).
Author
Owner

@jellyfin-bot commented on GitHub (Oct 13, 2024):

This issue was closed due to inactivity.

@jellyfin-bot commented on GitHub (Oct 13, 2024): This issue was closed due to inactivity.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: starred/jellyfin#5852
No description provided.