Arch Linux User Repository

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.

@TTsdzb fixed, thanks.

Could not open folder or files in file explorers. VSCode will start but opens a clean window instead of the requested file or folder.

The argument --unity-launch seems deprecated:

$ code --unity-launch
Warning: 'unity-launch' is not in the list of known options, but still passed to Electron/Chromium.

Removed this in the desktop entry, and it works fine now.

@st0ne @blueman Try to disable debug by adding a exclamation mark before it in /etc/makepkg.conf:

OPTIONS=(strip docs !libtool !staticlibs emptydirs zipman purge !debug lto)

This will prevent makepkg from generating corresponding debug packages. Not sure if there're side effects, but it works fine for me.

I've got the same "debugedit" warnings as @st0ne. Any idea what's causing this?

@shore you're welcome to use "Flag package out-of-date" in this page with a link to the new version instead of commenting

Out of date .....

hi with Update to 1.88.0 on $ makepkg -si ==> ERROR: Cannot find the debugedit binary required for including source files in debug packages.

遇到一些问题 got some problems

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
objcopy: ./opt/visual-studio-code/resources/app/node_modules.asar. unpacked/@vscode/vsce-sign/bin/vsce-sign: debuglink section already exists
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
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

vscode和linuxqq一起安装的时候会安装失败，冲突貌似在各自的debug程序上 When vscode and linuxqq are installed together, the installation fails, and the conflict seems to be on their respective debug programs

错误：无法提交处理 (有冲突的文件)
/usr/lib/debug/.build-id/b1/ace29c2ed9438afddbed0feb85e62b70014f5f 同时存在于 'visual-studio-code-bin-debug' 和 'linuxqq-debug'
/usr/lib/debug/.build-id/b1/ace29c2ed9438afddbed0feb85e62b70014f5f.debug 同时存在于 'visual-studio-code-bin-debug' 和 'linuxqq-debug'
/usr/lib/debug/.build-id/f8/92293f507294f22c5d8b7eda75c8b7bd530932 同时存在于 'visual-studio-code-bin-debug' 和 'linuxqq-debug'
/usr/lib/debug/.build-id/f8/92293f507294f22c5d8b7eda75c8b7bd530932.debug 同时存在于 'visual-studio-code-bin-debug' 和 'linuxqq-debug'
发生错误，没有软件包被更新。
 -> 安装时出错:  [/home/stone/.cache/yay/visual-studio-code-bin/visual-studio-code-bin-1.88.0-1-x86_64.pkg.tar.zst /home/stone/.cache/yay/visual-studio-code-bin/visual-studio-code-bin-debug-1.88.0-1-x86_64.pkg.tar.zst /home/stone/.cache/yay/linuxqq/linuxqq-2:3.2.7_240403-1-x86_64.pkg.tar.zst /home/stone/.cache/yay/linuxqq/linuxqq-debug-2:3.2.7_240403-1-x86_64.pkg.tar.zst] - exit status 1

@eryn.zofia and @laasonen, refer to previous comments regarding debug flag being flipped in /etc/makepkg.conf:100

https://aur.archlinux.org/cgit/aur.git/tree/code.desktop?h=visual-studio-code-bin

the --unity-launch leads to tiny cursors on HiDPI settings.

See https://github.com/microsoft/vscode/issues/136390#issuecomment-2020292160

https://github.com/microsoft/vscode/pull/209471

The fastest fix is to delete the --unity-launch option, just /usr/bin/code is fine.

Getting the same as @laasonen for either trying to update code or azure data studio:

error: failed to commit transaction (conflicting files)
/usr/lib/debug/.build-id/c1/1c9bc818110b2370d9992f885037b7a1f74378 exists in both 'visual-studio-code-bin-debug' and 'azuredatastudio-bin-debug'
/usr/lib/debug/.build-id/c1/1c9bc818110b2370d9992f885037b7a1f74378.debug exists in both 'visual-studio-code-bin-debug' and 'azuredatastudio-bin-debug'

Update fails:

error: failed to commit transaction (conflicting files)
/usr/lib/debug/.build-id/c1/1c9bc818110b2370d9992f885037b7a1f74378 exists in both 'visual-studio-code-bin-debug' and 'azuredatastudio-bin-debug'
/usr/lib/debug/.build-id/c1/1c9bc818110b2370d9992f885037b7a1f74378.debug exists in both 'visual-studio-code-bin-debug' and 'azuredatastudio-bin-debug'

@elduderino @bigbrozer Thanks a lot!

@elduderino, thanks for the notice ! I do not need this for most of the packages I install so I decided to disable debug adding again !debug to OPTIONS in /etc/makepkg.conf:

OPTIONS=(strip docs !libtool !staticlibs emptydirs zipman purge !debug lto)

I got the previous results (without the *-debug package and messages from debugedit). In case if others are interested...

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

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

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

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.

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

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.

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.

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?

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.

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?

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

logxx this doesn't help

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

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.

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

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, то есть поставить первым файловый менеджер. Подскажите пожалуйста как это решить!

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.

Would the icon (visual-studio-code.png) better be put under /usr/share/icons/hicolor/somewhere instead of just /usr/share/icons? Since everything else there are folders/icon packs.

I built this package manually with a non-root user:

$ makepkg -s

But VS code failed to start with the following error message:

You need to make sure that /opt/visual-studio-code/chrome-sandbox is owned by root and has mode 4755

So I tried adding a line to the PKGBUILD file to set the suid correctly, and it now starts fine after installation.

   cp -r "${srcdir}/${_pkg}/"* "${pkgdir}/opt/${_pkgname}"

+  # suid sandbox
+  chmod 4755 "${pkgdir}/opt/${_pkgname}/chrome-sandbox"
+
   # Launcher
   install -m755 "${srcdir}/${_pkgname}-bin.sh" "${pkgdir}/usr/bin/code"

I found an error in this package! The error interferes with the work of some third-party programs. Error description using the example of the timeshift program:

If you run this program from the console using the timeshift-launcher command, then we will be able to observe errors. Clicking on the "browse" button, we will see an error in the console that he is trying to use Visual Studio Code instead of the file manager (dolphin). This error is not in the package from the official repository.

How to fix it:

1) Open the terminal

2) Open the file "mimeapps.list":

nano ~/.config/mimeapps.list

3) Add the following parameter:

inode/directory=org.kde.dolphin.desktop

It should be in the [Default Applications] section

You also need to remove it from the [Remove Applications] section if it is in it

Нашёл ошибку в данном пакете! Ошибка мешает работе некоторым сторонним программам. Описание ошибки на примере программы timeshift:

Если запустить эту программу из консоли при помощи команды timeshift-launcher, то мы сможем наблюдать ошибки. Нажимая на кнопку "обзор" мы увидим ошибку в консоли о том, что он пытается использовать Visual Studio Code вместо файлового менеджера (dolphin). Этой ошибки нет в пакете из официального репозитория.

Как это исправить:

1) Открываем терминал

2) Открываем файл "mimeapps.list":

nano ~/.config/mimeapps.list

3) Добавляем следующий параметр:

inode/directory=org.kde.dolphin.desktop

Он должен находиться в разделе [Default Applications]

Также нужно удалить его из раздела [Remove Applications] если он есть в нём

the top menu color has problem in 1.82.0-1 version, I am using the solarized dark theme, at the previous version the top menu color is correct, but at this version the top menu color is white, it is not correct

<img alt="" src="http://fars.ee/klP0" />

I've been running into the same issue as @mxbonn. It took a bit of digging, but I'm fairly certain I'm running into the same issue as https://github.com/microsoft/vscode/issues/184124. From what I can tell, a regression in 1.82 breaks running natively in Wayland; only running in XWayland works for me, which is disappointing, but it seems like there's not much we can do other than wait for this to get fixed upstream.

v1.82.0-1 works 100% for me on my desktop and on a clean install of Arch

Updated to v1.82.0-1 and app crashes split second after opening.

@PHLAK mine is not blurry, but if I try to open a second window, it crashes

Updated to v1.82.0-1 and my app is blurry even when running with --ozone-platform-hint=auto. I assume this is due to the update to Electron 25. Is there a way to fix this?

code tunnel is not working. The output is : spawn /opt/visual-studio-code/bin/code-tunnel ENOENT There is a related issue but it is closed: https://github.com/microsoft/vscode/issues/189383

@mazix the latest version is still 1.80.2 here.

@mazix if there is a new version out you're welcome to use "Flag package out-of-date" in this page instead of commenting please

update version please

If you encounter keyring-related errors, the --password-store option may be helpful.

gnome-keyring: --password-store=gnome

KWallet: --password-store=kwallet5

ref: https://wiki.archlinux.org/title/Chromium#Force_a_password_store

@dcelasun Thanks. I've already filed a "bug" report for uutils: https://github.com/uutils/coreutils/issues/5027

@TheDcoder it's just a mistake, I'll fix it in the next release. Keep in mind that coreutils (the GNU one) is mandatory for AUR packages. Third party reimplementations are unsupported. It's on them to be compatible with GNU, bug for bug.

Why is cp -r "${srcdir}/${_pkg}/"* "${pkgdir}/opt/${_pkgname}" -R being used in the PKGBUILD? What's the reason behind specifying the recursive flag multiple times?

Build fails when using uutils-coreutils since their cp doesn't accept more than one recursive flag.

@PHLAK thank you for pointing that out. Fixed scaling for me on my new wayland setup. I had tried the arguments pointed out in the ArchWiki for electron, but it only worked with the sole --ozone-platform-hint=auto.

@stepinsilence I just tried using --ozone-platform-hint=auto (removing all other launch options) and it seems to be working well. 👍️

@Lightning5 It seems only we encountered this issue. Given I have been using VSCode natively under Wayland these days flawlessly, I incline that something might get messed up on our side.

BTW, as now VSCode is built on Electron 22.5.7, perhaps we could use --ozone-platform-hint=auto instead of --enable-features=UseOzonePlatform --ozone-platform=wayland.

@stepinsilence I can confirm that your solution works. I've updated VS Code again to 1.79.1, and it has crashed immediately when, I tried to start it. Clearing the flags for first startup and then restoring them worked.

I'll write a bug report if this is ok with everyone.

Well...After updating to VSCode 1.79.1, I have to temporarily remove the two ozone platform flags before starting the new VSCode for the first time, then restoring the flag config file; otherwise, VSCode immediately crashes. I don't know why.

@Lightning5 I can't speak to your specific situation but I have the following in my ~/.config/code-flags.conf file and everything is working as expected under Wayland.

--enable-features=UseOzonePlatform
--ozone-platform=wayland

@PHLAK VS Code 1.79 crashed on start on me with those errors. I had to go back to X11 to make it start. I have reverted to VS Code 1.78. I would do more tests but, I am in the middle of exams so, I guess, I will report at the next update :) Chrome actually had a similar bug a version or two ago. Didn't bother to research it because I use Firefox, but it got fixed in the latest version. It might be tied to the electron version used.

@Lightning5 As it says, this is just a warning and the parameters are still being passed to Electron. Nothing to worry about.

Hi,

Flag support is broken. When I try to run VS Code with Wayland flags, I get this error.

Warning: 'enable-features' is not in the list of known options, but still passed to Electron/Chromium. Warning: 'ozone-platform-hint' is not in the list of known options, but still passed to Electron/Chromium.

This worked until the last version.

@direc85 vscode's Electron version numbers don't follow upstream 1-to-1 https://github.com/microsoft/vscode/pull/182044

My vscode shows the following test in its about dialog:

Version: 1.78.2
Commit: b3e4e68a0bc097f0ae7907b217c1119af9e03435
Date: 2023-05-10T14:47:05.613Z
Electron: 22.5.2
Chromium: 108.0.5359.215
Node.js: 16.17.1
V8: 10.8.168.25-electron.0
OS: Linux x64 6.3.0-1-MANJARO
Sandboxed: Yes

There is no such Electron release, and the binaries downloaded from upstream seem to come with 22.3.5 instead. I don't even have Electron installed. Any ideas why the Electron version is (apparently) wrong?

x86_64 version patch for the current PKGBUILD. Use it if you want to update ASAP.

diff --git a/PKGBUILD b/PKGBUILD
index 2e68b1a..2461346 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -2,7 +2,7 @@

 pkgname=visual-studio-code-bin
 _pkgname=visual-studio-code
-pkgver=1.77.1
+pkgver=1.77.3
 pkgrel=1
 pkgdesc="Visual Studio Code (vscode): Editor for building and debugging modern web and cloud applications (official binary version)"
 arch=('x86_64' 'i686' 'aarch64' 'armv7h')
@@ -31,7 +31,7 @@ sha256sums=('10a5ee77a89fc934bcbd3e2a41a2ec4bd51d3cd048702f6d739ecec9eb3a7c4b'
             '2264dd138b77358709aa49fb3a7fe7d1b05b7ab0715760d66958000107bdd3dc'
             '24ba09a6398c9781ed7cb6f1a9f6f38ec204899ba1f33db92638bf6d3cb0aed6'
             '8257a5ad82fa1f7dec11dfa064217b80df4cfec24f50cec7ca0ad62cf8295bfe')
