Bug 447391 - digiKam refuses to launch with a 'version `GLIBC_2.29' not found' error
Summary: digiKam refuses to launch with a 'version `GLIBC_2.29' not found' error
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Bundle-AppImage (show other bugs)
Version: 7.4.0
Platform: Debian stable Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-12-22 15:50 UTC by Stephen S.
Modified: 2021-12-28 15:51 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 7.5.0


Attachments
Debian LTS schedule (79.36 KB, image/png)
2021-12-22 16:11 UTC, Stephen S.
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Stephen S. 2021-12-22 15:50:49 UTC
STEPS TO REPRODUCE
1. I am switching from digiKam 7.3.0 to digiKam 7.4.0
2. I download the AppImage and launch it from the Terminal
3. The application does not open and throws multiple errors involving the absence of `GLIBC_2.29`
4. I tried to install it in my Debian stable but could not find how

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Debian 10
KDE Frameworks 5.54.0
Qt 5.11.3 (built against 5.11.3)
Comment 1 caulier.gilles 2021-12-22 16:03:40 UTC
This is normal, as 7.4.0 AppImage is now compiled with a more recent Linux version than previous 7.3.0, for security reasons and other technical issues. It's difficult to be compatible with older Linux versions due to this low level dependency to glibc. It's a main problem with AppImage. We cannot provide more than one bundle at the same time, one for older Linux, one for recent version.
Typically, the target AppImage binary depend of the glibc version from the Linux host used to compile all binaries.
Comment 2 Stephen S. 2021-12-22 16:08:41 UTC
I understand your point Gilles.
Could you consider creating a Flatpak instead, as, in my experience, Flatpaks are way more upgradable than AppImages?
Comment 3 Stephen S. 2021-12-22 16:11:05 UTC
Created attachment 144787 [details]
Debian LTS schedule
Comment 4 Stephen S. 2021-12-22 16:12:12 UTC
As you can see in the above schedule, far from being an "old version" Debian 10 Buster is in LTS till June 2024...
Comment 5 caulier.gilles 2021-12-22 16:16:54 UTC
Well digiKam flatpak bundle already exists and are up-to-date. There are 2 repositories as you can read from this page :

https://invent.kde.org/graphics/digikam/-/tree/master/project/bundles/flatpak

But, by experience flatpak is not perfect and the main problem is the heavy sand-boxing level of application which reduce the interoperability with the host system. We have receive plenty of reports and feedback about this topic. This is why AppImage exists.
Comment 6 caulier.gilles 2021-12-25 09:03:18 UTC
Git commit e106aa64e8e18f23fc87266ecd0888c9581768c9 by Gilles Caulier.
Committed on 25/12/2021 at 08:57.
Pushed by cgilles into branch 'dev'.

add more details about host OS compatibility, especially AppImage and glibc version which must be >= to 2.29.
Related: bug 447304, bug 447150

M  +1    -1    TODO.org
M  +4    -4    themes/hugo-theme-digikam/layouts/partials/downloads.html

https://invent.kde.org/websites/digikam-org/commit/e106aa64e8e18f23fc87266ecd0888c9581768c9
Comment 7 caulier.gilles 2021-12-25 14:45:43 UTC
So for all system with glibc < 2.29, you can use previous digiKam 7.3.0, or use the flatpak 7.4.0 bundle instead.

Gilles Caulier
Comment 8 Stephen S. 2021-12-28 14:45:54 UTC
The issue with the current flatpak is that the MySQL driver is not loading when opening digiKam with an external MySQL database.
Comment 9 caulier.gilles 2021-12-28 15:51:49 UTC
Hi, for all Flatpak report about Mysql, please comment this entry from github :

https://github.com/flathub/org.kde.digikam/issues/17

For Linux, digiKam team only maintain the AppImage bundle, not the Flatpak version published on Flathub.

Gilles Caulier