All my ZorinPro 17 software is up to date, as far as I can see. However, I have an application that refuses to run because it cannot find GLIBC-2.38.
It is an astrophotography processing app....yes I know, I'll be contacting the developer in due course...but thought I'd ask here first.
The app has two versions; one suited to Ubuntu20.04 and the other to Ubuntu24.04 However, neither of them will run (I have ticked the executable box in the properties, to no avail, on both).
When I attempt to run the 24.04 version from the terminal, it says that it cannot find GLIBC-2.38. When I run the earlier version, it will only open by using the terminal command, and promptly crashes when I try to use it. It might have a crash log but I can't find it.
Is it possible that this app is just not suited to the Zorin distro?
Zorin OS 17 uses glibc 2.35, same as Ubuntu 22.04
This is a tricky one. The maintainer created a version that is generally compatible with Ubuntu 20.04. Also one that is generally compatible with 24.04.
None of the available versions explicitly state compatibility, however. None list their dependencies and... none are available as a debian format installer.
I suspect that the earlier version known to work on 20.04 lacks the python version present in 22.04.
An unimpressive workaround would be to run Windows OS or Ubuntu 24.04 in a VM - with SetiAstroSuite installed on that VM O.S.
It would take me some time to go through each version - find the one that is most compatible with 22.04 - then adapt it to work the rest of the way.
Zorin 17 is based on Ubuntu 22.04, so some things that require Ubuntu 24.04 may not work, and I know it's not using the newest glibc, as that's what prevents me from replacing the desktop environment with Plasma 6. When I looked into checking glibc versions, I found two main methods: running ldd --version, which reports 2.38 (the version you need), and simply typing out the location of the file (/lib/x86_64-linux-gnu/libc.so.6), which returns 2.35. I'm not sure how to account for the discrepancy.
Many maintainers just copy and paste a new depends file, without actually checking the needed dependencies, often the latest available instead of the ones that work the earliest. Which... is a Poor Practice and not one that I do...
I check them. I include the minimum dependencies required.
This does not apply to Plasma 6, sadly. It does genuinely require a higher glibc
But SetiAstro may not... I need to go through the files... and look.
Thanks for your input, both. So it might just work on a version of Zorin that we haven't yet reached in terms of glibc number...ok.
That does help me to understand where the app fits in. I'll follow up with the developer as best I can. Otherwise I will be forced to use (cough)Windows, if I want to run it regularly, I'm just trying to keep operations simple.
Side note: someone posted in "Share your Desktop ..." thread stated they installed Plasma 6 using jammy backports which I suspect is what KDE neon(user) uses.
Zorin OS 18 should be able to run the application.
KDE Neon uses own added KDE-Repo(s) for the Plasma Stuff. That doesn't come from Ubuntu.
Having used KDE Neon from 5.xx to 6.0 the updates stated Jammy repos and Debian bookworm, it is a hybrid OS like Linux Mint and Feren OS used to be.
Because I was interested to make a Frankenstein, I looked in the Past in the Repos of KDE Neon and there is the KDE Redo. Of Course there are Jammy Repos because it was in the Past based on Ubuntu Jammy - like here on Zorin OS. The Base is LTS and the Desktop is up-to-date - like on what You named Linux Mint.
But I read here the first Time about included Debian Bookworm. Maybe I should download KDE Neon again and take a Look at it.
It might have changed. I certainly won't touch it in the future due to the last time I installed a major update it became Ubuntu 24.04 with a fully blown Gnome DE. If trialling, use as a VM only.
I didn't want to ask this last night while the topic was unresolved, but now: why did I get two different values for two methods of finding the glibc version?
Yeah, I heard of this. They had Ubuntu 22 as Base and released an Update to upgrade the Base to Ubuntu 24. And that was not without Problems as far as I heard. But when You now download an ISO this will not happen because the Base is already updated. Okay, when Ubuntu 26 is out, this could come again if their new KDE OS or KDE Linux isn't finished.
The location /lib/x86_64-linux-gnu/libc.so.6 will show the system glibc version. However, the command ldd --version will show the ld linker ld.so
If you have installed as Flatpak package that included an ld.so of a higher version, that may show up using ldd --version
I have not tested this first hand as I have not flatpaks and I would need to know which flatpak package needed the dependency filled...
The world may never know. When I saw this reply, I checked my flatpaks and saw none I'd thought would be the culprit. I uninstalled three (OBS, ProtonPlus, and ProtonUp Qt), then checked ldd --version and it reported 2.35, same as the library. I reinstalled them, and it reported 2.35, same as the library.
When I read your first paragraph above, I thought perhaps my having updated GCC to 13.1.0 (Zorin comes with 11 something by default) could've been the cause, but that wouldn't explain having gotten 2.38 last night and 2.35 today, as I did that update when I switched to using Nvidia's .run installers over the the graphics-drivers PPA. So very confusing.