Arch Linux User Repository

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

Getting similar issues to what's described.

Vesktop will launch but not show on any display. I'm running AMD/AMD.

Here's the log.

I think the latest update causes screen sharing to be nearly unusable on my system (i9-13900k & RTX 4090, using proprietary NVIDIA drivers). Within a few seconds of screen sharing, Vesktop creates roughly 20 threads and they're all maxed out at 100% CPU, making my PC lag like crazy.

Not related to this package specifically, as I also experience it on the Flatpak version. Could be related to the Wayland changes in the comments prior to this one. On the Flatpak version I can just disable the wayland permission and that solves my issue, but here it's not as accessible.

@iiPython your crash looks like https://github.com/NVIDIA/open-gpu-kernel-modules/issues/644, which seems to be related to hardware acceleration on nvidia and Wayland.

Seeing that electron is not ready for Wayland+nvidia yet, I think --ozone-platform-hint=auto should ultimately be removed and vesktop should stick to the default electron behavior of running via Xwayland. Users wanting to use Wayland will either have to patch the PKGBUILD or pass command line arguments to electron by other means. (note that passing env ELECTRON_OZONE_PLATFORM_HINT=auto as a command line argument has no effect!)

I can confirm I have the issue on Wayland with Intel iGPU + nvidia dGPU (laptop) as well.

For those who need to revert: sudo downgrade vesktop-bin and use 1.5.4-2 instead of 1.5.4-3

Can confirm @iiPython. For the record, there is an open issue with electron that looks similar (https://github.com/electron/electron/issues/44607). What I'm wondering is whether this is an issue for everyone using Wayland, or an nvidia-specific issue (I'm using the 565.77 driver). Or maybe we're both missing something.

I might be missing something here, but the recent change to add --ozone-platform-hint=auto (on wayland, labwc) stops vesktop from launching with the following spat out:

ERR: ImageEGL.cpp:112 (operator()): eglCreateImage failed with 0x00003009
[3388:0125/001346.673291:ERROR:scoped_egl_image.cc(23)] Failed to create EGLImage: EGL_SUCCESS
[3388:0125/001346.673348:ERROR:native_pixmap_egl_binding.cc(118)] Unable to initialize binding from pixmap
[3388:0125/001346.673437:ERROR:ozone_image_backing.cc(309)] OzoneImageBacking::ProduceSkiaGanesh failed to create GL representation
[3388:0125/001346.673532:ERROR:shared_image_manager.cc(255)] SharedImageManager::ProduceSkia: Trying to produce a Skia representation from an incompatible backing: OzoneImageBacking
[3388:0125/001346.673702:ERROR:gpu_service_impl.cc(1161)] Exiting GPU process because some drivers can't recover from errors. GPU process will restart shortly.
[3297:0125/001346.690443:ERROR:gpu_process_host.cc(982)] GPU process exited unexpectedly: exit_code=8704
[3402:0125/001346.867027:ERROR:angle_platform_impl.cc(44)] ImageEGL.cpp:112 (operator()): eglCreateImage failed with 0x00003009

Removing it and switching back to the environment variable fixes it.

please remove debugedit from makedeps

@romch007 OK, I have made modifications according to your suggestion. However, I haven't used this program and Wayland myself. So if others have any problems, please provide feedback in time.

@zxp19821005 Yes, but that's an environment variable, and I'm not sure it belongs in the command line arguments of electron. And the current PKGBUILD doesn't work for wayland anyway.

@romch007 https://wiki.archlinux.org/title/Wayland#Electron