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

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: 1418
Popularity: 19.68
First Submitted: 2017-12-18 19:14 (UTC)
Last Updated: 2024-05-03 05:35 (UTC)

Required by (17)

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 .. 73 Next › Last »

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?

Antonio_8A commented on 2023-11-27 15:00 (UTC)

Visual Studio Code está consumiendo muchos recursos alguien sabe qué puedo hacer para solucionar, está actualizado a la última versión de todo. tanto Kernel como paquetes

Krator commented on 2023-11-07 19:15 (UTC)

logxx this doesn't help

logxx это не помогает

99linesofcode commented on 2023-11-07 09:45 (UTC) (edited on 2023-11-07 09:47 (UTC) by 99linesofcode)

Not entirely sure whether this is an issue with the PKGBUILD or vscode itself but the /opt/visual-studio-code/chrome-sandbox is not created using the correct permissions. It should set the setuid bit so that it can be run by root using the sandbox helper as per the output below:

code --verbose

[FATAL:setuid_sandbox_host.cc(158)] The SUID sandbox helper binary was found, but is not configured correctly. Rather than run without sandboxing I'm aborting now. You need to make sure that /opt/visual-studio-code/chrome-sandbox is owned by root and has mode 4755.

As of now, I need to update these permissions with every update.

logxx commented on 2023-11-06 19:02 (UTC)

Krator, you could try to run xdg-mime default org.kde.dolphin.desktop inode/directory as stated in https://wiki.archlinux.org/title/File_manager_functionality#Directories_are_not_opened_in_the_file_manager

Krator commented on 2023-11-02 17:55 (UTC) (edited on 2023-11-02 17:55 (UTC) by Krator)

Hello! Unfortunately, there was a problem with VSCode on archlinux again. The essence of the problem: VSCode takes over the opening of directories instead of a file manager. This manifests itself at least in the inactivity of the "browse" button in timeshift (you can make sure that the problem is due to VSCode by running it from the terminal with the timeshift-launcher command) I have already written about this here before and even gave a solution, but after updating the application it stopped working. What used to interfere with the work seems to have been fixed, but the problem has only worsened, since it has not been solved and the repair method does not work. A temporary solution is to change the order of applications in mimeinfo.cache, that is, put the file manager first. Please tell me how to solve this!

Здравствуйте! К сожалению опять появилась проблема с VSCode на archlinux. Суть проблемы: VSCode берет на себя открытие директорий вместо файлового менеджера. Это проявляется как минимум в неработоспособности кнопки "обзор" в timeshift (можно убедиться, что проблема из-за VSCode запустив его из терминала командой timeshift-launcher) Раньше я уже писал об этом здесь и даже давал решение, но после обновления приложения оно перестало работать. То, что раньше мешало работе вроде как исправлено, но проблема только усугубилась, так как не решена и способ починки не работает. Временное решение заключается в изменении порядка приложений в mimeinfo.cache, то есть поставить первым файловый менеджер. Подскажите пожалуйста как это решить!

werz0 commented on 2023-10-30 19:28 (UTC)

This package is regularly crashing on v1.83.1-1 I have tried running by disabling extensions, disabling gpu and few other fixes. But none have helped so far.