Arch Linux User Repository

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

@mjevange yes, pipewire + xdg-desktop-portal is the way. I guess you could check the wiki's pages for both and check if everything is working well.

The vesktop.sh script reads the flags from ${XDG_CONFIG_HOME}/vesktop-flags.conf, but I'm pretty sure the flags from ${XDG_CONFIG_HOME}/electron-flags.conf are also used by Vesktop, that's where I'm putting my flags.

As for which flags, I think you should first check the wiki's hardware video acceleration page to be sure, and then the wiki's page for Chromium's hardware video acceleration.

I'm using these flags, but some are probably not needed, either because they apply to the browser instead or you don't have a use case for them:

--enable-features=AllowQt,CanvasOopRasterization,UseChromeOSDirectVideoDecoder,PlatformHEVCDecoderSupport,AcceleratedVideoEncoder,AcceleratedVideoDecodeLinuxGL,AcceleratedVideoDecodeLinuxZeroCopyGL,SkiaGraphite,UseVulkanForWebGL,Vulkan,DefaultANGLEVulkan,VulkanFromANGLE,VaapiVideoDecoder,VaapiIgnoreDriverChecks
--enable-blink-features=MiddleClickAutoscroll
--gtk-version=4
--enable-unsafe-webgpu

Tried all sorts of flags but crashes after selecting a window or screen in share picker.

Are people using Pipewire + xdg-desktop-portal for screen share or something else?

Are people setting flags in electron-flags.conf, chromium-flags.conf, or /usr/bin/vesktop?

AMD GPU btw

Also ScreenShare works well at https://mozilla.github.io/webrtc-landing/gum_test.html so I know the Pipewire/desktop-portal config is working

If you suddenly start opening to a black/blank window, try disabling VPN if using one.

In my case, the black screen appears to be caused by network connections being blocked when using certain VPN endpoints (possibly Discord-side restrictions), rather than a graphics or configuration issue. Hope that helps others with the empty window issue.

Now that Vesktop uses Electron 39, the Wayland flags can be removed. Since Electron 38, it "now defaults to running as a native Wayland app when launched in a Wayland session".

Edit: from the Arch Wiki page about Chromium hardware video acceleration, the only flags needed now are:

• "AcceleratedVideoDecodeLinuxGL" to have hardware video acceleration
• "AcceleratedVideoDecodeLinuxZeroCopyGL" to possibly have better performance
• "VaapiOnNvidiaGPUs" to add support for the proprietary NVIDIA driver

I was personally able to get around the blank screen issues mentioned by removing the following command line args:

--enable-features=CanvasOopRasterization,VaapiVideoDecoder,UseChromeOSDirectVideoDecoder,VaapiIgnoreDriverChecks,PlatformHEVCDecoderSupport,Vulkan,DefaultANGLEVulkan,VulkanFromANGLE

I also get the same black screen when I open Vesktop.

I've also been having the same black screen issue. I've been temporarily fixing it by installing the latest electron37-bin (37.6.1-1), rebooting, downgrading to electron37-bin 37.6.0, rebooting, and then being able to open vesktop.

I'm unsure if opening vesktop in between reboots is necessary. Honestly I have no idea why this works, or why it only works untill the next reboot.

Currently have the same issue as others are describing in both Wayland and X11 only get a black screen after loading vesktop. Same thing with equibop. The official client works fine.

Having the following issue. Any idea what's going on?

APPIMAGE env is not defined, current application is not an AppImage
Vesktop v1.5.7
Disabled Chromium features: WinRetrieveSuggestionsOnlyOnDemand, HardwareMediaKeyHandling, MediaSessionService
checkForUpdatesAndNotify called, downloadPromise is null
[arRPC > ipc] listening at /run/user/1000/discord-ipc-0
[arRPC > websocket] listening on 6463
[arRPC > process] started
[17206:0702/000039.078554:FATAL:electron/shell/browser/electron_browser_main_parts.cc:502] Failed to shutdown.
zsh: trace trap (core dumped)  vesktop

equibop-bin is gives me the same thing.

@captcapslock I'm trying to fix it by reference the shell script of equibop-bin, will you please try again?