Repository navigation
[BUG] v1.5.3-ls329 is broken #161
Description
Is there an existing issue for this?
- I have searched the existing issues
Current Behavior
When I update to v1.5.3-ls329 the WEB-UI never comes online but when I downgrade to v1.5.3-ls328 everything starts working again. I suspect this message is related:
/app/bazarr/bin/bazarr/../libs/python_anticaptcha/__init__.py:2: UserWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html. The pkg_resources package is slated for removal as early as 2025-11-30. Refrain from using this package or pin to Setuptools<81. from pkg_resources import get_distribution, DistributionNotFound
seeing how the release before it is fairly close to the mentioned date I'm guessing that pkg_resources does not work anymore in v1.5.3-ls329
I made sure to remove all the containers and the caching files and rebuilt all the containers from online. Once you change the tag to the previous version it instantly works again.
Expected Behavior
Bazarr starting child process with PID 164... /app/bazarr/bin/bazarr/../libs/python_anticaptcha/__init__.py:2: UserWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html. The pkg_resources package is slated for removal as early as 2025-11-30. Refrain from using this package or pin to Setuptools<81. from pkg_resources import get_distribution, DistributionNotFound 2025-12-30 11:42:55,940 - root (7b959675ab28) : INFO (scheduler:77) - Scheduler will use this timezone: Europe/Amsterdam Connection to localhost (127.0.0.1) 6767 port [tcp/*] succeeded! [ls.io-init] done. 2025-12-30 11:43:03,432 - root (7b959675ab28) : INFO (main:74) - Interactive jobs queue started and waiting for tasks 2025-12-30 11:43:03,437 - root (7b956fbcbb30) : INFO (signalr_client:122) - BAZARR trying to connect to Sonarr SignalR feed... 2025-12-30 11:43:03,443 - root (7b956f99ab30) : INFO (signalr_client:189) - BAZARR trying to connect to Radarr SignalR feed... 2025-12-30 11:43:03,444 - waitress (7b959675ab28) : INFO (wasyncore:485) - BAZARR is started and waiting for requests on: http://***.***.***.***:6767 2025-12-30 11:43:03,501 - root (7b956f769b30) : INFO (signalr_client:217) - BAZARR SignalR client for Radarr is connected and waiting for events. 2025-12-30 11:43:03,517 - root (7b956f99ab30) : INFO (signalr_client:150) - BAZARR SignalR client for Sonarr is connected and waiting for events. 2025-12-30 11:43:13,015 - root (7b956f0d6b30) : INFO (get_providers:204) - Using podnapisi again after 1 hour, (disabled because: TooManyRequests)
Steps To Reproduce
in docker compose change image: linuxserver/bazarr:v1.5.3-ls328 to image: linuxserver/bazarr:v1.5.3-ls329 and the container stops booting infinitely (days/hours) with only this:
`───────────────────────────────────────
Linuxserver.io version: v1.5.3-ls329
Build-date: 2025-12-23T21:32:13+00:00
───────────────────────────────────────
[custom-init] No custom files found, skipping...
Bazarr starting child process with PID 164...
/app/bazarr/bin/bazarr/../libs/python_anticaptcha/init.py:2: UserWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html. The pkg_resources package is slated for removal as early as 2025-11-30. Refrain from using this package or pin to Setuptools<81.
from pkg_resources import get_distribution, DistributionNotFound
`
Environment
- OS: Ubuntu Server 24.04 minimal
- How docker service was installed:
sudo install -m 0755 -d /etc/apt/keyrings
curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo gpg --dearmor -o /etc/apt/keyrings/docker.gpg
sudo chmod a+r /etc/apt/keyrings/docker.gpg
echo \
"deb [arch="$(dpkg --print-architecture)" signed-by=/etc/apt/keyrings/docker.gpg] https://download.docker.com/linux/ubuntu \
"$(. /etc/os-release && echo "$VERSION_CODENAME")" stable" | \
sudo tee /etc/apt/sources.list.d/docker.list > /dev/null
sudo apt-get update && sudo apt-get install docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-pluginCPU architecture
x86-64
Docker creation
services:
bazarr:
image: linuxserver/bazarr
container_name: bazarr
environment:
- PUID=$PUID
- PGID=$PGID
- TZ=$TZ
ports:
- 6767:6767
restart: unless-stoppedContainer logs
[migrations] started
[migrations] no migrations found
usermod: user abc is currently used by process 1
───────────────────────────────────────
██╗ ███████╗██╗ ██████╗
██║ ██╔════╝██║██╔═══██╗
██║ ███████╗██║██║ ██║
██║ ╚════██║██║██║ ██║
███████╗███████║██║╚██████╔╝
╚══════╝╚══════╝╚═╝ ╚═════╝
Brought to you by linuxserver.io
───────────────────────────────────────
To support the app dev(s) visit:
Bazarr: https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=XHHRWXT9YB7WE&source=url
To support LSIO projects visit:
https://www.linuxserver.io/donate/
───────────────────────────────────────
GID/UID
───────────────────────────────────────
User UID: 1000
User GID: 1000
───────────────────────────────────────
Linuxserver.io version: v1.5.3-ls329
Build-date: 2025-12-23T21:32:13+00:00
───────────────────────────────────────
[custom-init] No custom files found, skipping...
Bazarr starting child process with PID 164...
/app/bazarr/bin/bazarr/../libs/python_anticaptcha/__init__.py:2: UserWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html. The pkg_resources package is slated for removal as early as 2025-11-30. Refrain from using this package or pin to Setuptools<81.
from pkg_resources import get_distribution, DistributionNotFound
Activity
github-actions commentedon Dec 30, 2025
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.
AcevedoR commentedon Dec 30, 2025
Same issue here, thanks a lot for the issue, first time user here wondering if his conf was wrong 😆
j0nnymoe commentedon Dec 30, 2025
Unable to replicate here with existing install - also get the same error in log but works fine. Also our CI test passes: https://ci-tests.linuxserver.io/linuxserver/bazarr/latest/index.html
Please check the actual bazarr.log file in your
/config/logfolder to see if there are any errors there.AcevedoR commentedon Dec 30, 2025
There was no log file in /config/log for me (but when I downgraded to v1.5.3-ls328 I did have regular logs)
gauth-fr commentedon Dec 30, 2025
Same issue here.
Nothing in the log file either.
So, I tried to create a new blank instance, just to see if it's starting. But no. Nothing, no even a log file.
Going back to ls328 seems to fix the issue.
trumpet7347 commentedon Dec 30, 2025
I am seeing the same behavior as well, ls329 shows the same pkg_resources error in the logs, and the web-ui never comes up, but ls328 works as expected
j0nnymoe commentedon Dec 30, 2025
People are going to need more information about their setups in that case (host os etc). I've not been able to replicate nor has the bazaar dev when we have spoke to them.
RacerBas commentedon Dec 31, 2025
I've listed my OS and docker install method in the issue creation. Is there a debug flag which I can use to see more details? It doesn't seem to start far enough to generate a log file on 329
The port 6767 launch from the CI test never happens in production.
Will try clean install vm tomorrow
RacerBas commentedon Dec 31, 2025
Extra information:
Client: Docker Engine - Community
Version: 29.1.3
API version: 1.52
Go version: go1.25.5
Git commit: f52814d
Built: Fri Dec 12 14:49:32 2025
OS/Arch: linux/amd64
Context: default
Server: Docker Engine - Community
Engine:
Version: 29.1.3
API version: 1.52 (minimum version 1.44)
Go version: go1.25.5
Git commit: fbf3ed2
Built: Fri Dec 12 14:49:32 2025
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: v2.2.1
GitCommit: dea7da592f5d1d2b7755e3a161be07f43fad8f75
runc:
Version: 1.3.4
GitCommit: v1.3.4-0-gd6d73eb8
docker-init:
Version: 0.19.0
GitCommit: de40ad0
dcbell commentedon Jan 1, 2026
Same issue here. I dug in and manually ran the child process that listens on 6767 and got this:
Xitro01 commentedon Jan 1, 2026
I have the exact same issue after updating. First I thought it was config/breaking changes related. But after seeing this issue, apparantly I am not alone!
makhlouta commentedon Jan 2, 2026
I have the same issue, same error, web interface not reachable. Debian VM on Proxmox VE, all updated.
Falling back to ls328 fixed the issue. I still get the same error in the logs, but I can use the web interface.
Are there any specific logs I can provide?
EDIT: add some info
docker version
Host info:
Linux DockerVM 6.12.57+deb13-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.12.57-1 (2025-11-05) x86_64 GNU/Linuxdrizuid commentedon Jan 2, 2026
just to be thorough, after someone reported in discord, i tried to replicate an issue (they reported the issue on a clean new install, so this is a clean new install)
Logs: https://pastebin.com/mctu1VSa
cpu:
model name : Intel(R) Xeon(R) CPU E31220 @ 3.10GHzdocker vversion:
dist info:
kernel:
compose:
2 remaining items
makhlouta commentedon Jan 2, 2026
Something in that image is the issue, I have 20+ containers running on that VM, including other *arr, and all are working fine. Bazaar itself on ls328 is working fine. Proxmox VE is running on an Intel i9 11900, and the VM is running Debian 13.2.
VM CPU flags:
fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx lm constant_tsc nopl xtopology cpuid tsc_known_freq pni cx16 x2apic hypervisor lahf_lm cpuid_fault ptidrizuid commentedon Jan 2, 2026
yep, there it is, doesn't support sse3 or 4, but it's a 2021 cpu and it should... is this a vm and you failed to passthrough all the relevant instructions from your cpu to the guest?
to add some notes, there are a number of users reporting the same thing. our assumption is this is due to cpu instructions. sse3+ (maybe sse4_1 and _2) are needed. We can see from the above user they lack those instructions (though i am nearly positive that cpu supports it and they're using a vm with it passed incorrectly, as intel shows
Intel® SSE4.1, Intel® SSE4.2, Intel® AVX2, Intel® AVX-512support) other users may simply have CPUs so old they CANNOT support the instructions and their options are currently limited. they can use the older working version and use this as a reason to upgrade their homelab gear as this issue will continue to come up more and more often or they can fork, and compile numpy differently to support their system as discussed in numpy/numpy#30492 (comment)As it stands right now, this is not a container issue and we have no plans ourselves to work around outdated cpu instructions. we have engaged with the bazarr dev to determine if there is currently a pressing reason to move to numpy 2.4 and perhaps that will result in a change in the upstream code.
makhlouta commentedon Jan 2, 2026
I changed the CPU type for the VM to match the host and updated to the latest image, it is working now.
This warning is still there, seems irrelevant:
Interesting... what makes Bazaar's image very unique that it requires all the additional flags?
drizuid commentedon Jan 2, 2026
nothing to do with bazarr, numpy 2.4 was compiled to be more efficient which means excluding super old stuff and using new instructions, though to be clear, sse3+ is also super old. sse3 is from 2004 and sse4 is from 2006.
i should also note, this was nothing to do with the docker image, this was a requirement from bazarr itself to use an up to date version of numpy.
j0nnymoe commentedon Jan 2, 2026
It doesn't require all those tags, it's the numpy package that requires the newer SSE tags.
drizuid commentedon Jan 2, 2026
we have feedback from the upstream dev that will resolve the issue FOR NOW
morpheus65535: I'll pinn requirements.txt to lower than 2.4.0 ASAP.note that at some point, pinning to this older version will not be feasible and users with outdated hardware will be forced to upgrade. consider this your notice of this.
Xitro01 commentedon Jan 2, 2026
Upgrade to what? I am running a brand spanking new Nuc 15 Pro
j0nnymoe commentedon Jan 2, 2026
You've not provided any details about what you were running this on so we can't say for your specific setup.
Going to assume you're running proxmox with an incorrectly configured virtual machine?
Xitro01 commentedon Jan 2, 2026
Proxmox -> OpenMediaVault -> Portainer/Docker with Sonarr/Radarr/Bazarr.
j0nnymoe commentedon Jan 2, 2026
Review your proxmox VM config like other users have done above to make sure they have the correct CPU instruction set.
Xitro01 commentedon Jan 2, 2026
Will do, thanks! Edit: works again after just setting the cpu to “host”
RacerBas commentedon Jan 3, 2026
same here!
thespad commentedon Jan 5, 2026
This should be fixed in both latest and development tags as of about 6 hours ago as upstream has pinned to numpy 2.3.5 for the time being.