AUR (en) - visual-studio-code-bin

Search Criteria

Enter search criteria

Search by

Keywords

Out of Date

Sort by

Sort order

Per page

Package Details: visual-studio-code-bin 1.89.1-2

Package Actions

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:	1420
Popularity:	19.07
First Submitted:	2017-12-18 19:14 (UTC)
Last Updated:	2024-05-12 05:01 (UTC)

Dependencies (17)

alsa-lib
gcc-libs (gccrs-libs-git^AUR, gcc11-libs^AUR, gcc-libs-git^AUR, gcc-libs-snapshot^AUR)
glibc (glibc-git^AUR, glibc-linux4^AUR, glibc-eac^AUR)
gnupg (gnupg-git^AUR, gnupg-largekeys^AUR)
gtk3 (gtk3-no_deadkeys_underline^AUR, gtk3-classic-xfce^AUR, gtk3-patched-filechooser-icon-view^AUR, gtk3-classic^AUR)
libnotify (libnotify-git^AUR)
libsecret
libxkbfile
libxss
lsof (lsof-git^AUR)
nss (nss-hg^AUR)
shared-mime-info
xdg-utils (busking-git^AUR, xdg-utils-slock^AUR, mimi^AUR, mimi-git^AUR, xdg-utils-handlr^AUR, opener^AUR, xdg-utils-betterlockscreen^AUR, xdg-utils-mimeo^AUR, mimejs-git^AUR)
glib2 (glib2-git^AUR, glib2-selinux^AUR, glib2-patched-thumbnailer^AUR) (optional) – Needed for move to trash functionality
icu69^AUR (icu69-bin^AUR) (optional) – Needed for live share
libdbusmenu-glib (optional) – Needed for KDE global menu
org.freedesktop.secrets (keepassxc-git^AUR, gnome-keyring-git^AUR, bitw-git^AUR, pass-secrets-git^AUR, keepassxc-allow-aur-extension-origin^AUR, keepassxc-allow-aur-extension-origin-bin^AUR, gnome-keyring, keepassxc, kwallet, kwallet5) (optional) – Needed for settings sync

Required by (17)

azure-sphere-sdk (requires code) (optional)
code-appicons (requires code)
code-features (requires code)
code-features-insiders (requires code)
code-icons (requires code)
code-marketplace (requires code)
code-nautilus-git (requires code) (optional)
dokytree (requires code) (optional)
dokytree-git (requires code) (optional)
meta-package-manager (requires code) (optional)
nautilus-code (requires code) (optional)
neopo-git (optional)
nwscript-code (requires code)
rust-analyzer-vscode-git (requires code)
stm32pio (requires code) (optional)
unity-editor-lts (optional)
unreal-engine-bin (requires code) (optional)

Sources (7)

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

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

elduderino commented on 2024-02-10 19:00 (UTC) (edited on 2024-02-10 19:04 (UTC) by elduderino)

@bigbrozer that's because in latest pacman update they decided to enable debug option by default inside /etc/makepkg.conf

bigbrozer commented on 2024-02-10 17:03 (UTC)

Similar to @Paeonia. Note that it also try to install a new package visual-studio-code-bin-debug aside of this one.

Paeonia commented on 2024-02-09 14:50 (UTC) (edited on 2024-02-09 14:53 (UTC) by Paeonia)

The following lines are reported when I install it via paru.

visual-studio-code-bin version = 1.86.1-1

Is there anything I need to pay attention to?

debugedit: ./opt/visual-studio-code/resources/app/node_modules.asar.unpacked/@parcel/watcher/build/Release/watcher.node: Unknown debugging section .debug_gnu_pubnames

debugedit: ./opt/visual-studio-code/resources/app/node_modules.asar.unpacked/@parcel/watcher/build/Release/watcher.node: Unknown debugging section .debug_gnu_pubtypes

debugedit: ./opt/visual-studio-code/resources/app/node_modules.asar.unpacked/@vscode/policy-watcher/build/Release/vscode-policy-watcher.node: Unknown debugging section .debug_gnu_pubnames

debugedit: ./opt/visual-studio-code/resources/app/node_modules.asar.unpacked/@vscode/policy-watcher/build/Release/vscode-policy-watcher.node: Unknown debugging section .debug_gnu_pubtypes

debugedit: ./opt/visual-studio-code/resources/app/node_modules.asar.unpacked/@vscode/spdlog/build/Release/spdlog.node: Unknown debugging section .debug_gnu_pubnames

debugedit: ./opt/visual-studio-code/resources/app/node_modules.asar.unpacked/@vscode/spdlog/build/Release/spdlog.node: Unknown debugging section .debug_gnu_pubtypes

debugedit: ./opt/visual-studio-code/resources/app/node_modules.asar.unpacked/@vscode/sqlite3/build/Release/vscode-sqlite3.node: Unknown debugging section .debug_gnu_pubnames

debugedit: ./opt/visual-studio-code/resources/app/node_modules.asar.unpacked/@vscode/sqlite3/build/Release/vscode-sqlite3.node: Unknown debugging section .debug_gnu_pubtypes

debugedit: ./opt/visual-studio-code/resources/app/node_modules.asar.unpacked/kerberos/build/Release/kerberos.node: Unknown debugging section .debug_gnu_pubnames

