Arch Linux User Repository

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

Hmm, I still need to have Exec=/usr/bin/vesktop -enable-features=UseOzonePlatform,WaylandWindowDecorations --ozone-platform=wayland %U in my vesktop.desktop file to avoid it starting with Xwayland.

Scratch that, I'm on the "vesktop" pkg, not "vesktop-bin".

Why must AMD users suffer to satisfy NVIDIA users and be the ones to hook/do custom shit instead of the other way around...? :(

@xiaoxigua-1 Thanks for your feedback, added it.

Enable Wayland IME support for proper input in Wayland sessions

From f475fd26cd2282e302332e41a8d6d31500a4270b Mon Sep 17 00:00:00 2001
From: xiaoxigua-1 <xigua@xigua.tw>
Date: Sun, 13 Apr 2025 12:47:50 +0800
Subject: [PATCH] Enable Wayland IME support

---
 .SRCINFO | 2 +-
 PKGBUILD | 6 +++---
 2 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/.SRCINFO b/.SRCINFO
index dc74472..53a8898 100644
--- a/.SRCINFO
+++ b/.SRCINFO
@@ -1,7 +1,7 @@
 pkgbase = vesktop-bin
    pkgdesc = A cross platform electron-based desktop app aiming to give you a snappier Discord experience with Vencord pre-installed.(Prebuilt version.Use system-wide electron)
    pkgver = 1.5.5
-   pkgrel = 1
+   pkgrel = 2
    url = https://github.com/Vencord/Vesktop
    arch = aarch64
    arch = x86_64
diff --git a/PKGBUILD b/PKGBUILD
index 757a775..fb36de9 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -6,7 +6,7 @@ _pkgname=Vesktop
 _appname=vencord-desktop
 pkgver=1.5.5
 _electronversion=34
-pkgrel=1
+pkgrel=2
 pkgdesc="A cross platform electron-based desktop app aiming to give you a snappier Discord experience with Vencord pre-installed.(Prebuilt version.Use system-wide electron)"
 arch=(
     'aarch64'
@@ -38,7 +38,7 @@ prepare() {
         s/@appname@/${pkgname%-bin}/g
         s/@runname@/app.asar/g
         s/@cfgdirname@/${pkgname%-bin}/g
-        s/@options@/--ozone-platform-hint=auto/g
+        s/@options@/--ozone-platform-hint=auto --enable-wayland-ime/g
     " -i "${srcdir}/${pkgname%-bin}.sh"
     sed -i "s/\/opt\/${_pkgname}\/${pkgname%-bin}/${pkgname%-bin}/g" "${srcdir}/usr/share/applications/${pkgname%-bin}.desktop"
 }
@@ -51,4 +51,4 @@ package() {
         install -Dm644 "${srcdir}/usr/share/icons/hicolor/${_icons}/apps/${pkgname%-bin}.png" \
             -t "${pkgdir}/usr/share/icons/hicolor/${_icons}/apps"
     done
-}
\ No newline at end of file
+}
-- 
2.49.0

@chaos2theory, can confirm since UI update the app will crash at random, at least once every couple hours.

Looks to have broken with the big discord UI update - get an error about looking for a CSS file that doesnt exist anymore

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.