Issues with VSCode on ArchLinux (Electron 2.0.x) #55934
Comments
|
UPDATE: with version visual-studio-code-insiders-1531459376 : |
|
@scippio I had a similar problem after an upgrade. In my case, the problem was with glibc. Reinstalling glibc 2.27-3 fixed the problem for me. |
|
@AndyHeasman Thanks! It's works! |
|
@scippio you're welcome! |
ghost
mentioned this issue
That's extraordinarily dangerous, glibc is backwards-compatible with programs built against older glibc, but not forwards-compatible with programs built against newer glibc. Any packages built after the glibc update stand a high chance of not running due to symbols too new for your ignored glibc package to provide. |
|
Apparently lots of software using the prebuilt electron distributions instead of the system electron provided by the Arch Linux official repos, are breaking. But the only common denominator is that they all use electron... so it would seem to be an electron issue. |
|
Can you clarify VS Code's version? ( |
Tyriar
added
info-needed
|
The issue is upstream Electron, just downloading the prebuilt .zip file and running |
|
Reported upstream as electron/electron#13972 |
|
The electron package from the Arch Linux community repository was actually built using glibc 2.27, nice try. ;) |
|
@eli-schwartz while I also see that entry, when I "lsof" electron shows "/usr/lib/libc-2.28.so (path dev=0,27)" |
|
I'm just going to rebuild Electron overnight and see what happens. If the Arch package works, I'll try a clean build with the default settings and no patches applied. |
Are you referring to the electron and riot-desktop package from the Arch repos? Because riot-desktop uses the system electron, which is already known to work... (This, coincidentally, goes to show why things should be built to use the system electron. :p) |
/usr/lib/libc.so.6 is a symlink to libc-${version}.so where ${version} is whatever version you have installed. It doesn't matter -- applications are only looking for the former and don't care how it is provided. |
|
Right: They both work (acknowledging riot uses system-electron) while vscode and skypeforlinux do not. Trying to think here... but if vscode/skype are using electron built around glibc 2.27 and crashes but the system electron .BUILDINFO is claiming to be built for 2.27 but is functioning with 2.28... something isn't meshing for me here. |
|
Looking at the symbols, the prebuilt binaries aren't built against glibc 2.27, they're built against 2.17. That's a pretty big version discrepancy, though it should still be compatible. |
|
For reference: |
|
For more reference: Electron Dockerfile, libchromiumcontent Dockerfile, points to Ubuntu 16.04, which uses glibc 2.23, but it could be no symbols are linked from that. |
|
Rebuilding Electron from source with Arch patches + glibc 2.28 works fine. Going to try a clean build now. |
|
So yeah, building using the default toolchain ( |
|
|
OK, turns out the build actually happens inside a Debian chroot that has glibc 2.19. I've also tried building Electron with the stock build setup and minimal patches using the system libraries, specifically applying these patches: This fails to dirty build, but I'm going to try a clean build overnight to see if that helps. |
|
@phil294 currently we recommend using the community package on AUR for Arch https://code.visualstudio.com/docs/setup/linux#_aur-package-for-arch-linux |
|
|
all problems described in #56342 seem to be fixed in 1.26.1 |
|
I'm with the same problem. Any fix?
|
|
Tried downloading Atom instead when this problem happened on me, but same problem happened when starting Atom. |
|
Can people seeing this issue please try out this build that uses Electron 2.0.9: Download |
|
@bpasero I can confirm that the Electron 2.0.9 based build you've linked resolves this issue for me. This is on On the same environment, the current deb package of code-insiders from |
|
Thanks, closing. We will ship this update for our September release. |
bpasero
added
bug
|
Verifier: start VSCode on an ArchLinux distribution. |
|
I am able to start an insider build using an up to date Arch Linux. Downloaded the insider tar.gz and extracted then ran Version: 1.28.0-insider |
|
Adding verified label since @kbrosnan verified |
and others
VSCode Version:
visual-studio-code-insiders-1533551722-1
visual-studio-code-insiders-1532668879
visual-studio-code-insiders-1531459376 - this version not SIGSEGV but just blink and turn off.
OS Version:
Linux lenovo-e450 4.17.12-arch1-1-ARCH Open Source VS Code #1 SMP PREEMPT Fri Aug 3 07:16:41 UTC 2018 x86_64 GNU/Linux
Steps to Reproduce:
I known this is primary a problem with nodejs - or something like that ... but I don't known what exactly it is... other Electron programs works fine. I test it with nodejs 10.8.0 and try downgrade to 10.7.0 and 10.6.0... but nothing helps...
EDIT:
And this is my packages update log (nothing extra like nodejs or other depends packages... 🤔 just new kernel etc... ):
The text was updated successfully, but these errors were encountered: