When Wayland is enabled, system log will be full of messages like this: [3718270:1106/133951.028741:ERROR:gbm_pixmap_wayland.cc(82)] Cannot create bo with format= YUV_420_BIPLANAR and usage=SCANOUT_CPU_READ_WRITE [3718270:1106/133951.028891:ERROR:gpu_channel.cc(502)] Buffer Handle is null. The root cause is a chromium issue (see URL) that is fixed in Chromium 131.0.6738.0. Electron e33 is still only at Chromium 130.0.6723.44 (see: https://www.electronjs.org/blog/electron-33-0 ) and discord is still only at Electron e32 There is a workaround: launch discord with --disable-gpu-memory-buffer-video-frames command-line argument when wayland is enabled. I propose we add --disable-gpu-memory-buffer-video-frames to the launch parameters of discord when wayland is used till the electron used in discord catches up with latest Chromium. Reproducible: Always
Created attachment 907998 [details, diff] Fix wayland log spam with launch paramter This is the diff of launcher.sh that fixes the problem for me.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=10edd70862670c0b6a9eb4930e6951192537b27e commit 10edd70862670c0b6a9eb4930e6951192537b27e Author: Nick Sarnie <sarnex@gentoo.org> AuthorDate: 2024-11-07 19:38:42 +0000 Commit: Nick Sarnie <sarnex@gentoo.org> CommitDate: 2024-11-07 19:38:42 +0000 net-im/discord: Fix system log spam on Wayland Closes: https://bugs.gentoo.org/942950 Signed-off-by: Nick Sarnie <sarnex@gentoo.org> net-im/discord/{discord-0.0.73.ebuild => discord-0.0.73-r1.ebuild} | 0 net-im/discord/files/launcher.sh | 1 + 2 files changed, 1 insertion(+)
