-
-
Notifications
You must be signed in to change notification settings - Fork 140
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] qt6-qtbase 6.6.2-r1 regression on Asustor NAS #301
Comments
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid. |
Here the qBittorrent internal logs
|
Does it work if you roll back the image? From our smoke tests, all seems to be ok: https://ci-tests.linuxserver.io/linuxserver/qbittorrent/latest/index.html Note, no one within the team has an asustor nas device plus we do not support/recommend portainer for our containers. |
Made some other tests.
It works fine until I restart the container, in that case the configuration is resetted again |
Ok, I can confirm it's some kind of regression. I've tried manually updating packages starting form 4.6.3 image. Workaround to use 4.6.4 without updating qt6-qtbase packages:
Restart the container et voilà, qBT updated and working fine |
Is there an existing issue for this?
Current Behavior
Following the 4.6.4 update, my qBT installation starts as if it were a clean one. It lost every settings and every torrents.
Restoring an old config folder backup and recreating the container with qbittorrent:4.6.3 image solves the issue
Expected Behavior
Like every past updates, I'd expect that all my settings will be ported to the new container
Steps To Reproduce
Environment
CPU architecture
arm64
Docker creation
Container logs
The TLS error are obviously caused by the lost of configuration path for the certificates
The text was updated successfully, but these errors were encountered: