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

Search Criteria

Enter search criteria

Search by

Keywords

Out of Date

Sort by

Sort order

Per page

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

Package Actions

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

Dependencies (17)

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

Required by (21)

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

Sources (7)

Pinned Comments

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

FREQUENTLY ASKED QUESTIONS (read before flagging or commenting!)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 .. 78 Next › Last »

andsmir commented on 2024-05-11 20:00 (UTC)

Is it possible to change StartupWMClass=Code to StartupWMClass=code-url-handler in code.desktop? At this moment window grouping and pining doesn't work correctly in gnome. original source of this solution: https://forum.endeavouros.com/t/why-cant-the-aur-vs-code-window-be-pinned-in-the-dash/46253/11

b-fg commented on 2024-05-11 16:38 (UTC) (edited on 2024-05-11 20:59 (UTC) by b-fg)

I have the problem of the empty blank window when launching the app, it stay like that for 30s and then works. I have downloaded and reinstalled it, but it does not work for me for the moment.

Maybe is a problem of the window manager though, I am unsure. Here is the debug info: http://0x0.st/XKzk.txt

Edit:

This is related and it fixes the problem: https://github.com/microsoft/vscode/issues/193188 Could this flag be included by default?

dcelasun commented on 2024-05-03 05:35 (UTC)

@TTsdzb fixed, thanks.

TTsdzb commented on 2024-05-03 03:02 (UTC)

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.

TTsdzb commented on 2024-05-03 02:51 (UTC)

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

blueman commented on 2024-05-02 19:11 (UTC)

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

FabioLolix commented on 2024-04-13 14:10 (UTC)

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

shore commented on 2024-04-13 13:58 (UTC)

Out of date .....

freebench commented on 2024-04-10 09:50 (UTC)

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

st0ne commented on 2024-04-06 13:20 (UTC)

遇到一些问题 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