-sha256sums_x86_64=('8d762387e72c6da60b934a1716751db353fa9bf06bb823e71ea1e80c1c31d97e')
+sha256sums_x86_64=('dc0333c196d8f455539b0b27f99d6b4fcffb66dca3f8de0e466b9cbfe19cc869')
 sha256sums_i686=('64360439cc2fa596838062f7e6f9757b79d4b775a564f18bad6cbad154bf850c')
 sha256sums_aarch64=('72a58535d42a77aa63522bdb5142b9279876e7efd4ccc730849a4680c7f95962')
 sha256sums_armv7h=('b204da3b4b5f0efdaf00df30cb41d2b8aa857705fa0a2bdc864dff64140c1cb7')

out of dated......

There is an extra white space in the end of the line:

install -d "${pkgdir}/usr/share/icons" 

@DHxchange you need to refresh your pacman db

I tried to install the linked tarball via makepkg -si, and it failed because the lsof dependency is no longer available. Accessing web pages via the browser works fine so I doubt this is a network problem on my machine.

$ makepkg -si
==> Making package: visual-studio-code-bin 1.75.1-1 (Tue 14 Feb 2023 19:32:16)
==> Checking runtime dependencies...
==> Installing missing dependencies...
[sudo] password for [user]: 
resolving dependencies...
looking for conflicting packages...

Packages (1) lsof-4.96.5-1

Total Download Size:   0.11 MiB
Total Installed Size:  0.20 MiB

:: Proceed with installation? [Y/n] 
:: Retrieving packages...
 lsof-4.96.5-1-x86_64.pkg.tar.zst failed to download
error: failed retrieving file 'lsof-4.96.5-1-x86_64.pkg.tar.zst' from mirror.2degrees.nz : The requested URL returned error: 404
error: failed retrieving file 'lsof-4.96.5-1-x86_64.pkg.tar.zst' from uvermont.mm.fcix.net : The requested URL returned error: 404
error: failed retrieving file 'lsof-4.96.5-1-x86_64.pkg.tar.zst' from mirrors.sonic.net : The requested URL returned error: 404
error: failed retrieving file 'lsof-4.96.5-1-x86_64.pkg.tar.zst' from mirror.alpix.eu : The requested URL returned error: 404
error: failed retrieving file 'lsof-4.96.5-1-x86_64.pkg.tar.zst' from repo.iut.ac.ir : The requested URL returned error: 404
error: failed retrieving file 'lsof-4.96.5-1-x86_64.pkg.tar.zst' from manjaro.mirror.garr.it : The requested URL returned error: 404
warning: failed to retrieve some files
error: failed to commit transaction (failed to retrieve some files)
Errors occurred, no packages were upgraded.
==> ERROR: 'pacman' failed to install missing dependencies.
==> Missing dependencies:
  -> lsof
==> Checking buildtime dependencies...
==> ERROR: Could not resolve all dependencies.

@friday13 that's a weird error, like your makepkg is broken for some reason. Try in a clean build directory without any AUR helpers.

Entering fakeroot environment...
/usr/share/makepkg/util/pkgbuild.sh: line 30: declare: `package_visual-studio-code-bin': not a valid identifier
/usr/share/makepkg/util/pkgbuild.sh: line 30: declare: `package_visual-studio-code-bin': not a valid identifier
==> Starting package()...
cp: target '-R': No such file or directory
==> ERROR: A failure occurred in package().
    Aborting...
 -> error making: visual-studio-code-bin

You need to make sure that /opt/visual-studio-code/chrome-sandbox is owned by root and has mode 4755

Because I run makepkg as a non-root user, it makes sense that any setuid binaries in the upstream tarball lose their setuid status during extraction.

This has been my problem more-or-less since I started using this package. After an update, I have to manually re-run the following command to restore the setuid bit on the sandbox helper binary:

# chmod 4755 /opt/visual-studio-code/chrome-sandbox

Again, since makepkg runs as a non-root user, I can't think of a way to resolve this in the PKGBUILD itself. It might be possible to automate this in a post-install hook, but I've never used that functionality so can't vouch for its effectiveness.

(EDIT: Accidentally pressed tab before pressing enter and posted unfinished comment)

@adelks chrome-sandbox is already owned by root. Are you sure you haven't made any local modifications?

$ ls -alh /opt/visual-studio-code/ | grep chrome
-rw-r--r--  1 root root 126K Jan 15 15:26 chrome_100_percent.pak
-rw-r--r--  1 root root 177K Jan 15 15:26 chrome_200_percent.pak
-rwxr-xr-x  1 root root 1,2M Jan 15 15:26 chrome_crashpad_handler
-rwxr-xr-x  1 root root  15K Jan 15 15:26 chrome-sandbox

Hello, please add a line to the PKGBUILD to fix this:

[6204:0115/161133.400478:FATAL:setuid_sandbox_host.cc(157)] 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

Thanks!

When using AUR helper (Pamac), it will fail to install (failed to generate visual-studio-code-bin information) because the PKGBUILD has this line: install=$pkgname.install but the file doesn't exist. Simply deleting that line (from PKGBUILD) will solve the issue.

@Tim_Paik do you have shared-mime-info-gnome installed as explained in the pinned FAQ?

I recently ran into the following problem with GNOME nautilus and VSCode: My default folder opens with VSCode!

xdg-mime query default inode/directory This command will output code.desktop, and then when I try to run open <dir_name> in the fish shell, fish will use VSCode to open this directory, GNOME keyboard The shortcut key also opens the main directory with VSCode by default.

However, when choosing the way to open the directory in nautilus, there is no option to change the default (I think this may be to prevent nautilus from being damaged due to carelessness)

I think it might be because of this commit: Rename desktop files to match upstream, since this happened to me recently.

I think this is definitely not expected, but I found a temporary workaround, you can run the following command to set the current user's default to normal:

xdg-mime default org.gnome.Nautilus.desktop inode/directory

Any objections to that? I don't want to keep pushing updates for a cosmetic issue.

I think patching "desktopName" to "code.desktop" in /opt/visual-studio-code/resources/app/package.json would be a better choice. Because by default, code-url-handler is hidden and cannot be pinned.

In current setting, the vscode window gets code-url-handler class and displays the right icon. But if we pin the normal vscode, then on the pannel, there will be two vscode icons.

I've renamed the desktop files, please let me know if there are any issues. I don't use Wayland myself so I can't test.

On line 7 there should not be the: (,) between

The /opt/visual-studio-code/resources/app/package.json file has "desktopName" entry with value of "code-url-handler.desktop"` which should match the actual desktop file name. Please consider patching this field or renaming desktop files.

@dcelasun @ZZYSonny It could be fixed by renaming .desktop files to code.desktop and code-url-handler.desktop like upstream (https://github.com/microsoft/vscode/tree/main/resources/linux), instead.

why i could't debug?

@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.

Could you please consider applying this workaround to make VSCode show its own icon instead of the generic wayland icon with "ozone-platform=wayland"? https://github.com/microsoft/vscode/issues/129953#issuecomment-1235360500

@Piroro-hs thanks, should be fixed now.

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

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

alsa-lib (libasound.so.2) should be added to depends list.

@phillipk alright then, I pushed the change.

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.

@philipk do you mean /usr/bin/code? Because /opt/visual-studio-code/bin/code is supplied by upstream and is not involved with $CODE_USER_FLAGS. I don't think changing the order of $CODE_USER_FLAGS and "$@" is a good idea. What exactly is the problem you're having?

I have to correct myself: Have not used VSCode on this Arch install for a while, but the arguments passed still seem to get lost if they are put after $CODE_USER_FLAGS.

code . only works for me if I change line 11 of /opt/visual-studio-code/bin/code to look like follows: exec /opt/visual-studio-code/bin/code "$@" $CODE_USER_FLAGS.

Can we take that change into this AUR package, or is there a negative side to this that i am not aware of?

Ever since v1.69 the when launching Code the running app is displayed as a separate, unstyled app icon in my dock instead of being tied to the original icon. In this screenshot you can see the VS Code icon on the left. When I clicked that icon the grey gear icon shows up and is the running instance of VS Code. The StartupWMClass of the .desktop file is correct. Not sure if this should be reported here or upstream.

EDIT: This looks like an issue with VS Code itself under Wayland.

I don't understand why this is flagged out of date. I can see that it is perfectly matching to the latest version of vscode we have

@digital wow, thanks a bunch! I tried it without sudo and it suddenly worked! Good to know!

@Smokus do not run yay with sudo

I am fairly new to the Linux world. I ran the following command to install VS Code: sudo yay -S visual-studio-code-bin, but I following error:

Avoid running yay as root/sudo.

:: Checking for conflicts...

:: Checking for inner conflicts...

[Repo:1] lsof-4.95.0-1

[Aur:1] visual-studio-code-bin-1.68.1-1

:: (0/1) Downloaded PKGBUILD: visual-studio-code-bin

-> error fetching visual-studio-code-bin: fatal: could not create work tree dir > 'visual-studio-code-bin': Permission denied

context: exit status 128

Installing "code" package from official Arch Repo works just fine. Any help is appreciated.

i don't know if help, but with this command is a easy way to know about last version:

curl 'https://code.visualstudio.com/sha/download?build=stable&os=linux-deb-x64' -s -L -I | grep 'filename=' | cut -f2 -d'"' | cut -f2 -d'_' | cut -f1 -d'-'

Because it's been more than a year since upstream enabled the sandbox on Linux and it's time this package caught up.

It doesn't start anymore without manually adding --no-sandbox to ~/.config/code-flags.conf now.

Why was this removed from the .desktop files?

Added icu69 to optdepends.

Yes,as below, live share does not work unless icu69 package is installed. Please add it (or icu69-bin which I used?) to the dependencies.See this issue.

After a recent upgrade, liveshare stopped working

command 'liveshare.startFromWelcomeContent' not found: Error: command 'liveshare.startFromWelcomeContent' not found

After consulting https://docs.microsoft.com/en-us/visualstudio/liveshare/reference/linux, I ran the script for the required dependencies, which indicated that icu69 was missing.

After installing the icu69 AUR package (https://aur.archlinux.org/packages/icu69), live share now works.

I've installed another arch in VM to specifically test this aur package with the sign in to sync settings issue I'm facing, and it is my machine, not the package, that is at fault. I don't know what to do to solve it but it's working fine in VM when I sync settings. I've tried installing on my main machine with and without an aur helper, so some setting somewhere must be being preserved between installs. Sorry to have bothered you.

Edit: paru -Sc did the trick, can now access my codespaces from visual studio code again! \n Edit2: The only thing that confuses me is I did try installing the tarball and doing makepkg -si and as far as I know my solution shouldn't of impacted that, but that still was having the same issue. Maybe it does interact some way?

@phillipk: That should be fixed now, thanks!

@vegancookies: I can't reproduce with Firefox. Could it be related to your browser somehow? I just pushed an update with a minor change to the URL handler, can you update and try again?

Recently I've been unable to sign in via github. It loads the browser for login, takes me through the 2fa process, and then the url handler goes back to vscode, where it attempts to login, but just ends up giving a notification of 'cancelled'.

I've put ubuntu on a virtual machine and the program works perfectly there. I've tried uninstalling and reinstalling, and deleting github authentication files left over from when I was signed in. I've also tried to revoke vscode on github and retry from the start, but the issue persists (only the aur version).

Is there anything the user can do to re-enable this functionality or any additional information you would fine useful (everything on my system is upto date, running arch vanilla).

The wrapper script in /usr/bin/code seems broken for me in some way. Running it in the terminal as code . does not seem to pass the current directory (either the last workspace or a blank instance opens). /opt/visual-studio-code/code . works, however. Sadly, I am too bad at bash to see the problem.

EDIT: Nvm, I have found a solution: If the path is passed as the first argument to /opt/visual-studio-code/bin/code it is working. So line 11 of the wrapper should be exec /opt/visual-studio-code/bin/code "$@" $CODE_USER_FLAGS

I suspect it has to do with line breaks in $XDG_CONFIG_HOME/code-flags.conf?

Are you able to add KDE wallet integration to this package?

I had to add ''gnome-keyring'' to be able to sync with my other copies of vs code, and it won't stop asking me for my default keyring.

The Wayland issue seems to be an Electron problem [1] and should be fixed by Electron v17.3.1, which was released 2 days ago [2]. They might (or might not) include this in the upcoming recovery build [3]. In the meantime, there are workarounds mentioned in the bug report [1].

[1] https://github.com/microsoft/vscode/issues/146349

[2] https://github.com/electron/electron/releases/tag/v17.3.1

[3] https://github.com/microsoft/vscode/issues/146388

With v1.66 there are two errors:

Warning: 'enable-features' is not in the list of known options, but still passed to Electron/Chromium.
Warning: 'ozone-platform' is not in the list of known options, but still passed to Electron/Chromium.

And Code does not start. I use these flags to enable wayland support. I am on Gnome/Wayland and for better font render I use these flags:

--enable-features=UseOzonePlatform
--ozone-platform=wayland

I removed the flags and no problem but the font render is bad again :). Any solution?

I confirm that 1.66 is a mess on wayland + gnome + nvidia, skip this!

After updating to 1.66 I get a (white) blank screen. It seems VScode bumped Electron from v13 to v17. Running with --verbose outputs

[50533:0331/104848.998408:ERROR:gpu_process_host.cc(983)] GPU process exited unexpectedly: exit_code=136

Starting with --disable-gpu seems to be working as a workaround. Gnome + Xorg + NVidia 510.54.

Here we go!

Hi, is normal that if the vscode is exit, the Visual Studio Code - URL Handler from /usr/share/applications/visual-studio-code-url-handler.desktop keeps running like 30% CPU?

@dcelasun kk, sorry for not seeing that..... and thanks for ur replay~~

@shore

BTW, the insider version on arch seems behind the main version

Not exactly. The insider package always builds the latest version (see pinned comment), so I don't manually update pkgver.

@dcelasun I actually did that, however the insider version works fine, so they closed the issue since it must have been fixed something........ BTW, the insider version on arch seems behind the main version lol........

@shore it's probably trying to connect to a Microsoft server which isn't reachable from China, and you're stuck until the request times out. You should report this on Github.

Hi I'm in China and installed the latest package as follow:

Version: 1.65.2 Commit: c722ca6c7eed3d7987c0d5c3df5c45f6b15e77d1 Date: 2022-03-10T15:36:26.048Z Electron: 13.5.2 Chromium: 91.0.4472.164 Node.js: 14.16.0 V8: 9.1.269.39-electron.0 OS: Linux x64 5.16.11-2-MANJARO

After reboot my computer, I found that each time first open vscode (meaning when open it, there is no other vscode window opened) it tooks extensive time to open it, unless I connect to the VPN (which allow me to visit google and some other webs). Also during the time it starting terminal, the extension marked is down too.

I don't know what happened and even mopped the system and re-install everything, it still like this.........

No menu reveals when I click the account button to sync and login to my account.

Using version: 1.65.0 b5205cc8eb4fbaa726835538cd82372cc0222d43 x64

EDIT: Solved by installing gnome-keyring libsecret libgnome-keyring

Having an issue where my sign in doesn't seem to persist. I'm finding that I have to constantly sign in again in order to sync my settings upon each start of the app. Any ideas?

EDIT: Now the settings sync is totally gone. Pressing account reveals no menu that would normally have "sign in with microsoft/github", and trying to sync in the settings errors with "no authentication headers".

Any idea why code is complaining about there being a new update when everything is 1.64.2?

Yes, the latest update indeed broke Remote SSH (but somehow I can't connect only to one of two identical remote machines). A fix is to put "remote.SSH.useLocalServer": false in your settings.json for the time being.

Another issue is that when running VSCode from the menu (e.g. KRunner) the Haskell extension complaints with "Project requires GHC but it isn't installed", which does not happen when it's run from the terminal (just code). I can't pinpoint where the issue is, though (the .desktop file? PATH is different? how to check it without running the built-in terminal?)

Somehow picom "window_type = 'popup_menu'" doesn't work on VSCode context menu (right-click menu that contains cut, copy, paste). Anyone know the exact WM_CLASS or WM_NAME of VSCode context menu?

Anyone else having issues SSH (remote) not working anymore?

[08:50:12.292] Platform: linux
[08:50:12.297] stderr> bash: line 1: syntax error near unexpected token `done'
[08:50:12.297] stderr> bash: line 1: `done'
[08:50:12.299] stderr> zsh: parse error near `}'
[08:50:12.300] > Installing to ...
[08:50:12.301] > 7bbfe4a1a79e%%1%%
[08:50:12.306] > Downloading with wget
[08:50:12.594] > wget download failed

