| 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: | 1463 |
| Popularity: | 14.53 |
| First Submitted: | 2017-12-18 19:14 (UTC) |
| Last Updated: | 2024-11-15 11:08 (UTC) |
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
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?
I confirm that 1.66 is a mess on wayland + gnome + nvidia, skip this!
After updating to 1.66 I get a (white) blank screen. It seems VScode bumped Electron from v13 to v17. Running with --verbose outputs
[50533:0331/104848.998408:ERROR:gpu_process_host.cc(983)] GPU process exited unexpectedly: exit_code=136
Starting with --disable-gpu seems to be working as a workaround. Gnome + Xorg + NVidia 510.54.
Here we go!
Hi, is normal that if the vscode is exit, the Visual Studio Code - URL Handler from /usr/share/applications/visual-studio-code-url-handler.desktop keeps running like 30% CPU?
@dcelasun kk, sorry for not seeing that..... and thanks for ur replay~~
@shore
BTW, the insider version on arch seems behind the main version
Not exactly. The insider package always builds the latest version (see pinned comment), so I don't manually update pkgver.
@dcelasun I actually did that, however the insider version works fine, so they closed the issue since it must have been fixed something........ BTW, the insider version on arch seems behind the main version lol........
@shore it's probably trying to connect to a Microsoft server which isn't reachable from China, and you're stuck until the request times out. You should report this on Github.
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.