@ZZYSonny that's an Electron bug that's been fixed upstream. It should make its way into vscode soon. Can someone on X using a dock test that workaround? If it doesn't break things for X, I can include it here.
Search Criteria
Package Details: visual-studio-code-bin 1.88.1-1
Package Actions
| 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: | 1418 |
| Popularity: | 21.22 |
| First Submitted: | 2017-12-18 19:14 (UTC) |
| Last Updated: | 2024-04-13 14:03 (UTC) |
Dependencies (17)
- alsa-lib
- gcc-libs (gccrs-libs-gitAUR, gcc11-libsAUR, gcc-libs-gitAUR)
- glibc (glibc-gitAUR, glibc-linux4AUR, glibc-eacAUR)
- gnupg (gnupg-gitAUR, gnupg-largekeysAUR)
- gtk3 (gtk3-ubuntuAUR, gtk3-no_deadkeys_underlineAUR, gtk3-patched-filechooser-icon-viewAUR, gtk3-classic-xfceAUR, gtk3-classicAUR)
- libnotify (libnotify-gitAUR)
- libsecret
- libxkbfile
- libxss
- lsof (lsof-gitAUR)
- nss (nss-hgAUR)
- shared-mime-info
- xdg-utils (busking-gitAUR, xdg-utils-slockAUR, mimiAUR, mimi-gitAUR, xdg-utils-handlrAUR, openerAUR, xdg-utils-betterlockscreenAUR, mimejs-gitAUR, xdg-utils-mimeoAUR)
- glib2 (glib2-gitAUR, glib2-selinuxAUR, glib2-patched-thumbnailerAUR) (optional) – Needed for move to trash functionality
- icu69AUR (icu69-binAUR) (optional) – Needed for live share
- libdbusmenu-glib (optional) – Needed for KDE global menu
- org.freedesktop.secrets (keepassxc-gitAUR, gnome-keyring-gitAUR, bitw-gitAUR, pass-secrets-gitAUR, keepassxc-allow-aur-extension-originAUR, keepassxc-allow-aur-extension-origin-binAUR, gnome-keyring, keepassxc, kwallet, kwallet5) (optional) – Needed for settings sync
Required by (18)
- azure-sphere-sdk (requires code) (optional)
- code-appicons (requires code)
- code-features (requires code)
- code-features-insiders (requires code)
- code-icons (requires code)
- code-marketplace (requires code)
- code-nautilus-git (requires code) (optional)
- code-oss-marketplace (requires code)
- dokytree (requires code) (optional)
- dokytree-git (requires code) (optional)
- meta-package-manager (requires code) (optional)
- nautilus-code (requires code) (optional)
- neopo-git (optional)
- nwscript-code (requires code)
- rust-analyzer-vscode-git (requires code)
- stm32pio (requires code) (optional)
- unity-editor-lts (optional)
- unreal-engine-bin (requires code) (optional)
Sources (7)
dcelasun commented on 2022-09-07 22:18 (UTC)
ZZYSonny commented on 2022-09-07 21:58 (UTC)
Could you please consider applying this workaround to make VSCode show its own icon instead of the generic wayland icon with "ozone-platform=wayland"? https://github.com/microsoft/vscode/issues/129953#issuecomment-1235360500
dcelasun commented on 2022-09-06 16:41 (UTC)
@Piroro-hs thanks, should be fixed now.
Piroro-hs commented on 2022-09-06 16:32 (UTC)
@dcelasun It doesn't start without alsa-lib.
error while loading shared libraries: libasound.so.2: cannot open shared object file: No such file or directory
dcelasun commented on 2022-09-06 15:19 (UTC)
@Piroro-hs which feature exactly depends on alsa-lib? Ignore the namcap output, that just shows everything that could theoretically be used by Electron.
Piroro-hs commented on 2022-09-06 15:10 (UTC)
alsa-lib (libasound.so.2) should be added to depends list.
dcelasun commented on 2022-09-01 22:25 (UTC)
@phillipk alright then, I pushed the change.
phillipk commented on 2022-09-01 22:17 (UTC) (edited on 2022-09-01 22:18 (UTC) by phillipk)
I now had the time to test a little:
All paths passed to /usr/bin/code have no effect as soon as .config/code-flags.conf contains at least one flag.
E.g., invoking code /some/file.txt will just restore the last session or open a new window and not open /some/file.txt anywhere. As soon as .config/code-flags.conf is empty or does not exist, it will work again.
The workaround I am currently applying after each update is to modify the last line of /usr/bin/code to have the arguments passed ("$@") before the configured flags $CODE_USER_FLAGS. Then it also works with flags present in .config/code-flags.conf.
dcelasun commented on 2022-08-10 05:58 (UTC)
@philipk do you mean /usr/bin/code? Because /opt/visual-studio-code/bin/code is supplied by upstream and is not involved with $CODE_USER_FLAGS. I don't think changing the order of $CODE_USER_FLAGS and "$@" is a good idea. What exactly is the problem you're having?
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.