Regarding flickering disturbances on the screen and videos when using wayland (im japanese im new here my english not good im sorry)

[Kenyuu]

Hello. Nice to meet you, my name is Kenyu. I am Japanese. I’m still learning English, so I use translation. I love Garuda Linux and use it often. I recently deleted Windows and switched to Garuda.
I’m having trouble with a certain problem. Does the screen black out when using wayland? The display may quickly fade to black. YouTube videos are also distorted. There are many disturbances and flickers, making it difficult to use on a daily basis. I’m currently using x11. Although x11 does not have zero problems, it is still usable in daily life.
I think wayland is good and would like to use it.
I’ve searched a lot and searched forums for similar problems, but I couldn’t find any.
I don’t know if it’s related to this issue, but when I log out or restart, a screen similar to the one in the screenshot appears.
I don’t know if it’s related because I don’t know much about it.
Sorry for my poor explanation
I would appreciate it if you could tell me how to deal with it. please.

╭─rodorin@rodorinPC in ~
╰─λ garuda-inxi
System:
Kernel: 6.7.9-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=dc0b2e6a-ab9f-426d-bbcd-eafc233813db rw rootflags=subvol=@
quiet resume=UUID=45b71144-8e18-4fd0-9fe5-79293cefb5ae loglevel=3 ibt=off
Desktop: KDE Plasma v: 6.0.1 tk: Qt v: N/A info: frameworks v: 6.0.0
wm: kwin_wayland vt: 1 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
Type: Desktop Mobo: ASRock model: B660 Pro RS serial: <superuser required>
uuid: <superuser required> UEFI: American Megatrends LLC. v: 6.03
date: 01/14/2022
CPU:
Info: model: 12th Gen Intel Core i5-12600KF bits: 64 type: MST AMCP
arch: Alder Lake gen: core 12 level: v3 note: check built: 2021+
process: Intel 7 (10nm ESF) family: 6 model-id: 0x97 (151) stepping: 2
microcode: 0x32
Topology: cpus: 1x cores: 10 mt: 6 tpc: 2 st: 4 threads: 16 smt: enabled
cache: L1: 864 KiB desc: d-4x32 KiB, 6x48 KiB; i-6x32 KiB, 4x64 KiB
L2: 9.5 MiB desc: 6x1.2 MiB, 1x2 MiB L3: 20 MiB desc: 1x20 MiB
Speed (MHz): avg: 800 high: 802 min/max: 800/4900:3600 scaling:
driver: intel_pstate governor: powersave cores: 1: 800 2: 800 3: 802 4: 800
5: 800 6: 800 7: 800 8: 800 9: 800 10: 800 11: 800 12: 800 13: 800 14: 800
15: 800 16: 800 bogomips: 117964
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: NVIDIA TU102 [GeForce RTX 2080 Ti Rev. A] vendor: ASUSTeK
driver: nvidia v: 550.54.14 alternate: nouveau,nvidia_drm non-free: 545.xx+
status: current (as of 2024-02; EOL~2026-12-xx) arch: Turing code: TUxxx
process: TSMC 12nm FF built: 2018-2022 pcie: gen: 1 speed: 2.5 GT/s
lanes: 16 link-max: gen: 3 speed: 8 GT/s ports: active: none
off: DP-2,HDMI-A-1 empty: DP-1,HDMI-A-2,Unknown-2 bus-ID: 01:00.0
chip-ID: 10de:1e07 class-ID: 0300
Display: wayland server: X.org v: 1.21.1.11 with: Xwayland v: 23.2.4
compositor: kwin_wayland driver: X: loaded: nvidia
unloaded: modesetting,nouveau alternate: fbdev,nv,vesa gpu: nvidia
d-rect: 4480x1440 display-ID: 0
Monitor-1: DP-2 pos: primary,left res: 2560x1440 size: N/A modes: N/A
Monitor-2: HDMI-A-1 pos: right res: 1920x1080 size: N/A modes: N/A
API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia device: 2
drv: swrast gbm: drv: nvidia surfaceless: drv: nvidia wayland: drv: nvidia
x11: drv: zink inactive: device-1
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 550.54.14
glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2
memory: 10.74 GiB display-ID: :1.0
API: Vulkan v: 1.3.279 layers: 14 device: 0 type: discrete-gpu name: NVIDIA
GeForce RTX 2080 Ti driver: nvidia v: 550.54.14 device-ID: 10de:1e07
surfaces: xcb,xlib,wayland device: 1 type: cpu name: llvmpipe (LLVM
17.0.6 256 bits) driver: mesa llvmpipe v: 24.0.2-arch1.2 (LLVM 17.0.6)
device-ID: 10005:0000 surfaces: xcb,xlib,wayland
Audio:
Device-1: Intel Alder Lake-S HD Audio vendor: ASRock driver: snd_hda_intel
v: kernel alternate: snd_sof_pci_intel_tgl bus-ID: 00:1f.3
chip-ID: 8086:7ad0 class-ID: 0403
Device-2: NVIDIA TU102 High Definition Audio vendor: ASUSTeK
driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
bus-ID: 01:00.1 chip-ID: 10de:10f7 class-ID: 0403
Device-3: Logitech G733 Gaming Headset
driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 1.1 speed: 12 Mb/s
lanes: 1 mode: 1.1 bus-ID: 1-4.4:9 chip-ID: 046d:0ab5 class-ID: 0300
API: ALSA v: k6.7.9-zen1-1-zen status: kernel-api with: aoss
type: oss-emulator tools: N/A
Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
Server-2: PipeWire v: 1.0.3 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Intel Ethernet I219-V vendor: ASRock driver: e1000e v: kernel
port: N/A bus-ID: 00:1f.6 chip-ID: 8086:1a1d class-ID: 0200
IF: enp0s31f6 state: up speed: 1000 Mbps duplex: full mac: <filter>
Info: services: NetworkManager,systemd-timesyncd
Bluetooth:
Device-1: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) driver: btusb
v: 0.8 type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-7:5
chip-ID: 0a12:0001 class-ID: e001
Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 2.1
lmp-v: 4 status: discoverable: no pairing: no class-ID: 6c0104
Drives:
Local Storage: total: 5.48 TiB used: 189 GiB (3.4%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 970 EVO 500GB
size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: 2B2QEXE7 temp: 27.9 C
scheme: GPT
ID-2: /dev/sda maj-min: 8:0 vendor: Toshiba model: DT01ACA100
size: 931.51 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
tech: HDD rpm: 7200 serial: <filter> fw-rev: A750 scheme: GPT
ID-3: /dev/sdb maj-min: 8:16 vendor: SanDisk model: SDSSDH3 1T00
size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 40RL scheme: GPT
ID-4: /dev/sdc maj-min: 8:32 vendor: Crucial model: CT525MX300SSD1
size: 489.05 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: R060 scheme: GPT
ID-5: /dev/sdd maj-min: 8:48 vendor: Western Digital
model: WD30EZRZ-00GXCB0 size: 2.73 TiB block-size: physical: 4096 B
logical: 512 B speed: 6.0 Gb/s tech: HDD rpm: 5400 serial: <filter>
fw-rev: 0A80 scheme: GPT
Partition:
ID-1: / raw-size: 431.16 GiB size: 431.16 GiB (100.00%)
used: 188.99 GiB (43.8%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 584 KiB (0.2%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
ID-3: /home raw-size: 431.16 GiB size: 431.16 GiB (100.00%)
used: 188.99 GiB (43.8%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-4: /var/log raw-size: 431.16 GiB size: 431.16 GiB (100.00%)
used: 188.99 GiB (43.8%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-5: /var/tmp raw-size: 431.16 GiB size: 431.16 GiB (100.00%)
used: 188.99 GiB (43.8%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: partition size: 34.3 GiB used: 0 KiB (0.0%)
priority: -2 dev: /dev/nvme0n1p3 maj-min: 259:3
ID-2: swap-2 type: zram size: 31.18 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 16 dev: /dev/zram0
Sensors:
System Temperatures: cpu: 27.0 C mobo: N/A
Fan Speeds (rpm): N/A
Info:
Memory: total: 32 GiB available: 31.18 GiB used: 12.49 GiB (40.1%)
Processes: 432 Power: uptime: 26m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 12.43 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 255 default: graphical
tool: systemctl
Packages: pm: pacman pkgs: 2225 libs: 606 tools: octopi,pamac,paru,trizen
pm: appimage pkgs: 0 Compilers: clang: 17.0.6 gcc: 13.2.1 Shell: garuda-inxi
default: fish v: 3.7.0 running-in: konsole inxi: 3.3.33
Garuda (2.6.23-1):
System install date:     2024-02-12
Last full system update: 2024-03-12
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut nvidia-dkms
Windows dual boot:       No/Undetected
Failed units:            vmware.service

[Ankur]

Currently there are lot of things going on as KDE had shifted from KDE5 to KDE6,
You can try other browsers to see if it is browser specific problem or not .

[Bro]

NVidia rendering. That’s searchable here.

[filo]

Some people had improvements with Nvidia on Wayland adding the kernel boot parameter nvidia-drm.modeset=1.
You can do that with the Garuda Boot Options tool.
But for many this has had no effect at all.
The error message is unrelated in my opinion.
It is probably due to an Electron app (pcloud?) not working correctly, probably in Wayland.
I don’t know if this can help:
https://wiki.archlinux.org/title/Wayland#Electron
Here it seems that something similar helped:

Some of Electron apps are flashing on my PC with NVIDIA graphics card

Can you try with --enable-features=UseOzonePlatform,WaylandWindowDecorations --ozone-platform=wayland See if that changes anything? Hmm looking on the internet this seems a very common issue with not a lot of great solutions save for frustrated people going back to x11. Electron applications do not redraw properly to reflect latest input (reuse old frames) · Issue #187 · NVIDIA/open-gpu-kernel-modules · GitHub

But see also this recent comment:

Information for KDE users - KDE 6 available in Arch repos

I have an NVIDIA gpu and electron based apps are slow an glitchy on wayland, so I have to stick with X11. X11 is usable, but it feels a bit laggy; I’ll wait for more updates that can fix that.

[Kenyuu]

Thank you for taking the trouble to look into this. I will give it a try. Appreciate it.

[Ezahn]

@filo

But see also this recent comment:

I have an NVIDIA gpu and electron based apps are slow an glitchy on wayland, so I have to stick with X11. X11 is usable, but it feels a bit laggy; I’ll wait for more updates that can fix that.

I have the same experience, unfortunately: excellent desktop with Wayland, but completely flickering unsable gaming and streaming. With a GTX970. Never again an nVidia card to use with Linux, for me.