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!

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!

FWIW: the arrpc package seems to conflict with Vesktop's Rich Presence - Enable Rich Presence via arRPC--and as the arRPC user service seems to be enabled by default on installation, this causes Vesktop to not reflect Rich Presence updates.

For now, the solution is to either:

• Disable user arrpc.service, and enable only Vesktop's Rich Presence setting (or not have the arrpc package installed)

• Enable user arrpc.service, disable Vesktop's Rich Presence setting and enable the WebRichPresence (arRPC) Plugin.

@Kyuunex, thanks, fixed. I just didn't bumped the pkgrel because I think it doesn't deserve a rebuild for every AUR user just for that.

You are not renaming the downloaded source file on line 22, resulting in filenames like "v1.5.3.tar.gz" which may cause filename collisions on systems with SRCDEST env var set.

read: https://wiki.archlinux.org/title/PKGBUILD#source

@XcroatoanX, it worked because flatpak uses a different directory for the config, which is what apparently got broken at some point. In some sense, it's the same as deleting the old config directory and starting again.

@Edu4rdSHL, It fixed my issue, now working! What's weird, the screen sharing was working out of the box for me on flatpak. Though, Vesktop itself was loading for ages, so this is working much better for me. Thank you for your work!

Ok, I experienced the issue itself. There was some Discord ¿? update that broke it. If you go to the app settings, you will not see anything related to Vesktop but only Discord, as if it has overwritten the whole Vesktop interface and options.

The fix: Close the Vesktop app, mv ~/.config/vesktop ~/config/vesktop.old, open the app again and login, see if the issue is fixed (that worked for me).

If everything is good, you can rm -r ~/.config/vesktop.old if you like.