Created empty artist folders do not have their permissions set #4361

New issue

Open

opened 2026-02-20 03:04:15 -05:00 by deekerman · 0 comments

deekerman commented

2026-02-20 03:04:15 -05:00

Owner

Originally created by @goldenkirbi on GitHub (Jan 28, 2026).

Is there an existing issue for this?

I have searched the existing open and closed issues

Current Behavior

When SetPermissionsLinux and CreateEmptyArtistFolders are enabled, Lidarr creates the artist folder but does not set the permissions based on the configured ChmodFolder and ChownGroup.

Expected Behavior

When SetPermissionsLinux and CreateEmptyArtistFolders are enabled, Lidarr creates the artist folder and sets the artist folder permissions based on the configured ChmodFolder and ChownGroup.

Sonarr sets the permissions on created series folders: https://github.com/Sonarr/Sonarr/blob/v5-develop/src/NzbDrone.Core/MediaFiles/DiskScanService.cs#L115

Steps To Reproduce

Enable the following settings in Settings - Media Management: Create empty Artist folders, Set Permissions and choose a chmod Folder setting that differs from what would be created by default. I used 775
Add a new artist, and scan.
Verify that the artist folder was created
Verify that the folder permissions have not been set correctly.

Environment

- OS: Talos Linux v1.10.7
- Lidarr: 3.1.2.4902@sha256:dab0e07502a34436fc50c3e789388f0a29f8cbf681fb7a02ed703ad7c368a22c
- Docker Install: No
- Using Reverse Proxy: Yes
- Database: Postgres 16

What branch are you running?

Develop

Trace Logs?

Trace logs for adding new artist Burial alongside screenshots of configuration and the created folder (wrong permissions)
Logs-01_28_2026, 08_00_18 PM.txt

Trace Logs have been provided as applicable. Reports may be closed if the required logs are not provided.

I have read and followed the steps in the wiki link above and provided the required trace logs - the logs contain trace - that are relevant and show this issue.

Originally created by @goldenkirbi on GitHub (Jan 28, 2026). ### Is there an existing issue for this? - [x] I have searched the existing open and closed issues ### Current Behavior When `SetPermissionsLinux` and `CreateEmptyArtistFolders` are enabled, Lidarr creates the artist folder but does not set the permissions based on the configured `ChmodFolder` and `ChownGroup`. ### Expected Behavior When `SetPermissionsLinux` and `CreateEmptyArtistFolders` are enabled, Lidarr creates the artist folder and sets the artist folder permissions based on the configured `ChmodFolder` and `ChownGroup`. Sonarr sets the permissions on created series folders: https://github.com/Sonarr/Sonarr/blob/v5-develop/src/NzbDrone.Core/MediaFiles/DiskScanService.cs#L115 ### Steps To Reproduce 1. Enable the following settings in `Settings - Media Management`: `Create empty Artist folders`, `Set Permissions` and choose a` chmod Folder` setting that differs from what would be created by default. I used `775 ` 2. Add a new artist, and scan. 3. Verify that the artist folder was created 4. Verify that the folder permissions have not been set correctly. ### Environment ```markdown - OS: Talos Linux v1.10.7 - Lidarr: 3.1.2.4902@sha256:dab0e07502a34436fc50c3e789388f0a29f8cbf681fb7a02ed703ad7c368a22c - Docker Install: No - Using Reverse Proxy: Yes - Database: Postgres 16 ``` ### What branch are you running? Develop ### Trace Logs? Trace logs for adding new artist Burial alongside screenshots of configuration and the created folder (wrong permissions) [Logs-01_28_2026, 08_00_18 PM.txt](https://github.com/user-attachments/files/24920434/Logs-01_28_2026.08_00_18.PM.txt) <img width="726" height="109" alt="Image" src="https://github.com/user-attachments/assets/222fe1ed-6789-468e-a17e-36c43fbc8396" /> <img width="692" height="511" alt="Image" src="https://github.com/user-attachments/assets/f2e143fe-bbc1-44f8-95ae-4d10449145b5" /> <img width="348" height="31" alt="Image" src="https://github.com/user-attachments/assets/e4eeb927-f2f4-4634-a6f5-26f3cbec46ad" /> ### Trace Logs have been provided as applicable. Reports may be closed if the required logs are not provided. - [x] I have read and followed the steps in the wiki link above and provided the required trace logs - the logs contain `trace` - that are relevant and show this issue.