https://bugs.kde.org/show_bug.cgi?id=520803
[email protected] changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #1 from [email protected] --- digiKam Windows installer include the ImageMagick codecs only (we uses the C++ API for the image loaders). digiKam set the IM codecs path pointing to the internal place of the bundle : https://invent.kde.org/graphics/digikam/-/blob/master/core/app/utils/digikam_globals_bundles.cpp?ref_type=heads#L579 There is no ImageMagick CLI tools in digiKam bundle. So you need to use an external ImageMagick installation on your system (your case) and to disable the default path to the IM codecs used by digiKam. So the behavior and your solution is normal. Problem with your solution: all extra and exotic image formats supported by the internal ImageMagick cannot be loaded anymore in BQM. Best regards Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
