mirror of
https://github.com/qbittorrent/qBittorrent.git
synced 2026-03-02 22:57:32 -05:00
when extracting *qB!--> file, status is incorrectly "downloading" and then "stalled" #3108
Labels
No labels
Accessibility
AppImage
Bounty
Build system
CI
Can't reproduce
Code cleanup
Confirmed bug
Confirmed bug
Core
Crash
Data loss
Discussion
Docker
Documentation
Duplicate
Feature
Feature request
Feature request
Feature request
Filters
Flatpak
GUI
Has workaround
I2P
Invalid
Libtorrent
Look and feel
Meta
NSIS
Network
Not an issue
OS: *BSD
OS: Linux
OS: Windows
OS: macOS
PPA
Performance
Project management
Proxy/VPN
Qt bugs
Qt6 compat
RSS
Search engine
Security
Temp folder
Themes
Translations
Triggers
Waiting diagnosis
Waiting info
Waiting upstream
Waiting web implementation
Watched folders
WebAPI
WebUI
autoCloseOldIssue
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/qBittorrent#3108
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @WaterSibilantFalling on GitHub (Sep 19, 2015).
Version 3.3.0 (Beta)
on Debian 32bit, 4.1.0-2-rt-686-pae #1 SMP PREEMPT RT Debian 4.1.6-1 (2015-08-23) i686 GNU/Linux
As per the subject line, when a file is extracting, the GUI's status is "downloading" then switching to "stalled". If I do not independently discover that a file is, in fact, being extracted, this can be very confusing.
Currently I have a file extracting (4GB) and it's status is stalled and its "progress" is 0.0%, both the file as a whole and for each of its parts when looking at the "content" tab. Correctly, it's progress is 100% and its status is "extracting".
@ngosang commented on GitHub (Sep 17, 2018):
We are closing all issues related to old qBittorrent versions (qBittorrent < 4.1.0).
Please, update to last release and, if the bug/error/crash is still present, open another issue.
Thank you.
@WaterSibilantFalling commented on GitHub (Sep 17, 2018):
Well, version 4.1 is not available in the Debian distribution, testing, yet. Still 4.0.3. If 4.1 never makes it to Debian, then no more bugs. One way to remove 2000 open tickets at once.
And Debian defines itself by its stable distribution, which must be have a qbittorrent back in the 3.4 or something.