debugedit: ./opt/visual-studio-code/resources/app/node_modules.asar.unpacked/kerberos/build/Release/kerberos.node: Unknown debugging section .debug_gnu_pubtypes

debugedit: ./opt/visual-studio-code/resources/app/node_modules.asar.unpacked/kerberos/build/Release/obj.target/kerberos.node: Unknown debugging section .debug_gnu_pubnames

debugedit: ./opt/visual-studio-code/resources/app/node_modules.asar.unpacked/kerberos/build/Release/obj.target/kerberos.node: Unknown debugging section .debug_gnu_pubtypes

debugedit: ./opt/visual-studio-code/resources/app/node_modules.asar.unpacked/native-keymap/build/Release/keymapping.node: Unknown debugging section .debug_gnu_pubnames

debugedit: ./opt/visual-studio-code/resources/app/node_modules.asar.unpacked/native-keymap/build/Release/keymapping.node: Unknown debugging section .debug_gnu_pubtypes

debugedit: ./opt/visual-studio-code/resources/app/node_modules.asar.unpacked/node-pty/build/Release/pty.node: Unknown debugging section .debug_gnu_pubnames

debugedit: ./opt/visual-studio-code/resources/app/node_modules.asar.unpacked/node-pty/build/Release/pty.node: Unknown debugging section .debug_gnu_pubtypes

objcopy: ./opt/visual-studio-code/resources/app/node_modules.asar.unpacked/node-vsce-sign/bin/vsce-sign: debuglink section already exists

debugedit: ./opt/visual-studio-code/resources/app/node_modules.asar.unpacked/vsda/build/Release/vsda.node: Unknown debugging section .debug_gnu_pubnames

debugedit: ./opt/visual-studio-code/resources/app/node_modules.asar.unpacked/vsda/build/Release/vsda.node: Unknown debugging section .debug_gnu_pubtypes

IMBJR commented on 2024-02-08 16:27 (UTC)

Currently seeing the following when building the package:

objcopy: ./opt/visual-studio-code/resources/app/node_modules.asar.unpacked/node-vsce-sign/bin/vsce-sign: debuglink section already exists /usr/share/makepkg/tidy/strip.sh: line 48: debugedit: command not found

with the second line repeated a number of times.

Nowaker commented on 2024-01-15 11:00 (UTC)

@Raadush This package takes the official binary from Microsoft. You should be reporting it to the upstream.

Raadush commented on 2024-01-15 08:42 (UTC)

I dont know if anyone noticed or if it is my problem, but since last update I am experiencing pretty high memory consumption. It was definitely not the case in previous versions. My idle system runs on around 2.5GB ram, I open vs code, it goes to 3.5GB, connect to docker image through docker extension (4,9GB), run npm application (5,7GB), open that application in chrome (6.8GB) and then when I develop it goes up and up until at 12GB system starts to become unstable and I need to close code and start over.

kjkent commented on 2024-01-10 01:43 (UTC) (edited on 2024-01-10 01:44 (UTC) by kjkent)

Also having the same issue as 99linesofcode (https://aur.archlinux.org/packages/visual-studio-code-bin#comment-942412)

/opt/visual-studio-code/chrome-sandbox has 0755 perms but requires 4755 perms or vscode silently fails to open. AFAIK this only affects those with the kernel flag unprivileged_userns_clone = 0 set for security hardening, but can be remediated by the correct file permissions set.

Ofc, until this is fixed in packaging/upstream, updates will overwrite chrome-sandbox and reset its perms. In the interim, the following, placed in /etc/pacman.d/hooks/, offers a workaround:

# /etc/pacman.d/hooks/60-visual-studio-code-bin.hook

[Trigger]
Operation = Install
Operation = Upgrade
Type = Path
Target = opt/visual-studio-code/chrome-sandbox

[Action]
Description = "Fixing file permissions on /opt/visual-studio-code/chrome-sandbox"
When = PostTransaction
Exec = /usr/bin/chmod 4755 /opt/visual-studio-code/chrome-sandbox

NB, the lack of / before opt in Target = isn't a typo.

heddxh commented on 2024-01-07 09:38 (UTC)

My Vscode always launch in wrong cgroup on Kde plasma, which is the only application have this problem. For example, when I launch it through krunner, it will under background.slice/app-krunner.slice instead of its own app slice. If I run it with systemd-run --user /opt/visual-studio-code/code then everything will be fine. Is this something about launch script or a upstream problem?

cbrnr commented on 2023-12-14 10:41 (UTC) (edited on 2023-12-14 10:48 (UTC) by cbrnr)

I disabled all extensions, and using plain GNOME I cannot pin VS Code to the dock either. Not sure if this is an issue related to the PKGBUILD or upstream. EDIT: It might be the issue reported here: https://github.com/microsoft/vscode/issues/154693 So if anyone else also experienced this problem, feel free to +1 the top comment.

cbrnr commented on 2023-12-11 13:23 (UTC)

I use the Dash to Panel GNOME extension, and when right-clicking on the VS Code icon, I do not get a "Pin to Dash" option. I suspect that maybe some setting in the launcher is confusing the panel, because the window list (F2+lg) shows VS Code as "code-url-handler.desktop". Any ideas how to fix this?