| Git Clone URL: | https://aur.archlinux.org/visual-studio-code-bin.git (read-only, click to copy) |
|---|---|
| Package Base: | visual-studio-code-bin |
| Description: | Visual Studio Code (vscode): Editor for building and debugging modern web and cloud applications (official binary version) |
| Upstream URL: | https://code.visualstudio.com/ |
| Licenses: | custom: commercial |
| Conflicts: | code |
| Provides: | code, vscode |
| Submitter: | dcelasun |
| Maintainer: | dcelasun |
| Last Packager: | dcelasun |
| Votes: | 1465 |
| Popularity: | 13.44 |
| First Submitted: | 2017-12-18 19:14 (UTC) |
| Last Updated: | 2024-11-15 11:08 (UTC) |
Safe fully-functional workaround for now:
libxml2 and icuusr/lib/* contents from archives somewhere (ie. ~/lib_overrides)LD_LIBRARY_PATH=~/lib_overrides codehttps://archive.archlinux.org/packages/l/libxml2/libxml2-2.9.8-2-x86_64.pkg.tar.xz
https://archive.archlinux.org/packages/i/icu/icu-61.1-1-x86_64.pkg.tar.xz
This works with the current workaround version of this package & requires no system-wide downgrades.
The issue for me seems to be that while glibc 2.27 is required for electron to not segfault right away, the most recent versions of libxml2 and icu require glibc 2.28 to work properly, which appear to be used for all file browser functionality.
While using the 2.27 workaround, these libraries cause a segfault whenever a file prompt is meant to be displayed.
I had originally tried downgrading all involved packages, and while that made VSCode work again, it however broke my KDE entirely, so I do not recommend it. In case the package maintainer wants to try a workaround (similar to what was done for glibc), these are the packages I downgraded:
Again, I do not recommend downgrading these globally as it will break your system.
Until this issue is fixed, you might want to try the experimental Electron 3 build.
Quick workarounds:
Use your file manager to navigate to the folder I need to open on, then drag and drop the folder on to vs code.
Use the command line to navigate to the directory I want to open, then run the command code .
I'm getting a similar issue. VSCode will crash when trying to bring up any kind of file browser window, ie via File > Open or File > Save. I'm using KDE Plasma if that makes any difference.
Not sure how relevant this is, but I see it while pushing Ctrl+S to bring up the save dialog, immediately before crashing:
[main 8:56:19 PM] windowsService#showSaveDialog 1
(code:2568): Gtk-WARNING **: 20:56:19.087: Could not load a pixbuf from icon theme.
This may indicate that pixbuf loaders or the mime database could not be found.
**
Gtk:ERROR:gtkiconhelper.c:494:ensure_surface_for_gicon: assertion failed (error == NULL): Failed to load /usr/share/icons/Numix/16/status/image-missing.svg: Unable to load image-loading module: /usr/lib/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-svg.so: /opt/visual-studio-code/glibc/usr/lib/libc.so.6: version `GLIBC_2.28' not found (required by /usr/lib/libxml2.so.2) (gdk-pixbuf-error-quark, 5)
Server response: <?xml version="1.0" encoding="UTF-8"
This makes the program pretty much unusable.
I noticed my VS Code was segfaulting when I tried to open it earlier today. I did another update and I got a patch. Then I came here and read about the glibc issue. Everything was fine after the patch.
Until now at least... Now it crashes when I click "Open Folder". I can't get it to run from the command line because it just opens a GUI window right away and control returns to the terminal, but it did say this... I wonder if this means anything:
[mattwelke@mdesklin browser-b2-upload-file-example]$ code --verbose [main 20:46:54] Sending env to running instance... [main 20:46:54] Sent env to running instance. Terminating... [main 20:46:54] Lifecycle#kill() [20468:0814/204654.559987:ERROR:browser_gpu_channel_host_factory.cc(103)] Failed to launch GPU process.
@edoantonioco, you also need to revert the workaround commit from this package if you want to use the system glibc.
But I still don't understand why it doesn't work for you with the bundled 2.27 glibc. Are you sure you are on 1.26.0-2 of this package?
So I went to one of the FTP servers from pacman mirrorlist and downloaded the required glibc-2.28-4, and then installed it locally.
Visual studio code still doesnt work.
@anohigisavay: glibc 2.28-1 is problematic, it breaks electron apps. That's why I have included 2.27 in the PKGBUILD. Either wait for 2.28-4 to hit [core] (which reverts the problematic bits) or use this package with an update system, which should work fine. See previous comments for details.
Pinned Comments
dcelasun commented on 2017-11-15 06:20 (UTC) (edited on 2020-02-06 21:33 (UTC) by dcelasun)
FREQUENTLY ASKED QUESTIONS (read before flagging or commenting!)
This is the official binary distribution from Microsoft. The one in the community repo is an unofficial build made from source. Beyond the license difference and branding, there are some proprietary features not available in the open source version.
Please check this page before flagging as out-of-date. If there is no new version on that page, it's not yet released. A tag on Github is NOT a release! If you can see the new version on the updates page but the AUR package is still not updated, flag it and give it time. It's usually done within a day or two.
Sometimes AUR helpers do weird things. Download the tarball and install it manually with
makepkg -si. If that works, report the problem to your AUR helper's upstream, not here.xdg-openuses vscode, not my file manager! How do I fix this?Install shared-mime-info-gnome. Also see this reddit thread.
Just because $X is not required to open the app, doesn't mean there is nothing that depends on it. Always search the comment history on AUR to see if that dependency has been previously discussed before writing your own comment. Still nothing? Then use namcap to make sure it's really not needed. If namcap doesn't complain, please leave a comment here and I'll investigate.
The problem might be a packaging issue (wrong paths, dependencies, icons), so please write a comment here first. If you don't get a reply, or if someone says it's an upstream issue, you can report it on Github.
No, you won't get a reply. Please stop doing this. Leave a comment here instead and be patient.