@blackpanther why is this being reported here? does vscodium directly from upstream not have this issue?
Search Criteria
Package Details: vscodium 1.96.2.24355-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/vscodium.git (read-only, click to copy) |
---|---|
Package Base: | vscodium |
Description: | Free/Libre Open Source Software Binaries of VSCode (git build from latest release). |
Upstream URL: | https://github.com/VSCodium/vscodium.git |
Licenses: | MIT |
Conflicts: | codium, vscodium, vscodium-bin, vscodium-git |
Provides: | codium, vscodium |
Submitter: | cedricroijakkers |
Maintainer: | cedricroijakkers (daiyam) |
Last Packager: | daiyam |
Votes: | 73 |
Popularity: | 1.84 |
First Submitted: | 2021-04-10 15:12 (UTC) |
Last Updated: | 2024-12-21 01:24 (UTC) |
Dependencies (23)
- alsa-lib
- cairo (cairo-gitAUR)
- fontconfig (fontconfig-gitAUR, fontconfig-ubuntuAUR)
- glibc (glibc-gitAUR, glibc-linux4AUR, glibc-eacAUR, glibc-eac-binAUR, glibc-eac-rocoAUR)
- gtk3 (gtk3-no_deadkeys_underlineAUR, gtk3-classicAUR, gtk3-classic-xfceAUR, gtk3-patched-filechooser-icon-viewAUR)
- libnotify (libnotify-gitAUR)
- libxkbfile
- libxss
- libxtst
- nss (nss-hgAUR)
- git (git-gitAUR, git-glAUR) (make)
- git-lfs (git-lfs-gitAUR) (make)
- gulp (gulp-cliAUR) (make)
- jq (jq-gitAUR, jaq-binAUR) (make)
- libxdmcp (make)
- nvmAUR (nvm-gitAUR) (make)
- patch (patch-gitAUR) (make)
- pkg-config (pkgconf-gitAUR, pkg-config-gitAUR, pkgconf) (make)
- python (python37AUR, python311AUR, python310AUR) (make)
- python-distutils-extra (make)
- yarn (yarn-pnpm-corepackAUR, corepackerAUR, yarn-berryAUR) (make)
- gvfs (gvfs-gitAUR) (optional) – For move to trash functionality
- libdbusmenu-glib (optional) – For KDE global menu
Required by (2)
Sources (4)
Latest Comments
« First ‹ Previous 1 2 3 4 5 6 7 .. 11 Next › Last »
MithicSpirit commented on 2024-05-30 18:15 (UTC)
blackpanther commented on 2024-05-30 16:56 (UTC)
Describe the bug https://github.com/VSCodium/vscodium/blob/master/docs/index.md) this link is not working after installing vscodium first time in arch linux . when I try to launch vscodium from terminal it gives this error mentioned in below image
Yes, I confirm that this problem is VSCodium-specific - [ ] This bug doesn't happen if I use Microsoft's Visual Studio Code. It only happens in VSCodium.
yes, I confirm that the issue/resolution isn't already documented - [ ] I checked the Docs page and the Troubleshooting page and my issue is not mentioned there.
To Reproduce Steps to reproduce the behavior: 1. yay -S vscodium (to install vscodium i narch linux) 2.type vscodium in terminal 3. press enter 4. you will see the error message
Expected behavior There was a problem in /usr/share/vscodium/resources/app/product.json I edited this line
as this
"linkProtectionTrustedDomains": [ "https://open-vsx.org" ],
It solved problem and loaded vscodium and now it's works fine
Error message codium node:internal/modules/cjs/loader:1343 throw err; ^
SyntaxError: /usr/share/vscodium/resources/app/product.json: Expected ':' after property name in JSON at position 3747 (line 96 column 2) at parse (<anonymous>) at Module._extensions..json (node:internal/modules/cjs/loader:1340:39) at Module.load (node:internal/modules/cjs/loader:1126:32) at Module._load (node:internal/modules/cjs/loader:967:12) at c._load (node:electron/js2c/node_init:2:13672) at Module.require (node:internal/modules/cjs/loader:1150:19) at require (node:internal/modules/cjs/helpers:119:18) at Object.<anonymous> (/usr/share/vscodium/resources/app/out/cli.js:4:9509) at Module._compile (node:internal/modules/cjs/loader:1271:14) at Module._extensions..js (node:internal/modules/cjs/loader:1326:10) at Module.load (node:internal/modules/cjs/loader:1126:32) at Module._load (node:internal/modules/cjs/loader:967:12) at c._load (node:electron/js2c/node_init:2:13672) at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:101:12) at node:internal/main/run_main_module:23:47
daiyam commented on 2024-05-10 16:25 (UTC)
@patlefort Thanks for pointing out the python-distutils-extra
@alexmurkoff For the directory issue, the unity-launch
flag has been deprecated and have to removed so VSCodium can open directories correctly from any explorer
More here: https://github.com/VSCodium/vscodium/pull/1866
The 1.89.1 should fix both issues.
patlefort commented on 2024-05-10 10:31 (UTC)
Why force python < 3.12? Installing python-distutils-extra
works fine on 3.12. Are there other issues I'm not aware of?
alexmurkoff commented on 2024-05-08 23:27 (UTC)
Latest version behaves rather strangely. Latest normally working version is vscodium 1.88.1.24104-1
For more info, look at this forum post:
https://bbs.archlinux.org/viewtopic.php?id=295570
TL;DR: Files don't properly open, you have to manually drag n drop each file you need to open or manually open a file with ^O
. If you don't care about being able to double-click-open a file from file explorer - ignore this comment.
patlefort commented on 2024-05-06 13:58 (UTC)
Missing python-distutils-extra
in makedepends.
jnanar commented on 2024-05-05 09:44 (UTC)
I could build it with the following steps. It's a hack but it worked. I hope the node-gyp upstream team will update the requirements or fix their code to work in the stable release.
git clone https://aur.archlinux.org/vscodium.git
cd vscodium/
python -m venv venv
source venv/bin/activate
pip install setuptools
sudo pacman -U vscodium-1.88.1.24104-1-x86_64.pkg.tar.zst
kreijstal commented on 2024-04-27 14:08 (UTC)
This will no longer build because node-gyp from node18 uses python distutils which are removed in python 3.12. RIP.
sausix commented on 2024-01-18 21:58 (UTC)
Of course it would conflict extra/code. But most people won't install VSCode if they already have VSCodium :-)
Wasn't a request to this package. Just wanted to share my workaround since VSCodium hasn't a dedicated ArchWiki page.
Haven't thought about putting it in ~/.local/bin. Thanks. Applications still may ignore the PATH variable and just look into the known binary folders. Who knows. But I'll test that on UE5.
MithicSpirit commented on 2024-01-18 21:24 (UTC)
@sausix that would make this package conflict with extra/code
, which is not necessarily desirable. You could make a separate package that depends on this package but provides and conflicts with code
that has that symlink, or just make it manually as you already have (although I would recommend placing the symlink in ~/.local/bin
instead).
Pinned Comments