@kxxt Thanks for noticing! It's fixed now.
Search Criteria
Package Details: vscodium-bin 1.116.02821-1
Package Actions
| Git Clone URL: | https://aur.archlinux.org/vscodium-bin.git (read-only, click to copy) |
|---|---|
| Package Base: | vscodium-bin |
| Description: | Binary releases of VS Code without MS branding/telemetry/licensing. |
| Upstream URL: | https://github.com/VSCodium/vscodium |
| Licenses: | MIT |
| Conflicts: | vscodium |
| Provides: | codium, vscode, vscodium |
| Submitter: | ckatri |
| Maintainer: | Icelk |
| Last Packager: | Icelk |
| Votes: | 377 |
| Popularity: | 7.39 |
| First Submitted: | 2020-09-23 18:58 (UTC) |
| Last Updated: | 2026-04-27 15:00 (UTC) |
Dependencies (14)
- alsa-lib
- bash (bash-gitAUR, bash-devel-gitAUR)
- cairo (cairo-gitAUR)
- fontconfig (fontconfig-gitAUR, fontconfig-ubuntuAUR)
- gcc-libs (gcc-libs-gitAUR, gccrs-libs-gitAUR, gcc-libs-snapshotAUR)
- glibc (glibc-gitAUR, glibc-eacAUR, glibc-git-native-pgoAUR)
- gtk3 (gtk3-no_deadkeys_underlineAUR, gtk3-classicAUR, gtk3-patched-filechooser-icon-viewAUR, gtk3-classic-xfceAUR)
- libnotify (libnotify-gitAUR)
- libxss
- libxtst
- nss (nss-hgAUR)
- python
- gvfs (gvfs-gitAUR, gvfs-googledriveAUR) (optional) – For move to trash functionality
- libdbusmenu-glib (optional) – For KDE global menu
Required by (9)
- noon-optional
- python-ocp-vscode (requires vscode) (optional)
- vscode-xdg-patch-hook (requires vscode) (optional)
- vscodium-all-marketplace (requires codium) (optional)
- vscodium-bin-marketplace
- vscodium-features (requires vscodium)
- vscodium-marketplace (requires vscodium)
- vscodium-prod-patcher (requires vscodium)
- vscodium-xdg-dir-patch (requires codium)
Sources (8)
- https://github.com/VSCodium/vscodium/releases/download/1.116.02821/VSCodium-linux-arm64-1.116.02821.tar.gz
- https://github.com/VSCodium/vscodium/releases/download/1.116.02821/VSCodium-linux-x64-1.116.02821.tar.gz
- https://raw.githubusercontent.com/VSCodium/vscodium/refs/tags/1.116.02821/src/stable/resources/linux/code.svg
- LICENSE
- vscodium-bin-url-handler.desktop
- vscodium-bin.desktop
- vscodium-bin.install
- vscodium-bin.sh
Latest Comments
« First ‹ Previous 1 .. 4 5 6 7 8 9 10 11 12 13 14 .. 31 Next › Last »
Icelk commented on 2024-07-02 13:08 (UTC)
kxxt commented on 2024-06-28 12:33 (UTC)
There is a typo in the filename of vscodium-bin-uri-handler.desktop and /usr/share/applications/codium-uri-handler.desktop. It should be url instead of uri, as vscodium sets its app_id to "codium-url-handler". This typo is causing the window of vscodium having a generic wayland icon when running in wayland.
<deleted-account> commented on 2024-06-04 13:39 (UTC)
We keep separate desktop entries as some users may wish to continue to run VSCodium under X11. This is done by many other electron-based apps. Unity launch will be fixed in my next push.
jongeduard commented on 2024-05-26 15:05 (UTC) (edited on 2024-05-26 15:05 (UTC) by jongeduard)
Can you please (like ZorinArch also asked) remove --unity-launch from the .desktop file?
It causes actual problems.
The command in de desktop file is written /usr/bin/codium --unity-launch %F, but not only does this command give a warning ("Warning: 'unity-launch' is not in the list of known options, but still passed to Electron/Chromium.") when I type it myself, but it also fails to open VSCodium with a directory passed as argument through the %F parameter (which for example happens when I right click a directory to open it with VSCodium in my Thunar file explorer).
I now have to customize the shortcut myself in order to get it working properly.
hype-vhs commented on 2024-05-22 22:24 (UTC) (edited on 2024-05-22 22:24 (UTC) by hype-vhs)
We can unconditionally pass in --ozone-platform-hint=auto in vscodium-bin.sh. This opts into Wayland if and only if it's available at runtime.
matejdro commented on 2024-05-22 06:08 (UTC)
Any reason why there are two desktop files for launching VSCodium? Couldn't install script detect whether you are running X11 or Wayland and install only one?
OliverP commented on 2024-05-20 20:18 (UTC)
Hello! Back to my last issue from a few months ago with chrome-sandbox's setuid bits not being correct, and inhibiting it running on the linux-hardened kernel. Seems like the problem was that it also required 'chown root' being set too.
I have added the following to the end of the package function in PKGBUILD and it seems to make it work correctly:
chown root "${pkgdir}/opt/vscodium-bin/chrome-sandbox"
chmod 4755 "${pkgdir}/opt/vscodium-bin/chrome-sandbox"
Let me know if there are any other problems, I will be available.
ZorinArch commented on 2024-05-09 04:36 (UTC)
Hi @Icelk, please remove deprecated --unity-launch flag from vscodium-bin.desktop and vscodium-bin-wayland.desktop. https://github.com/VSCodium/vscodium/pull/1866
renyuneyun commented on 2024-04-21 13:37 (UTC)
For some reason, when working with Python project, VSCodium says isort failed to start, which in turn complains missing pygls module. Manually installing python-pygls fixes this. But I'm not sure if this is a potential problem for the package itself (e.g. a missing opt-dependency) or due to my configuration. Thought worth mentioning in case others encounter as well.
Icelk commented on 2024-04-14 15:24 (UTC)
@Ranguna Excellent, thanks for investigating!
Pinned Comments
<deleted-account> commented on 2021-05-12 00:31 (UTC)
@Icelk set up a script that checks for new releases and pushes updates if there are any new ones. I believe it runs every hour so there's no need to flag OOD, unless there's something that needs changed with the PKGBUILD.