My thoughts on Slackware, life and everything

Handbrake reaches 1.0.0 milestone after 13 years of development

handbrake_logoChristmas creates a different focus for the average IT guy, spending time with family instead of computers. It was nice. But it’s over and done now, even though the Christmas tree in the corner of our living room is still on fire (metaphorically speaking).

Tonight I have time to write about the latest Handbrake release. It took the developer team “only” 13 years to reach the stable milestone, 1.0.0. Congratulations are appropriate, because it is great software. But still there’s that nagging thought at the back of my mind… why the fuck is its GUI depending on a recent GTK+3 and therefore almost enforcing the use  of a Gnome-based distro? GTK has always been a moving target, theoretically separate from Gnome but in all honesty, the two are bonded with superglue. I can not compile Handbrake for Slackware 14.1 or older, and this GTK crap does not lend itself for static compilation inside the handbrake package. There now, I vomited a little. Why the fuck did they drop the Qt-based GUI? People can make bad decisions out of habit… this was definitely one.
I think we must be glad that we can compile the GUI for Handbrake 1.0.0 at all on Slackware 14.2.

By the way, compiling the command-line version of Handbrake is possible, even on Slackware 14.1 because that does not require GTK+3 as a dependency (although it depends on a lot of other X libraries on Slackware… i.e. the command-line program is unusable on a headless server without X.Org and friends installed).

Enjoy the new Handbrake!


Packages for Slackware 14.2 and -current can be obtained from my “restricted” repository. Handbrake employs some software libraries that are under patent dispute (the MP3 and AAC audio encoders) so I can not host the package on the Slackware server in the US. The regular repository does have a handbrake directory but that hosts only the scripts, sources and patches, not the Slackware packages.

Get them here:



  1. Didier Spaier

    The preview works well, including sound. Now ripping…

    Thanks a lot, Eric!

  2. Didier Spaier

    Addendum: only caveat, overheating here while ripping (97°C) It starts many threads at once, uses a lot of CPU.

    This is on quad core, so hardinfo reports four lines like this:
    Intel(R) Core(TM) i7-2640M CPU @ 2.80GHz 3137,00MHz


    Hi , im not sure if you patch this issues , but some patches related to encoding processes here.

  4. alienbob

    Arch Linux took those patches from the original repository, where they were added as commits to the master branch after the 1.0.0 release:


    2 of the patches are official patches

    and the other its from gentoo

    in the PKGBUILD , can see description and link.

  6. alienbob

    The gentoo patch is not relevant for my package.
    The other patches in the Arch handbrake package are not official patches, they are git commits that address a *potential* crash.

    If someone tells me he experiences that particular crash scenario while using my handbrake package, I will apply those two commits as patches to my package.

  7. steve

    Why did they drop Qt?
    It was a real bad decision.

  8. Didier Spaier

    @steve: this is debatable. Qt4 weighs 470M uncompressed in Slackware (and this doesn’t includes the docs and the demos), GTK+2 53M and GTK+3 67M, thus not all distributions ship Qt in their ISOs. Maybe this was considered in the decision?

  9. alienbob

    That is a bogus argument. Because not all distros ship Qt, let’s drop the Qt interface?
    Also, I highly doubt that the added bytes for a Qt GUI are 8 times the size of a GTK interface layer. Since when does size matter in this online world anyway?

  10. Didier Spaier

    Well, I stand corrected. About the size of Qt4, I see now that I had read it on /var/log/packages but I had rebuilt this package including all docs and the demos. The genuine 64-bit Slackware package weighs just 133420 K installed, according to PACKAGES.TXT Sorry for the noise.

  11. alienbob

    Didier, no problem. Arguments and discussion are what keeps us going.




    Fixed a potential crash when using the VP8 or VP9 video encoders
    Fixed a potential crash when using 2-pass ABR

  13. Tosh

    So if I read correct, only 2 patches that are being used are official, or all that’s needed, and the other 4 aren’t needed?

    Also I don’t understand why the empty ‘contrib’ directory?

    Thank you

  14. alienbob

    What’s your point Tosh? Your post contains exactly zero relevance.

  15. Tosh

    Sorry I thought what I was saying was clear.

    Actually including diff you have 7 patches and only 3 are being used, these are all I see being used;


    So the directory /gtk and /contrib I assume can be deleted?

    Also these are not being used and can be deleted?


    Thank you

  16. alienbob

    Tosh, if those files are bothering you, by all means delete them. They do not bother me.

  17. Tosh

    It’s my understanding these are just your own personal slackbuilds, not like official, or like

    Bothering me is not the concern, I was just trying to figure out if you were still working on this slackbuild, and maybe the reason I was seeing this, is it’s not completed is all…

    So I was only asking if it was ok to remove these and you were done with the slackbuild and they are not needed?

    thank you

  18. alienbob

    Whenever I upload a package and its sources/scripts, I am done working on them and the scripts that I publish will produce the package I uploaded.

    It is no different situation with the handbrake.SlackBuild. The script will use some, not all of the patches in the build/ directory. I don’t understand why you are so obsessed with the other, no longer used, patches which I kept for historical purposes in case someone needs to compile an older version of handbrake. Note that my repository does not just contain a handbrake 1.0.0 package but if you look inside the Slackware directories for 14.1 and older you will find handbrake-0.9.9 packages which require other patches than 1.0.0.

  19. Tosh

    I’m not obsessed or bothered, as I said, I was only trying to figure out why I was just seeing what I was seeing is all.

    Anyhow, you have made it clear now…


  20. alienbob

    I have uploaded a handbrake 1.0.1 package to the restricted repository. For proper form I also added two patches that I am not using in the SlackBuild.

    Hopefully the new package fixes the crashes people report on LQ when trying to access DVD media.

  21. Johannes

    Thanks Eric!
    Right on time (as I was thinking about installing Handbrake ;).

    However, the preview doesn’t work for me, it’s complaining about missing GStreamer h.264 and AAC decoders. I have a full Slackware64 14.2 install. I have the following GStreamer packages installed:

  22. alienbob

    I think perhaps you are still missing a gst-plugins-libav package (I believe that the SBo version is called “gst-libav” instead).

  23. tesloid

    The dependency of a command-line utility on X11 drives me nuts too. Have you noticed that the ‘sox’, ie, ‘play’ command now can’t be used without X, thanks to pulseaudio?

  24. Didier Spaier

    tesloid: I just tried “play ” on a console and it worked, I could hear a violin concerto from Vivaldi.

  25. Didier Spaier

    tesloid: furthermore, running ./configure –help in the source archive of pulseaudio-9.0 I saw this option:
    –disable-x11 Disable optional X11 support
    So there is no dependency on X of the server itself.

  26. angstrom

    “I can not compile Handbrake for Slackware 14.1 or older, and this GTK crap does not lend itself for static compilation inside the handbrake package.”

    I’m just wondering: given that Slackware 14.1 has gtk+3 (v3.8.2), is the specific problem that this version of gtk+3 is too old? Or is there a gnome-specific dependency somewhere? (From what you write, the problem would seem to be gtk+3.)

  27. alienbob

    angstrom – it is indeed the Slackware 14.1 version of gtk+3 and its supporting lower-level libraries like glib2, gdk-pixbuf etc that are too old.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

© 2024 Alien Pastures

Theme by Anders NorenUp ↑