@teej: I think you have a corrupted file.
$ sha256sum visual-studio-code.desktop
de88d95db3f55ce58ffd3c229cbde566099384d4f005cf887b00ccaeed605984 visual-studio-code.desktop
| 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: | 1668 |
| Popularity: | 31.05 |
| First Submitted: | 2017-12-18 19:14 (UTC) |
| Last Updated: | 2026-05-20 10:43 (UTC) |
« First ‹ Previous 1 .. 64 65 66 67 68 69 70 71 72 73 74 .. 90 Next › Last »
@teej: I think you have a corrupted file.
$ sha256sum visual-studio-code.desktop
de88d95db3f55ce58ffd3c229cbde566099384d4f005cf887b00ccaeed605984 visual-studio-code.desktop
The latest version has an invalid checksum for the .desktop file. I was able to install it by manually changing the checksum.
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 licence difference and branding, there are some proprietary features not available in the open-source version.
This package depends on both the official tarball and files from GitHub. Please check this page AND this page before flagging as out-of-date. If the new version isn't on both pages, this package cannot be updated! If you can see the new version on both pages, but the AUR package is still not updated, flag it and give it time. It's usually done within hours.
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-open uses vscode, not my file manager! How do I fix this?Install shared-mime-info-gnome gnome-session which now includes mimemapps.
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.
Pinned Comments
dcelasun commented on 2017-11-15 06:20 (UTC) (edited on 2026-01-23 13:07 (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 licence difference and branding, there are some proprietary features not available in the open-source version.
This package depends on both the official tarball and files from GitHub. Please check this page AND this page before flagging as out-of-date. If the new version isn't on both pages, this package cannot be updated! If you can see the new version on both pages, but the AUR package is still not updated, flag it and give it time. It's usually done within hours.
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-gnomegnome-sessionwhich now includes mimemapps.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.