KDE Plasma 6.0.5 Wayland, also seen on KDE Plasma 5.27.11 Wayland
What happens when the bug or crash occurs?
Whenever I stream using vesktop on KDE wayland, my mouse cursor shows up as the wrong color (stream shows orange cursor, actual cursor is purple), and the cursor is on screen at all times regardless of whether or not its actually visible. This is visible both on stream and on the stream preview. This happens regardless of what is being streamed (full screen or specific window).
Here is a video example where these exact issues can be seen while streaming slime rancher:
(sorry for low bitrate, not much i can do about it, however i believe the issue should be easy to see regardless)
This video was taken while using nvidia gpu as primary render gpu in kwin, but I have also replicated this using an intel gpu as the main gpu with no involvement from nvidia. it doesn't seem to make any difference.
What is the expected behaviour?
I expect the mouse cursor to be the correct color if possible, and, much more importantly, not be on screen even when the mouse is meant to be hidden. It is difficult to stream games or movies and having people complain about my cursor obstructing the screen at all times.
How do you recreate this bug or crash?
Stream any app where mouse should be hidden at any point on KDE wayland (unsure if issue affects other desktop environments)
mouse is discolored and also not hidden
Debug Logs
Gtk-Message: 17:12:42.324: Failed to load module "appmenu-gtk-module"
src/gbm_drv_common.c:131: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000
src/gbm_drv_common.c:131: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000
src/gbm_drv_common.c:131: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000
src/gbm_drv_common.c:131: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000
src/gbm_drv_common.c:131: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000
[arRPC > ipc] not available, trying again (attempt 1)
[arRPC > ipc] listening at /run/user/1000/discord-ipc-1
[arRPC > websocket] 6463 in use!
[arRPC > websocket] listening on 6464
[arRPC > process] started
'loop->recurse > 0' failed at ../pipewire/src/pipewire/thread-loop.c:426 pw_thread_loop_wait()
[2024-06-12 17:13:04.329] [venmic] [info] [patchbay] (get) running venmic 3.4.2
[2024-06-12 17:13:04.346] [venmic] [info] [patchbay] (handle) found default metadata: 37
[2024-06-12 17:13:04.346] [venmic] [info] [patchbay] (meta_update) speaker name: "alsa_output.usb-Sony_Interactive_Entertainment_Wireless_Headset-00.analog-stereo"
'loop->recurse > 0' failed at ../pipewire/src/pipewire/thread-loop.c:426 pw_thread_loop_wait()
[25846:0612/171319.365475:ERROR:vaapi_wrapper.cc(1558)] Could not get a valid VA display
[25846:0612/171319.365594:ERROR:vaapi_video_encode_accelerator.cc(1141)] Calling NotifyErrorStatus(7), message=Failed initializing VAAPI for profile h264 baseline
[25846:0612/171319.365650:ERROR:mojo_video_encode_accelerator_service.cc(361)] Call NotifyErrorStatus(): code=7, message=Failed initializing VAAPI for profile h264 baseline
[25846:0612/171323.412011:ERROR:vaapi_wrapper.cc(1558)] Could not get a valid VA display
[25846:0612/171323.412138:ERROR:vaapi_video_encode_accelerator.cc(1141)] Calling NotifyErrorStatus(7), message=Failed initializing VAAPI for profile h264 baseline
[25846:0612/171323.412189:ERROR:mojo_video_encode_accelerator_service.cc(361)] Call NotifyErrorStatus(): code=7, message=Failed initializing VAAPI for profile h264 baseline
[25846:0612/171327.422790:ERROR:vaapi_wrapper.cc(1558)] Could not get a valid VA display
[25846:0612/171327.422898:ERROR:vaapi_video_encode_accelerator.cc(1141)] Calling NotifyErrorStatus(7), message=Failed initializing VAAPI for profile h264 baseline
[25846:0612/171327.422939:ERROR:mojo_video_encode_accelerator_service.cc(361)] Call NotifyErrorStatus(): code=7, message=Failed initializing VAAPI for profile h264 baseline
Request Agreement
[X] I have searched the existing issues and found no similar issue
[X] I am using the latest Vesktop and Vencord versions
[X] This issue occurs on an official release (not just the AUR or Nix packages)
Discord Account
queenbiscuit311
Operating System
Arch Linux, also seen on Kubuntu 24.04 LTS
Linux Only ~ Desktop Environment
KDE Plasma 6.0.5 Wayland, also seen on KDE Plasma 5.27.11 Wayland
What happens when the bug or crash occurs?
Whenever I stream using vesktop on KDE wayland, my mouse cursor shows up as the wrong color (stream shows orange cursor, actual cursor is purple), and the cursor is on screen at all times regardless of whether or not its actually visible. This is visible both on stream and on the stream preview. This happens regardless of what is being streamed (full screen or specific window).
Here is a video example where these exact issues can be seen while streaming slime rancher:
https://github.com/Vencord/Vesktop/assets/88851292/129524fb-f16b-4eba-9d82-f8c8a6275ab2
(sorry for low bitrate, not much i can do about it, however i believe the issue should be easy to see regardless)
This video was taken while using nvidia gpu as primary render gpu in kwin, but I have also replicated this using an intel gpu as the main gpu with no involvement from nvidia. it doesn't seem to make any difference.
What is the expected behaviour?
I expect the mouse cursor to be the correct color if possible, and, much more importantly, not be on screen even when the mouse is meant to be hidden. It is difficult to stream games or movies and having people complain about my cursor obstructing the screen at all times.
How do you recreate this bug or crash?
Debug Logs
Request Agreement