Arch Linux User Repository

As of 2024-09-16, this package is being co-maintained by official vesktop developers, and any packaging decisions they make will not be questioned on my part unless it's something harmful for the users, which is very unlikely to happen. As I see it coming, they will not use the system's electron on this package purposely, if you don't like it, use vesktop-electron, which is also maintained by the same devs.

Thanks!

@Edu4rdSHL: Does it work if using makepkg directly?

No, as that is what i was using when I got the same error.

Tried using yay as well, and that didn't work either (I don't know why I tried, but it was nice to see anyway).

fyi- if vesktop.sh is going to use /bin/sh, it should be POSIX-compliant. The [[ syntax for tests is a bashism. I am using dash as my /bin/sh, and just noticed that vesktop is silently throwing an error on every startup.

I would recommend adjusting the script to use a single [ (looks like that will still work portably!), or failing that, you can specify that you want /bin/bash in your shebang.

Does it work if using makepkg directly?

Unfortunately, the problem what @itlis pointed out occurs when installing manually without the use of pamac as well.

==> Making package: vesktop 1.5.5-4 (Thu 06 Mar 2025 06:17:21 PM CST)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found Vesktop-1.5.5.tar.gz
  -> Found vesktop.desktop
  -> Found vesktop.sh
  -> Found afterPack.js
==> Validating source files with sha256sums...
    Vesktop-1.5.5.tar.gz ... Passed
    vesktop.desktop ... Passed
    vesktop.sh ... Passed
    afterPack.js ... Passed
==> Extracting sources...
  -> Extracting Vesktop-1.5.5.tar.gz with bsdtar
==> Removing existing $pkgdir/ directory...
==> Starting build()...
/home/swirly/.config/nvm/versions/node/v22.13.0/lib/node_modules/corepack/dist/lib/corepack.cjs:21535
  if (key == null || signature == null) throw new Error(`Cannot find matching keyid: ${JSON.stringify({ signatures, keys })}`);
                                              ^

Error: Cannot find matching keyid: {"signatures":[{"sig":"MEUCIQD4HgoU3gpD1VhZl66ZKcKEjoK5+najimL8eN5vXJQQAwIgA3wqaVibkcwBu4ep9EF70MchM0G+Z3FxlMsgj+4UaJo=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"keys":[{"expires":null,"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","keytype":"ecdsa-sha2-nistp256","scheme":"ecdsa-sha2-nistp256","key":"MFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAE1Olb3zMAFFxXKHiIkQO5cJ3Yhl5i6UPp+IhuteBJbuHcA5UogKo0EWtlWwW6KSaKoTNEYL7JlCQiVnkhBktUgg=="}]}
    at verifySignature (/home/swirly/.config/nvm/versions/node/v22.13.0/lib/node_modules/corepack/dist/lib/corepack.cjs:21535:47)
    at fetchLatestStableVersion (/home/swirly/.config/nvm/versions/node/v22.13.0/lib/node_modules/corepack/dist/lib/corepack.cjs:21553:5)
    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
    at async fetchLatestStableVersion2 (/home/swirly/.config/nvm/versions/node/v22.13.0/lib/node_modules/corepack/dist/lib/corepack.cjs:21672:14)
    at async Engine.getDefaultVersion (/home/swirly/.config/nvm/versions/node/v22.13.0/lib/node_modules/corepack/dist/lib/corepack.cjs:22298:23)
    at async Engine.executePackageManagerRequest (/home/swirly/.config/nvm/versions/node/v22.13.0/lib/node_modules/corepack/dist/lib/corepack.cjs:22396:47)
    at async Object.runMain (/home/swirly/.config/nvm/versions/node/v22.13.0/lib/node_modules/corepack/dist/lib/corepack.cjs:23102:5)

Node.js v22.13.0
==> ERROR: A failure occurred in build().
    Aborting...

Nothing else is helping. I am unable to use Vesktop as of now (except for the tar.gz version on it's GitHub releases page). This is great. Sooooo great.

Hi. I'm trying to install vesktop via "pamac install vesktop" but getting "Error: Cannot find matching keyid". Can someone help with it or at least explain what might be wrong? Full output (what looks like keys or ids removed to prevent leaks):

Building vesktop...
==> Making package: vesktop 1.5.5-4 (Sun 16 Feb 2025 15:31:35)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found Vesktop-1.5.5.tar.gz
  -> Found vesktop.desktop
  -> Found vesktop.sh
  -> Found afterPack.js
==> Validating source files with sha256sums...
    Vesktop-1.5.5.tar.gz ... Passed
    vesktop.desktop ... Passed
    vesktop.sh ... Passed
    afterPack.js ... Passed
==> Removing existing $srcdir/ directory...
==> Extracting sources...
  -> Extracting Vesktop-1.5.5.tar.gz with bsdtar
==> Removing existing $pkgdir/ directory...
==> Starting build()...
/usr/lib/node_modules/corepack/dist/lib/corepack.cjs:21535
  if (key == null || signature == null) throw new Error(`Cannot find matching keyid: ${JSON.stringify({ signatures, keys })}`);
                                              ^

Error: Cannot find matching keyid: {"signatures":[{"sig":"---","keyid":"SHA256:---"}],"keys":[{"expires":null,"keyid":"SHA256:---","keytype":"ecdsa-sha2-nistp256","scheme":"ecdsa-sha2-nistp256","key":"---"}]}
    at verifySignature (/usr/lib/node_modules/corepack/dist/lib/corepack.cjs:21535:47)
    at fetchLatestStableVersion (/usr/lib/node_modules/corepack/dist/lib/corepack.cjs:21553:5)
    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
    at async fetchLatestStableVersion2 (/usr/lib/node_modules/corepack/dist/lib/corepack.cjs:21672:14)
    at async Engine.getDefaultVersion (/usr/lib/node_modules/corepack/dist/lib/corepack.cjs:22298:23)
    at async Engine.executePackageManagerRequest (/usr/lib/node_modules/corepack/dist/lib/corepack.cjs:22396:47)
    at async Object.runMain (/usr/lib/node_modules/corepack/dist/lib/corepack.cjs:23102:5)

Node.js v23.4.0
==> ERROR: A failure occurred in build().
    Aborting...

Hey, don't know if it was asked before, but instead of using the node.js package and then enabling pnpm through corepack, wouldn't it be better to just use the pnpm package from the extra repo? it would take less resources and would also mean that pnpm would be up to date with version 10.

hey everyone, i can't seem to be able to compile. i ran yay -S vesktop and it just doesn't launch. i am cleanbuilding the app.

Progress: resolved 0, reused 553, downloaded 0, added 578, done
Done in 1.6s

> vesktop@1.5.3 build /home/archuser/.cache/yay/vesktop/src/Vesktop-1.5.3
> tsx scripts/build/build.mts

  • electron-builder  version=25.1.8 os=6.11.3-arch1-1
  • loaded configuration  file=package.json ("build" field)
  • description is missed in the package.json  appPackageFile=/home/archuser/.cache/yay/vesktop/src/Vesktop-1.5.3/package.json
  • writing effective config  file=dist/builder-effective-config.yaml
  • executing @electron/rebuild  electronVersion=31.1.0 arch=x64 buildFromSource=false appDir=./
  • installing native dependencies  arch=x64
  • completed installing native dependencies
  • packaging       platform=linux arch=x64 electron=31.1.0 appOutDir=dist/linux-unpacked
  ⨯ zip: not a valid zip file
github.com/develar/app-builder/pkg/archive/zipx.(*Extractor).extractAndWriteFile
    /Users/runner/work/app-builder/app-builder/pkg/archive/zipx/unzip.go:234
github.com/develar/app-builder/pkg/archive/zipx.Unzip.func1.1
    /Users/runner/work/app-builder/app-builder/pkg/archive/zipx/unzip.go:104
github.com/develar/app-builder/pkg/util.MapAsyncConcurrency.func2
    /Users/runner/work/app-builder/app-builder/pkg/util/async.go:68
runtime.goexit
    /Users/runner/hostedtoolcache/go/1.21.13/arm64/src/runtime/asm_amd64.s:1650  
  ⨯ /home/archuser/.cache/pnpm/dlx/ynnkdjpmvut7ntkjttccistpde/192a04edb18-7a34/node_modules/.pnpm/app-builder-bin@5.0.0-alpha.10/node_modules/app-builder-bin/linux/x64/app-builder process failed ERR_ELECTRON_BUILDER_CANNOT_EXECUTE
Exit code:
1  failedTask=build stackTrace=Error: /home/archuser/.cache/pnpm/dlx/ynnkdjpmvut7ntkjttccistpde/192a04edb18-7a34/node_modules/.pnpm/app-builder-bin@5.0.0-alpha.10/node_modules/app-builder-bin/linux/x64/app-builder process failed ERR_ELECTRON_BUILDER_CANNOT_EXECUTE
Exit code:
1
    at ChildProcess.<anonymous> (/home/archuser/.cache/pnpm/dlx/ynnkdjpmvut7ntkjttccistpde/192a04edb18-7a34/node_modules/.pnpm/builder-util@25.1.7/node_modules/builder-util/src/util.ts:255:14)
    at Object.onceWrapper (node:events:633:26)
    at ChildProcess.emit (node:events:518:28)
    at maybeClose (node:internal/child_process:1104:16)
    at Process.ChildProcess._handle.onexit (node:internal/child_process:304:5)
==> ERROR: A failure occurred in build().
    Aborting...
 -> error making: vesktop-exit status 4
 -> Failed to install the following packages. Manual intervention is required:
vesktop - exit status 4

what is the issue at hand here?

Any reason why we aren't using the scalable ico here?: https://github.com/Vencord/Vesktop/blob/main/static/icon.ico

using pngs for the icon isnt the best idea imo, leads to issues for example with fuzzel, the app launcher, where it is unable to display the large icon due to it not having a scalable version of the icon.

repeatedly getting this error when I try to run Vesktop. I'm using DWM on Arch Linux (so it is an X11 build). [17528:1007/171441.765763:ERROR:gbm_wrapper.cc(74)] Failed to get fd for plane.: No such file or directory (2) [17528:1007/171441.765786:ERROR:gbm_wrapper.cc(257)] Failed to export buffer to dma_buf: No such file or directory (2) ... [28048:1007/174104.114551:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 1 times! [28048:1007/174113.647400:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 2 times! [28048:1007/174113.648632:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 3 times! { discordBranch: 'stable', richPresence: 'on', importSettings: 'on', minimizeToTray: 'on' } Failed to import settings: Error: ENOENT: no such file or directory, scandir '/home/ioan_ciobanescu/.config/Vencord/settings' at readdirSync (node:fs:1507:26) at t.readdirSync (node:electron/js2c/node_init:2:13773) at WebContents.<anonymous> (VCDMain:87:4067) at WebContents.emit (node:events:519:28) { errno: -2, code: 'ENOENT', syscall: 'scandir', path: '/home/ioan_ciobanescu/.config/Vencord/settings' } Failed to fetch https://api.github.com/repos/Vendicated/Vencord/releases/latest. Gonna retry with backoff. Failed to fetch https://github.com/Vendicated/Vencord/releases/download/devbuild/vencordDesktopMain.js.map. Gonna retry with backoff. Failed to fetch https://github.com/Vendicated/Vencord/releases/download/devbuild/vencordDesktopPreload.js. Gonna retry with backoff. Failed to fetch https://github.com/Vendicated/Vencord/releases/download/devbuild/vencordDesktopPreload.js.map. Gonna retry with backoff. Failed to fetch https://github.com/Vendicated/Vencord/releases/download/devbuild/vencordDesktopRenderer.css. Gonna retry with backoff. Failed to fetch https://github.com/Vendicated/Vencord/releases/download/devbuild/vencordDesktopRenderer.css.map. Gonna retry with backoff. Failed to fetch https://github.com/Vendicated/Vencord/releases/download/devbuild/vencordDesktopRenderer.js. Gonna retry with backoff. Failed to fetch https://github.com/Vendicated/Vencord/releases/download/devbuild/vencordDesktopRenderer.js.LEGAL.txt. Gonna retry with backoff. Failed to fetch https://github.com/Vendicated/Vencord/releases/download/devbuild/vencordDesktopRenderer.js.map. Gonna retry with backoff. Failed to fetch https://github.com/Vendicated/Vencord/releases/download/devbuild/vencordDesktopMain.js.LEGAL.txt. Gonna retry with backoff. Failed to fetch https://github.com/Vendicated/Vencord/releases/download/devbuild/vencordDesktopMain.js. Gonna retry with backoff. I'm honestly at a loss for what I can do. I tried installing via AUR, Flatpak, and I've even done it Manually now. Same errors.

As of 2024-09-16, this package is being co-maintained by official vesktop developers, and any packaging decisions they make will not be questioned on my part unless it's something harmful for the users, which is very unlikely to happen. As I see it coming, they will not use the system's electron on this package purposely, if you don't like it, use vesktop-electron, which is also maintained by the same devs.

Thanks!