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!

The /bin/sh shebang in the shell script is incorrect; the double brackets ([[ and ]]) are a bashism and ought to be converted to single brackets or explicitly requesting bash as the shell.

I'm using the package on Gnome Wayland, and I'm certainly not affected, so your claim is false. Plus, the upstream issue has very little interaction, so I doubt that's impacting "everyone".

In fact, only 3 persons have reported issues here on this package.

The issue is with electron, but it affects everyone using KDE Wayland (possible Gnome or Wayland in general?) EDIT: It affects everyone using Wayland, which is most people on Arch...

The package should be downgraded to electron29 until it's fixed upstream, this issue also affects alot of other electron packages such as VSCode/VSCodium which have also held back electron and added the platform hint flag.

This package works just fine, the issue is present on only a few setups and is a problem with electron, not the package itself.

This package is broken, segfaults. vesktop-bin seems to work fine.

The workaround isn't functional on my setup, even explicitly giving --ozone-platform-hint=x11 outright.

That said, I have instead: 1. Installed electron29 2. Put the following script early in my PATH as vesktop:

#!/bin/sh
exec electron29 /usr/lib/vesktop/app.asar

...and this works for me for now.

(...Copying the handling of vesktop-flags.conf is left as an exercise to the reader :P)

I don't want to be that guy, but:

• If the package builds using makepkg -s, I don't care if your AUR helper doesn't work, it's a problem with your AUR helper and needs to be fixed there. Here's the build log for the latest version: https://gist.github.com/Edu4rdSHL/929a7eba81165da5166c4d0974d0e96f
• I can't reproduce the current electron issue with v30, and seems that only a few users are having the issue. So I don't see any reason to downgrade the electron version for everyone. Plus, Athonathonathon put a workaround for it, which seems to be related to the current Chrome breakage on Wayland setups.

The Wayland issue has been fixed from 1.5.1-2 onwards.

On Wayland a fix I found was by passing in --ozone-platform-hint=auto from the command line or setting it in the electron config file.

See: https://wiki.archlinux.org/title/Wayland#Command_line_flags

==> Запускается build()...
Lockfile is up to date, resolution step is skipped
Packages: +574
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 ERR_PNPM_LINKING_FAILED  Error: EINVAL: invalid argument, copyfile '/home/restranger/.local/share/pnpm/store/v3/files/cf/83e1357eefb8bdf1542850d66d8007d620e4050b5715dc83f4a921d36ce9ce47d0d13c5d85f2b0ff8318d2877eec2f63b931bd47417a81a538327af927da3e' -> '/home/restranger/.cache/yay/vesktop/src/Vesktop-1.5.1/node_modules/@vencord/venmic_tmp_75278/node_modules/node-addon-api/nothing.c'
Progress: resolved 0, reused 1, downloaded 0, added 0
==> ОШИБКА: Произошел сбой в build().
    Прерывание...
 -> ошибка сборки: vesktop-exit status 4
 -> Failed to install the following packages. Manual intervention is required:
vesktop - exit status 4

electron30 is broken and segfaults on many setups. see https://github.com/electron/electron/issues/41839

fix is to downgrade to electron29