Renaming creates duplicate files #1234

Open
opened 2026-02-20 01:13:22 -05:00 by deekerman · 5 comments
Owner

Originally created by @tge101 on GitHub (Oct 28, 2020).

Describe the bug
When renaming files, duplicate files are created with the new naming convention and original files remain.

To Reproduce
Steps to reproduce the behavior:

  1. Go to any album
  2. Click on Preview Rename
  3. Accept choices and rename
  4. If folder changes names, i will have the old one with the old files, and a new one with the new naming convention containing the files with the new naming convention

Expected behavior
To only have the new files, named correctly.

Screenshots
If applicable, add screenshots to help explain your problem.
image

Logs
https://paste.ee/p/5ffbK#o0RBgItDSohoEuFzJ7nBJvtnBnBwrPzz

System info (please complete the following information):

  • Lidarr Version: 0.7.1.1381
  • Operating System OMV 5/Docker
  • .net Framework (Windows) or mono (macOS/Linux) Version: Mono Version 5.20.1.34

AB#287

Originally created by @tge101 on GitHub (Oct 28, 2020). **Describe the bug** When renaming files, duplicate files are created with the new naming convention and original files remain. **To Reproduce** Steps to reproduce the behavior: 1. Go to any album 2. Click on Preview Rename 3. Accept choices and rename 4. If folder changes names, i will have the old one with the old files, and a new one with the new naming convention containing the files with the new naming convention **Expected behavior** To only have the new files, named correctly. **Screenshots** If applicable, add screenshots to help explain your problem. ![image](https://user-images.githubusercontent.com/73597437/97446556-eb1c5c00-1904-11eb-8279-94ebc6e6e7df.png) **Logs** https://paste.ee/p/5ffbK#o0RBgItDSohoEuFzJ7nBJvtnBnBwrPzz **System info (please complete the following information):** - Lidarr Version: 0.7.1.1381 - Operating System OMV 5/Docker - .net Framework (Windows) or mono (macOS/Linux) Version: Mono Version 5.20.1.34 [AB#287](https://dev.azure.com/Servarr/7ab38f4e-5a57-4d70-84f4-94dd9bc5d6df/_workitems/edit/287)
Author
Owner

@bakerboy448 commented on GitHub (Jul 13, 2022):

still occuring in v1?

@bakerboy448 commented on GitHub (Jul 13, 2022): still occuring in v1?
Author
Owner

@grunwalski commented on GitHub (Jul 28, 2023):

Just installed Lidarr.

Version 1.2.6.3313

I had this problem. Old folder and files remain, duplicate with new name scheme is created.

@grunwalski commented on GitHub (Jul 28, 2023): Just installed Lidarr. > Version 1.2.6.3313 I had this problem. Old folder and files remain, duplicate with new name scheme is created.
Author
Owner

@jersam commented on GitHub (Aug 15, 2024):

Just installed Lidarr.

Version 1.2.6.3313

I had this problem. Old folder and files remain, duplicate with new name scheme is created.

So I did the rename and now I have a ton of dupes. Find a solution?

@jersam commented on GitHub (Aug 15, 2024): > Just installed Lidarr. > > > Version 1.2.6.3313 > > I had this problem. Old folder and files remain, duplicate with new name scheme is created. So I did the rename and now I have a ton of dupes. Find a solution?
Author
Owner

@github-actions[bot] commented on GitHub (Aug 15, 2024):

👋 @tge101, In order to help you further we'll need to see logs. You'll need to enable trace logging and replicate the problem that you encountered. Guidance on how to enable trace logging can be found in our troubleshooting guide.

@github-actions[bot] commented on GitHub (Aug 15, 2024): :wave: @tge101, In order to help you further we'll need to see logs. You'll need to enable trace logging and replicate the problem that you encountered. Guidance on how to enable trace logging can be found in our [troubleshooting guide](https://wiki.servarr.com/lidarr/troubleshooting#logging-and-log-files).
Author
Owner

@hideki2k02 commented on GitHub (Feb 14, 2025):

No solution so far? :(

@hideki2k02 commented on GitHub (Feb 14, 2025): No solution so far? :(
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/Lidarr#1234
No description provided.