Qbittorrent: Bug. Version 4.1.6 is still available for download. Please take down.

It works fine on Linux.

Working fine on windows 10 as well. Dunno what @a-raccoon is going on about.

Dunno what @a-raccoon is going on about.

This:

https://github.com/qbittorrent/qBittorrent/issues/10581/
https://github.com/qbittorrent/qBittorrent/issues/10602/
https://github.com/qbittorrent/qBittorrent/issues/10604/
https://github.com/qbittorrent/qBittorrent/issues/10605/
https://github.com/qbittorrent/qBittorrent/issues/10630/
https://github.com/qbittorrent/qBittorrent/issues/10639/
https://github.com/qbittorrent/qBittorrent/issues/10642/
https://github.com/qbittorrent/qBittorrent/issues/10643/
https://github.com/qbittorrent/qBittorrent/issues/10647/
https://github.com/qbittorrent/qBittorrent/issues/10655/
https://github.com/qbittorrent/qBittorrent/issues/10657/
https://github.com/qbittorrent/qBittorrent/issues/10663/

I've already suggested that v4.1.5 should be restored as the default download, a week ago:
https://github.com/qbittorrent/qBittorrent/issues/10630#issuecomment-491952500

sledgehammer_999 is fully aware of the current issues, so leaving v4.1.6 up on the server doesn't make any sense at this point!:
https://qbforums.shiki.hu/index.php/topic,5916.msg31035.html#msg31035

@THEtomaso oh well, me nor any of my friends have experienced any problems with 4.1.6 .. I've even tried to replicate some of the issues you linked myself on both mine and one of my friends computers to see if I could get a single crash and still have yet to hit one. So maybe me and him are just one of the lucky few who has a good copy of 4.1.6 or something. ¯\_(ツ)_/¯

I also find this strange after so many people reporting issues.
On some private trackers there are people recommending going back to 4.1.5 because of "seeding issues" in 4.1.6.

Not sure if everyone has those issues but still, 4.1.6 shouldn't be the default version I believe.