It seems to happen after latest updates.

Version 1.64.2 constantly uses 30% of CPU. Downgrading to 1.64.1 solves the issue.

Hello, would you like to change the license to 'Microsoft EULA'? Since this isn't a paid for/freemium/commercial, just a proprietary program

Updated with ~/.config/code-flags.conf support. Thanks to @n0k0m3 for the PR!

@n0k0m3 It should be possible to create a wrapper that would work for both. I'll take a look when I have some spare time. In the meantime, PRs are welcome :)

@dcelasun Just realized this will only work if you use code . from terminals, but the current .desktop file point straight to /opt path so this won't work.

Maybe change the exec path to /usr/bin/code as well, or is there a reason to start with the main bin?

@n0k0m3 thanks, that looks like a good approach. I can add it with the next version.

Can we have launch script similar to google-chrome* AUR packages for wayland/user option parsing?

Current version of script I'm using for /usr/bin/code

#!/bin/bash

XDG_CONFIG_HOME=${XDG_CONFIG_HOME:-~/.config}

# Allow users to override command-line options
if [[ -f $XDG_CONFIG_HOME/code-flags.conf ]]; then
   CODE_USER_FLAGS="$(cat $XDG_CONFIG_HOME/code-flags.conf)"
fi

# Launch
exec /opt/visual-studio-code/bin/code $CODE_USER_FLAGS "$@"

FYI, I found this: https://github.com/microsoft/vscode/pull/135191

So for anyone looking for a solution in the future, you'll likely need to modify ~/.vscode/argv.json but first that PR needs to be merged and a new version needs to be released. :)

@dipunm i can't help you with the config but i'm just using a wrapper script which calls vscode with the parameters. an alias would work, too...

I am trying to get vscode running in wayland mode.

I was able to run the following command: code --enable-features=UseOzonePlatform --ozone-platform=wayland

However I can't get it to run with these args as default using a flag file. I have tried the following:

.config/electron-flags.conf .config/electron12-flags.conf .config/electron13-flags.conf .config/code-flags.conf

(I checked the about dialog, it says it is running electrum 13)

Has anyone been able to set this up? Context: https://wiki.archlinux.org/title/Visual_Studio_Code#Running_natively_under_Wayland

Doesn't work with i686

$ cd /home/mocambo/.cache/yay/visual-studio-code-bin
$ makepkg -si
==> Making package: visual-studio-code-bin 1.63.2-1 (E 24 jaan  2022 02:40:14)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found visual-studio-code.desktop
  -> Found visual-studio-code-url-handler.desktop
  -> Found visual-studio-code-workspace.xml
  -> Found code_ia32_1.63.2.tar.gz
==> Validating source files with sha256sums...
    visual-studio-code.desktop ... Passed
    visual-studio-code-url-handler.desktop ... Passed
    visual-studio-code-workspace.xml ... Passed
==> Validating source_i686 files with sha256sums...
    code_ia32_1.63.2.tar.gz ... Passed
==> Extracting sources...
  -> Extracting code_ia32_1.63.2.tar.gz with bsdtar
==> Removing existing $pkgdir/ directory...
==> Entering fakeroot environment...
==> Starting package()...
install: cannot stat '/home/mocambo/.cache/yay/visual-studio-code-bin/src/VSCode-linux-ia32/resources/completions/bash/code': No such file or directory
==> ERROR: A failure occurred in package().
    Aborting...

You should add "Provides: vscode" in the PKGBUILD, just like "code-oss" in the arch linux official repository.

@dcelasun @suienzan Thanks! :)

@suienzan, @francoism90: I've added those files, thanks for letting me know.

@dcelasun I assume that @francoism90 is talking about the bash-completion and zsh-completions. There are completion definitions under resources/completions/ in vscode source. The code package in community repo set the @@APPNAME@@ and then install them.

ETA: Resolved by completely removing and reinstalling. Leaving the rest of my comment for the next person.

After updating to 1.61.1-1, I can no longer open code on any folder. I tried moving my Code folder from ~/.config to start fresh, no joy. I've since installed appmenu-gtk-module and no difference. Some suggestions on Stack Overflow indicate I should set DISPLAY in my shell, which didn't make a difference. I'm running Plasma 5.22.5. code was operational on the prior package version.

Here is me opening an arbitrary folder in verbose mode. Anybody else running into this?

❯ code --verbose launch4j
Gtk-Message: 09:05:32.674: Failed to load module "appmenu-gtk-module"
[24287:1016/090532.805774:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process.
[main 2021-10-16T13:05:32.831Z] Starting VS Code
[main 2021-10-16T13:05:32.832Z] from: /opt/visual-studio-code/resources/app
[main 2021-10-16T13:05:32.832Z] args: {
  _: [ '/home/jsimon/Dropbox/Development/launch4j' ],
  diff: false,
  add: false,
  goto: false,
  'new-window': false,
  'reuse-window': false,
  wait: false,
  help: false,
  'list-extensions': false,
  'show-versions': false,
  version: false,
  verbose: true,
  status: false,
  'prof-startup': false,
  'no-cached-data': false,
  'prof-v8-extensions': false,
  'disable-extensions': false,
  'disable-gpu': false,
  telemetry: false,
  debugRenderer: false,
  logExtensionHostCommunication: false,
  'skip-release-notes': false,
  'skip-welcome': false,
  'disable-telemetry': false,
  'disable-updates': false,
  'disable-keytar': false,
  'disable-workspace-trust': false,
  'disable-crash-reporter': false,
  'crash-reporter-id': 'id removed',
  'skip-add-to-recently-opened': false,
  'unity-launch': false,
  'open-url': false,
  'file-write': false,
  'file-chmod': false,
  'driver-verbose': false,
  force: false,
  'do-not-sync': false,
  trace: false,
  'force-user-env': false,
  'force-disable-user-env': false,
  'open-devtools': false,
  __sandbox: false,
  'no-proxy-server': false,
  'no-sandbox': false,
  nolazy: false,
  'force-renderer-accessibility': false,
  'ignore-certificate-errors': false,
  'allow-insecure-localhost': false,
  logsPath: '/home/jsimon/.config/Code/logs/20211016T090532'
}
[main 2021-10-16T13:05:32.834Z] Resolving machine identifier...
[main 2021-10-16T13:05:32.834Z] Resolved machine identifier: id removed
[main 2021-10-16T13:05:32.835Z] Main->SharedProcess#connect
[main 2021-10-16T13:05:32.855Z] StorageMainService: creating global storage
[main 2021-10-16T13:05:32.856Z] lifecycle (main): phase changed (value: 2)
[main 2021-10-16T13:05:32.857Z] windowsManager#open
[main 2021-10-16T13:05:32.858Z] windowsManager#open pathsToOpen [
  {
    workspace: { id: '4885d14bb4de934a00dd04311d4fceda', uri: [g] },
    exists: true
  }
]
[main 2021-10-16T13:05:32.860Z] IPC Object URL: Registered new channel vscode:5f5db832-238c-48f3-bc97-b897dbac9814.
[main 2021-10-16T13:05:32.860Z] window#validateWindowState: validating window state on 1 display(s) { mode: 0, x: 0, y: 36, width: 1024, height: 768 }
[main 2021-10-16T13:05:32.861Z] window#validateWindowState: 1 monitor working area { x: 0, y: 36, width: 1920, height: 978 }
[main 2021-10-16T13:05:32.861Z] window#ctor: using window state { mode: 0, x: 0, y: 36, width: 1024, height: 768 }
/dev/fd/3: No such file or directory
Server response:

@francoism what do you mean by completion? Be specific please.

@dcelasun Could you please add completion as seen in the code PKG? :)

Anyone can tell me why my config is empty? 0.0

Fonts looks ugly and i cant fix it.

@Maverick good idea, done.

An optional dependency "org.freedesktop.secrets" should probably be added as it is required for sync to work.

@SebastianWae sorry, this package follows upstream as closely as possible. If you'd like this change made, you can open an issue here.

Could the code binary be wrapped to make it follow the flags set in ${XDG_CONFIG_HOME}/electron-flags.conf?

This would be nice for wayland users and make it more consistent with other packages of vscode.

https://wiki.archlinux.org/title/Visual_Studio_Code#Running_natively_under_Wayland

https://wiki.archlinux.org/title/wayland#Electron

https://github.com/archlinux/svntogit-community/blob/packages/electron/trunk/electron-launcher.sh

Heads up to the maintainer, I ran into https://github.com/microsoft/vscode/issues/128331 following an upgrade from 1.57.1-1 to 1.58.2-1. The issue was resolved with the chmod referenced in the release notes for the upcoming 1.59 release:

sudo chmod 4755 /opt/visual-studio-code/chrome-sandbox

I suspect this change may need to be integrated into the PKGBUILD.

armv7h version has a bug

uname -m
armv7l

./code
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
Server response: 
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
Server response: 
[main 2021-06-09T19:00:35.908Z] update#setState idle
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
Server response: 
Server response: 
Server response: 
[10632:0609/220038.270642:FATAL:gpu_data_manager_impl_private.cc(415)] GPU process isn't usable. Goodbye.
Server response: 
Server response: 
Trace/breakpoint trap

googling "sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:CRASHING:seccomp-bpf failure in syscall 0403" shows this bug appear in recent chromium that is compiled for 32 bit architecture. armv7h is a 32 bit arch. Visual-studio-code uses chromium as a web engine for own gui.

To display the debugger fonts properly, dependency noto-fonts is required. before: <img alt="" src="https://imgur.com/OpQ0Eiy.png" /> after: <img alt="" src="https://imgur.com/LkpD33D.png" />

@edoantonioco all AUR packages assume you already have the base-devel group installed. Run pacman -S base-devel and try again.

It doesnt work It shows this:

==> ERROR: Cannot find the strip binary required for object file stripping.

@Remisa I don't have that package installed and this package installs fine. It sounds like a problem with your AUR helper, you should report it to them.

