Arch Linux User Repository

This package has renamed to vesktop-bin (https://aur.archlinux.org/packages/vesktop-bin).

Electron dependency on package needs to be fixed, it doesn't automatically installed needed dependency electron31 and will give the user the error ERROR: Could not resolve all dependencies. and will fail to build unless you manually install the dependency yourself.

@HAZZA, @altermetax

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.

this fixed it for me :D

Hey, Same problem as last person, can't run screenshare on wayland and x11

Same for me, screensharing stopped working on both X11 and Wayland. It opens the popup to pick the window, framerate, resolution, audio etc., but the stream isn't started in the end

Hey! Unfortunately, Screen Sharing stopped working, and started giving me this error

(node:20896) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 11)

@v1993 Thanks for your feedback. The problem with the flags I've fixed, and env ELECTRON_OZONE_PLATFORM_HINT=auto was according to https://wiki.archlinux.org/title/Wayland#Environment_variable

User flags file is not actually working. In the wrapper script, options are loaded into the flags array, but _USER_FLAGS is then used in command invocation; simply replacing both instances of flags with _USER_FLAGS fixes the problem.

Also, env ELECTRON_OZONE_PLATFORM_HINT=auto doesn't seem to have any effect, so I have to pass --ozone-platform-hint=auto as an argument.

@chaos2theory Maybe you don't know the difference between pkgver and pkgrel. When I've modified the PKGBUILD or something else, push on AUR, I would change the pkgrel , now the pkgver. 1.5.2-2 means that the pkgver is 1.5.2, and I've two commits. I think you need to read the related wiki carefully.

@troy0h Thanks for your feedback , there was a mistake in vesktop.sh , fixed now.

Hi, the newest update (1.5.2-1) now gives an error when trying to run, saying that the Electron module can't be found:

❯ vesktop
node:internal/modules/cjs/loader:1058
  throw err;
  ^

Error: Cannot find module 'electron'
Require stack:
- /usr/lib/vesktop/app.asar/dist/js/main.js
    at Module._resolveFilename (node:internal/modules/cjs/loader:1055:15)
    at Module._load (node:internal/modules/cjs/loader:908:27)
    at c._load (node:electron/js2c/node_init:2:13672)
    at Module.require (node:internal/modules/cjs/loader:1122:19)
    at require (node:internal/modules/helpers:130:18)
    at Object.<anonymous> (VCDMain:15:6191)
    at Module._compile (node:internal/modules/cjs/loader:1256:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1311:10)
    at Module.load (node:internal/modules/cjs/loader:1098:32)
    at Module._load (node:internal/modules/cjs/loader:945:12) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [ '/usr/lib/vesktop/app.asar/dist/js/main.js' ]
}