VSCodeVim / VSCodeVim/Vim

Extension Signature Verification Failed: Vim

Open
#9,634 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
15.2k
Forks
1.5k
Avg merge
3d 18h
Merged PRs (30d)
6

Description

Type: Bug

Please include following log F1 > Open View... > Shared below.

2025-05-19 19:52:51.429 [info] [Shared] Getting Manifest... vscodevim.vim
2025-05-19 19:52:51.528 [info] [Shared] Installing extension: vscodevim.vim {"pinned":true,"productVersion":{"version":"1.100.2","date":"2025-05-15T18:08:15.674Z"},"operation":3,"isApplicationScoped":false,"profileLocation":{"$mid":1,"external":"vscode-userdata:/home/hagabaka/.vscode-oss/extensions/extensions.json","path":"/home/hagabaka/.vscode-oss/extensions/extensions.json","scheme":"vscode-userdata"}}
2025-05-19 19:52:51.812 [info] [Shared] Extension signature verification result for vscodevim.vim: UnknownError. Internal Code: 159. Executed: true. Duration: 9ms.
2025-05-19 19:52:51.814 [error] [Shared] Error while installing the extension vscodevim.vim Signature verification failed with 'UnknownError' error. vscode-userdata:/home/hagabaka/.vscode-oss/extensions/extensions.json
2025-05-19 19:52:51.814 [error] [Shared] [uncaught exception in sharedProcess]: Signature verification failed with 'UnknownError' error.: SignatureVerificationInternal: Signature verification failed with 'UnknownError' error.
at yh.xb (file:///usr/lib/code/out/vs/code/electron-utility/sharedProcess/sharedProcessMain.js:74:64415)
at async yh.wb (file:///usr/lib/code/out/vs/code/electron-utility/sharedProcess/sharedProcessMain.js:74:62886)

Extension version: 1.29.0
VS Code version: Code - OSS 1.100.2 (848b80aeb52026648a8ff9f7c45a9b0a80641e2e, 2025-05-15T18:08:15.674Z)
OS version: Linux x64 6.14.2-zen1-1-zen
Modes:

System Info
Item Value
CPUs AMD Ryzen 7 7700X 8-Core Processor (16 x 5471)
GPU Status 2d_canvas: enabled
canvas_oop_rasterization: enabled_on
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_graphite: disabled_off
video_decode: enabled
video_encode: disabled_software
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: disabled_off
webnn: disabled_off
Load (avg) 2, 1, 1
Memory (System) 30.46GB (14.84GB free)
Process Argv --no-sandbox --unity-launch
Screen Reader no
VM 0%
DESKTOP_SESSION plasma
XDG_CURRENT_DESKTOP KDE
XDG_SESSION_DESKTOP KDE
XDG_SESSION_TYPE wayland

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The report provides only the extension-installation log and the generated sharedProcessMain.js stack trace; begin by reproducing the failure in Code - OSS 1.100.2 on Linux. Trace the UnknownError/Internal Code 159 path for vscodevim.vim, then verify that installing the extension completes without the signature-verification error.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript, vscode
Domain
devtools
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.