MKVToolNix fails to install on Ubuntu 20.04

Installation fails with the following errors:

The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 74AF00ADF2E32C85
Reading package lists... Done
W: GPG error: https://mkvtoolnix.download/ubuntu focal InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 74AF00ADF2E32C85
E: The repository 'https://mkvtoolnix.download/ubuntu focal InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

It’s a remote Ubuntu 20.04 server.

Thank you.
<3

I don’t offer current versions as packages for Ubuntu 20.04 anymore. I do offer older versions, and for those you have to install my GPG key. See the download page for instructions.

Thank you for clarifying. I see that Ubuntu 20.04 can get upto version 81.0. So, is there no way to get the latest versions of MKVToolNix installed on 20.04?
<3

You can try building it from source, though I don’t know if the minimum version requirements on libraries can still be met on Ubuntu 20.04.

Alright, I’ll give that a go. Will post the updates here to help out those running into similar situation. Thank you again.
<3

I followed the instructions at the link you provided: MKVToolNix Source Code – Matroska tools for Linux/Unix and Windows, to build from source. However, I ran into a snag during the process. When I executed the command $sudo dpkg-buildpackage -b --no-sign, I received the following error message:

dpkg-buildpackage: error: cannot read debian/control: No such file or directory

It seems the system couldn’t locate the debian/control file. Any thoughts on what might be causing this?

Ah. I forgot to update the instructions for a change a while ago that requires certain files to be created from template files. I’ve fixed the instructions. You have to run the following after copying the packaging/debian directory:

./debian/create_files.rb

BTW, I highly doubt you can still build current MKVToolNix on Ubuntu 20.04 as Ubuntu 20.04 doesn’t provide Qt6 if I’m not mistaken, and that’s required by MKVToolNix now. You should give the AppImage a try (though I cannot say whether that runs either; I’m simply not testing on Ubuntu 20.04 anymore).

Thank you for the updated instructions! I believe I’m making progress, but I’m still encountering an issue with Qt6. Specifically, I’m receiving the following error after executing dpkg-buildpackage -b --no-sign:

dpkg-buildpackage: info: source package mkvtoolnix dpkg-buildpackage: info: source version 91.0-0~bunkus01 dpkg-buildpackage: info: source distribution oracular dpkg-buildpackage: info: source changed by Moritz Bunkus <moritz@bunkus.org> dpkg-buildpackage: info: host architecture amd64 dpkg-source --before-build . dpkg-source: info: using options from mkvtoolnix-91.0/debian/source/options: --compression=xz dpkg-checkbuilddeps: error: Unmet build dependencies: qt6-multimedia-dev dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied; aborting dpkg-buildpackage: warning: (Use -d flag to override.)

The error message indicates that the qt6-multimedia-dev package is missing!

Also tried the AppImage, but it wouldn’t run, just as you expected :frowning:

Yeah, like I said, I wasn’t sure that you can still build it in 20.04 in the first place. If Qt6 is not available on 20.04, you cannot.

Wow real time with Bill Maher! As you said, you were correct. I did continue to be stubborn, though, lol. Basically, I’m using 20.04 because X2GO and XFCE work best on it. The newer ones are really glitchy. I might have to try ThinLinc and see if it works better. If it does, I should be able to use the latest Ubuntu and get the newest MKVToolNix on there.

Like I also said above, give the AppImage a try. It might still run as it’s built on AlmaLinux 8 & includes its own copy of most required libraries including Qt6. See the download page for instructions how to use it, including how to invoke the CLI utilities.

Right, about the AppImage, mb. I did try running it earlier, but unfortunately, it wouldn’t launch. However, I understand you’d like me to try again, so I’ll give it another go and post the results here shortly.

Are you on Discord? I promise not to bug you too much :sweat_smile:

No, I’m not on Discord.

Gotcha. I’ll keep this post updated with my findings.