Corel hasn’t been maintaining its Linux distribution packages of AfterShot Pro 3 too well. It gave me trouble installing the RPM from the AfterShot website on a recent version of Fedora Linux. Here’s how I got the software up and running on Fedora 32.
This article is divided into two parts: Part one is step-for-step instructions for how to install AfterShot Pro 3 on Fedora 32. The instructions might work for other recent versions as well. In the second part, I’ll explain in more detail about how I came up with the step-for-step instructions.
Installing AfterShot Pro 3
The first step is to install the RPM package from Corel’s website. It depends on some specific outdated library versions. We’ll install the RPM, but ignore its dependencies. The following command downloads, and installs the RPM without its dependencies:
The RPM installs into
/opt/AfterShot3\(64-bit\)/. The AfterShot binary is dynamically linked, but the installation includes dozens of outdated libraries that don’t play well with current versions of Fedora. We’ll move all those old libraries — except one proprietary library that is specific to AfterShot — out of the way first. The following commands does make these changes happen:
Now that the outdated libraries are out of the way, it’s time to fetch some newer versions from the Fedora library. The following command installs all the libraries AfterShot Pro 3 requires:
AfterShot 3 also bundles its own Qt configuration file that causes some problems. It’s not needed, so we’ll simply move it out of the way with the following command:
That’s it! You should be able to run AfterShot 3 now. Continue reading if you want to learn more about how I came up with these instructions.
How I found the required libraries
Out-of-repository RPM (and DEB) installation packages tend to quickly get outdated. Out-of-repository software vendors — whether they be proprietary or open source — can keep their packages current a bit longer by shipping statically linked binaries that contain all their dependencies. Corel has done something in between and created a mess in the process.
Luckily, it’s not impossible to work around issues like this. As long as the binary dynamically loads libraries from the system, we can get it to have it run newer versions. The first step in this instance was to look at the bundled libraries and install them through the system’s package manager.
However, the RPM also wanted to install additional dependencies onto the system. You can get a list of its dependencies by inspecting the RPM using the following command (the URL may change so over time so get the latest URL from the AfterShot website):
That still wasn’t enough to get AfterShot to run, though. It also had some additional undeclared and unbundled dependencies. I completed the list by inspecting the binary to see what libraries it needed to load:
At this point, I had almost all the dependencies. That’s the one library we copied back out of the backup directory and into the library directory. That specific library is AfterShot-specific.
Fixing the last problem
When I tried to start AfterShot, I ran into one last problem:
This is a common error for Qt applications. AfterShot bundles its own
qt.conf file that referenced a non-existent directory path. That directory path now resides inside the backup directory I’d created earlier. Rather than updating the reference, I just moved AfterShot’s configuration file aside. It didn’t do any good, anyway.