mirror of
https://github.com/RandomNinjaAtk/arr-scripts.git
synced 2026-03-02 22:57:35 -05:00
[BUG] - Lidarr - TypeError: spawn() got an unexpected keyword argument 'dry_run' #221
Labels
No labels
Needs Triage
Not Reproducible
Upstream Issue
User Error
bug
documentation
enhancement
good first issue
help wanted
invalid
lidarr
lidarr
question
radarr
readarr
sabnzbd
sonarr
synology (host)
unraid (host)
waiting for logs
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/arr-scripts#221
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Poisonsting on GitHub (Feb 7, 2026).
Application
Lidarr
Host platform
Proxmox LXC running docker compose
Describe the bug
Setup fails to install the required python packages
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The script completes setup and begins to work as normal
Logs/Screenshots
Additional context
This install was working flawlessly for about a month before I tried updating the container. I can no longer get anything to work.
@N0cky commented on GitHub (Feb 10, 2026):
Same issue here (linuxserver/lidarr on Unraid).
Workaround: I replaced my /custom-cont-init.d/scripts_init.bash with the upstream setup.bash content and pinned Beets to an older version:
beets==2.5.1 (instead of beets)
With beets==2.6.1 the dependency chain pulls in numba -> llvmlite, and llvmlite fails to build/compile in this container, so the install aborts. Pinning to 2.5.1 avoids the llvmlite build and everything completes.
@Poisonsting commented on GitHub (Feb 10, 2026):
That's a good stop-gap, but I'm actually really looking forward to this level of documentation in the new repo...
@progecon commented on GitHub (Feb 12, 2026):
I got the same problem but using
beets==2.5.1did not solve it for me.@mkaltner commented on GitHub (Feb 12, 2026):
I pushed a fix for it that at least works on my machine! I know, classic developer response.
@progecon commented on GitHub (Feb 12, 2026):
I am still running into issues. I restarted the container, let it install everything, then restarted again:
@mkaltner commented on GitHub (Feb 12, 2026):
You can't create a backup file, it runs everything. Remove scripts_init.bash.bkp
For these errors: ^2026-02-13 00:19:24 :: QueueCleaner :: 2.1 :: is not ready, sleeping until valid response...
See my other PR linked above
@progecon commented on GitHub (Feb 12, 2026):
Thank you, I got it running now, and will take your other PR into account.
Just so you know, there seems to be one more thing with
LyricExtractor.bash:[[Error] LyricExtractor.bash: jq: parse error: Invalid numeric literal at line 1, column 6@mkaltner commented on GitHub (Feb 12, 2026):
I'm not a formal contributor, just fixing things that are keeping me from using the scripts. :)