starred/qBittorrent

Fork 0

mirror of https://github.com/qbittorrent/qBittorrent.git synced 2026-03-02 22:57:32 -05:00

Uploading is forced while downloading a file #9673

New issue

Closed

opened 2026-02-21 20:19:08 -05:00 by deekerman · 5 comments

deekerman commented

2026-02-21 20:19:08 -05:00

Owner

Originally created by @Shulbick on GitHub (Jan 22, 2020).

Please provide the following information

qBittorrent version and Operating System

qBittorrent v4.2.1 (64-bit)
Windows 10

If on linux, libtorrent-rasterbar and Qt version

Not on linux

What is the problem

No matter the options set by the user, uploading of torrents downloading in queue is forced. I used:

Options->BitTorrent->Torrent queueing->Maximum active uploads-> set it to zero

I also tried at the same this one:
Options->Connection Limits->Global maximum number of upload slots->set it to zero
But upon restarting the program it was immediately reverted again and again.

What is the expected behavior

To stop uploading any torrent at all

Steps to reproduce

1.- Have at least one torrent downloading
2.- Options->BitTorrent->Torrent queueing->Maximum active uploads-> set it to zero
3.- Uploading should still be happening

Extra info(if any)

This same bug (but with different steps to reproduce) was reported by me back in December. I tried the solution given to me by Sledgehammer999 and as it doesn't work I am reporting the bug again with the "solution" given as steps to reproduce

https://github.com/qbittorrent/qBittorrent/issues/11719

Originally created by @Shulbick on GitHub (Jan 22, 2020). **Please provide the following information** ### qBittorrent version and Operating System qBittorrent v4.2.1 (64-bit) Windows 10 ### If on linux, libtorrent-rasterbar and Qt version Not on linux ### What is the problem No matter the options set by the user, uploading of torrents downloading in queue is forced. I used: Options->BitTorrent->Torrent queueing->Maximum active uploads-> set it to zero I also tried at the same this one: Options->Connection Limits->Global maximum number of upload slots->set it to zero But upon restarting the program it was immediately reverted again and again. ### What is the expected behavior To stop uploading any torrent at all ### Steps to reproduce 1.- Have at least one torrent downloading 2.- Options->BitTorrent->Torrent queueing->Maximum active uploads-> set it to zero 3.- Uploading should still be happening ### Extra info(if any) This same bug (but with different steps to reproduce) was reported by me back in December. I tried the solution given to me by Sledgehammer999 and as it doesn't work I am reporting the bug again with the "solution" given as steps to reproduce https://github.com/qbittorrent/qBittorrent/issues/11719

deekerman

2026-02-21 20:19:08 -05:00

closed this issue
added the
Not an issue
label

deekerman commented

2026-02-21 20:19:12 -05:00

Author

Owner

@The5kull commented on GitHub (Jan 28, 2020):

So you are asking for a leech only version of qB if I understand you correctly?

@The5kull commented on GitHub (Jan 28, 2020): So you are asking for a leech only version of qB if I understand you correctly?

deekerman commented

2026-02-21 20:19:13 -05:00

Author

Owner

@Shulbick commented on GitHub (Jan 28, 2020):

Yup, optional leeching should be possible

Users should be able to opt out

@Shulbick commented on GitHub (Jan 28, 2020): Yup, optional leeching should be possible Users should be able to opt out

deekerman commented

2026-02-21 20:19:13 -05:00

Author

Owner

@xavier2k6 commented on GitHub (Feb 8, 2021):

So you are asking for a leech only version of qB if I understand you correctly?

Yup

This isn't supported & more than likely will not be implemented, however I will leave this issue open for now so that other dev's can have their say.......

@xavier2k6 commented on GitHub (Feb 8, 2021): >So you are asking for a leech only version of qB if I understand you correctly? >Yup This isn't supported & more than likely will not be implemented, however I will leave this issue open for now so that other dev's can have their say.......

deekerman commented

2026-02-21 20:19:13 -05:00

Author

Owner

@Shulbick commented on GitHub (Feb 9, 2021):

Even if the functionality is chosen not to be implemented, having the appearance of an option that would allow the user to do it, but which in fact, does not do what it says amounts to deceiving the user. The bug would still stand in the form of a fake and deceiving menu option

Not to mention that there are plenty of good reasons to do what is informally called "leeching". One of them is checking files for copyright infringements.

Currently, qBittorrent is absolutely useless to good-willed authors wanting to check whether their work is being pirated, because they can't avoid engaging in piracy themselves when they just want to download and check files for possible copyright infringements. qBitTorrent is effectively enforcing piracy (!) in these and other use cases

@Shulbick commented on GitHub (Feb 9, 2021): Even if the functionality is chosen not to be implemented, having the appearance of an option that would allow the user to do it, but which in fact, does not do what it says amounts to deceiving the user. The bug would still stand in the form of a fake and deceiving menu option Not to mention that there are plenty of good reasons to do what is informally called "leeching". One of them is checking files for copyright infringements. Currently, qBittorrent is absolutely useless to good-willed authors wanting to check whether their work is being pirated, because they can't avoid engaging in piracy themselves when they just want to download and check files for possible copyright infringements. **qBitTorrent is effectively enforcing piracy** (!) in these and other use cases

deekerman commented

2026-02-21 20:19:13 -05:00

Author

Owner

@FranciscoPombal commented on GitHub (Mar 1, 2021):

You misunderstand how the BitTorrent protocol works. In order to download, you must necessarily upload, at least the amount related to protocol overhead - this is true for any transfer protocol. In BitTorrent, you also trade pieces with other peers - the so-called tit-for-tat mechanism. So it is impossible to prevent an active download from uploading pieces at all, unless the whole swarm is made up of seeds. From qBittorrent's perspective, the settings that control "max active uploads" only concern seeding torrents, i.e., completed torrents that are only uploading.

Not to mention that there are plenty of good reasons to do what is informally called "leeching". One of them is checking files for copyright infringements.

Currently, qBittorrent is absolutely useless to good-willed authors wanting to check whether their work is being pirated, because they can't avoid engaging in piracy themselves when they just want to download and check files for possible copyright infringements. qBitTorrent is effectively enforcing piracy (!) in these and other use cases

lmao

@FranciscoPombal commented on GitHub (Mar 1, 2021): You misunderstand how the BitTorrent protocol works. In order to download, you must necessarily upload, at least the amount related to protocol overhead - this is true for any transfer protocol. In BitTorrent, you also trade pieces with other peers - the so-called tit-for-tat mechanism. So it is impossible to prevent an active download from uploading pieces at all, unless the whole swarm is made up of seeds. From qBittorrent's perspective, the settings that control "max active uploads" only concern seeding torrents, i.e., completed torrents that are _only_ uploading. > Not to mention that there are plenty of good reasons to do what is informally called "leeching". One of them is checking files for copyright infringements. > > Currently, qBittorrent is absolutely useless to good-willed authors wanting to check whether their work is being pirated, because they can't avoid engaging in piracy themselves when they just want to download and check files for possible copyright infringements. **qBitTorrent is effectively enforcing piracy** (!) in these and other use cases lmao