Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#52268 - [qbittorrent] Multiple issues with libtorrent-rasterbar
Attached to Project:
Community Packages
Opened by tuxayo (tuxayo) - Sunday, 25 December 2016, 21:54 GMT
Last edited by Antonio Rojas (arojas) - Sunday, 17 September 2017, 20:41 GMT
Opened by tuxayo (tuxayo) - Sunday, 25 December 2016, 21:54 GMT
Last edited by Antonio Rojas (arojas) - Sunday, 17 September 2017, 20:41 GMT
|
DetailsSee https://github.com/qbittorrent/qBittorrent/issues/6132 for a list of known issues.
What should be done? I see two options: - wait until upstream solves all these issues but that could be a long time with some annoying bugs and potentially a critical one (6131: Files corruptions) - create an official libtorrent-rasterbar 1.0.x package (based on an old version of libtorrent-rasterbar or using libtorrent-rasterbar-1_0-git as a base) and build qbittorrent against it. |
This task depends upon
Not really sure I see the value of this. qbittorrent and libtorrent-rasterbar are both stable releases, I think it makes more sense to file bugs if qbittorrent doesn't play nicely with libtorrent-rasterbar 1.1.x, and expect them to fix it.