@dcelasun I got dependency error from yay while installing this package and after installing it manually and tried again, it worked.

@Remisa what is it needed for?

@dcelasun cool, thanks!

Regarding the wayland detection, probably that won't be implemented upstream (Chromium), for Chromium & Chrome we still rely on an ArchLinux-specific hack or on bash aliases :)

@alumni thanks! I've pushed a fix for the WM class. As for Wayland detection, I think that's better suited as a feature request upstream :)

WM_CLASS is Code instead of code.

Seems that the case is irrelevant under XWayland, but if you run it under Wayland with --enable-features=UseOzonePlatform --ozone-platform=wayland, the windows will not be grouped and they won't have an icon. Changing to StartupWMClass=Code would fix this.

Also, cool to have: if $XDG_SESSION_TYPE is wayland, it would be nice to add those flags automatically :)

Several errors are thrown when starting vscode and a black window appears :

[74124:0503/224332.626557:ERROR:gl_utils.cc(314)] [.RendererMainThread-0x27c5f87ca500] GL_INVALID_OPERATION: Program not linked.
[74124:0503/224332.627021:ERROR:gl_utils.cc(314)] [.RendererMainThread-0x27c5f87ca500] GL_INVALID_OPERATION: Program object expected.
[74124:0503/224332.628433:ERROR:gl_utils.cc(314)] [.RendererMainThread-0x27c5f87ca500] GL_INVALID_OPERATION: Program not linked.
[74124:0503/224332.628696:ERROR:gl_utils.cc(314)] [.RendererMainThread-0x27c5f87ca500] GL_INVALID_OPERATION: Program object expected.
[74124:0503/224332.628813:ERROR:gl_utils.cc(314)] [.RendererMainThread-0x27c5f87ca500] GL_INVALID_OPERATION: Program object expected.

This error seems connected to this bug https://bugs.chromium.org/p/chromium/issues/detail?id=1000938, simply adding --disable-gpu when starting vscode solves the problem.

@crepererum done, thanks for letting me know.

Please add xdg-utils (which provides the xdg-open binary) as an optional dependency. Otherwise, vscode cannot open browser links (e.g. when clicking on Help > Join us on twitter, when logging into github/microsoft for settings sync, when clicking on "view privacy policy", etc.).

@dcelasun thanks! I'm new to arch and thought pacman was a one stop shop for all; I learnt to use makepkg

@gatmnear: It's a git URI, you are not meant to send an HTTP request to it. Try git clone https://aur.archlinux.org/visual-studio-code-bin.git

the git clone link is empty; "HTTP request sent, awaiting response... 404 Not Found"

@heftig: Thank you for that point, I wasn't aware of that hook and the install script.

@dcelasun: Thanks for adding my changes. And thank you for committing the fixes.

@heftig thanks, I should have reviewed it before merging. It's fixed now.

The mime change is broken. post_install would have to exist in the install script, not the PKGBUILD. As is, it has no effect.

In any case, it's unnecessary as the shared-mime-info package contains a hook that automatically rebuilds the database when a package contains a file matching usr/share/mime/packages/*.xml .

So you can remove the post_install function.

@NeedleNardleNoo I pulled your commit in, thanks!

The deb and rpm packages currently have installation scripts that register *.code-workspace files as a mime type. I have added this functionality in the following commit on GitHub: https://github.com/conradhaupt/aur-visual-studio-code-bin/commit/61d3be3d042c206409b725f0290c03eab8785e6a

This allows VSCode to be the default program for workspaces but not all text/plain files and directories, as indicated by the bundled .desktop file.

I am currently merging changes from this AUR package with this commit on every release for my personal use. @dcelasun, you may use the commit and its changes if you feel it will be useful to visual-studio-code-bin.

Sometimes the CDN has issues, try again a bit later.

curl: (28) Failed to connect to az764295.vo.msecnd.net port 443: Connection timed out

From Indonesia, what do you think?

It's no bother at all! I've updated the package to avoid an extra redirect :)

@dcelasun I was debugging your package, cause i wasnt being able to download due to a network problem, and i noticed that https://vscode-update.azurewebsites.net/ was responding with http 301 and redirecting to https://update.code.visualstudio.com/. Thats why i asked. Sorry to bother you.

@pdimh: I wasn't aware of that domain. I do know that vscode-update.azurewebsites.net is an official Microsoft domain for vscode. But I'll switch it over to avoid a double redirect.

@dcelasun i was meaning update.code.visualstudio.com, doesnt seems region-dependant. But its ok, thanks.

@pdimh no. These URLs are generic on purpose, the actual locations are region-dependant and might change over time.

@dcelasun firstly, thanks for your job. binary urls in PKGBUILD return a http 301 status. Isnt it safer to change to the current url?

OK so it does conflict with code from community. I've added it back.

error: failed to commit transaction (conflicting files)
visual-studio-code-bin: /usr/bin/code exists in filesystem (owned by code)

FYI,

This package allows using the new python language server pylance. An unofficial build from the community repo it doesn't.

https://github.com/microsoft/pylance-release/issues/483

