The current latest version (visual-studio-code-bin-1.92.0-1) seems to segfault immediately, too early to even log any crash data.
EDIT: A reinstall fixed it.
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: | 1509 |
Popularity: | 16.78 |
First Submitted: | 2017-12-18 19:14 (UTC) |
Last Updated: | 2025-04-17 07:24 (UTC) |
« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 12 .. 81 Next › Last »
The current latest version (visual-studio-code-bin-1.92.0-1) seems to segfault immediately, too early to even log any crash data.
EDIT: A reinstall fixed it.
Historical reasons, mostly. There is a long tradition of proprietary binaries ending up in /opt.
Is there a reason why vscode is installed to /opt? It's not that big, and I checked 5 pages of the comment history before getting bored.
pacman 6.0.2-9 started building debug packages by default and whatever AUR helper you are using seems to be installing these debug packages unconditionally. Add !debug
to the OPTIONS
array in /etc/makepkg.conf
to fix it.
I've exactly the same slack-desktop-debug conflict as ViToni!
For me this package conflicts with slack-desktop-debug
. As it also conflicts with zulip-desktop-bin
(mentioned below) I'd tend to agree the actual reason could be the common dependency as all three are electron
based apps (as was already mentioned).
Wondering if this is an issue of the package itself or how AUR packages are built in general.
visual-studio-code-bin-debug: /usr/lib/debug/.build-id/09/ff65463755b887e71c59f7b68228e92a84bd46 exists in filesystem (owned by slack-desktop-debug)
visual-studio-code-bin-debug: /usr/lib/debug/.build-id/09/ff65463755b887e71c59f7b68228e92a84bd46.debug exists in filesystem (owned by slack-desktop-debug)
visual-studio-code-bin-debug: /usr/lib/debug/.build-id/15/1f079fb274bc8b986bddea21c82a6b2ce21690 exists in filesystem (owned by slack-desktop-debug)
visual-studio-code-bin-debug: /usr/lib/debug/.build-id/15/1f079fb274bc8b986bddea21c82a6b2ce21690.debug exists in filesystem (owned by slack-desktop-debug)
visual-studio-code-bin-debug: /usr/lib/debug/.build-id/c7/dd943c9a2f9568fcd82fa7baddb1f22f38fb22 exists in filesystem (owned by slack-desktop-debug)
visual-studio-code-bin-debug: /usr/lib/debug/.build-id/c7/dd943c9a2f9568fcd82fa7baddb1f22f38fb22.debug exists in filesystem (owned by slack-desktop-debug)
visual-studio-code-bin-debug: /usr/lib/debug/.build-id/f3/a26db3f1c4644e02d50fa102282631595594df exists in filesystem (owned by slack-desktop-debug)
visual-studio-code-bin-debug: /usr/lib/debug/.build-id/f3/a26db3f1c4644e02d50fa102282631595594df.debug exists in filesystem (owned by slack-desktop-debug)
This makes me think it's related to the electron shipped with all those applications
Another conflict is with slack (slack-desktop-debug) with the same directories
It also conflicts with (at least) both teams-for-linux
and teams-for-linux-bin
, for the exact same directories.
This package somehow conflicts with zulip-desktop-bin
:
error: failed to commit transaction (conflicting files)
visual-studio-code-bin-debug: /usr/lib/debug/.build-id/09/ff65463755b887e71c59f7b68228e92a84bd46 exists in filesystem (owned by zulip-desktop-bin-debug)
visual-studio-code-bin-debug: /usr/lib/debug/.build-id/09/ff65463755b887e71c59f7b68228e92a84bd46.debug exists in filesystem (owned by zulip-desktop-bin-debug)
visual-studio-code-bin-debug: /usr/lib/debug/.build-id/15/1f079fb274bc8b986bddea21c82a6b2ce21690 exists in filesystem (owned by zulip-desktop-bin-debug)
visual-studio-code-bin-debug: /usr/lib/debug/.build-id/15/1f079fb274bc8b986bddea21c82a6b2ce21690.debug exists in filesystem (owned by zulip-desktop-bin-debug)
visual-studio-code-bin-debug: /usr/lib/debug/.build-id/c7/dd943c9a2f9568fcd82fa7baddb1f22f38fb22 exists in filesystem (owned by zulip-desktop-bin-debug)
visual-studio-code-bin-debug: /usr/lib/debug/.build-id/c7/dd943c9a2f9568fcd82fa7baddb1f22f38fb22.debug exists in filesystem (owned by zulip-desktop-bin-debug)
visual-studio-code-bin-debug: /usr/lib/debug/.build-id/f3/a26db3f1c4644e02d50fa102282631595594df exists in filesystem (owned by zulip-desktop-bin-debug)
visual-studio-code-bin-debug: /usr/lib/debug/.build-id/f3/a26db3f1c4644e02d50fa102282631595594df.debug exists in filesystem (owned by zulip-desktop-bin-debug)
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-open
uses 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.