Error message with no obvious effect

Does anyone know what exactly this module ‘knight’ is?
Starting dt from cli in X11 mode:
QT_QPA_PLATFORM=xcb /home/dan/programs/bin/darktable
0.5173 [view_load_module] failed to open `knight’: libjxl.so.0.8: cannot open shared object file: No such file or directory

dnf list libjxl*

Last metadata expiration check: 2:10:18 ago on Fri 05 Apr 2024 06:00:16 PM CEST.
Installed Packages
ibjxl.i686              1:0.10.2-3.fc41
libjxl.x86_64           1:0.10.2-3.fc41
libjxl-devel.x86_64     1:0.10.2-3.fc41
libjxl-devtools.x86_64  1:0.10.2-3.fc41
libjxl-utils.x86_64     1:0.10.2-3.fc41

Apparently, it's the wrong libjxl version. So I created a symlink but it didn't help
`ln -s /usr/lib64/libjxl.so.0.10 /usr/lib64/libjxl.so.0.8`

darktable git version a3140d3
Operating System: Fedora Linux 41
KDE Plasma Version: 6.0.3
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.9.0-0.rc2.23.fc41.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 32 × AMD Ryzen 9 3950X 16-Core Processor
Memory: 62.7 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2
Manufacturer: Micro-Star International Co., Ltd.
Product Name: MS-7C37
System Version: 1.0

You’ll need to rebuild darktable w/ the new libjxl version.

sure, that is the most obvious, but downgrading the library could cause some other issues. What is exactly the ‘knight’ module?

Could it be related to the built-in game, that has already been removed?

Added in 2.2.0, removed in 3.2.0 only recently.
There are some ‘knight’ strings in .po files, too.

I think that’s it. But those files have only been removed after version 4.6.1 came out (I still have them in my source download of 4.6.1). That doesn’t mean the game would still run, but it’s still present and possibly compiled into the last stable version.

But that begs the question “Why does it need libjxl?” (libjxl has to do with image formats…)

Anyway, I’m not sure “downgrading” a library by creating a symlink is a good way to handle the issue. We’re at version 0.x, so basically in development. No way to tell if there are any API changes that break compatibility.

It’s not :slight_smile:

it’s just a work around to see how it works