Inko
17 March 2021 21:29
1
Suddenly after an update I get this spammed in the log, and cant open qbittorrent.
It’s been working fine for months.
Any advice how to fix this? I found this in another thread but it is related to another qbit torrent container and it seems to be advice for when you build the docker image yourself, which Im not expert enough to try.
opened 07:17PM - 16 Jan 19 UTC
closed 06:18PM - 17 Jan 19 UTC
Seems a few people are experiencing this, but there is a simple fix if you can include it in the image:
pacman...
pacman -S binutils
strip --remove-section=.note.ABI-tag /usr/lib64/libQt5Core.so.5
1 Like
As per the readme here: GitHub - linuxserver/docker-qbittorrent
If you are running a very old (3.x) kernel you may run into this issue which can be worked around using this method
opened 12:07AM - 14 Feb 21 UTC
closed 02:06PM - 03 May 21 UTC
------------------------------
## Expected Behavior
Start container, access … UI
## Current Behavior
UI never loads, error `/usr/bin/qbittorrent-nox: error while loading shared libraries: libQt5Core.so.5: cannot open shared object file: No such file or directory` appears repeatedly in log.
## Steps to Reproduce
1. Upgrade to `latest`/`version-14.3.3.99202101191832-7248-da0b276d5ubuntu20.04.1` image
2. Start container
3. Check log
## Environment
**OS:** GNU/Linux synology_avoton_1515+ 3.10.108
**CPU architecture:** x86_64
**How docker service was installed:** Synology docker package
## Workaround
Downgrade back to version-14.3.3.99202101191832-7248-da0b276d5ubuntu18.04.1
1 Like