| 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: | 1694 |
| Popularity: | 26.45 |
| First Submitted: | 2017-12-18 19:14 (UTC) |
| Last Updated: | 2026-07-16 05:32 (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.
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.
@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:)
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.
Hmmm, thanks. Looks like my company is blocking this domain for some reason...
@cbrbr they work fine for me. Likely an outage with GitHub. They've had a lot of those lately.
I'm getting timeouts for the three *.in sources - is this a GitHub issue or is it just me?
I WILL BECOME BACK MY MONEY
@flavius this package is already updated by CI. It checks for updates every 6 hours, which I feel is more than enough.
If that's too slow for you, I agree with the suggestions to update it locally or automating it yourself.
That's a great idea but I'll likely work on automating the whole thing.
Pinned Comments
dcelasun commented on 2017-11-15 06:20 (UTC) (edited on 2026-06-04 12: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 licence difference and branding, there are some proprietary features not available in the open-source version.
This package depends on the official tarball. Please check this page before flagging as out-of-date. If the new version isn't on that page, this package cannot be updated! If you can see the new version there, but the AUR package is still not updated, flag it and give it time. It's usually done within hours.
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-gnomegnome-sessionwhich now includes mimemapps.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.