| 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: | 1465 |
| Popularity: | 13.44 |
| First Submitted: | 2017-12-18 19:14 (UTC) |
| Last Updated: | 2024-11-15 11:08 (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.
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......
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!)
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.
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.
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.xdg-openuses vscode, not my file manager! How do I fix this?Install shared-mime-info-gnome. Also see this reddit thread.
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.
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.
No, you won't get a reply. Please stop doing this. Leave a comment here instead and be patient.