Launch error: GLIBCXX_3.4.29 not found

[IgnacioHeredia]

Description

Zettlr 3.1.0 fails to launch on my machine (Ubuntu 20.04; amd64; installed from .deb).

❯ zettlr
A JavaScript error occurred in the main process
Uncaught Exception:
Error: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /usr/lib/zettlr/resources/app.asar.unpacked/.webpack/main/native_modules/build/Release/Nodehun.node)
    at process.func [as dlopen] (node:electron/js2c/node_init:2:2214)
    at Module._extensions..node (node:internal/modules/cjs/loader:1489:18)
    at Object.func [as .node] (node:electron/js2c/node_init:2:2441)
    at Module.load (node:internal/modules/cjs/loader:1214:32)
    at Module._load (node:internal/modules/cjs/loader:1030:12)
    at c._load (node:electron/js2c/node_init:2:13672)
    at Module.require (node:internal/modules/cjs/loader:1242:19)
    at require (node:internal/modules/helpers:176:18)
    at 19572 (/usr/lib/zettlr/resources/app.asar/.webpack/main/index.js:2:1434793)
    at r (/usr/lib/zettlr/resources/app.asar/.webpack/main/index.js:2:3563974)
MESA-INTEL: warning: Performance support disabled, consider sysctl dev.i915.perf_stream_paranoid=0

Zettlr 3.0.5 launches fine though.

Reproducing

Download and try to open.

Zettlr Version

Stable (most recent version)

Specify version

3.1.0

Installation Method

From the Website or GitHub

Your Platform

• Windows
• macOS
• Linux

Architecture

• Intel 64bit
• ARM 64bit

Operating System Version

Ubuntu 20.04

Additional Information

No response

[nathanlesage]

Does the last beta I released work?

[IgnacioHeredia]

Hi @nathanlesage ,
none of the betas work. I tried all of them: beta.0, beta.1, beta.2, beta.3.

[dustdfg]

It looks like ubuntu 20.04 doesn't have the required version of the library. Stack Overflow said about ppa but ¯\_(ツ)_/¯

[AIBN60]

Same here :-( Memo to myself: I shouldn't update. Especially not when Zettlr is urgently needed

[IgnacioHeredia]

@AIBN60 Find your version in the Releases page

[AIBN60]

@AIBN60 Find your version in the Releases page

Thanks, Found it the very moment after I posted my comment. Sometimes it's worth to try something before posting a question ;-) Sorry

[nathanlesage]

… does this mean 3.1.1 fixed this issue, too?

[nasava]

For me the issue stayed unfortunately also with the 3.1.1 debian file and AppImage.

I am on Debian 11 (bullseye) amd64.

When installing node+yarn I can run the dev variant as a workaround. But then the configuration folder is another one, so my settings are not the same as before.

[AIBN60]

… does this mean 3.1.1 fixed this issue, too?

No, not at all. DEB and Appimage don't work.

When I said, I found out after my post, I meant that I found the link to download older versions. It was just a direct answer to IgnacioHeredia

[IgnacioHeredia]

I can also confirm that 3.1.1 didn't fix the error (Ubuntu 20.04, deb.).

[nathanlesage]

I did some digging, and something that appeared to pop up as a workaround to at least get it going was to start Zettlr with the command line flag --no-sandbox: https://www.electronjs.org/docs/latest/api/command-line-switches#--no-sandbox

This is definitely a potential security risk, so we shouldn't recommend this, but I would appreciate if someone could try out if that would solve this particular issue.

Since this appears to be mostly confined to Ubuntu (and I found some mentions of openSUSE) it might very well be just a missing library, which we might even be able to pass into the installer script during build so that Ubuntu platforms install that library.

[nasava]

For me the --no-sandbox did not have any effect, at least with the AppImage.

I think the problem was introduced with this commit: 9e2178a

It moved the CI build to ubuntu 22.04 which ships with a newer GLIBC, so the people having ubuntu 20.04 and other distros having older GLIBC versions will have this problem.

Is it possible to use an ubuntu 20.04 for the CI pipeline again? Or was it necessary to get to a newer node version?
For me node 20.12.2 runs on my older debian (bullseye) without a problem -- even starting Zettlr from source worked ;)

[nathanlesage]

I just accepted that PR because newer versions are always better but the 20.04 is still in LTS support frame so yes it should work. If that fixes this issue, I'm happy to accept a pr!

[IgnacioHeredia]

Hi @nathanlesage ,
I tested it and it seems to fix the issue. I opened a PR with the changes: #5170

If anyone else wants to test it, this a release I created to test the changes.