Vscode oss can't verify extensions

[thomas85]

I’m facing this issue.

If I understood this comment right, the latest version 1.100.2-1, has fixed the problem for Arch, but didn’t do it for my Manjaro machine.

In the github issue they also talk that the package must not be stripped for it to work, though this might only be relevant for packages using tar ball provided by Microsoft - since it includes the required vsce-sign module without listing it in package.json.

Does anybody besides me use the OSS code version with Manjaro and can report on if installing or updating extensions works for them with the latest version?

Is there anybody else who can improve my understanding of the situation why it’s not fixed on my machine although the latest version was intended to?

[Aragorn]

@thomas85

Is there anybody else who can improve my understanding of the situation why it’s not fixed on my machine although the latest version was intended to?

I myself don’t use code, but what I can tell you is that we import that package from Arch verbatim — i.e. in binary form — and that we have the exact same version — i.e. 1.100.2-1, the newest version — in all three of the branches.

[linux-aarhus]

@thomas85

Does anybody besides me use the OSS code version with Manjaro and can report on if installing or updating extensions works for them with the latest version?

I don’t usually use VS code but if it can help - I did a fresh installed Code OSS - with the purpose of answering the question.

 $ pamac info code | grep -e 'Version' -e 'Packager' -e 'Build Date'
Version               : 1.100.2-1
Packager              : Massimiliano Torromeo <mtorromeo@archlinux.org>
Build Date            : tor 15 maj 2025 20:05:34 CEST

Installing Python extension throws a message on the inability to verify extension signature

The message is Signature verification failed with ‘UnknownError’ error.

The options are

• Install Anyway (Don’t Verify Signature)
• Report Issue
• Cancel
• Learn More

Where the first option will let the extension setup continue successfully.

[thomas85]

Thank you both for your replies!

@linux-aarhus Yes that’s exactly what I’m seeing on my machine too.

I’ll try asking in the closed vscode github issue if this fix indeed works with “raw” Arch and if so if the can speculate why it wouldn’t with Manjaro even though it

“imports that package from Arch verbatim”

[Mirdarthos]

I have Code - OSS too, and it does not work on the marketplace by default. For that you need to install code-marketplace from the AUR:

$ pamac search --installed code
[...]
code-marketplace  1.100.2-1                                                                                                                                                                                                  AUR
Enable vscode marketplace in Code OSS
[...]

I have also replaced my marketplace with:

https://open-vsx.org

And I have 0 issues.

[thomas85]

thank you for that reply! How do you replace the vscode marketplace with https://open-vsx.org ? You don’t need to answer that I’ll google it later - I have to run now though. Thanks!

[Mirdarthos]

Easy:

Using Open VSX in VS Code

I answered anyway, consider it a gift saving you a Google.

[linux-aarhus]

@thomas85

I’ll try asking in the closed vscode github issue if this fix indeed works with “raw” Arch

I suggest you spin a virtual machine using Arch - and verify the issue with such vm.

//EDIT 2025-05-21T09:29:00Z:

The result (my previous comment) is the same with a clean Arch Linux installation.

[thomas85]

wow! you guys are amazing, thank you @linux-aarhus & @Mirdarthos & @Aragorn !! I’ve seldom received such amazing support, not even when paying for it

[soundofthunder]

I’m sure you are most welcome.

You can pay it forward by summarising whatever the solution might be for the benefit of others finding this topic in the future.

Don’t forget to mark whichever post that helped you the most as the Solution to the topic.

Regards.

[thomas85]

well, I tried the open-vsx thing but I still get the verification errors.
But since it’s an Arch upstream error and the maintainer has announced that it will be fixed in a future version, I don’t think there’s any more Manjaro or it’s forum user could / should do.