Anonymous
excerpt from
OkularBuildDiscussion.txt
There is a peculiarity apparent in the Stretch-derivative implementation
of Okular, which is based on 16.08.2 and 16.08.3, revealed in the attached
file, OkularBuildPkgs.txt. The 2 kde-runtime modules are version 16.08.3, but
okular is version 16.08.2. It seems then that okular may not take advantage
of the latest kde-runtime features and corrections.Of the 4 distros tested, okular works fine anyway on 3 of them,
Debian Stretch, MX18.3, and Devuan 2.1 ascii.
Okular doesn’t run on AntiX-17.5.
The 16.08.3-2 version of kde-runtime (and kde-runtime-data) provided only a few only minor//unremarkable changes, none of which should be expected to “fix” your reported issue.
ref: metadata.ftp-master.debian.org/changelogs//main/k/kde-runtime/kde-runtime_16.08.3-2_changelog
To solve this puzzle, I expect you would need to take note of the exact version of each of the (many! and chained) dependant packages found on one of your other working ( MX18.3? ) installs… and compare the version of each against same found in your antiX 17.5 install (or, you may discover that one of the chained dependencies is somehow missing from your antiX 17.5 install).
^–v
Another possible approach would be to use this utility to “capture, and repackage” the files found on your working (MX 18.3?) install:
packages.debian.org/bullseye/dpkg-repack
A generic (non-debian) make .. make install approach will probably not lead to success.
You would need to “git clone” the exact//specific correct tagged fileset from the source repository, then “git clone” the debian-specific files hosted on salsa.debian.org and merge those files into the fileset of the upstream source tree… and then create the debfile by using a debian utility such as dpkg-buildpackage (xref: http://www.debian.org/doc/manuals/maint-guide/build.en.html)