[digiKam-users] digiKam 7.6 appimage do not start

[Gilles Caulier]

Hi all,

After verification, there is no option around libgio* as explicit
dependency while compiling Qt5.

On the other hand, with Qt6, there are new options for extra dependencies
to support GTK, as I can see. But, that's another story...

So, I don't know exactly where this dependency has been introduced. Perhaps
with new AVIF, HEIF, and JPEGXL codecs compiled with the last stable code.
This needs more investigation.

Note : I recompile from scratch the AppImage in my VM. It's not yet
complete. I will be back when all will be ready to test.
Best

Gilles Caulier


Le mar. 15 mars 2022 à 12:37, Gilles Caulier <caulier.gilles at gmail.com> a
écrit :

> Hi all,
>
> This weird dependency to libgio and other stuff with Qt5 have been
> introduced a few weeks ago with i switched appimage to QT5 LTS (aka
> currently Qt 5.15.3 ++). It's a complex puzzle that i need to review again.
> So please be patient...
>
> Best
>
> Gilles Caulier
>
> Le mar. 15 mars 2022 à 00:53, Andrew Goodbody <ajg02 at elfringham.co.uk> a
> écrit :
>
>> On 14/03/2022 17:47, Hans-Peter Huth wrote:
>> > You are right, my problem is different. After some recherche, i found
>> that
>> > the reason might be that the glibc on my system is too new and the
>> appimage
>> > does not include one. Search for "undefined symbol: g_module_open_full"
>> and
>> > you will find some entries.
>> >
>> > So i have to wait until the appimage also uses a recent glibc.
>>
>> But the undefined symbol is in libgio-2.0.so.0 which is in the package
>> libglib2.0-0, not glibc.
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20220318/a26987ab/attachment-0001.htm>