vscode: Signature: UnknownError

Testing #164452

2022-10-26 16:43:48.609 [info] Extension host agent started.
2022-10-26 16:43:51.256 [error] [172.17.0.1][ddd63f6d][ExtensionHostConnection] Unknown reconnection token (never seen).
2022-10-26 16:43:51.280 [error] [172.17.0.1][7d248857][ManagementConnection] Unknown reconnection token (never seen).
2022-10-26 16:43:54.628 [warning] No ptyHost heartbeat after 6 seconds
2022-10-26 16:43:57.487 [info] [172.17.0.1][75f1ef47][ManagementConnection] New connection established.
2022-10-26 16:43:57.751 [info] [172.17.0.1][d79102fd][ExtensionHostConnection] New connection established.
2022-10-26 16:43:57.813 [info] [172.17.0.1][d79102fd][ExtensionHostConnection] <1285> Launched Extension Host Process.
2022-10-26 16:44:03.637 [warning] No ptyHost heartbeat after 6 seconds
2022-10-26 16:44:04.241 [warning] Using the in-memory credential store as the operating system's credential store could not be accessed. Please see https://aka.ms/vscode-server-keyring on how to set this up. Details: libsecret-1.so.0: cannot open shared object file: No such file or directory
2022-10-26 16:46:24.186 [info] Getting Manifest... nikhgup1.component-creator
2022-10-26 16:46:24.893 [info] Installing extension: nikhgup1.component-creator
2022-10-26 16:46:36.746 [error] Error while installing the extension: nikhgup1.component-creator
2022-10-26 16:46:36.825 [error] Failed to install extension. nikhgup1.component-creator
2022-10-26 16:46:36.857 [error] Signature: UnknownError
    at Sn.download (/root/vscode-server-linux-armhf-web/out/vs/server/node/server.main.js:90:4035)
    at async V.doRun (/root/vscode-server-linux-armhf-web/out/vs/server/node/server.main.js:146:92152)
2022-10-26 16:46:37.899 [error] Signature: UnknownError
    at Sn.download (/root/vscode-server-linux-armhf-web/out/vs/server/node/server.main.js:90:4035)
    at async V.doRun (/root/vscode-server-linux-armhf-web/out/vs/server/node/server.main.js:146:92152)

Version: 1.73.0-insider
Commit: c3eebaead9d3bf1cb961b91fca1b8af31990d328
Date: 2022-10-26T09:14:47.017Z
Browser: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/106.0.0.0 Safari/537.36 Edg/106.0.1370.52

(Using VS Code Server armhf build in a Docker container with armhf hardware emulation.)

About this issue

Original URL
State: closed
Created 2 years ago
Reactions: 1
Comments: 43 (15 by maintainers)

Most upvoted comments

Workaround set extensions.verifySignature to false in your settings.json.

isidorn on Dec 1, 2022

It means you can use it, but the settings editor doesn’t explicitly show it as a setting you can use. But if you type it in and save it, it should work.

omrihar on Dec 15, 2022

After setting the "extensions.verifySignature": false in your settings, note that reloading the window via the command palette does not work. You have to restart vscode.

Kinyugo on Dec 15, 2022

Thanks for everybody that provided feedback here - we really appreciate it. We have pushed a fix so that this error should no longer be blocking.

For those that have added extensions.verifySignature": false to their setting - can you please remove it? And let us know if you still see any problems. To be clear, you should NOT see any errors now even if you remove the setting, but it will help us in detecting other potential issues.

isidorn on Jan 11, 2023

@manastalukdar are you sure you applied the extensions.verifySignature to false in the right setting file. What is the error that you get when you have this setting set?

isidorn on Dec 9, 2022

Have same issue: Unsaved Image 124 My vs code version:

Version: 1.74.0-insider
Commit: d0e44be43287acadb13f7c2808332e00fe52568d
Date: 2022-11-25T08:00:14.076Z
Electron: 19.1.6
Chromium: 102.0.5005.167
Node.js: 16.14.2
V8: 10.2.154.15-electron.0
OS: Linux x64 6.0.11-arch1-1
Sandboxed: Yes

Updating the JSON setting extensions.verifySignature to false helped!

d2r2 on Dec 4, 2022