-
Notifications
You must be signed in to change notification settings - Fork 21
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
Acreom AppImage won't open with Glibc >=2.41 #28
Comments
I have the same issue
|
Hi, Probably related to Glibc update 2.41 : https://lists.gnu.org/archive/html/info-gnu/2025-01/msg00014.html
You can find many other apps handling this new behavior: Dedicated bug on arch: Reason for this change (TLDR: Security) : Upstream report (it is an expected behavior and nothing will be changed in Glibc): So Glibc has broken userspace and Arch is one the the first distribution having the issue, but others will follow as soon as they include glibc 2.41. Wanted to test Acreom, but it's seems it is not for today unfortunately. @psygreg Maybe change the title to "Acreom AppImage won't open with Glibc >=2.41" ? Thanks ! |
Here is the log obtained by running it from terminal:
A JavaScript error occurred in the main process
Uncaught Exception:
Error: /tmp/.org.chromium.Chromium.mSyf4l: não foi possÃvel habilitar pilhas de executável como requisitado pelo objeto compartilhado: Argumento inválido
at process.func [as dlopen] (node:electron/js2c/asar_bundle:2:2131)
at Object.<anonymous> (node:internal/modules/cjs/loader:1356:18)
at Object.func [as .node] (node:electron/js2c/asar_bundle:2:2358)
at Module.load (node:internal/modules/cjs/loader:1126:32)
at node:internal/modules/cjs/loader:967:12
at Function._load (node:electron/js2c/asar_bundle:2:13327)
at Module.require (node:internal/modules/cjs/loader:1150:19)
at require (node:internal/modules/cjs/helpers:110:18)
at Object.<anonymous> (/tmp/.mount_acreomcpgzfb/resources/app.asar/node_modules/koffi/index.js:537:16)
at Module._compile (node:internal/modules/cjs/loader:1271:14)
The text was updated successfully, but these errors were encountered: