Arch Linux User Repository

if you are having problems with the installation step with it giving a decoder error, you need to uninstall and reinstall vscodium-bin and vscodium-bin-marketplace. then try to install this package again.

Like you've read in my link "uninstall and reinstall vscodium-bin and vscodium-bin-marketplace. then try to install this package again" is exactly what has been done, and this is the problematic package. So yeah, to prove that "you are having problems with the installation step with it giving a decoder error", you can "uninstall and reinstall vscodium-bin and vscodium-bin-marketplace. then try to install this package again" but to get this package to work it's not the right thing to do, the right thing for this package is to be corrected, or to rewrite all his files upon un/installing

if you are having problems with the installation step with it giving a decoder error, you need to uninstall and reinstall vscodium-bin and vscodium-bin-marketplace. then try to install this package again.

https://aur.archlinux.org/packages/vscodium-bin-marketplace#comment-899369

Getting the following error with the current revision (385c507d60e6): sed: can't read +: No such file or directory

@bkb try it now, updated so it would be inline with code-features package

Broken XHR

RequestService#request (browser) - error https://marketplace.visualstudio.com/_apis/public/gallery/extensionquery Error: XHR failed", source: vscode-file://vscode-app/opt/vscodium-bin/resources/app/out/vs/workbench/workbench.desktop.main.js (616)

EDIT: Now it's worse, just having reinstalled the same version

node:internal/modules/cjs/loader:1190
    throw err;
    ^

SyntaxError: /opt/vscodium-bin/resources/app/product.json: Unexpected token , in JSON at position 13192
    at parse (<anonymous>)
    at Module._extensions..json (node:internal/modules/cjs/loader:1187:22)
    at Module.load (node:internal/modules/cjs/loader:988:32)
    at Module._load (node:internal/modules/cjs/loader:829:12)
    at c._load (node:electron/js2c/asar_bundle:5:13343)
    at Module.require (node:internal/modules/cjs/loader:1012:19)
    at require (node:internal/modules/cjs/helpers:102:18)
    at Object.<anonymous> (/opt/vscodium-bin/resources/app/out/cli.js:4:9247)
    at Module._compile (node:internal/modules/cjs/loader:1118:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1173:10)
    at Module.load (node:internal/modules/cjs/loader:988:32)
    at Module._load (node:internal/modules/cjs/loader:829:12)
    at c._load (node:electron/js2c/asar_bundle:5:13343)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:77:12)
    at node:internal/main/run_main_module:17:47

e736b35e8f673fcabbe561016c4daa5d /opt/vscodium-bin/resources/app/product.json

770e2bb260e6831d6cf967444050bcdb /opt/vscodium-bin/resources/app/out/cli.js

Same hash upon re-downloading, so it's the right one

With only vscodium e9b562813f694221194afa56b04d31f8 /usr/share/vscodium/resources/app/product.json, and it works

What are the feature that we're talking about?

No, unless the product.json format is changed upstream

Does this package's version need to be matched to exact installed version of vscodium-bin? I.e. vscodium-bin-features 1.66.1-1 will not work with vscodium-bin 1.66.2-1, correct? It corrupts my product.json.

If yes, then I think it is a good idea to hard depend on a specific version. Something like depends=('vscodium-bin=${pkgver}' 'sed').