It turns out that for three days now it has been released to update 3.3.11, but from the repositories of Linuxmint the client has not yet been updated. I think maybe it's a bit early for this latest version in these repositories, but as I'm a little dubious I leave here this comment to know if anyone knows anything about this topic.

Please, someone who has not yet updated the client from the PPAs of some Linux system?

Regular people - such as the qBittorrent team - cannot upload new versions to the repository of Linux Mint, Debian or Ubuntu for example.Simply, add the Ubuntu PPA (for Linux Mint), and it will update and work like a charm.

The official site says: Linux Mint 17.2 features Cinnamon 2.6, MDM 2.0, a Linux kernel 3.16 and an Ubuntu 14.04 package base.

Regular people - such as the qBittorrent team - cannot upload new versions to the repository of Linux Mint, Debian or Ubuntu for example.Simply, add the Ubuntu PPA (for Linux Mint), and it will update and work like a charm.

The official site says: Linux Mint 17.2 features Cinnamon 2.6, MDM 2.0, a Linux kernel 3.16 and an Ubuntu 14.04 package base.

That is just very weird.Try simply a Terminal. (Don't be afraid, doesn't bite.)

Quote

sudo apt-get updatesudo apt-get dist-upgrade

It should upgrade.(Mint's Update Manager is a bit crazy, like it holds off kernel updates and whatnot like they are the work of the devil. )

Hello good day.

The truth is that it does not work with those commands either. I have tried to disable PPAs and update the cache and re-enable them, but it does not work either. I have changed the suppositories to some of England, and I have also updated the cache, and it does not work either.

The truth is that I do not know what can happen, because the last update 3.3.10 was updated through the PPA.

If you go into /etc/apt/sources.list.d/ folder, and open the qBittorrent PPA .list file, what's the content of it?A file browser should be able to open this file, you don't need root or anything (only to edit).

If you go into /etc/apt/sources.list.d/ folder, and open the qBittorrent PPA .list file, what's the content of it?A file browser should be able to open this file, you don't need root or anything (only to edit).

This is crazy.Why would the main PPA page show the latest 3.0.11 version YET, they failed?Even the repo (via web browser) shows only the 3.0.10 version.I made PPAs myself, yet I never had this happen - or I don't remember this happening.

I have a Xenial deploy only, which was a "lucky version" that got built.That's why I didn't even think the build failed.

Even though the latest log contains error, according to the Github ticket the PPA will need a new libtorrent (>1.1.0) before proceeding.When will that get uploaded... good question.The best answer I can give is "as soon as possible."

This is crazy.Why would the main PPA page show the latest 3.0.11 version YET, they failed?Even the repo (via web browser) shows only the 3.0.10 version.I made PPAs myself, yet I never had this happen - or I don't remember this happening.

I have a Xenial deploy only, which was a "lucky version" that got built.That's why I didn't even think the build failed.

Even though the latest log contains error, according to the Github ticket the PPA will need a new libtorrent (>1.1.0) before proceeding.When will that get uploaded... good question.The best answer I can give is "as soon as possible."

I am sorry for the confusion / "mislead".

There is no problem, on the contrary, thank you very much for investigating and helping me to leave doubts. When it's released, I'll come back to warn you (if I can remember)

I use LM 17.3 (and will until it is no longer supported, so 2 years ½ left on my most powerful desktop (AMDFX-8350 octocore 4ghz each, 24gb of 1866mhz of Corsair ram) and I can keep the thing running in my non-watered cool, but it does have a lot of large fans in the side case, back and one at the top pushing the air out.

I saw the update manager had a blue "!" after waking up from a nap, there it was, 3.3.12, and when I look at update history, it's from the important basic repos, 3.3.12-0ppa1~trusty1. So I guess from the ubuntu repos.

I use LM 17.3 (and will until it is no longer supported, so 2 years ½ left on my most powerful desktop (AMDFX-8350 octocore 4ghz each, 24gb of 1866mhz of Corsair ram) and I can keep the thing running in my non-watered cool, but it does have a lot of large fans in the side case, back and one at the top pushing the air out.

I saw the update manager had a blue "!" after waking up from a nap, there it was, 3.3.12, and when I look at update history, it's from the important basic repos, 3.3.12-0ppa1~trusty1. So I guess from the ubuntu repos.

Well yes, now the new update has arrived, and with it the problems in my torrent client after updating to the latest version.

It turns out that after updating the client, I have disappeared the name of two private trackers, of a total of three, and the only one that remains only recognizes 10 torrents plus the ones I am assigning, and this whole problem with a total of 1100 torrents.

The thing is that two trackers have disappeared, but all the torrents appear on the web pages (I think). Is there any solution for this, or do I have to wait for the next update, or should I go back to the latest version I had?

Could you please elaborate on the solution? I'm running Ubuntu Budgie 17.04 and I encountered a similar issue. I'm stuck at version 3.3.7 from the Ubuntu repositories, adding the qbittorrent-stable ppa only returns libtorrent packages when I run

cat /var/lib/apt/lists/ppa.launchpad.net_qbittorrent-team_qbittorrent-stable_*_Packages | grep "Package:" | sortedit:Found it, while the cause of the issue is not the same as in this topic, here is more info and a workaround: https://github.com/qbittorrent/qBittorrent/issues/6152