Package Details: visual-studio-code-bin 1.96.2-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: 1480
Popularity: 16.83
First Submitted: 2017-12-18 19:14 (UTC)
Last Updated: 2024-12-20 03:54 (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 .. 6 7 8 9 10 11 12 13 14 15 16 .. 78 Next › Last »

Camrais commented on 2023-06-28 07:16 (UTC)

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

PHLAK commented on 2023-06-16 17:00 (UTC)

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

stepinsilence commented on 2023-06-16 11:47 (UTC)

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

Lightning5 commented on 2023-06-14 16:03 (UTC)

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

stepinsilence commented on 2023-06-14 10:30 (UTC)

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.

PHLAK commented on 2023-06-12 22:44 (UTC)

@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

Lightning5 commented on 2023-06-12 21:44 (UTC) (edited on 2023-06-12 21:46 (UTC) by Lightning5)

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

PHLAK commented on 2023-06-12 18:12 (UTC)

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

Lightning5 commented on 2023-06-12 14:34 (UTC) (edited on 2023-06-12 14:34 (UTC) by Lightning5)

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.

dcelasun commented on 2023-05-22 18:53 (UTC)

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

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