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

Git Clone URL: (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:
Licenses: custom: commercial
Conflicts: code
Provides: code, vscode
Submitter: dcelasun
Maintainer: dcelasun
Last Packager: dcelasun
Votes: 1255
Popularity: 23.00
First Submitted: 2017-12-18 19:14 (UTC)
Last Updated: 2022-10-06 18:20 (UTC)

Required by (17)

Sources (8)

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!)

  • 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 license 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?

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.

  • 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. Also see this reddit thread.

  • 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

1 2 3 4 5 6 .. 65 Next › Last »

Piroro-hs commented on 2022-09-22 15:33 (UTC) (edited on 2022-09-22 15:36 (UTC) by Piroro-hs)

@dcelasun @ZZYSonny It could be fixed by renaming .desktop files to code.desktop and code-url-handler.desktop like upstream (, instead.

HercyNians commented on 2022-09-08 07:02 (UTC)

why i could't debug?

dcelasun commented on 2022-09-07 22:18 (UTC)

@ZZYSonny that's an Electron bug that's been fixed upstream. It should make its way into vscode soon. Can someone on X using a dock test that workaround? If it doesn't break things for X, I can include it here.

ZZYSonny commented on 2022-09-07 21:58 (UTC)

Could you please consider applying this workaround to make VSCode show its own icon instead of the generic wayland icon with "ozone-platform=wayland"?

dcelasun commented on 2022-09-06 16:41 (UTC)

@Piroro-hs thanks, should be fixed now.

Piroro-hs commented on 2022-09-06 16:32 (UTC)

@dcelasun It doesn't start without alsa-lib. error while loading shared libraries: cannot open shared object file: No such file or directory

dcelasun commented on 2022-09-06 15:19 (UTC)

@Piroro-hs which feature exactly depends on alsa-lib? Ignore the namcap output, that just shows everything that could theoretically be used by Electron.

Piroro-hs commented on 2022-09-06 15:10 (UTC)

alsa-lib ( should be added to depends list.

dcelasun commented on 2022-09-01 22:25 (UTC)

@phillipk alright then, I pushed the change.

phillipk commented on 2022-09-01 22:17 (UTC) (edited on 2022-09-01 22:18 (UTC) by phillipk)

I now had the time to test a little: All paths passed to /usr/bin/code have no effect as soon as .config/code-flags.conf contains at least one flag. E.g., invoking code /some/file.txt will just restore the last session or open a new window and not open /some/file.txt anywhere. As soon as .config/code-flags.conf is empty or does not exist, it will work again. The workaround I am currently applying after each update is to modify the last line of /usr/bin/code to have the arguments passed ("$@") before the configured flags $CODE_USER_FLAGS. Then it also works with flags present in .config/code-flags.conf.