Main menu:


Please consider a small donation:



Or you can donate bitcoin:


Thanks to TekLinks in Birmingham, AL, for providing colocation and bandwidth.

Page Rank


FOSS Force Best Blog--2013 Award

Recent posts

Recent comments

About this blog

I am Eric Hameleers, and this is where I think out loud.
More about me.


Subscribe to Blog via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 425 other subscribers

My Favourites



April 2019
« Mar    

RSS Alien's Slackware packages

RSS Alien's unofficial KDE Slackware packages

RSS Alien's multilib packages

RSS Slackware64-current



New package for qbittorrent, now based on Qt5

Not related per se to the fall-out of last weekend’s update to the icu4c and poppler packages, my qbittorrent package for slackware-current had stopped working sometime ago – caused by an update in -current of the boost package on which the torrent library depends.

I needed to update qbittorrent too therefore, after having taken care of the icu4c/poppler breakage. The thing is, I had tried to delay the switch in qbittorrent from Qt4 to Qt5 for as long as possible. The ‘new’ 4.x series of qbittorrent have a hard dependency on Qt5, and Qt4 is no longer supported. So I bit the bullet and made packages for bittorrent-4.0.4 and its dependency, libtorrent-rasterbar-1.1.6.
Since the program uses Qt5 now, the dependencies have changed. If you were running qbittorrent 3.x on slackware-current previously then you have to ensure that you have libxkbcommon, qt5 and qt5-webkit packages installed now.

For good times’ sake, I have kept the old SlackBuild scripts and sources but I renamed them to libtorrent-rasterbar10.SlackBuild and qbittorrent3.SlackBuild. If you want the old Qt4 based interface back, then compile the two packages using these SlackBuild scripts (first libtorrent-rasterbar, then qbittorrent). You can install either the new, or the old versions. They can not be co-installed.


Comment from Geremia
Posted: April 4, 2018 at 15:39

I’ve never used qbittorrent. How does it compare to Ktorrent? Any advantages?

Comment from alienbob
Posted: April 4, 2018 at 16:11

I love it. Ktorrent is OK of course, but I have been using qbittorrent for years. The best of all Linux based graphical torrent clients if you ask me.

Comment from matteo
Posted: April 4, 2018 at 18:55

Many thanks!!

Comment from dakd2
Posted: April 5, 2018 at 00:35

I think the advantage of qbittorrent is that it has python search engine plugins for the different torrent indexers

Pingback from Links 5/4/2018: Mesa 17.3.8 and WordPress Patches | Techrights
Posted: April 5, 2018 at 13:39

[…] [Slackware] New package for qbittorrent, now based on Qt5 […]

Comment from chrisretusn
Posted: April 5, 2018 at 15:26

Switched to 4.x series last November, libtorrent-rasterbar gave me a few headaches, until the 1.1.6 release. All is well now.

Comment from Geremia
Posted: May 7, 2018 at 22:45

I’ve now switched over to qBitTorrent and like it better than KTorrent. Ktorrent kept spawning several “” processes for some reason that were monopolizing my CPU. Someone told me those had to do with Akonadi, but I don’t think so.

Comment from KG Hammarlund
Posted: May 14, 2018 at 13:34

Another package that sadly doesn’t cope with the openssl upgrade.
First error was ‘qbittorrent: error while loading shared libraries: cannot open shared object file: No such file or directory’
After creating a symlink I get:
‘qbittorrent: symbol lookup error: /usr/lib64/ undefined symbol: SSL_library_init’

Comment from KG Hammarlund
Posted: May 14, 2018 at 16:49

…so it was actually libtorrent-rasterbar that broke. Package rebuilt using ponce’s buildscript and patches ( ) and qbittorrent is alive again!

Comment from KG Hammarlund
Posted: May 15, 2018 at 13:36

Thanks for the rebuilt libtorrent-rasterbar! And ffmpeg!

Write a comment