Wayland broken mouse cursor since a few versions ago
-
when running Vivaldi under Wayland (either with the vivaldi://flags/#ozone-platform-hint set to auto or
Vivaldi --enable-features=UseOzonePlatform --ozone-platform=wayland
) the mouse cursor does not work correctly ( what it's actually pointing to in Vivaldi is off from whats render on-screen)EDIT: works fine on the latest chromium from the arch repos
Version 105.0.5195.102 (Official Build) Arch Linux (64-bit)
so it seems to be a Vivaldi bug?EDIT2: NVM was able to reproduce on the same chromium build. It seems random though some launchs it will work fine and others the mouse input will be off. on vivaldi its consistant
btw noticed I didn't provide sys specs
inxi -b System: Host: Garuda-Linux Kernel: 5.19.8-269-tkg-bmq arch: x86_64 bits: 64 Desktop: KDE Plasma v: 5.25.5 Distro: Garuda Linux Machine: Type: Desktop Mobo: ASRock model: X470 Taichi serial: <superuser required> UEFI: American Megatrends v: P4.90 date: 05/18/2022 CPU: Info: 6-core AMD Ryzen 5 5600X [MT MCP] speed (MHz): avg: 3897 min/max: 2200/4650 Graphics: Device-1: AMD Navi 22 [Radeon RX 6700/6700 XT/6750 XT / 6800M] driver: amdgpu v: kernel Display: wayland server: X.org v: 1.21.1.4 with: Xwayland v: 22.1.3 compositor: kwin_wayland driver: X: loaded: amdgpu unloaded: modesetting,radeon gpu: amdgpu resolution: 1: 2048x864 2: 1536x864 OpenGL: renderer: AMD Radeon RX 6700 XT (navy_flounder LLVM 14.0.6 DRM 3.47 5.19.8-269-tkg-bmq) v: 4.6 Mesa 22.1.7 Network: Device-1: Intel Dual Band Wireless-AC 3168NGW [Stone Peak] driver: iwlwifi Device-2: Intel I211 Gigabit Network driver: igb Drives: Local Storage: total: 2.96 TiB used: 3.91 TiB (132.4%) Info: Processes: 437 Uptime: 27m Memory: 31.27 GiB used: 14.85 GiB (47.5%) Shell: fish inxi: 3.3.20
-
might be related to this?
-
@zany130 Running Vivaldi as native Wayland app is currently not supported. To my knowledge bugs won’t be fixed, you are on your own. Run Vivaldi as XWayland app for full support.
-
I've not experienced it on sway yet, but you said it yourself that it's a chromium thing.
I've actually not read about any vivaldi-specific wayland bugs yet, so everything that does not work will likely be caused and (for now) to be fixed by upstream chromium. Thank you for the post still, I very much appreciate such warnings.
-
ah ok problem is kde currently has problems with Xwayland apps being blurry