Figure out how to revert to an older version of qBittorrent (i.e, 4.3.9) that uses libtorrent-rasterbar 1.x. This assumes the problem was newly introduced in the 2.x series. (I know there were plenty of issues with the initial release.) @wntr gives this suggestion above. However, this might not be sustainable for an Arch-based distro like Manjaro.
Use a torrent client that does not use libtorrent-rasterbar. (This might not be to your preference, since the performance, speed, and integration of such clients might not be to your liking. Personally, I prefer qBittorrent over all the other options out there.)
Review the libtorrent-rasterbar options used in qBittorrent 4.4.x. These are found under the “Advanced” tab. It could be a particular setting or value, or even a combination of settings that causes this issue. Once again, it could also be one of those rare cases where it’s a combination of your hardware/filesystem/network/libtorrent-rasterbar options.
File a bug report against qBittorent and/or libtorrent-rasterbar 2.x.
Cool, looks like qBittorrent rolled Libtorrent back to the old version for the newest 4.4.5 release. Will have to wait until it hits stable before I can test it.
They offer a Qt5 and Qt6 version for Windows, and now there’s also a libtorrent-rasterbar 1.x and libtorrent-rasterbar 2.x version.
Let’s hope the upstream projects smooth things over so that there isn’t the need for multiple flavors.
Sorry to rain on your parade, but the Arch package maintainer for qBittorrent is building version 4.4.5 to use libtorrent-rasterbar 2.0.7. (By default, since they follow the latest release of libtorrent-rasterbar from upstream.)
Not a huge fan of Flatpak myself, regardless. Couldn’t really say.
The two AUR options would make more sense.
However, perhaps you can re-visit this with qBittorrent 4.4.5 from the official repository once it hits Manjaro Stable. If the issue still persists, you can try the version from the AUR here: AUR (en) - qbittorrent-libtorrent-v1
Well, for sure, if a simple download of qBittorrent has an issue, there’s no point thinking another version will solve that issue.
qBittorrent had no issues in all the time I used it - not unless the partitions weren’t mounted right, or the folder permissions were messed up somehow. However, moving on to NEW versions is sometimes problematic as some trackers have whitelisted applications.
I’ve had issues with Sonarr, but never qb. Binary install certainly rules in this case far above Flatpak…
Having said that, it wouldn’t take more than five minutes to purge qb, install the flatpak, test it, purge that, reinstall qb.
Just to be clear, you’re saying when logged in as mhee, there’s an issue. Did you try creating a new user, logging in to that user TEST and do a trial run downloading on that plain new account?
@HallpMhee already tried a fresh user account. Same issues.
Only occurs with libtorrent-rasterbar clients (e.g, qBittorrent, Deluge), but no issues with other clients that do not use libtorrent-rasterbar (such as Transmission).
Using an older version of qBittorrent (4.3.9), or a version from the AUR that is built against an older version of libtorrent-rasterbar (1.x, instead of 2.0.7) might further narrow does down to specifically libtorrent-rasterbar 2.0.7.
It could just be an unfortunate combination in which it normally works fine for most people, but those with specific hardware/storage face issues with 2.0.7.
Users of qBittorrent made enough complaints that qBittorrent now ships by default with libtorrent-rasterbar 1.x, starting with qBittorrent 4.4.5, and offers versions of the program with libtorrent-rasterbar 2.0.7 as an alternative option.
So libtorrent-rasterbar 2.x was not embraced with flowers and candy. People were indeed facing issues with it.
I hope this helps others.
I have a very similar problem, only torrents with multiple levels of subdirectories error out immediately.
But if I change the download location, it works for a wee bit, then stops again.
I solved it by selecting the option “Don’t create subfolders”.
