Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: GLIBC version mismatch on Rocky/RHEL 9 (requires 2.35) #386

Open
3 tasks done
egg82 opened this issue Aug 24, 2024 · 2 comments
Open
3 tasks done

[Bug]: GLIBC version mismatch on Rocky/RHEL 9 (requires 2.35) #386

egg82 opened this issue Aug 24, 2024 · 2 comments
Assignees
Labels
System: Linux For Linux/BSD distributions Type: Bug Something isn't working as intended Type: Installation Installing, building, and/or launching the program

Comments

@egg82
Copy link

egg82 commented Aug 24, 2024

Checklist

  • I am using an up-to-date version.
  • I have read the documentation.
  • I have searched existing issues.

TagStudio Version

Alpha v9.3.2

Operating System & Version

Rocky Linux 9.4

Description

Portable binary fails with the following error:

Failed to load Python shared library '/tmp/_MEIe8CWw8/libpython3.12.so.1.0': dlopen: /lib64/libm.so.6: version `GLIBC_2.35' not found (required by /tmp/_MEIe8CWw8/libpython3.12.so.1.0)

Non-portable fails with a similar error:

Failed to load Python shared library '/home/X/.local/bin/_internal/libpython3.12.so.1.0': dlopen: /lib64/libm.so.6: version `GLIBC_2.35' not found (required by /home/X/.local/bin/_internal/libpython3.12.so.1.0)

If this is expected, the installation instructions should be updated to reflect that only specific GLIBC versions are supported.

The latest Rocky release comes with 2.34, but 2.35+ is required:

ldd --version 

ldd (GNU libc) 2.34
Copyright (C) 2021 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Written by Roland McGrath and Ulrich Drepper.

Expected Behavior

Program to launch

Steps to Reproduce

  1. Download + extract latest release on a system with an older GLIBC version
  2. Run

Logs

No response

@egg82 egg82 added the Type: Bug Something isn't working as intended label Aug 24, 2024
@CyanVoxel CyanVoxel added Type: Installation Installing, building, and/or launching the program System: Linux For Linux/BSD distributions labels Aug 24, 2024
@Leseratte10
Copy link

Leseratte10 commented Sep 9, 2024

Same issue happens on Ubuntu 20.04 which is still supported by Canonical and comes with glibc 2.31.

2.35 is the glibc version that comes with Ubuntu 22.04. Looking at the release.yml which is used to build the project, that seems to be using the ubuntu 22.04 image which would explain the issue.

Any software built for Linux is going to have some minimum Glibc version. Ideally, you'd build software for Linux on the oldest distribution you want to support. Unless there's a particular reason other than "it's the default" as to why TagStudio uses 22.04, I'd say the easiest way to fix that would be to build TagStudio on a machine with Ubuntu 20.04 or Debian 11 Bullseye.

I'll fork the repo and see if it builds on 20.04 as well. If it does, then changing that would most likely fix the issue on Rocky Linux as well.

EDIT: See #479

@roboticforest
Copy link

Greetings,

I'm getting this same error on both of my Linux Mint machines when trying to launch the portable version of TagStudio Alpha 9.4.2. Specifically:

[PYI-132790:ERROR] Failed to load Python shared library '/tmp/_MEIcETaw2/libpython3.12.so.1.0': dlopen: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by /tmp/_MEIcETaw2/libpython3.12.so.1.0)

I haven't yet tested the non-portable version.

My main laptop runs Linux Mint 20.3 (Ubuntu 20.3) and has GLIBC 2.31, and
the other runs Mint 20 (Ubuntu 20) and also has GLIBC 2.31.
On Windows 11 things are running fine.

I've never packaged a Python program before, only C++. I understand this error has something to do with how it's packaged, and maybe related to a container environment? I want to help fix this to make the portable version more portable, but I'm not sure yet what to do other than report the issue. I'm only just starting to learn this software.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
System: Linux For Linux/BSD distributions Type: Bug Something isn't working as intended Type: Installation Installing, building, and/or launching the program
Projects
None yet
Development

No branches or pull requests

5 participants