@tomatopeel clone the git repo (https://aur.archlinux.org/visual-studio-code-bin.git), switch to an older commit, run updpkgsums (from the pacman-contrib package) and install with makepkg -si.

@Nehu I've removed the conflict with code. Let me know if there are any issues.

I have the same issue as DonJogi here. (for ctrl+f people like me: InitializeSandbox())

There seems to be something broken between keepassxc and vscode. I used the secret service integration but if I have it and keepassxc running then vscode crashes on startup. I fixed this by removing the vscode sync entry in keepassxc and then it worked again even after syncing it again. Weird...

thanks the one one in the community repo has a signing issue, it just stuck on loading for me, but this version seem to have fixed that and managed to sync my settings.

I want to install an older version because the new version is performing worse for me, so I need to test if that is the problem.

When I try to install any older major version, I get e.g.:

==> Validating source_x86_64 files with sha256sums...
    code_x64_1.52.0.tar.gz ... FAILED
==> ERROR: One or more files did not pass the validity check!

How can I install an older version? Cheers

Would it be possible to not mark this package as conflicting with code?

As far as I'm aware, the OSS version and this one do not share the same config folder (~/.config/Code vs ~/.config/Code OSS).

Removing the "conflicts" statement would allow a parallel installation of both, which in turn is useful for using this binary release for C# development (in a properly secured environment) and the OSS release (in a more flexible environment) for everything else.

No crashes here either.

@cusidawgs it's not crashing for me. Perhaps you should report it upstream?

Is it just me or the new version crashes on my installation. Followed all steps on the pinned comment and deleted every vscode configuration folder, yet the problem still persists

Thank you @bulletmark. I'm not using yay, but the package cache was the issue.

Also refer to the stickied FAQ please, particularly the third bullet point.

@mcmar, delete the cached file, e.g rm -rf ~/.cache/yay/visual-studio-code-bin then run yay again.

@mcmar I've pushed a new release with updated checksums. Did you try installing 1.53.1-2?

@dcelasun I don't understand. You said it "should be fine now" and then said "read the comment below". I read all the comments and it's not fine. The package update still fails. What's the fix?

@dcelasun thanks!

@GeneralPoxter read the comment below.

I got the following error:

==> Validating source_x86_64 files with sha256sums...
    code_x64_1.53.1.tar.gz ... FAILED
==> ERROR: One or more files did not pass the validity check!
error downloading sources: visual-studio-code-bin

@emptyDir looks like they've replaced the x64 package without releasing a new version. Should be fine now.

Looks like the PKGBUILD has an incorrect checksum for the x86_64 package:

 ==> Validating source_x86_64 files with sha256sums...
    code_x64_1.53.1.tar.gz ... FAILED

From PKGBUILD:

sha256sums_x86_64=('1ca01ed57ae47b3bf25eaac185e64102e78810caa2df6d14fc233beb1d8d7103')

Downloaded the package manually and compared the checksum to the version downloaded by makepkg, and they seem consistent, but don't match the above:

$ sha256sum code_x64_1.53.1.tar.gz 
23c93a7bf6ceed346f9f2034b4630d8d497dcc3f4b9cce6b67f08f8d272e1530  code_x64_1.53.1.tar.gz

$ sha256sum ~/Downloads/code-stable-x64-1613044905.tar.gz 
23c93a7bf6ceed346f9f2034b4630d8d497dcc3f4b9cce6b67f08f8d272e1530  /home/emptyDir/Downloads/code-stable-x64-1613044905.tar.gz

EDIT: I think it was caused by firejail. I enabled firejail for every program with #firecfg. Cleaning with #firecfg --clean and vs code started after right click -> open with.

Although one or two months ago, the problem did not exist.

When visual-studio-code-bin is closed, are you guys able to open a file by right clicking it and selecting open with vs code?

Nothing happens, when I do that. Kate opens fine.

If I have vs code open, I can right click and select open with vs code and everything works, as supposed to.

EDIT: more specific, text files are fine, json for example not.

@dcelasun, note you don't have to bump the pkgrel. Just push the commit. Anybody who already has it installed isn't affected because the built package is the same version anyhow.

@Magissia sure, but I don't want to bump pkgrel just for that, so I'll add it with the next release.

Could you consider adding a "pentium4" architecture to the pkgbuild ? This architecture would still use ia32 archive for installation.

arch variable would need to be modified to arch=('x86_64' 'i686' 'pentium4' 'aarch64' 'armv7h')

Additional source need to be added :

source_pentium4=(code_ia32_${pkgver}.tar.gz::https://vscode-update.azurewebsites.net/latest/linux-ia32/stable)

Additional instruction for package() is required : if [ "${CARCH}" = "pentium4" ]; then _pkg=VSCode-linux-ia32 fi

If for any reason Microsoft stop providing the ia32 archive, both i686/pentium4 should be removed.

Context https://bbs.archlinux32.org/viewtopic.php?pid=7714#p7714

Thank you.

The SHA is wrong for x64, should be 8c30fddfab0b403b68b8151e79a3c2ccb4a3d44ba8e063c0f957f901165e72cd

options=('!strip')?

@enkeyz AUR packages assume you already have the base-devel group installed. Run pacman -S base-devel and try again.

yay giving me error when trying to install: "ERROR: Cannot find the strip binary required for object file stripping."

Please add to PKGBUILD: options=('!strip')

This will speed up packaging significantly.

It is a handy option when repackaging binary.

Thanks @ItachiSan and @TheCycoONE, I've updated the PKGBUILD.

Hi @cdelasun,

As @TheCycoONE has mentioned, there are some issues with the sources definition. Sources in the source array (not the _ARCH ones) are used for all architectures, while architecture specific ones will be used on the specific architecture.

With this said you can improve the PKGBUILD in this way:

diff --git a/PKGBUILD b/PKGBUILD
index 1e1ee8d..9801312 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -14,38 +14,18 @@ conflicts=('code')
 depends=(libxkbfile gnupg gtk3 libsecret nss gcc-libs libnotify libxss glibc lsof)
 optdepends=('glib2: Needed for move to trash functionality'
             'libdbusmenu-glib: Needed for KDE global menu')
-source=(code_x64_${pkgver}.tar.gz::https://vscode-update.azurewebsites.net/${pkgver}/linux-x64/stable
-               ${_pkgname}.desktop ${_pkgname}-url-handler.desktop)
-
-
-source_x86_64=(code_x64_${pkgver}.tar.gz::https://vscode-update.azurewebsites.net/latest/linux-x64/stable
-               ${_pkgname}.desktop ${_pkgname}-url-handler.desktop
-               )
-source_aarch64=(code_arm64_${pkgver}.tar.gz::https://vscode-update.azurewebsites.net/latest/linux-arm64/stable
-               ${_pkgname}.desktop ${_pkgname}-url-handler.desktop
-               )
-source_armv7h=(code_armhf_${pkgver}.tar.gz::https://vscode-update.azurewebsites.net/latest/linux-armhf/stable
-               ${_pkgname}.desktop ${_pkgname}-url-handler.desktop
-               )
-source_i686=(code_ia32_${pkgver}.tar.gz::https://vscode-update.azurewebsites.net/latest/linux-ia32/stable
-              ${_pkgname}.desktop ${_pkgname}-url-handler.desktop
-              )
-
-sha256sums=('e08e5826afdb838cb3a04d9f13d2161f3d7219884b85fcfe133401fbb415dda1'
-            '0deefcb638e06c35a52e7e9fb8e19b2dc393f01e5c1c122d2938cddeb22cf8de'
+source=(${_pkgname}.desktop ${_pkgname}-url-handler.desktop)
+source_x86_64=(code_x64_${pkgver}.tar.gz::https://vscode-update.azurewebsites.net/latest/linux-x64/stable)
+source_aarch64=(code_arm64_${pkgver}.tar.gz::https://vscode-update.azurewebsites.net/latest/linux-arm64/stable)
+source_armv7h=(code_armhf_${pkgver}.tar.gz::https://vscode-update.azurewebsites.net/latest/linux-armhf/stable)
+source_i686=(code_ia32_${pkgver}.tar.gz::https://vscode-update.azurewebsites.net/latest/linux-ia32/stable)
+# This generates cleaner checksums
+sha256sums=('0deefcb638e06c35a52e7e9fb8e19b2dc393f01e5c1c122d2938cddeb22cf8de'
             'be3d123aacd575d8f836728266eb421ea70399d713d1fc30378dbc5602b519fb')
-sha256sums_x86_64=('e08e5826afdb838cb3a04d9f13d2161f3d7219884b85fcfe133401fbb415dda1'
-                   '0deefcb638e06c35a52e7e9fb8e19b2dc393f01e5c1c122d2938cddeb22cf8de'
-                   'be3d123aacd575d8f836728266eb421ea70399d713d1fc30378dbc5602b519fb')
-sha256sums_i686=('64360439cc2fa596838062f7e6f9757b79d4b775a564f18bad6cbad154bf850c'
-                 '0deefcb638e06c35a52e7e9fb8e19b2dc393f01e5c1c122d2938cddeb22cf8de'
-                 'be3d123aacd575d8f836728266eb421ea70399d713d1fc30378dbc5602b519fb')
-sha256sums_aarch64=('657dc3190e44095efe283e9c2b776c68fffaf6ad6675db13dca173f918701001'
-                    '0deefcb638e06c35a52e7e9fb8e19b2dc393f01e5c1c122d2938cddeb22cf8de'
-                    'be3d123aacd575d8f836728266eb421ea70399d713d1fc30378dbc5602b519fb')
-sha256sums_armv7h=('b5003b3a87ef57f508996fa85e3ea285ac942f69734a68ddc889386f3ec2a244'
-                   '0deefcb638e06c35a52e7e9fb8e19b2dc393f01e5c1c122d2938cddeb22cf8de'
-                   'be3d123aacd575d8f836728266eb421ea70399d713d1fc30378dbc5602b519fb')
+sha256sums_x86_64=('e08e5826afdb838cb3a04d9f13d2161f3d7219884b85fcfe133401fbb415dda1')
+sha256sums_i686=('64360439cc2fa596838062f7e6f9757b79d4b775a564f18bad6cbad154bf850c')
+sha256sums_aarch64=('657dc3190e44095efe283e9c2b776c68fffaf6ad6675db13dca173f918701001')
+sha256sums_armv7h=('b5003b3a87ef57f508996fa85e3ea285ac942f69734a68ddc889386f3ec2a244')


 package() {

The multiarch handling seems slightly off, on aarch64 it downloads and extracts both the x64 and arm64 versions, and the shared files are checked multiple times.

The end result works, but I think only the non-arch files (.desktop files) belong in source=, and they shouldn't be repeated in the source_arch sections.

With version 1.50.1 I've added ARM builds to this package. I don't have an ARM system to test with so let me know if you see any issues.

The current version of this package only supports x64, not the (new) arm or arm64/aarch64 builds of VSCode. I had no issues using the official tar.gz for 1.50 from https://aka.ms/linux-arm64 on a Pinebook Pro (aarch64).

To anyone get this error:

:: (1/1) Parsing SRCINFO: visual-studio-code-bin
==> ERROR: PKGBUILD contains CRLF characters and cannot be sourced.
error downloading sources: visual-studio-code-bin

Use command git config --global core.autocrlf false and delete ~/.cache/yay/visual-studio-code-bin might help

Pretty common for people to hardcode for Ubuntu.

@alosarjos I'd say that's a bug with their tool. Instead of checking a hardcoded path they should look for the code binary in $PATH. I'd report it upstream.

I was checking the official binary install paths. Seems to be different than this package. The official Ubuntu .deb seems to install on /usr/share/code.

In the case of the Flutter framework, their doctor tool to check if VSCode is correctly installed has the /usr/share/code/bin/code path hardcoded to check if it's installed on the system, so it doesn't detect the installation from this package.

While this is a minor thing that won't stop Flutter from working with Flutter, I don't know if this could lead to another frameworks or tools problems that need to detect if VSCode is installed using the expected binary path from the official packages.

PD: Thanks a lot for maintaining this package.

I get the following error when I try to download it using yay: curl: (7) Failed to connect to az764295.vo.msecnd.net port 443: Verbindungsaufbau abgelehnt (Translation: Connection refused)

@samueldy I think you have a corrupted package. I don't see any CRLF characters:

$ grep -U $'\015' visual-studio-code-bin/PKGBUILD
$

Updating via yay -Syu gives the error:

:: (1/1) Parsing SRCINFO: visual-studio-code-bin
==> ERROR: PKGBUILD contains CRLF characters and cannot be sourced.
error downloading sources: visual-studio-code-bin

Navigating to the downloaded package directory (~/.cache/yay/visual-studio-code-bin for me), running dos2unix on PKGBUILD and the two .desktop files, and running makepkg -i worked for me.

I've tried updating from 1.47.0.1 -> 1.47.1.1 using yay today. Updating failes:

curl: (6) Could not resolve host: update.code.visualstudio.com
==> ERROR: Failure while downloading https://vscode-update.azurewebsites.net/1.47.1/linux-x64/stable
Aborting...
Error downloading sources: visual-studio-code-bin

Same thing happens if I run makepkg -si on the tarball.

I've tried to update this package (pkgver 1.41.1) several times over several days in the last week or so and every time the download times out. I can't even download directly.

wget https://update.code.visualstudio.com/1.41.1/linux-x64/stable/code_x64_1.41.1.tar.gz
HTTP request sent, awaiting response... 404 Not Found

Anyone have similar issues?
Is there an alternative URL?
Any ideas whatsoever welcome.

@emke Thanks, can confirm that it failed on pamac, but works with yay

@lordflaron after the latest pamac update, I no longer get that error.

@lordflaron then that's a problem with pamac. Please read the pinned Frequently Asked Questions.

@dcelasun I'm using the pamac GUI with air support

@lordflaron that file is definitely in the package. How are you installing this package, with an AUR helper?

Hi, I'm getting this error when building:

ERROR: visual-studio-code.desktop was not found in the build directory and is not a URL.

shrug yea, maintainers rarely wanna co-maintain (even me back when I was doing it).

@Det Yep, I can do the actual download and replace with the actual checksum just as easily, but doing an extra git commit and push would allow me to share it, just wanted to check if that was an option.

@mixedCase, well.. on quick glance looks like you could maintain this locally with:

pkgver=$(curl -sL https://code.visualstudio.com/updates | grep -Pom1 "version \K[^)]*") # cut up from after "version " to the first ")" ("<h1>April 2020 (version 1.45)</h1>"), -m1: use only first result
pkgrel=1 # reset
sha256sums[0]='SKIP'

Put it at the end of the PKGBUILD, and it's a portable piece of text that doesn't even conflict with anything.

@dcelasun Yes, and thank you for keeping it within reasonable bounds all this time!. I'm offering because I update packages within the hour (usually less), since I automate new release checks to fire an e-mail usually before an user files the package as out of date, edit the PKGBUILD, make some quick tests and ship it.

As for my personal reason, I've been working with VS Code much more often recently and the damned gear with the notification gets on my nerves, but I understand being hesitant.

Let me know if you do change your mind :)

@mixedCase thanks for the offer! Over the years I've managed to keep this updated within hours of release. I'll ping you if that becomes untenable in the future.

Hi @dcelasun. I've been using your package for, well a couple of years now. I've noticed that MS tends to release updates during my office hours, making it practical for me to help out making version bumps shortly after releases occur. Would you accept a co-maintainer?

@Nowaker https://aur.archlinux.org/packages/visual-studio-code-insiders/

Would you mind creating visual-studio-code-insiders-bin? The Insiders version of the package would be very similar to this one - only pointing to a different URL, and having sha256sums=SKIP since Insiders is a daily build. Thank you.

@op3 done, let me know if it doesn't work as expected.

The upstream code package is providing a .desktop file that includes a “New Empty Window” option. I find this very useful and would appreciate if you introduced this feature to the .desktop file provided with this package.

@Xaekai I'm not sure how up-to-date this page is, but Micrososft maintains such a list here.

I request that "proprietary features" in your FAQ be linkified to an enumeration of those features if possible. Thank you.

Wow, ok, cool. Does that warrant like a FAQ mention?

@Det this package is the official build from Microsoft and can use the name "Visual Studio Code". The package in community is an unofficial build and isn't allowed to use Microsoft branding so it's only called "code".

So wait, what was the reason again this had a different name from community/code?

@dcelasun @jaysistar

I was the maintainer of vscodium-bin-multiarch. I have now added ARM support into vscodium-bin and deleted my package.

From now, vscodium-bin supports ARM and ARM64.

@dcelasun Thanks! I'd like Microsoft to support ARM64, but I'll use Codium until they do.

@jaysistar this package is only for the official binaries from Microsoft, which doesn't support ARM. Until it does, you can try vscodium-bin-multiarch.

Please update this package to work with aarch64.

@fifthecho, please don't do that. That's what the flag button is for.

1.14.1 is out which has a SHA256 SUM for me of:

2a2353ea85b5a3d729e0134ff36b29461bb4264b708786e2486927b7f3c06601  code-stable-1576682093.tar.gz

@dcelasun I also experienced the issue mentioned by @bike-bill In my case my VSCode can't be launched from rofi launcher, which launch /opt/visual-studio-code/code. Running it from CLI got the same error.

But, it's working and opened without error if I launch /opt/visual-studio-code/bin/code

@dcelasun I think I somehow deleted my original message that you responded to. My issue is this: I first noticed my Dash icon was not launching Code. When I start from the command line from /opt/visual-studio-code I get:

$ ./code [18860:1114/105201.766613:FATAL:setuid_sandbox_host.cc(157)] 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. Trace/breakpoint trap (core dumped)

Executing

sudo chmod 4755 /opt/visual-studio-code/chrome-sandbox

fixes the issue.

@bike-bill This package doesn't set the SUID bit (so 0755) but I don't see any errors.

$ ls -alh /opt/visual-studio-code/ | grep sandbox
-rwxr-xr-x 1 root root 231K Nov  8 10:07 chrome-sandbox

I'm not sure if this is an upstream issue or a packaging one, but none of the hover tooltips work for me with this package. They do work with the open source package in community. Anybody else having this issue?

jplatte,

You're doing G-d's work. :D Thanks for helping to get us one step closer to a world in which people no longer use the which program.

Seems like the which dependency will be removed in the next release :)

I opened a PR to get rid of the which dependency: https://github.com/microsoft/vscode/pull/82097

@farseerfc good point! I've updated this package and visual-studio-code-insiders.

@dcelasun which is in base-devel which means that is assumed to be installed where makepkg is run. But we cannot safely assume the machine/environment runs makepkg is the same machine/environment that installs the package. In other words, base-devel is assumed to be in the makedepends array of all AUR packages, but not the depends array. If a program needs something from base-devel in runtime, I think that package should be added to depends.

@dcelasun

Oh, which is indeed in base-devel. maybe because base package replace, which and some packages marked unused packages (orphans) by pacman -Qdt... ( and I uninstalled these...

I think I need reinstall base-devel Please ignore my previous comment (XD

@akiirui, which is in the base-devel group which is assumed to be installed by all AUR packages.

There is somrthing that wasn't noted in arch wiki is that the "code" default Community repo can't run bash profile commands. When I installed NVM and then installed nodejs with it, node and npm commands can't be run in tasks.json or launch.json, you can only run those commands in integrated terminal. Although, this official visual code build runs those commands in tasks and launch.json without problems.

If you use NVM, flutter... I recommend you to use this package.

Seems like more people should know this bin package tracks their telemetry and sends it back to Microsoft.

To remove that caveat people should us vscodium-bin https://vscodium.com/

Just learned this myself and am switching away.

@brainplot thanks for letting me know. Looks like Electron has already set the default to gio, so I've replaced gvfs dependency with glib2 (which provides gio). Anyone wishing to use other thrash implementations can set ELECTRON_THRASH environment variable as described in the wiki.

The gvfs optional dependency should be removed. As per the wiki (https://wiki.archlinux.org/index.php/Visual_Studio_Code#Unable_to_move_items_to_trash), Electron doesn't necessarily need gvfs to move files to the Trash. An environment variable needs to be set to tell Electron which program to use.

For FREE Skin Warts Solution - https://www.newsworldlab.com/how-can-apple-cider-vinegar-help-you-remove-warts/

FREE FREE GIFTS To WIN :- https://www.newsworldlab.com/

For FREE Skin Warts Solution - https://www.newsworldlab.com/how-can-apple-cider-vinegar-help-you-remove-warts/

FREE FREE GIFTS To WIN :- https://www.newsworldlab.com/

@dehein binutils is in the base-devel group which is mandatory for installing AUR packages. Quoting from the wiki:

Packages in the AUR assume that the base-devel group is installed, i.e. they do not list the group's members as dependencies explicitly.

Please add binutils as dependency

if you want to use docker plugin on kde you need to install gnome-keyring, i suppose it should be also added to dependencies. as it cannot save secrets without it.

I've just pushed 1.36.0 with Electron 4, which doesn't support 32 bit Linux so I've removed it from this package as well. Users on 32 bit systems should stay on the previous version.

I'm on Gnome as well and I don't have this behaviour you are describing. Still, see this reddit thread for a solution.

By the way, this is upstream behaviour, not something specific to the Arch package.

EDIT: I've updated the stickied FAQ with this information.

It doesn't purposefuly try to hijack it, but it does as a side effect of setting it's support for inode/directory. Most editors do support opening folders as well but don't declare it on their .desktop files; so far this has been the only case I have had this happen with an editor (I did have a similar issue when installing multiple file managers though). Also, I did try to use xdg-open (which is DE independent afaik) to make sure it wasn't a gnome specific issue or had something to do with my own configuration before checking the .desktop file and coming here to check if it was a known issue. You own the package so feel free to keep it as it is, just be aware this same issue could happen to more people.

This package doesn't hijack anything. Visual Studio Code can open directories, so the desktop file declares support for it. If your desktop environment makes that the default, there should be a way to change it. If there isn't, that's a problem with that DE, not this package.

Like @noirscape mentioned, this package is hijacking the inode/directory mimetype; the .desktop file provided with the package explicitly sets itself as the application to open folders, which I assume is something most users don't want.

Not entirely sure why this is happening, but for some reason the package ends up prioritizing itself for inode/directory for me, which causes things related to xdg-open to use VS Code.

While I can change it manually back each time by editing the relevant line in /usr/share/applications/mimeinfo.cache, it would be handy if there's some sort of way to repair it without having to do that on each update.

@Gonzalo2683 you can use the same process. Download the package, extract it and install with makepkg -si.

I'm new to arch, I've installed the previous version of visual studio code with the command makepkg -s, how do I update to the latest version?

I'm using deepin and still the old logo

@dcelasun Ah ok, thanks for updating it, I do happen to use xfce.

@dcelasun Ah ok, thanks for updating it, I do happen to use xfce.

@jolan thanks, fixed. Note that code.png is only used as a workaround for an Xfce bug. Other DEs get the icon from upstream.

FYI, the icon was changed but code.png wasn't updated.

https://code.visualstudio.com/updates/v1_35#_updated-visual-studio-code-icon

Spam is being posted a lot nowadays, maybe the devs should add something like re-captcha. :|

wow good information provide this post. happy best post. http://freegiftcardgenrator.com -> http://onlinefreegiftcodesgenerator.com -> http://onlinefreegiftcardgenerator.com -> http://realgiftcardgenerator.com -> http://topvideodownloader.com

@dcelasun Works! The icon is back on the desktop.

@manuelino should be fixed now.

@dcelasun

Thanks for the workaround, but as is it does not work, because the image under hicolor is named "code.png", while the desktop entry refers to it as "visual-studio-code".

Simply renaming the image and updating the icon cache sorts it out. Also, the image has executable bits set (0755 rather than 0644).

@manuelino I've added a workaround, please try with the latest version and report back.

@dcelasun Here is the link to the issue:

https://bugzilla.xfce.org/show_bug.cgi?id=15294

@manuelino, can you link me to that issue? I wouldn't resize it at build time (it would require a dependency), but I'd be willing to ship a static image with the PKGBUILD.

It seems that there is a bug in the current XFCE packages, which causes desktop launchers not to display icons if they are placed under /usr/share/icons and not under a theme. It also breaks if moving the icon under the hicolor theme but under a 1024x1024 directory.

Is there any chance the icon could be resized at build time to 512x512 and installed under the hicolor theme? I understand this is really an issue with the DE (I have reported this to the devs), but this packages is the only one I have seen in a while that does not store the icons under the hicolor theme and that has such a large image.

If this looks feasible, I am willing to provide a patch. Since the proposed path is standardized by the Icon Theme Specification, it should have no negative impact on other DE's.

@cogwerkz Many thanks... I didn't read the FREQUENTLY ASKED QUESTIONS at the top. The FAQ is very useful and it must be red by all users before posting repetitive comments, sorry it was my issue.

@saverio The one in the Community repo is the fully open source version, meaning it only has the open source base, and hasn't got direct access to proprietary elements like the marketplace.

This version has a commercial license, which is something you'll never see on anything in the official repos.

Hi dcelasun, is there any difference between this AUR maintained package and the one available in the official Arch Community repo? (https://www.archlinux.org/packages/community/x86_64/code/)

As far as I can see, both Community and your AUR package have the same version...

I'm on arch 32Bit. I downloaded the snapshot and installed the package with makepkg -sirc. Everything worked fine. If I start either from the menu or with "code" from the terminal it starts but all I get is a blank screen. Did I missed something?

1.33.0-2 works! Thanks @dcelasun.

Sorry, fixed.

:: Searching databases for updates...
:: Searching AUR for updates...
:: 1 Packages to upgrade.
1  aur/visual-studio-code-bin  1.32.3-1 -> 1.33.0-1
==> Packages to not upgrade: (eg: 1 2 3, 1-3, ^4 or repo name)
==> 


install: cannot stat '/home/elgs/.cache/yay/visual-studio-code-bin/src/VSCode-linux-x64/resources/app/LICENSE.txt': No such file or directory
==> ERROR: A failure occurred in package().
    Aborting...
Error making: visual-studio-code-bin

@melkopisi, @HerHde, there are plenty of solutions to this problem, all of them a quick search away. For example:

• https://bbs.archlinux.org/viewtopic.php?id=207725
• https://bbs.archlinux.org/viewtopic.php?id=222344

There should be more for other DEs as well.

Well, about the "inode/directory" link: It interferes with almost every software on my freshly installed system (Manjaro), including Nautilus and Firefox.

butother apps suggest open their file in visual studio code instead from nautilus like Android studio because it has the priority above nautilus to open folders

any idea how to fix this?

@melkopsi, that's needed for opening directories with VS Code. If it interferes with Nautilus, that must be a configuration issue on your end. It works fine for me here.

Please can you stop adding "inode/directory" to the MimeType because it interferes with nautilus?

@albertvaka that has been asked and answered several times, read the comments please.

Why is this package needed now that "code" is in the main repo?

@davidmcinnis, that URL does exist. It works fine for me.

Hash problem seems to be gone now. Just removed the old download and aurget installed vscode just fine.

Thanks to @dcelasun for reporting upstream.

I've reported it upstream: https://github.com/Microsoft/vscode/issues/68621

And what do we do?

@pedromello, thanks for the confirmation. The hash I'm getting from both the Netherlands and UK is 154a316eb6785c126e2fccd80a5c76291321ca2d6945e7a2a13f2e262be89bde. Can someone else from a different country check as well?

EDIT: Checked from USA and Turkey as well, both get the above hash. I'm guessing this is a Latin American mirror issue.

I've got the same hash as @xereda 39e953dc16f248399d286cdca1653345ff32927affc0256ea4a62607f8f5f232 code_x64_1.31.1.tar.gz

I've noticed both me and @xereda are from Brazil (based on the language of the yay output in his post). I this case, @dcelasun hint about a mirror with a different version is valid... and annoying at the same time :)

OK first of all, please don't make multiple comments in succession. Just make one and edit it if necessary.

Secondly, please try without yay (see the stickied FAQ comment, just use makepkg -si). If that still doesn't work, my guess is the mirror you are downloading from has either a corrupted tarball or simply a different version.

@xereda, something must have gone wrong with your download which corrupted the file. Delete it and try again.

$ sha256sum code_x64_1.31.1.tar.gz 
154a316eb6785c126e2fccd80a5c76291321ca2d6945e7a2a13f2e262be89bde  code_x64_1.31.1.tar.gz

Getting the following error while upgrading from 1.30.2-1 -> 1.31.0-2

(OK):download completed.
mv: cannot stat '/tmp/yaourt-tmp-munim/aur-visual-studio-code-bin/stable': No such file or directory
  -> Found visual-studio-code.desktop
  -> Found visual-studio-code-url-handler.desktop
==> Validating source_x86_64 files with sha256sums...
    code_x64_1.31.0.tar.gz ... NOT FOUND
    visual-studio-code.desktop ... Passed
    visual-studio-code-url-handler.desktop ... Passed
==> ERROR: One or more files did not pass the validity check!
==> ERROR: Makepkg was unable to build visual-studio-code-bin.
==> Restart building visual-studio-code-bin ? [y/N]

@dcelasun thanks for your suggestion! I wanted to try this right now, but the new version 1.31.0-2 works great, so it's solved for me. Thanks again!

https://github.com/Microsoft/vscode/pull/65744/files In 1.31.0. gconf no longer needs.

@Donjogi, can you try code --disable-gpu and see if it helps?

I tried to install visual-studio-code-bin today freshly with yay on KDE Plasma 5.14.5. On startup the app crashes before showing a window with the following stacktrace. I double-checked the current "code" arch package which works out of the box.

Any hint if I can solve this by myself?

$ code --verbose
[21302:0204/194114.705115:ERROR:sandbox_linux.cc(344)] InitializeSandbox() called with multiple threads in process gpu-process. [main 7:41:14 PM] Sending env to running instance... [main 7:41:14 PM] [ 'TypeError: Cannot read property \'call\' of undefined', ' at e.onPromise (/opt/visual-studio-code/resources/app/out/vs/code/electron-main/main.js:191:666)', ' at e.onRawMessage (/opt/visual-studio-code/resources/app/out/vs/code/electron-main/main.js:191:326)', ' at /opt/visual-studio-code/resources/app/out/vs/code/electron-main/main.js:190:769', ' at e.fire (/opt/visual-studio-code/resources/app/out/vs/code/electron-main/main.js:123:512)', ' at a (/opt/visual-studio-code/resources/app/out/vs/code/electron-main/main.js:200:948)', ' at Socket._socketDataListener (/opt/visual-studio-code/resources/app/out/vs/code/electron-main/main.js:201:153)', ' at emitOne (events.js:116:13)', ' at Socket.emit (events.js:211:7)', ' at addChunk (_stream_readable.js:263:12)', ' at readableAddChunk (_stream_readable.js:250:11)', ' at Socket.Readable.push (_stream_readable.js:208:10)', ' at Pipe.onread (net.js:594:20)' ]

@noraj code is maintained by the Arch team. It is them taking the VS Code code base and building their own open source version. It is technically an unoffical release of VS Code.

visual-studio-code-bin is the official release by Microsoft repacked to be installed on Arch.

There are advantages and disadvantages to both of them. Most notably, code is open source and visual-studio-code-bin has many of Microsoft's closed source improvements (it works via X11 forwarding for example, whereas most other Electron apps do not).

(at least that is my take on why there would be interest in this one)

Now that there is https://www.archlinux.org/packages/community/x86_64/code/, what is the interest of visual-studio-code-bin ?

https://github.com/Microsoft/vscode/commit/ffe6f7950ec123b533f6aec85b7b770ef236e22d Finally gconf will be dropped in next version.

OK, I've restored StartupWMClass.

@dcelasun I agree with @jgierer12.

I haven't been using VS Code for a long time, so my advice for @nix6839 was more in general manner, but after looking into it more I don't think this is upstream issue.

Hi @dcelasun, I don't think this is an upstream issue. The PR you linked removed the StartupWMClass from visual-studio-code-url-handler.desktop, but not from visual-studio-code.desktop. I'm having the same issue as @nix6839 and was also able to fix it by re-adding StartupWMClass=code into the latter file.

@Anty0 I'm not fixed that way either.

@dcelasun I hope to put it in visual-studio-code.desktop. (Ref to https://github.com/Microsoft/vscode/blob/master/resources/linux/code.desktop and https://aur.archlinux.org/cgit/aur.git/tree/visual-studio-code.desktop?h=visual-studio-code-bin)

@nix6839 Try re-add (remove it and add it again) VS Code to your favorites. You probably have added wrong one (the one which was starting before fix).

@nix6839, since that was done on purpose, you should report it upstream.

Please re-add "StartupWMClass". Without it, an error occurs. The error is as follows the dock contains multiple copies of the same icon.

@teohhanhui, thanks for the heads up. This should be working now, e.g xdg-open vscode://file/etc/pacman.conf or xdg-open vscode-insiders://file/etc/pacman.conf for the insiders build.

Please add the code-url-handler.desktop file (visual-studio-code-url-handler.desktop in our case) to support vscode:// URIs. See https://github.com/Microsoft/vscode/pull/56727 and https://github.com/Microsoft/vscode/pull/63750

I'm on Manjaro Deepin, and VS Code cannot access my system-wide $PATH variable. I am not being able to properly debug .net core apps because of that.

On VS Code, "echo $PATH" prints:

/home/matfantinel/.nvm/versions/node/v11.3.0/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/lib/jvm/default/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl:/usr/lib/jvm/default/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl

Which seems to be a default configuration, but doesn't update if I set $PATH outside of it. If I set the variable inside VS Code Terminal, it will reset after restart.

I've noticed this behavior in the Flatpak version of VS Code in Linux Mint once. In that case, installing from the website worked.

For delete to trash to work, this environment variable needs to be set: ELECTRON_TRASH=gio

(or trash-cli, kioclient5, kioclient)

there is new code version build specially for the flatmap-stream https://dev.azure.com/vscode/VSCode/_build/results?buildId=10878&view=logs

version 1.29.1 uses/installs flatmap-stream 0.1.1 for the references-view extension.

If you have installed this package, you should read over https://github.com/dominictarr/event-stream/issues/116#issue-382854428 and determine if you are affected or not.

All right, thanks for voicing your opinions everyone. I've decided to remove pylint as an optdepend in the next version. I also won't be adding any language specific dependencies from now on.

IMO, pylint is an optional dependency for an extension you can install, not for the editor itself, so it probably shouldn't be an optdepend. Optional dependencies for things like trash support definitely make sense because it's an optional editor feature, but I can think of a number of other extensions that also ask for things to be installed (the Go extension prompts to install linters, C/C++ extension asks about clang-format, etc), and I wouldn't personally want those added as optdepends either. If you configure the extension to specify a different linter (flake8/pep8), then it'll show the same prompt but for that other tool too, pylint's just the default. Always running pylint is going to stop being the default in the python extension anyway [1] [2].

[1] https://github.com/Microsoft/vscode-python/issues/974

[2] https://github.com/Microsoft/vscode-python/issues/3007

(Disclaimer, I work on the python team at Microsoft, but this isn't any sort of official opinion or anything. I just noticed the added dep during an update on my personal machine.)

And of course all of this is just my opinion, so feel free to change my mind, if you know something I don't. :)

*But only packages, that can be used by that package without any plugins. (= If visual studio code does not support python without additional plugin, python-pylint should not be added as optdependcy, but if visual studio code support python by default and opening python file shows that warning without installing additional plugin, we should add python-pylint as optdependcy.)

@elgs I think, that optdepends are not about what you want, but about what you may want. So they should contain packages, that can be for someone only "pollution".

Personally, I think, that in optdepends should be every package, which can be used by that package in any way. Also sometimes it is good idea to add as optdependcy package, that is not used by that package, but can make usage of that package significantly easier. (There are lot of examples of that in official Arch Linux packages.)

Personally, I don't mind if there is a ton of optdepends.

I know you don't mind. But other people may see it as pollution. Many people don't like anything which is not necessary for them.

Fair point. You can't just add a ton of optdepends for every eventuality; you need to draw a line somewhere.

I see two main criteria, each of which is a good reason for an optdepends:

1. The package is essential for a basic core functionality ( here 'basic Python support'. VSC complains about this package missing, not about 'pyflakes' )

2. The package is arguably supposed to be installed --asdeps. If there is no package to optdepend on it, then it becomes an orphan as far as Pacman is concerned.

Both rules apply here imo. You could even make a point for XDebug for PHP even though VSC doesn't complain about that one. QtCreator for example has even git, mercury, valgrind etc. as optdepends.

If it gets too much, as it might happen with multi-language editors, then that's rather an argument for splitting the package into multiple optimized ones, like with Eclipse and Netbeans, not for letting the user whack-an-error-message.

Personally, I don't mind if there is a ton of optdepends. Let me know on install what else might be useful in combination with the main package.

I also think adding python specific things as dependency (even optional) is a bad idea.

@Caldazar that's a really bad idea.. VSCode has nothing with Python. So let's add Java, dotnet, and all other languages as a optional dependency -.- That's also does not change anything, so I wonder why that should be a optional dependency. There is also other python linter: pyflakes.

Could you please add 'python-pylint' as an optional depenendcy ( python-pylint: Code analysis for Python )?

As soon as I opened a *.py file, VSC complained "Linter pylint is not installed" and tried to make me install it via pip. It seems to consider it as a must-have for python language support.

I installed it explicitly with pacman but I'd rather have it --asdeps for VSC.

Please change the description in PKGBUILD to:

pkgdesc="Visual Studio Code (vscode): Editor for building and debugging modern web and cloud applications (official binary version)"

This will make searching way easier. Thanks.

@daveshaheen: Thank you for your trick!

Another option instead of modifying /etc/makepkg.conf is to create a ~/.curlrc file with the line --http1.1

It fails when it tries to download v 1.28.0 from https://vscode-update.azurewebsites.net/1.28.0/linux-x64/stable (I'm using pacaur)

However, I could manually download the tar.gz from the above link, insert it on the pacaur cache folder, and the installation was successfully.

@tavuntu, It's the lines starting with http::/usr/bin/curl and https::/usr/bin/curl in the DLAGENTS array in /etc/makepkg.conf.

@dcelasun which line do I add that flag in?

@Chipsterjulien as a temporary workaround, you can edit DLAGENTS in /etc/makepkg.conf and add --http1.1 to the curl command.

Unable to download file:

-> Téléchargement de code_x64_1.28.0.tar.gz… % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 130 100 130 0 0 84 0 0:00:01 0:00:01 --:--:-- 84 0 0 0 0 0 0 0 0 --:--:-- 0:00:02 --:--:-- 0 curl: (16) Error in the HTTP2 framing layer ==> ERREUR : Erreur lors du téléchargement de https://vscode-update.azurewebsites.net/1.28.0/linux-x64/stable

@ghotrix, that's a network on your end. I can download the tarball just fine.

OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to z764295.vo.msecnd.net:443 while trying to install. Does anyone also experienced such an error?

@pascenio, update your whole system first (pacman -Syu) before updating this one.

Hi guys!

I'm trying to update this package but get the following error:

error: the operation could not be prepared (the dependencies could not be satisfied) :: lib32-glibc: installing «glibc» (2.28-4) dependence breaks with «glibc=2.26»

Do you have some workaround for this issue?

@loodoons sorry, no idea. You might try asking on Github.

@dcelasun You're right. It was a GPU issue. Your answer fixed my problem.

Do you know why I've got this issue?
I've installed all the intel graphic drivers.

@loodoons, I can't reproduce the problem. The cli and .desktop launchers are meant to be separate, there have been many problems in the past when using the same one for both cases.

The issue you are seeing sounds like a gpu problem. Can you try replacing:

Exec=/opt/visual-studio-code/code %f

with

Exec=/opt/visual-studio-code/code --disable-gpu %f

and see if that fixes it?

I found a bug that is annoying. When you drag and drop inside the user
interface, Code freeze. There's nothing in the log. This bug only occur when you launch the software with the .desktop file.
So I found a fix.

Just edit this file /usr/share/applications/visual-studio-code.desktop and replace this line

Exec=/opt/visual-studio-code/code %f

with

Exec=/opt/visual-studio-code/bin/code %f

I think there's missing many env var when you launch Code from /opt/visual-studio-code. Can you apply the fix in the package?

Thank you very much,
Guillaume Quittet

https://www.reddit.com/r/archlinux/comments/9enz79/vs_code_is_finally_in_the_official_repos/

The Conflicts package should be changed to 'code'?

@Visione sure, will do so at the next version.

1.27.1 is out now

https://code.visualstudio.com/updates/v1_27

@dcelasun great work, thanks!

Have you thought about including libdbusmenu-glib as an optional dependency? It allows vs code to pass the menu through DBus, makes KDE global menu work.

@adlerdias: Seems to be a Windows-only bug as stated here: https://github.com/Microsoft/vscode/issues/58032#issuecomment-419013555

Nevertheless 1.27.1 is expected to be released pretty soon.

The package has been marked as outdated, but the maintainer must wait until 1.27.1 because of the bug:

https://github.com/Microsoft/vscode/issues/57982

Bug: Dragging files and other draggable items causes complete lock Posted a bug in detail on https://github.com/Microsoft/vscode/issues/57766

Quick Note: this bug only happens when running code from /opt/visual-studio-code/code, and not the ones in /opt/visual-studio-code/bin/code and /usr/bin/code

Not 100% sure if this is a pkgbuild issue or not as I'm not too versed in pkgbuilds (not sure why there are two binaries in the first place?)

@clockface, if I understand that thread correctly, this affects a single key combination and the workaround is non trivial: It introduces a new dependency and even then it doesn't work for everyone. GTK 3.24 is scheduled for release in September, so I'd rather wait a few weeks for that.

But if you or anyone else can come up with a simple, non-invasive patch I'd be happy to take a look.

@dcelasun, any plans for a work around to this issue:

https://github.com/Microsoft/vscode/issues/48480

until gtk 3.24 is released

@LChris314 fixed, thanks!

Thanks for the quick update! I suppose the following two lines should be removed from the PKGBUILD?

14 makedepends=(patchelf)
24 noextract=("glibc-2.27-3-${CARCH}.pkg.tar.xz")

Updated to 1.26.1, which removes the various glibc workarounds and replaces gtk2 with gtk3.

https://www.google.co.uk">google

[url="https://www.google.co.uk/"]google[/url]

[url=https://google.co.uk/]google[/url]

xxxxxxxxxxx

[[http://www.google/|xxxxxxxxxxxxxx]]

(Example: [a=https://google.com/]xxxxxxxxxxxxx[/a])

"xxxxxxxxx":http://www.google.com/

[A=http://www.google.com/]google[/A]

[google]url:http://www.google.co.uk/

[link=http://www.google.com/]google[/link]

"xxxxxxxxx":http://www.google.com/

Thanks for the heads up @orangecake. I will wait another 24 hours before reverting the workarounds and give all mirrors time to catch up, so everyone can update without problems.

glibc 2.28-4 has landed in core. So it seems that all the extra patching logic can be removed. I've been running this without any changes with glibc from testing for quite some days without any issues.

@dogumon, are you using a custom launcher? Because I've added the library override to both the official cli launcher (/usr/bin/code) and the .desktop launcher.

@dcelasun I had to add LD_LIBRARY_PATH=/opt/visual-studio-code/libs to my .desktop file manually (maybe because mine already existed), but otherwise this works fine for me & is much preferable to a manually managed solution. Thank you for updating, glad I could help.

@dogumon, thanks for debugging this.

I've pushed a new pkgrel with private copies of libxml2 and icu. File browser is working for me, but please report any issues you see.

Safe fully-functional workaround for now:

1. Download previous versions of libxml2 and icu
2. Extract usr/lib/* contents from archives somewhere (ie. ~/lib_overrides)
3. Launch code with LD_LIBRARY_PATH=~/lib_overrides code

https://archive.archlinux.org/packages/l/libxml2/libxml2-2.9.8-2-x86_64.pkg.tar.xz
https://archive.archlinux.org/packages/i/icu/icu-61.1-1-x86_64.pkg.tar.xz

This works with the current workaround version of this package & requires no system-wide downgrades.

The issue for me seems to be that while glibc 2.27 is required for electron to not segfault right away, the most recent versions of libxml2 and icu require glibc 2.28 to work properly, which appear to be used for all file browser functionality.
While using the 2.27 workaround, these libraries cause a segfault whenever a file prompt is meant to be displayed.

I had originally tried downgrading all involved packages, and while that made VSCode work again, it however broke my KDE entirely, so I do not recommend it. In case the package maintainer wants to try a workaround (similar to what was done for glibc), these are the packages I downgraded:

1. glibc and lib32-glibc to 2.27-3
2. libxml2 to 2.9.8-2
3. icu to 61.1-1

Again, I do not recommend downgrading these globally as it will break your system.

Until this issue is fixed, you might want to try the experimental Electron 3 build.

Quick workarounds:

1. Use your file manager to navigate to the folder I need to open on, then drag and drop the folder on to vs code.

2. Use the command line to navigate to the directory I want to open, then run the command code .

I'm getting a similar issue. VSCode will crash when trying to bring up any kind of file browser window, ie via File > Open or File > Save. I'm using KDE Plasma if that makes any difference.

Not sure how relevant this is, but I see it while pushing Ctrl+S to bring up the save dialog, immediately before crashing:

[main 8:56:19 PM] windowsService#showSaveDialog 1
(code:2568): Gtk-WARNING **: 20:56:19.087: Could not load a pixbuf from icon theme.
This may indicate that pixbuf loaders or the mime database could not be found.
**
Gtk:ERROR:gtkiconhelper.c:494:ensure_surface_for_gicon: assertion failed (error == NULL): Failed to load /usr/share/icons/Numix/16/status/image-missing.svg: Unable to load image-loading module: /usr/lib/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-svg.so: /opt/visual-studio-code/glibc/usr/lib/libc.so.6: version `GLIBC_2.28' not found (required by /usr/lib/libxml2.so.2) (gdk-pixbuf-error-quark, 5)
Server response: <?xml version="1.0" encoding="UTF-8"

This makes the program pretty much unusable.

I noticed my VS Code was segfaulting when I tried to open it earlier today. I did another update and I got a patch. Then I came here and read about the glibc issue. Everything was fine after the patch.

Until now at least... Now it crashes when I click "Open Folder". I can't get it to run from the command line because it just opens a GUI window right away and control returns to the terminal, but it did say this... I wonder if this means anything:

[mattwelke@mdesklin browser-b2-upload-file-example]$ code --verbose [main 20:46:54] Sending env to running instance... [main 20:46:54] Sent env to running instance. Terminating... [main 20:46:54] Lifecycle#kill() [20468:0814/204654.559987:ERROR:browser_gpu_channel_host_factory.cc(103)] Failed to launch GPU process.

@edoantonioco, you also need to revert the workaround commit from this package if you want to use the system glibc.

But I still don't understand why it doesn't work for you with the bundled 2.27 glibc. Are you sure you are on 1.26.0-2 of this package?

So I went to one of the FTP servers from pacman mirrorlist and downloaded the required glibc-2.28-4, and then installed it locally.

Visual studio code still doesnt work.

@anohigisavay: glibc 2.28-1 is problematic, it breaks electron apps. That's why I have included 2.27 in the PKGBUILD. Either wait for 2.28-4 to hit [core] (which reverts the problematic bits) or use this package with an update system, which should work fine. See previous comments for details.

@viechang: I kinda have the same issue, except GLIBC_2.28 is required by /usr/lib/libsqlite3.so.0 (I have built sqlite-replication from AUR to use lxd).

@dcelasun: No, contrarily, it's because the system is too new. These packages are built with glibc-2.28 but the libc provided by your PKGBUILD is 2.27.

@bulletmark, nice catch! But no, I won't bother with it since fixed glibc will be in [core] very soon.

@dcelasun, I noticed you copied my PKGBUILD except you put back the two _i686 lines which I deleted. If you are going to bother supporting 32 bit then you need to also fix the --set-interpreter line for that case.

Thanks for the quickfix. I want to point out that v1.26.0 is using gtk3 file dialogs. Moreover, namcap says gtk2 is not needed anymore.

@viechang: Update your system.

/opt/visual-studio-code/bin/../code: /opt/visual-studio-code/glibc/usr/lib/libc.so.6: version `GLIBC_2.28' not found (required by /usr/lib/libsystemd.so.0)

The relevant glibc commit in [core] has been reverted. Updating to glibc=2.28-4 will fix it (it's currently in [testing]).

In the meantime, I've pushed a workaround.

@headkase thanks. I was able to download the 1.25.1 into a temp directory and it works.

@elgs to downgrade download the PKGBUILD as normal and then edit it and in the version change 1.26.0 to 1.25.1. Then with MakePkg use the --skipinteg parameter as the PKGBUILD will then download the older version instead of the latest.

@fardog how did you do the downgrade?

@dcelasun here's how other AUR packages for Electron-based apps worked around the glibc segfault:

Skype: https://aur.archlinux.org/cgit/aur.git/commit/?h=skypeforlinux-preview-bin&id=e3fa08c20b44

Slack: https://aur.archlinux.org/cgit/aur.git/commit/?h=slack-desktop&id=9e49accb247d

Here's a temporary PKGBUILD which patches in a private copy of glibc v2.27 until this bug gets fixed: https://gist.github.com/bulletmark/846dca96d4c96d72e1b2d977bb67a8d0

I'm experiencing the same issue, segfault on 1.26.0. Downgrading to the previous version 1.25.1 (git sha of aur package repo is 6d42188) has resolved the issue, so this doesn't appear to be due to some other upgraded system package.

fwiw this is happening on the insiders package as well.

@rawkode and @headkase see this issue: https://github.com/Microsoft/vscode/issues/55934

/usr/bin/code: line 35: 26811 Segmentation fault (core dumped) ELECTRON_RUN_AS_NODE=1 "$ELECTRON" "$CLI" "$@"

v1.26

With 1.26.0-1 I'm getting a segmentation fault on launch. Previous versions worked correctly.

@Marcel_K: You are right, despite the commit being much older than 1.25, it's not in the release for some reason. Reverted to gtk2 and bumped pkgver. The insiders release does have gtk3 though.

@kenokabe: Are you sure that is already included in version 1.25.1? I'm asking because I still see a GTK2 file selector and namcap also says (among other things):

visual-studio-code-bin E: Dependency gtk2 detected and not included (libraries ['usr/lib/libgtk-x11-2.0.so.0', 'usr/lib/libgdk-x11-2.0.so.0'] needed in files ['opt/visual-studio-code/code'])
[…]
visual-studio-code-bin W: Dependency included and not needed ('gtk3')

Dependencies of gtk2 is outdated. As you can see, VSCode shifted from gtk2 to gtk3.

https://github.com/Microsoft/vscode/commit/2e6a761f8c225ae7aad144c071414bb080916ad9

On Manjaro Deepin, the dock icon tends to clear itself from the dock, see: https://github.com/Microsoft/vscode/issues/49183

Under the hood, deepin seems to be using some elements inherited from Gnome. This could be related to that.

This package stores lots of stuff in ~/.config/Code/ that doesn't seem to belong in $XDG_CONFIG_HOME.

In particular:

• Cache/, CachedData/, CachedExtensions/, GPUCache/, logs/ : user-specific cached data should be in $XDG_CACHE_HOME ($HOME/.cache by default)

• 'Local Storage'/, Backups/, User/workspaceStorage/, Cookies, Cookies-journal, machineid : This looks like stuff that belongs in $XDG_DATA_HOME ($HOME/.local/share by default)

• storage.json : I'm not sure about this but it smells fishy :P

For a reference, see https://wiki.archlinux.org/index.php/XDG_Base_Directory_support and https://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html and https://github.com/Microsoft/vscode/issues/3884

The information you share is very useful. It is closely related to my work and has helped me grow. Thank you! http://instagquotes.com

Installing this package changed my xdg default for folders. xdg-open, which is also used by other programs, now opens VS Code for folders instead of my previous default (nautilus).

I don't think a software installation should change defaults. However, I don't know if this is a bug of this package or an upstream bug.

Manually restoring the previous default is possible with: xdg-mime default org.gnome.Nautilus.desktop inode/directory

@spacepluk: Fixed, thanks.

:: Checking visual-studio-code-bin integrity... ==> ERROR: provides contains invalid characters: ',,'

https://github.com/Microsoft/vscode/commit/2e6a761f8c225ae7aad144c071414bb080916ad9

As you can see, VSCode shifted from gtk2 to gtk3.

@Batou: This package follows upstream. Feel free to use other packages and/or a personal settings.json.

There is a massive amount of "telemetry" or spying going on within this package. Much more so than when you build the VSCode yourself (the code in AUR). I suggest to everyone to add some anti-telemetry preferences to their user settings at the bare minimum. You should also add some domain blocks to your hosts file. One of the options that's also problematic is the automatic update which is set by default. You should definitely not be updating from within this application so disable it.

I've created a short guide here: https://ghostbin.com/paste/8tqtz Maybe the maintainer should create ~/.config/Code/User/settings.json with the above defaults for all new installations?

I'm having a problem when I try to open an ASP.NET Core app. I've never had this problem before. In the bottom right corner I get a notification saying:

Some projects have trouble loading. Please review the output for more details.

There's more in the "show more output", including a stacktrace. This gist (https://gist.github.com/welkie/1ab978ff495124700fb8db64d0564364) includes that, along with my versions of "mono" and "msbuild". I didn't have the msbuild package installed yet, but my troubleshooting led me to manually install that to try to solve this. This GitHub issue (https://github.com/OmniSharp/omnisharp-vscode/issues/2267) details the error when I reported it.

Using the C# plugin, I keep getting the following error: "The .NET CLI tools cannot be located. .NET Core debugging will not be enabled. Make sure .NET CLI tools are installed and on the path."

How do I resolve this?

EDIT: I just renamed my "~/.vscode/extensions" directory before changing and then renamed it back, after renaming the newly created one.

@Anty0 I realise that it replaces "visual-studio-code": "Replaces: visual-studio-code". But will the installed extensions be retained. I'm not looking forward to re-installing and re-configuring a lot of extensions. I know where to find my code config file.

@Twiki Just install "visual-studio-code-bin", it automatically replaces "visual-studio-code". Or have you got any problem with it?

Hello,

Is there a "proper" way to go from "visual-studio-code" to "visual-studio-code-bin". Right now I'm editing the 2 "visual-studio-code" installer files feeding makepkg, but it's a bit cumbersome.

@Sanya_M Please search for inode/directory on this link.

Please, remove "inode/directory;" from MimeTypes in the .desktop file. When "inode/directory" is there, Gnome tries to automatically open connected MTP device (phone) in Visual Studio and do other crazy things

Looks like the problem with unresolved symbol is SOLVED. There was a rogue installation of nwjs in /opt on my system. Removed /opt/nwjs and all work again. My bad. Sorry.

Just upgraded to 1.22.0-1. /opt/visual-studio-code/bin/../code: symbol lookup error: /opt/visual-studio-code/bin/../code: undefined symbol: _ZN6icu_588ByteSink15GetAppendBufferEiiPciPi

@Alad, @dotfile: no, when I uninstall c++ addons, it doesn't work. And now I use visual-code-git(aur), which works well(also install c++ addons). emmm, It's strange. maybe something broken in dependencies.

@xaver: thank you!

pharra: if you use the C++ plugin, it might be related. Microsoft has the tendency to mess up that one frequently.

@dotfile: https://code.visualstudio.com/docs/supporting/faq#_why-does-visual-studio-code-have-a-different-license-than-the-vscode-github-repository

@pharra, maybe too many installed addons? On my PC vscode with some python addons uses like 250M for python project.

@dcelasun, can you explain why license is commercial? (on github: MIT)

My vscode uses 3G memory when I just edits single file like a.cpp. Could you tell what's wrong with it.

Electron based application will make Arch block. Did this happen on you guys' computer?

@Nowaker: Sure, with the next version.

Can you please change the description to:

Visual Studio Code: Editor for building and debugging modern web and cloud applications (official binary version) (vscode)

This way pacaur/yaourt -Ss vscode will show this package.

I do have gvfs, but get an error about being unable to move a file to trash when I delete it from within visual-studio-code. I don't know if any one else has this experience? Any ideas of what I could do to debug it?

@pr0xity: You shouldn't use --force without really making sure you need it. What was the conflict? Did you install another package that provides /usr/bin/code?

Is this package broke? suddenly I cant open vscode and the file /urs/bin/code and /usr/share/applicationc/visual-studio-code.desktop is empty.

EDIT: Needed to run the install with --force all good now :)

I've copy the desktop file to fix the display of the icon in ALT-TAB, and Application icon in the menu bar of Gnome 3

sudo cp /usr/share/applications/visual-studio-code.desktop /usr/share/applications/code.desktop

Otherwise the /usr/share/icons/gnome/256x256/mimetypes/binary.png is used...

Quick fix here for anyone who is experiencing vscode opening all file path, which is quite annoying. If nautilus is your file manager, just run

xdg-mime default org.gnome.Nautilus.desktop inode/directory

If you are suddenly seeing all "open folder" actions in other apps use vscode as your file manager, this is due to the new inode/directory mimetype in the desktop file. On some DEs, it apparently becomes the default the handler (see here for details). To fix it, create or edit /etc/xdg/mimeapps.list and add the following, replacing Nautilus with your preferred file manager:

[Default Applications]
inode/directory=org.gnome.Nautilus.desktop

@AveryFreeman: Seems to work fine for me.

I can't seem to get SCM to work with Git, it says there is no Software Control Manager installed. Git is installed on my system. I tried adding "/usr/bin" to git.path in settings, didn't seem to work. Is anyone else having this issue?

Please update .desktop file in package. Microsoft provided their .desktop file for vscode https://github.com/Microsoft/vscode/blob/master/resources/linux/code.desktop

MimeType=text/plain;inode/directory; is missing in current version of package.

% cat /usr/share/applications/visual-studio-code.desktop             
[Desktop Entry]
Exec=/opt/visual-studio-code/code %f
Icon=visual-studio-code
Terminal=false
Type=Application
Name=Visual Studio Code
Comment=Editor for building and debugging modern web and cloud applications
Categories=Development;WebDevelopment;IDE;Utility;TextEditor;
StartupNotify=true
StartupWMClass=code

@Alad: I've replied to the deletion request on list.

"Breaking people's updates" is not a valid reason to go against the AUR's packaging guidelines. Please submit a -bin version for this one to be merged to.

For anybody who is launching code through dmenu, rofi, etc.; and vscode just opens a file named code-stdin-whatever:

This is expected behavior, and you are supposed to use the .desktop file for running vscode outside of a terminal [0].

I expressed my thoughts on this on the issue tracker [1], but this might or might not be acted upon.

For now, I just reconfigured my launcher to use .desktop files by default (it's the more common usecase anyway). Maybe you can do the same too.

[0] https://github.com/Microsoft/vscode/issues/40264#issuecomment-351930866

[1] https://github.com/Microsoft/vscode/issues/40351#issuecomment-352205798

Works as expected for me as well. Thanks.

OK, just pushed another release. Now /usr/bin/code is a symlink to the shell script, but the .desktop file calls the binary. Seems to be working as expected for me.

Would it be possible for code to be a wrapper script that calls the CLI script if we are in a tty, and the binary otherwise?

I'm asking because if we launch the binary from a terminal, it gives the ioctl error message described below, and the process doesn't get detached from the terminal. Not a big deal, but still annoying.

bash: cannot set terminal process group (-1): Inappropriate ioctl for device bash: no job control in this shell

When I upgraded to the following version, I got the error message above each time I start code:

Version 1.19.0 Commit 816be6780ca8bd0ab80314e11478c48c70d09383 Date 2017-12-14T09:56:48.842Z Shell 1.7.9 Renderer 58.0.3029.110 Node 7.9.0 Architecture x64

@aguniyal: It's a packaging issue and it's fixed now. Next time, please read the pinned comment before opening an issue upstream.

Opening via dmenu has different behaviour now - https://github.com/Microsoft/vscode/issues/40264

@teej: I think you have a corrupted file.

$ sha256sum visual-studio-code.desktop

de88d95db3f55ce58ffd3c229cbde566099384d4f005cf887b00ccaeed605984  visual-studio-code.desktop

The latest version has an invalid checksum for the .desktop file. I was able to install it by manually changing the checksum.

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.