ELECTRON BAD Versions List

[theofficialgman]

keep your eyes on these upstream projects as they are known to use electron:

auto updating: tabby turbowarp whatsapp electron fiddle webcord armcord vscodium

apt repo: vscode

manual updating: github desktop edex-ui balenaetcher GDLauncher

gmans electron blacklist for issues that I deem critical to desktop linux (with special attention to armhf/arm64): electron 22-25 (might be backported to other stable versions, but will be fixed in electron 26) (wayland screen share broken) https://github.com/electron/electron/issues/36660 https://github.com/electron/electron/issues/37463 electron 22.0.0-22.1.0 (tray icons broken on DEs that don't support StatusIconLinuxDbus) https://github.com/electron/electron/issues/36602 electron 19.0.0-19.0.4 (too high glibc on arm64) electron 18.0.0-18.2.3 (too high glibc on arm64) electron < 13.5.0 (bad on bullseye/jammy and newer glibc)

[ryanfortner]

Another day, another Electron bug. :)

[Rak1ta]

3.2.0 installed on Buster and started install-success-Discord.log

[theofficialgman]

3.2.0 installed on Buster and started install-success-Discord.log

it shouldn't start unless you have a franken debian and have glibc 2.29+, which you should not have on buster (glibc 2.28) report the output from these:

ldd --version

and

echo '// Part of iq.OpenGenus.org
#include <stdio.h>
#include <stdlib.h>
#include <gnu/libc-version.h>

int main(int argc, char *argv[])
{
    // Print glibc version
    printf("GNU libc version: %s\n", gnu_get_libc_version());
    exit(EXIT_SUCCESS);
}
' > glibc.cpp
g++ -std=c++11 glibc.cpp -o glibc
./glibc

[theofficialgman]

also it is quite possible that only ARM64 libffmpeg by chance depended on libc 2.29, and that armhf libffmpeg did not. regardless... this is still an issue and upstream is building on focal which caused it

[theofficialgman]

also it is quite possible that only ARM64 libffmpeg by chance depended on libc 2.29, and that armhf libffmpeg did not. regardless... this is still an issue and upstream is building on focal which caused it

yes this is the case. due to compiler chance x86_64 and armhf only depend on libc 2.17+ while arm64 depends on libc 2.29+

[theofficialgman]

https://github.com/electron/electron/pull/34491

Progress ^

[theofficialgman]

merged into electron 19.x.y and 20.x.y (current beta branch), will be fixed in their next releases

[theofficialgman]

electron 19.0.5 is being built and will be available shortly https://github.com/electron/electron/commit/0764bb1560411d663f747427eca410e309b2b040

[theofficialgman]

Scratch that, 19.0.6 now because 19.0.5 timed out 😆

edit: they are on the struggle bus with this release... we will just have to wait and see what version it releases as

[Sussy-OS]

Any updates on this yet?

[theofficialgman]

nope not yet... both 19.0.6 and 19.0.5 timed out and the release numbers were reverted. this is probably pushed back to the end of this week. just watch (click the watch button) at electron to get notified when a new release is made https://github.com/electron/electron

[theofficialgman]

actually looks like they are trying again as of 12 minutes ago https://github.com/electron/electron/commit/c0588770eac69e56c457063d29a5e4077b9a188a

we will see if it finishes and a release is published. releases usually come out 3 hours or so after the build succeeds

[theofficialgman]

electron 19.0.5 has released a few hours ago https://github.com/electron/electron/releases/tag/v19.0.5

@smartfrigde @SpacingBat3 @cycool29 please rebuild your respective applications on electron 19.0.5+ as 19.0.0-19.0.4 are broken releases on arm64 linux buster/bionic (glibc 2.29+ was required)

I have said this before, but electron is pretty much never stable on release and almost always broken. please consider updating to the next version of electron at the END of a release cycle, and not at the beginning.

[theofficialgman]

closing as the affected projects have been bumped to 19.0.5

[smartfrigde]

ArmCord 3.1.2 has reverted back to Electron 21, if possible please update to it.