Package Details: visual-studio-code-bin 1.121.0-1

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: 1668
Popularity: 31.68
First Submitted: 2017-12-18 19:14 (UTC)
Last Updated: 2026-05-20 10:43 (UTC)

Required by (26)

Sources (7)

Pinned Comments

dcelasun commented on 2017-11-15 06:20 (UTC) (edited on 2026-01-23 13:07 (UTC) by dcelasun)

FREQUENTLY ASKED QUESTIONS (read before flagging or commenting!)

  • What is the difference between this package and the one in the community repo?

This is the official binary distribution from Microsoft. The one in the community repo is an unofficial build made from source. Beyond the licence difference and branding, there are some proprietary features not available in the open-source version.

  • There is a new version out, why is the package not updated?

This package depends on both the official tarball and files from GitHub. Please check this page AND this page before flagging as out-of-date. If the new version isn't on both pages, this package cannot be updated! If you can see the new version on both pages, but the AUR package is still not updated, flag it and give it time. It's usually done within hours.

  • I'm using an AUR helper (yay, yaourt etc.) and I can't install it. Why?

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.

  • When I install this package xdg-open uses vscode, not my file manager! How do I fix this?

Install shared-mime-info-gnome gnome-session which now includes mimemapps.

  • Why is $X a dependency? I don't like it.

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.

  • Something is broken with the app, where do I report it?

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.

  • I have a problem with this package, can I email you?

No, you won't get a reply. Please stop doing this. Leave a comment here instead and be patient.

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 .. 90 Next › Last »

MrAnno commented on 2026-04-14 20:00 (UTC)

Oh, this is probably it: https://bugs.archlinux.org/task/65655

MrAnno commented on 2026-04-14 19:59 (UTC)

@dcelasun Thanks for the quick answer. I guess this is for people who disable user namespaces. Not sure how common that is, since it would break pretty much all container and sandboxing tools.

dcelasun commented on 2026-04-14 19:34 (UTC)

Thanks for those links. There's been many comments over the years about having to manually set the setuid bit and I was just reminded of it today when looking at Discord's PKGBUILD in the Arch repos, so I added it.

If we're sure vscode's Electron version doesn't require it at all, I can remove it with the next update.

gtsiam commented on 2026-04-14 18:40 (UTC) (edited on 2026-04-14 18:42 (UTC) by gtsiam)

AFAICT the setuid sandbox is now just a fallback (reddit, chromium bug). Chrome now just uses unprivileged namespaces for sandboxing, which would work in arch kernels.

What issue is this fixing? Was there any indication that the sandbox was failing that led to this change?

Given that chromeos removed the setuid bit from chrome-sandbox in 2018 (chromeos bug), we should probably drop it as well.

dcelasun commented on 2026-04-14 17:58 (UTC)

@MrAnno it's an Electron requirement for the sandboxing to work correctly. Many official packages already do this, see Discord in the repos for example. I'm just late to the party:)

MrAnno commented on 2026-04-14 17:17 (UTC) (edited on 2026-04-14 17:22 (UTC) by MrAnno)

Hi,

Can you share some details on the latest commit setting setuid for one of the processes?

chmod u+s "${pkgdir}/opt/${_pkgname}/chrome-sandbox"

What changed that now requires setuid when it wasn't needed before? I'm asking because it looked a bit scary when this popped up in my paru package update diff.

cbrnr commented on 2026-04-10 07:57 (UTC)

Hmmm, thanks. Looks like my company is blocking this domain for some reason...

dcelasun commented on 2026-04-10 06:58 (UTC)

@cbrbr they work fine for me. Likely an outage with GitHub. They've had a lot of those lately.

cbrnr commented on 2026-04-10 06:43 (UTC)

I'm getting timeouts for the three *.in sources - is this a GitHub issue or is it just me?

banana777 commented on 2026-03-25 21:31 (UTC)

I WILL BECOME BACK MY MONEY

« First ‹ Previous 1 2 3 4 5 6 7 .. 90 Next › Last »