Perhaps more intriguing is how versions seem to be repeatedly released to the general public as official, stable releases after (what appears to be, or otherwise might as well be regardless) virtually no testing beforehand, consistently leading to very unseemly results. Even if internal testing might be debatably impractical or whatever for whatever reasons, I don't think it'd be especially difficult to go through a cycle of christening every or most releases initially as beta or RC and releasing them as stable to the public only after a bug-ironing-out period (and only then auto-notifying every user that's only on the stable branch for updates about the new, now stable version). It's not exactly a unique idea, so all things considered the current and recent state of things is somewhat baffling.

Also, like I've pointed out on more than one occassion; I don't like the idea of including libtorrent SVN fixes in stable releases:
https://github.com/qbittorrent/qBittorrent/issues/9056#issuecomment-396670386
Basically, this turns a stable qBittorrent release into a beta (or perhaps even alpha) version.

Seems to be random; while one has problems the other don't, including myself. As a heavy user I didn't had any crashes or other weird things since release.

I do agree with THEtomaso about the SVN fixes though.

Anyone know how can i revert it back to the previous version without losing data?

Anyone know how can i revert it back to the previous version without losing data?

Simply install over, you don't lose the data. :)

Anyone know how can i revert it back to the previous version without losing data?

Simply install over, you don't lose the data. :)

Thanks for the answer.

I just did this and the installer couldn't write qbittorrent.exe and when i clicked abort installation button, it seemed to be stuck. I cancelled it, and the program was completely gone from that location lol. Actually it was gone before i cancelled it, cause the installer uninstalls it first, before installing the "new" one..

I tried to install it again in the same directory and it finished fine this time. My torrents and settings are still there, and v.4.1.5 works fine.

So before installing, it's a good idea to write down the location of qBittorrent.

qbittorrent.exe can take several minutes to close if you have a lot of activity / torrents loaded. You have to wait for the process to terminate or force close it (task manager / process explorer) before you can upgrade or downgrade in Windows. The install location isn't important to preserving your settings, since those are stored in your user directories separate and apart from the software.

Hey, How should I comeback to 4.1.5 in Ubuntu?

4.1.6 should be removed from default as well, as long as old fastresume exist, it would crash.

Having the same problem on Linux with v.4.1.6...
Well, shifting to another torrent client!

I also find this strange after so many people reporting issues.
On some private trackers there are people recommending going back to 4.1.5 because of "seeding issues" in 4.1.6.

Not sure if everyone has those issues but still, 4.1.6 shouldn't be the default version I believe.

i got this weird issue suddenly on 4.1.6

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

Pull it! With confirmed problems, makes no sense to leave it up! Seriously damaging the reputation of qBittorrent!

Pull it! With confirmed problems, makes no sense to leave it up! Seriously damaging the reputation of qBittorrent!

+1, i just reinstalled 4.1.5 as of now!

It's far too late already. 6 weeks in and qBittorrent's reputation has been damaged beyond repair. A permanent nuke has been issued and most trackers now forbid clients that identify as QB from connecting to them. This repository will be converted to archive-only. It was a nice run. :crying_cat_face:

@a-raccoon

It's far too late already. 6 weeks in and qBittorrent's reputation has been damaged beyond repair. A permanent nuke has been issued and most trackers now forbid clients that identify as QB from connecting to them. This repository will be converted to archive-only. It was a nice run. 😿

Stop spreading FUD. Nothing of the sort has happened.

How about instead of spewing bullshit you start contributing to the project? Or are you too busy spamming messages like these in other threads?

Making passive-agressive flame-baiting comments like these is not welcome. People are doing this out of their spare time, for the benefit of everyone.
If you can't contribute constructively to the project, then don't post here at all.

EDIT: to clarify, I am not denying that the v4.1.6 Windows release has issues. I just wanted to address the FUD comment.

This issue has no point anymore. The only person who can do that (the maintainer) is not available but when he comes back he'll surely release 4.1.7.

Wow. Great response. Not.
Yes, a-raccoon was over the top, but that doesn't change the fact that _great damage_ is being done to qBittorrent by leaving up the known bad release. I know of several people who have already given up and switched to other clients, and I've stopped recommending it. The messages you are sending are that qBittorrent isn't reliable and dependable, and for many (most?) people, it's not worth the grief.

So what BitTorrent client are people supposed to flee to?

uTorrent (and BitTorrent "regular") are overrun with ads.
Vuze is too, plus being Java app.
BiglyBT is Vuze's successor...but it still uses Java and it's very much stuck in alpha/beta mode atm.
Deluge... which also uses libtorrent like qBT does... has its own problems: https://dev.deluge-torrent.org/ticket/2149#comment:24
Lots of other BT clients have dropped support (Halite), are proprietary (BitComet), command-line only (rtorrent?), or only work on some OSes.

I guess Transmission is usable, if you don't mind very limited feature set and poor DL/UL performance.

So what BitTorrent client are people supposed to flee to?

There are good alternatives, but this is not the proper place to discuss that.

Works superb for me. Machines and setups used:

• Dedicated server with Server 2019 = 1/1gbps = Finland.
• Dedicated server with Ubuntu 18.04 + PPA = 1/1gbps = Finland.
• Virtual machine with Ubuntu 18.04 + PPA = 1/1gbps = UK.
• Desktop 1 using Windows 10 1903 = 1/1gbps = Central EU.
• Desktop 2 using Windows 10 1903 = 1/1gbps = Central EU.
• Desktop 3 using Windows 10 1903 = 1gbps/100mbps = France.
• Desktop 4 using Windows 10 1903 = 1gbps/100mbps = Netherlands.
• Laptop 1 using Windows 10 1903 (Haswell) = 1gbps + 5ghz wifi = Central EU.
• Laptop 2 using Windows 7 (Penryn) = 1gbps = 2.4ghz wifi = Central EU.

There are about ~10 more machines I cannot bother to list (relatives, friends, coworker PCs, etc)
They all push insane amounts of data up and down. Not part of any seed groups, just heavy use, corporate use. But, have not seen a single error in the current or previous releases at all. Last bug I saw was 4.1.5 when it couldn't close after I hit close on it but could be closed in Task Manager. Was not a big thing. Disappeared after 4.1.6 update.

Ps.: There is a mixed use of Server + Desktop Windows. The underlying is mix of NVMe SSD, SSD, USB, SWRAID, HWRAID. There are virtual, physical machines. The machine languages are English US, French, German. Mixed. I use SOCKS5, VPN, normal connection. Somewhere it's open, somewhere it's closed port setup. And nothing. Not. A. Crash.
Not saying it doesn't exist, I mean sure, I saw the tickets above. But there must be some very specific circumstance to crash it, since well, I have a set of 20+ machines, yet to see one crash. There must be something.

Some of these have had qBittorrent installed for 5-10+ versions, ie.: they've been upgraded. Some are fresh deployments.

Bully for you, but small comfort for many others for whom it does not work.

I know "works for me" is not especially helpful. But, it's a version that works better for me, than 4.1.5 did. (4.1.5 had this 'un-closable' problem at me.) So honestly, not sure which would be a better choice...

If I had to guess, the crashes are circumstantial to a user state. It crashes on me, and I have 431 torrents loaded, 80% of them complete and seeding. When QB crashes, it does a recheck on all the incompleted torrents. There were a lot of changes made to rechecking / moving functions. I'll bet my sweet ass the crash loop is a file access violation. Sometimes it crashes immediately, and sometimes it crashes 3 minutes later, and then it'll crash immediately ten times in a row.

@a-raccoon
Any chance you have a couple torrents that share filenames somewhere?

@Seeker2
I do not have any overlapping files. I use folders, and I'm careful to note that torrents have unique names. I have experienced this phenomenon years ago, and the behavior is basically an alternating between the two torrents; one going from 100% back down to 0%, when the other one reaches 100% (part files), or just back and forth interference as you might expect. A separate issue that I think should also be addressed, but not an issue affecting me.