-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
crash at startup on ubuntu 20.04 snap version #1656
Comments
Thanks for reporting this, somebody on Discord reported the same error using the .deb package and Appimage on Debian. Not sure yet what's causing this. I'll try to change ffmpeg packaging in the next release to see if it changes anything. |
I am also having the same issue. Is it entirely related to GLIBC ??
|
I have the same issue on Ubuntu 24.04. I discovered nuclear and I wanted to try it, but it won't launch unfortunately. I'm using version
|
Are you able to find out what version of glibc you have installed? |
Thanks. Are all dependencies not supposed to be shipped in the snap package itself, so that the snap runs independently of the host system? On my host system, I have glibc 2.39. I tried to see how the snap package declares its dependencies, but I could not find the
|
That is definitely how it should be, and it's pretty weird that it's not, I just want to find out how it relates to your local setup. A snap should be fully separated from the rest of the system. |
Thanks. My system is a plain Ubuntu 24.04 setup. I've tried the 0.6.39 AppImage and .deb package. Both work and do not crash on startup. This would hint at a packaging issue with the snap package (outdated dependencies declared? old |
We use electron-builder which is supposed to handle snap building automatically, so there's no snapcraft.yml. Maybe it's a matter of updating some dependencies? |
Interesting, I wasn't aware of electron-builder. It would seem the nuclear snap uses the core20 base snap, which includes glibc 2.31, yet it also ships a newer version of chromium that requires glibc 2.32. Hence the mismatch. If this theory would be correct, that would hint at an upstream bug in electron-builder. The resolution of upstream issue #8548 could indirectly bring a fix when electron-builder starts using the core22 or core24 snaps, which ship higher versions of glibc. In the meantime, are there any settings in electron-builder to downgrade chromium to a version that uses glibc 2.31? |
Platform:
ubuntu 20.04 snap version
Nuclear version:
0.6.31
Description of the issue:
The application doesn't launch anymore, when I try to run in a shell I get the following "crashdump":
Is this because of a wrong libc version in the electron/chromium executable ?
Thanks a lot !
The text was updated successfully, but these errors were encountered: