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

Git Clone URL: https://aur.archlinux.org/visual-studio-code-bin.git (read-only, click to copy)
Package Base: visual-studio-code-bin
Description: Visual Studio Code (vscode): Editor for building and debugging modern web and cloud applications (official binary version)
Upstream URL: https://code.visualstudio.com/
Licenses: custom: commercial
Conflicts: code
Provides: code, vscode
Submitter: dcelasun
Maintainer: dcelasun
Last Packager: dcelasun
Votes: 1491
Popularity: 19.68
First Submitted: 2017-12-18 19:14 (UTC)
Last Updated: 2025-01-17 07:47 (UTC)

Required by (21)

Sources (7)

Pinned Comments

dcelasun commented on 2017-11-15 06:20 (UTC) (edited on 2020-02-06 21:33 (UTC) by dcelasun)

FREQUENTLY ASKED QUESTIONS (read before flagging or commenting!)

  • What is the difference between this package and the one in the community repo?

This is the official binary distribution from Microsoft. The one in the community repo is an unofficial build made from source. Beyond the license difference and branding, there are some proprietary features not available in the open source version.

  • There is a new version out, why is the package not updated?

Please check this page before flagging as out-of-date. If there is no new version on that page, it's not yet released. A tag on Github is NOT a release! If you can see the new version on the updates page but the AUR package is still not updated, flag it and give it time. It's usually done within a day or two.

  • I'm using an AUR helper (yay, yaourt etc.) and I can't install it. Why?

Sometimes AUR helpers do weird things. Download the tarball and install it manually with makepkg -si. If that works, report the problem to your AUR helper's upstream, not here.

  • When I install this package xdg-open uses vscode, not my file manager! How do I fix this?

Install shared-mime-info-gnome. Also see this reddit thread.

  • Why is $X a dependency? I don't like it.

Just because $X is not required to open the app, doesn't mean there is nothing that depends on it. Always search the comment history on AUR to see if that dependency has been previously discussed before writing your own comment. Still nothing? Then use namcap to make sure it's really not needed. If namcap doesn't complain, please leave a comment here and I'll investigate.

  • Something is broken with the app, where do I report it?

The problem might be a packaging issue (wrong paths, dependencies, icons), so please write a comment here first. If you don't get a reply, or if someone says it's an upstream issue, you can report it on Github.

  • I have a problem with this package, can I email you?

No, you won't get a reply. Please stop doing this. Leave a comment here instead and be patient.

Latest Comments

« First ‹ Previous 1 .. 4 5 6 7 8 9 10 11 12 13 14 .. 78 Next › Last »

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

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

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

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

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

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

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

kidonng commented on 2023-10-30 06:32 (UTC) (edited on 2023-10-30 17:36 (UTC) by kidonng)

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.

laurence6 commented on 2023-10-14 21:43 (UTC)

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"

Krator commented on 2023-10-11 17:40 (UTC) (edited on 2023-10-14 12:00 (UTC) by Krator)

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] если он есть в нём

Sherlock-Holo commented on 2023-09-11 03:15 (UTC)

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" />

saghm commented on 2023-09-11 01:17 (UTC)

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.

nkukard commented on 2023-09-10 10:10 (UTC)

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

mxbonn commented on 2023-09-10 09:38 (UTC)

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

« First ‹ Previous 1 .. 4 5 6 7 8 9 10 11 12 13 14 .. 78 Next › Last »