| 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: | 1695 |
| Popularity: | 26.60 |
| First Submitted: | 2017-12-18 19:14 (UTC) |
| Last Updated: | 2026-07-18 05:35 (UTC) |
So I guess I can try to point to the new icon, but after update of this package its difficult to find out, where it is.
I first thought maybe it pointed to the wrong icon, but it looks correct. The desktop file has Icon=vscode and the icon itself is at /usr/share/pixmaps/vscode.png which is the correct place.
Perhaps it's an icon cache issue on your end? I don't know anything about KDE.
@dcelasun
Are you using a custom theme?
No, just standard "Breeze Dark" in KDE Plasma. So I guess I can try to point to the new icon, but after update of this package its difficult to find out, where it is. Can it be somehow fixed to work as on previous updates where no manual intervention was required?
@syriusz in 1.123.0-5 we switched to upstream's own .desktop files from the official deb packages which has Icon=vscode whereas we previously had Icon=visual-studio-code. But the icon file has also changed to /usr/share/pixmaps/vscode.png so it shouldn't be a problem.
Are you using a custom theme?
There is some issue with the last update of this package (1.123.0-5) - no proper icon is available for VS Code in KDE Plasma... Tested on two separated machines with Arch. In main KDE menu VS Code has some default icon (empty sheet of paper) and no VS Code icon is found when I try to set the proper icon using Menu Editor in KDE...
@SuperNinja_4965 I'm aware, will delete those with the next version.
@dcelasun if the .in files are not required anymore - would you be able to remove them from the repo? It appears they got left behind. Thanks
Thanks to @the-k's work, 1.123.0-5 now uses the upstream deb file (instead of the generic tarball) because it includes the resource files, which means this package no longer needs GitHub tags.
Upstream is potentially looking into automating tags on the git repo, so we might be able to go back to tagged resource files in a future version.
If you need help, feel free to make a co-maintainer. I'd absolutely love to keep the package up-to-date and deliver the updates the right way.
The package is already updated by CI, which makes sure it actually builds and is installable before pushing. Its schedule has been increased repeatedly to utterly wasteful levels because there are enough people who absolutely must have the latest build within seconds of Microsoft publishing it, and they must have it from this package as they're unwilling to build it locally.
I don't need help maintaining the package. I do need people to stop emailing me unless there has been AT LEAST 24 hours since the upstream update. Ideally, it would be 2-3 times that...
Do you know why I made the change to committed resource files today? Because I've received 6 emails SO FAR, demanding an update, even though it hasn't even been 24 hours since the upstream release.
If none of that matters to you, fair enough! You can always set your own CI pipeline using whatever PKGBUILD you'd like.
@dcelasun, how are you gonna check whether .desktop and .xml files need updating then? Or are you not gonna do that? And don't you find it inefficient that every user will have to do the same? Either way, it's not great if you're not willing to spend the effort in order to do the right thing. This is currently the 6th most voted package in AUR, so this affects a lot of people. If you need help, feel free to make a co-maintainer. I'd absolutely love to keep the package up-to-date and deliver the updates the right way.
Pinned Comments
dcelasun commented on 2017-11-15 06:20 (UTC) (edited on 2026-06-04 12: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 licence difference and branding, there are some proprietary features not available in the open-source version.
This package depends on the official tarball. Please check this page before flagging as out-of-date. If the new version isn't on that page, this package cannot be updated! If you can see the new version there, 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.