Package Details: visual-studio-code-bin 1.88.1-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: 1418
Popularity: 21.22
First Submitted: 2017-12-18 19:14 (UTC)
Last Updated: 2024-04-13 14:03 (UTC)

Required by (17)

Sources (7)

Pinned Comments

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

FREQUENTLY ASKED QUESTIONS (read before flagging or commenting!)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Latest Comments

« First ‹ Previous 1 .. 6 7 8 9 10 11 12 13 14 15 16 .. 73 Next › Last »

bulletmark commented on 2022-05-12 01:43 (UTC)

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.

ambantis commented on 2022-05-11 11:34 (UTC)

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.

vegancookies commented on 2022-04-20 13:52 (UTC) (edited on 2022-04-20 22:54 (UTC) by vegancookies)

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?

dcelasun commented on 2022-04-19 21:30 (UTC)

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

vegancookies commented on 2022-04-19 21:13 (UTC)

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

phillipk commented on 2022-04-14 11:07 (UTC) (edited on 2022-04-14 11:23 (UTC) by phillipk)

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?

zensei commented on 2022-04-12 22:13 (UTC)

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.

dcelasun commented on 2022-04-01 10:36 (UTC) (edited on 2022-04-01 10:36 (UTC) by dcelasun)

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

fincan commented on 2022-04-01 10:28 (UTC)

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?

abique commented on 2022-03-31 08:21 (UTC)

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

« First ‹ Previous 1 .. 6 7 8 9 10 11 12 13 14 15 16 .. 73 Next › Last »