Problem with KWin, Wayland or Nvidia (I am not sure)

Desktop Environments Plasma
1

Hello.

Yesterday, I was comfortably playing Transport Fever 2 (which runs under Vulkan) and wanted to quickly tab out to write something in Discord. I noticed that although I could see Discord, I couldn’t do anything in it. Then I tried to open a browser, which worked, but the browser remained invisible. This happened with everything… until the taskbar crashed.

I had to restart the PC and did a full system update (you never know). Anyway, I noticed that I suddenly had a new icon saying that my desktop was now running in software mode. No idea why.

I then tinkered with ChatGPT, and the command kwin_wayland --replace helped to remove the icon. But now, the desktop keeps crashing.

Occasionally, when I try to click something in the taskbar, the taskbar crashes briefly and then comes back. The system is currently barely usable, and I simply don’t know enough about it to fix it myself.

Attached are an Inxi and a Journalctl.
This is my machine:

  Kernel: 6.13.5-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: initrd=\1b84d8b4717e4bffa8575f20f8f55d61\6.13.5-zen1-1-zen\initrd
    nvme_load=YES nowatchdog rw root=UUID=296daed9-0f47-4863-8425-1c37a5785919
    rw root=UUID=296daed9-0f47-4863-8425-1c37a5785919
    systemd.machine_id=1b84d8b4717e4bffa8575f20f8f55d61
  Desktop: KDE Plasma v: 6.3.2 tk: Qt v: N/A info: frameworks v: 6.11.0
    wm: kwin_wayland vt: 1 dm: SDDM Distro: EndeavourOS base: Arch Linux
Machine:
  Type: Desktop System: Gigabyte product: Z170X-UD3 v: N/A
    serial: <superuser required>
  Mobo: Gigabyte model: Z170X-UD3-CF v: x.x serial: <superuser required>
    uuid: <superuser required> UEFI: American Megatrends v: F23g date: 03/09/2018
CPU:
  Info: model: Intel Core i7-6700 bits: 64 type: MT MCP arch: Skylake-S
    gen: core 6 level: v3 note: check built: 2015 process: Intel 14nm family: 6
    model-id: 0x5E (94) stepping: 3 microcode: 0xF0
  Topology: cpus: 1x dies: 1 clusters: 4 cores: 4 threads: 8 tpc: 2
    smt: enabled cache: L1: 256 KiB desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB
    desc: 4x256 KiB L3: 8 MiB desc: 1x8 MiB
  Speed (MHz): avg: 800 min/max: 800/4000 scaling: driver: intel_pstate
    governor: powersave cores: 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800
    8: 800 bogomips: 54398
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: gather_data_sampling status: Vulnerable: No microcode
  Type: itlb_multihit status: KVM: Split huge pages
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT
    vulnerable
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed mitigation: IBRS
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
    prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
    sanitization
  Type: spectre_v2 mitigation: IBRS; IBPB: conditional; STIBP: conditional;
    RSB filling; PBRSB-eIBRS: Not affected; BHI: Not affected
  Type: srbds mitigation: Microcode
  Type: tsx_async_abort mitigation: TSX disabled
Graphics:
  Device-1: NVIDIA TU104 [GeForce RTX 2060] driver: nvidia v: 570.124.04
    alternate: nouveau,nvidia_drm non-free: 550/565.xx+ status: current (as of
    2025-01; 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: HDMI-A-1 empty: DP-1,DP-2,DP-3
    bus-ID: 01:00.0 chip-ID: 10de:1e89 class-ID: 0300
  Display: wayland server: X.org v: 1.21.1.16 with: Xwayland v: 24.1.6
    compositor: kwin_wayland driver: X: loaded: nvidia unloaded: modesetting
    alternate: fbdev,nouveau,nv,vesa gpu: nvidia,nvidia-nvswitch display-ID: 0
  Monitor-1: HDMI-A-1 model: Asus VS248 serial: <filter> built: 2014 res:
    mode: 1920x1080 hz: 60 scale: 100% (1) dpi: 92 gamma: 1.2
    size: 531x299mm (20.91x11.77") diag: 609mm (24") ratio: 16:9 modes:
    max: 1920x1080 min: 640x480
  API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia gbm:
    drv: nvidia surfaceless: drv: nvidia wayland: drv: nvidia x11: drv: nvidia
  API: OpenGL v: 4.6.0 vendor: nvidia v: 570.124.04 glx-v: 1.4
    direct-render: yes renderer: NVIDIA GeForce RTX 2060/PCIe/SSE2
    memory: 5.86 GiB display-ID: :1.0
  API: Vulkan v: 1.4.304 layers: 6 device: 0 type: discrete-gpu
    name: NVIDIA GeForce RTX 2060 driver: N/A device-ID: 10de:1e89
    surfaces: xcb,xlib,wayland
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor gpu: nvidia-settings,nvidia-smi
    wl: wayland-info x11: xdpyinfo, xprop, xrandr
Audio:
  Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: Gigabyte
    driver: snd_hda_intel v: kernel alternate: snd_soc_avs bus-ID: 00:1f.3
    chip-ID: 8086:a170 class-ID: 0403
  Device-2: NVIDIA TU104 HD Audio driver: snd_hda_intel v: kernel pcie:
    gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 01:00.1 chip-ID: 10de:10f8
    class-ID: 0403
  Device-3: C-Media CMI8788 [Oxygen HD Audio] vendor: ASUSTeK Virtuoso 100
    driver: snd_virtuoso v: kernel bus-ID: 0f:04.0 chip-ID: 13f6:8788
    class-ID: 0401
  Device-4: Texas Instruments PCM2902 Audio Codec
    driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 1.1 speed: 12 Mb/s
    lanes: 1 mode: 1.1 bus-ID: 1-14:5 chip-ID: 08bb:2902 class-ID: 0300
  API: ALSA v: k6.13.5-zen1-1-zen status: kernel-api
    tools: alsactl,alsamixer,amixer
  Server-1: PipeWire v: 1.2.7 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: Gigabyte driver: e1000e v: kernel
    port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15b8 class-ID: 0200
  IF: enp0s31f6 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Info: services: NetworkManager,systemd-timesyncd
Drives:
  Local Storage: total: 2.27 TiB used: 199 GiB (8.6%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Micron model: MTFDDAV256TBN-1AR1ZABHA
    size: 238.47 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
    tech: SSD serial: <filter> fw-rev: 0014 scheme: GPT
  ID-2: /dev/sdb maj-min: 8:16 vendor: Samsung model: SSD 850 EVO 500GB
    size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    tech: SSD serial: <filter> fw-rev: 2B6Q scheme: GPT
  ID-3: /dev/sdc maj-min: 8:32 vendor: SanDisk model: SD8SN8U256G1122
    size: 238.47 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    tech: SSD serial: <filter> fw-rev: 0000 scheme: GPT
  ID-4: /dev/sdd maj-min: 8:48 vendor: Western Digital
    model: WD10EZEX-08WN4A0 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: 1A02 scheme: GPT
  ID-5: /dev/sde maj-min: 8:64 vendor: Crucial model: CT480BX200SSD1
    size: 447.13 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
    tech: SSD serial: <filter> fw-rev: .6 scheme: GPT
Partition:
  ID-1: / raw-size: 225.5 GiB size: 220.9 GiB (97.96%) used: 198.56 GiB (89.9%)
    fs: ext4 dev: /dev/sdc3 maj-min: 8:35
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: no
  ID-1: swap-1 type: partition size: 12 GiB used: 42.2 MiB (0.3%)
    priority: -2 dev: /dev/sdc2 maj-min: 8:34
Sensors:
  System Temperatures: cpu: 32.0 C mobo: N/A
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 24 GiB available: 23.42 GiB used: 3.49 GiB (14.9%)
  Processes: 238 Power: uptime: 1h 4m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 9.3 GiB services: power-profiles-daemon,upowerd
    Init: systemd v: 257 default: graphical tool: systemctl
  Packages: pm: dpkg pkgs: 0 pm: pacman pkgs: 2045 libs: 431 tools: yay
    Compilers: clang: 19.1.7 gcc: 14.2.1 alt: 13 Shell: tim-inxi default: Bash
    v: 5.2.37 running-in: konsole inxi: 3.3.37

and this is the post-crash journalctrl part, that is written in deepred and yellow:

Mär 09 00:54:29 Linux plasmashell[6635]: warning: queue 0x7bb69c004280 destroyed while proxies still attached:
Mär 09 00:54:29 Linux plasmashell[6635]:   wl_callback#378 still attached
Mär 09 00:54:29 Linux plasmashell[6635]:   wp_linux_drm_syncobj_timeline_v1#382 still attached
Mär 09 00:54:29 Linux plasmashell[6635]:   wl_buffer#384 still attached
Mär 09 00:54:29 Linux plasmashell[6635]:   wp_linux_drm_syncobj_timeline_v1#150 still attached
Mär 09 00:54:29 Linux plasmashell[6635]:   wl_buffer#390 still attached
Mär 09 00:54:29 Linux plasmashell[6635]:   wp_linux_drm_syncobj_timeline_v1#394 still attached
Mär 09 00:54:29 Linux plasmashell[6635]:   wl_buffer#396 still attached
Mär 09 00:54:29 Linux plasmashell[6635]:   wl_surface#141 still attached
Mär 09 00:54:29 Linux plasmashell[6635]:   wp_linux_drm_syncobj_surface_v1#398 still attached
Mär 09 00:54:29 Linux plasmashell[6635]:   wp_linux_drm_syncobj_manager_v1#400 still attached
Mär 09 00:54:29 Linux plasmashell[6635]:   wp_tearing_control_v1#402 still attached
Mär 09 00:54:29 Linux plasmashell[6635]: Tried to add event to destroyed queue
Mär 09 00:54:29 Linux systemd-coredump[6948]: Process 6635 (plasmashell) of user 1000 terminated abnormally with signal 6/ABRT, processing...
Mär 09 00:54:29 Linux systemd[1]: Started Process Core Dump (PID 6948/UID 0).
Mär 09 00:54:31 Linux systemd-coredump[6949]: [🡕] Process 6635 (plasmashell) of user 1000 dumped core.
                                               
                                               Module [dso] without build-id.
                                               Module [dso] without build-id.
                                               Module [dso] without build-id.
                                               Module [dso] without build-id.
                                               Module [dso] without build-id.
                                               Module [dso] without build-id.
                                               Module [dso] without build-id.
                                               Stack trace of thread 6638:
                                               #0  0x00007bb773ca5624 n/a (n/a + 0x0)
                                               #1  0x00007bb773c4bba0 n/a (n/a + 0x0)
                                               #2  0x00007bb773c33582 n/a (n/a + 0x0)
                                               #3  0x00007bb776dd4734 n/a (n/a + 0x0)
                                               #4  0x00007bb776dd6d86 n/a (n/a + 0x0)
                                               #5  0x00007bb77536d5f1 n/a (n/a + 0x0)
                                               #6  0x00007bb7744d8a9b n/a (n/a + 0x0)
                                               #7  0x00007bb773ca370a n/a (n/a + 0x0)
                                               #8  0x00007bb773d27aac n/a (n/a + 0x0)
                                               ELF object binary architecture: AMD x86-64
Mär 09 00:54:31 Linux systemd[1]: systemd-coredump@14-6948-0.service: Deactivated successfully.
Mär 09 00:54:31 Linux systemd[1]: systemd-coredump@14-6948-0.service: Consumed 1.525s CPU time, 724.3M memory peak.
Mär 09 00:54:31 Linux systemd[1073]: plasma-plasmashell.service: Main process exited, code=dumped, status=6/ABRT
Mär 09 00:54:31 Linux systemd[1073]: plasma-plasmashell.service: Failed with result 'core-dump'.
Mär 09 00:54:31 Linux systemd[1073]: plasma-plasmashell.service: Consumed 21.684s CPU time, 346.2M memory peak.
Mär 09 00:54:31 Linux systemd[1073]: plasma-plasmashell.service: Scheduled restart job, restart counter is at 3.
Mär 09 00:54:31 Linux systemd[1073]: Starting KDE Plasma Workspace...
Mär 09 00:54:32 Linux systemd[1073]: Started KDE Plasma Workspace.
Mär 09 00:54:32 Linux plasmashell[6964]: kf.plasma.quick: Applet preload policy set to 1
Mär 09 00:54:32 Linux plasmashell[6964]: file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/main.qml:178:25: QML FolderViewDropArea (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property>
                                          file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/main.qml:201:9
Mär 09 00:54:32 Linux plasmashell[6964]: Toolbox not loading, toolbox package is either invalid or disabled.
Mär 09 00:54:33 Linux systemd[1073]: Started dbus-:1.2-org.kde.KSplash@10.service.
Mär 09 00:54:33 Linux plasmashell[6964]: qt.svg: <input>:303:256: Could not add child element to parent element because the types are incorrect.
Mär 09 00:54:33 Linux plasmashell[6964]: qt.svg: <input>:303:461: Could not add child element to parent element because the types are incorrect.
Mär 09 00:54:33 Linux plasmashell[6964]: qt.svg: <input>:303:657: Could not add child element to parent element because the types are incorrect.
Mär 09 00:54:33 Linux plasmashell[6964]: qt.svg: <input>:303:911: Could not add child element to parent element because the types are incorrect.
Mär 09 00:54:33 Linux plasmashell[6964]: qt.svg: <input>:303:1047: Could not add child element to parent element because the types are incorrect.
Mär 09 00:54:33 Linux plasmashell[6964]: qt.svg: <input>:303:1249: Could not add child element to parent element because the types are incorrect.
Mär 09 00:54:33 Linux plasmashell[6964]: qt.svg: <input>:303:1451: Could not add child element to parent element because the types are incorrect.
Mär 09 00:54:33 Linux plasmashell[6964]: qt.svg: <input>:303:1629: Could not add child element to parent element because the types are incorrect.
Mär 09 00:54:33 Linux plasmashell[6964]: qt.svg: <input>:303:1737: Could not add child element to parent element because the types are incorrect.
Mär 09 00:54:33 Linux plasmashell[6964]: qt.svg: <input>:303:1978: Could not add child element to parent element because the types are incorrect.
Mär 09 00:54:33 Linux plasmashell[6964]: qt.svg: <input>:303:2221: Could not add child element to parent element because the types are incorrect.
Mär 09 00:54:33 Linux plasmashell[6964]: file:///usr/share/plasma/plasmoids/org.kde.plasma.kickoff/contents/ui/main.qml:310:13: QML Image: Cannot open: file:///usr/share/plasma/plasmoids/org.kde.plasma.kickoff/contents/ui/start-here-kd>
Mär 09 00:54:33 Linux plasmashell[6964]: file:///usr/share/plasma/plasmoids/org.kde.plasma.private.systemtray/contents/ui/main.qml:50:9: QML KSortFilterProxyModel: Binding loop detected for property "sourceModel"
Mär 09 00:54:33 Linux plasmashell[6964]: file:///usr/share/plasma/plasmoids/org.kde.plasma.private.systemtray/contents/ui/main.qml:50:9: QML KSortFilterProxyModel: Binding loop detected for property "sourceModel"
Mär 09 00:54:33 Linux plasmashell[6964]: qt.dbus.integration: Could not connect "org.cups.cupsd.Notifier" to PrinterFinishingsChanged(QString, QString, QString, uint, QString, bool) :
Mär 09 00:54:34 Linux plasmashell[6964]: QFont::setPointSizeF: Point size <= 0 (0.000000), must be greater than 0
Mär 09 00:54:34 Linux plasmashell[6964]: qt.svg: <input>:303:256: Could not add child element to parent element because the types are incorrect.
Mär 09 00:54:34 Linux plasmashell[6964]: qt.svg: <input>:303:461: Could not add child element to parent element because the types are incorrect.
Mär 09 00:54:34 Linux plasmashell[6964]: qt.svg: <input>:303:657: Could not add child element to parent element because the types are incorrect.
Mär 09 00:54:34 Linux plasmashell[6964]: qt.svg: <input>:303:911: Could not add child element to parent element because the types are incorrect.
Mär 09 00:54:34 Linux plasmashell[6964]: qt.svg: <input>:303:1047: Could not add child element to parent element because the types are incorrect.
Mär 09 00:54:34 Linux plasmashell[6964]: qt.svg: <input>:303:1249: Could not add child element to parent element because the types are incorrect.
Mär 09 00:54:34 Linux plasmashell[6964]: qt.svg: <input>:303:1451: Could not add child element to parent element because the types are incorrect.
Mär 09 00:54:34 Linux plasmashell[6964]: qt.svg: <input>:303:1629: Could not add child element to parent element because the types are incorrect.
Mär 09 00:54:34 Linux plasmashell[6964]: qt.svg: <input>:303:1737: Could not add child element to parent element because the types are incorrect.
Mär 09 00:54:34 Linux plasmashell[6964]: qt.svg: <input>:303:1978: Could not add child element to parent element because the types are incorrect.
Mär 09 00:54:34 Linux plasmashell[6964]: qt.svg: <input>:303:2221: Could not add child element to parent element because the types are incorrect.

I hope that someone can see the problem and know how to solve it.
Thank you.

2

Welcome to the community! :enos_flag: :vulcan_salute:

Have you checked to see if there is an update available for your BIOS?
F23g date: 03/09/2018

Also, what is the output of:

pacman -Q | grep -A 0 -E "(steam|mango|game|vulk|vlk|nvidia|amd|hypr|wayland|linux|headers)"
3

Hi, and thank you.

This computer is rather old, as you can see. The 2018 update was the newest, that was avaible.

Here is the output:

[sfox@Linux ~]$ pacman -Q | grep -A 0 -E "(steam|mango|game|vulk|vlk|nvidia|amd|hypr|wayland|linux|headers)"
aarch64-linux-gnu-binutils 2.43-1
aarch64-linux-gnu-gcc 14.2.0-1
aarch64-linux-gnu-glibc 2.40-1
aarch64-linux-gnu-linux-api-headers 6.12-1
--
archlinux-keyring 20250123-1
--
egl-wayland 4:1.1.18-1
--
heroic-games-launcher-bin 2.16.0-2
--
kwayland 6.3.2-1
kwayland-integration 6.3.2-1
kwayland5 5.116.0-1
--
lib32-nvidia-utils 570.124.04-1
--
lib32-util-linux 2.40.4-1
lib32-vulkan-icd-loader 1.4.304.1-1
lib32-wayland 1.23.1-1
--
linux-api-headers 6.13-1
linux-firmware 20250210.5bc5868b-1
linux-firmware-whence 20250210.5bc5868b-1
linux-zen 6.13.5.zen1-1
linux-zen-docs 6.13.5.zen1-1
linux-zen-headers 6.13.5.zen1-1
--
mangohud 0.8.0-3
--
nvidia-dkms 570.124.04-1
nvidia-hook 1.5.1-1
nvidia-inst 25.2-1
nvidia-settings 570.124.04-1
nvidia-utils 570.124.04-1
--
opencl-nvidia 570.124.04-1
--
python-steamgriddb 1.0.5-4
--
qt5-wayland 5.15.16+kde+r59-3
--
qt6-wayland 6.8.2-1
--
steam 1.0.0.82-1
--
util-linux 2.40.4-1
util-linux-libs 2.40.4-1
--
vulkan-headers 1:1.4.304.1-2
vulkan-icd-loader 1.4.304.1-1
vulkan-tools 1.4.304.1-1
--
wayland 1.23.1-1
wayland-utils 1.2.0-2
--
xorg-xwayland 24.1.6-1
--
xwaylandvideobridge 0.4.0-2
[sfox@Linux ~]$

I´d like to say, that the system was running perfectly stable since first install. These problems just kicked in yesterday.

4

Welcome to the forum :enos_flag: :enos:
Well if a system is aging there can ofcourse be a chance of failing hardware, if all hardware is from the same age as your motherboard. Did you check if the fans on the graphics card are still running ? Did you test your memory ? If the Power supply is also of the same age could that be a problem? Could there be a problem with the hard drive ?

5

Hi, and thanks.
The graphics card isn’t actually causing any problems. I can still play games like Cyberpunk 2077 or Baldur’s Gate 3 without any issues. There is a problem, though, since I switched from Garuda Linux to Endeavour OS in December: the graphics card’s fan runs at 100% whenever a game starts (even if the card barely gets warmer than 30°C). But according to ChatGPT, this is due to an incompatibility between the nvidia-dkms driver and Wayland.
However, this has been the case since December last year and isn’t a recent change that could explain the current problem.

The problem I’m having is also not easy to put into words. Imagine my taskbar is stable. Then you click on the clock, then on Dolphin, and suddenly it briefly disappears and reappears. For 2 seconds.
Then I click on Dolphin again and Dolphin starts. I can use the program itself without any issues at first.
Sometimes, especially when a game is running in the background, I want to open, for example, Vivaldi, Spotify, or Discord, and I find that although the application opens, I can’t do anything in it. It’s as if I’m only seeing a screenshot. And sometimes it opens, but I can’t “get in.” No matter if I click on the taskbar or switch with ALT-TAB, I can’t activate the application.

6

That sounds like Plasma Shell is crashing. If you can replicate it, it could be worth reporting it on the KDE bug tracker.

7

Have you tried X11 instead of wayland ?

8

@MyNameIsRichard Hi,

I don’t know nearly enough to report anything. I don’t even know if it’s just a configuration problem or if something is seriously broken. Not to mention that “because I was playing Transport Fever 2” doesn’t seem like a meaningful explanation for it.

@keescase No, I haven’t yet. Endeavour comes with Wayland. I’m afraid that switching will mess everything up. Besides, X11 has been practically dead since 2021. Installing something of this magnitude just to avoid a problem, rather than solving it, doesn’t seem right to me either.

9

Did Chatgpt tell you all this about x11 ?
Besides there is nothing to install just switch from wayland to x11. Maybe ask Chatgpt how to do that ? :grinning:

10

Log out of KDE Plasma, and in the bottom left of yhe log-in screen, you should be able to select X11 instead of Wayland.

Simply log in with that.

11

Ok… I am on X11 now.
And the problem is gone, entirely.
… so it is not a KWIN nor a KDE Plasma problem but a Wayland issue?!

12

That is because wayland only offers good support for the latest hardware. Chatgpt should have told you that.

13

Does that mean that yesterday was the cutoff date when my hardware suddenly became too old and Wayland started producing errors? While the day before yesterday, it was still new enough not to produce any errors?

14

Anything is possible with Wayland , because it is not as “mature” as it should be and still can have some bugs in it.

15

Eh… STOP listening to ChatGPT it is full of shit! And bad info.
AI my ass…
And never run any terminal stuff or worse scripts :scream: coming from ChatGPT,

16

You said i thought it :grinning_face_with_smiling_eyes:

17

Well they want to learn the hard way, if endeavor can’t break their system…chatgpt can :rofl:

18

This is a fair point. I would say no, it shouldn’t suddenly become too old.

On just one of my EndeavourOS systems (of 5), I continually encounter much the same issues as you’ve described. Interestingly, my system is markedly different to yours, being an AMD Ryzen 5900X, on an Asus board, and a different generation Nvidia GPU, yours being Turing TU104, mine being the next gen Ampere GA104GL.

I’m not at all convinced the age of your PC is the issue, but where it stems from is hard to pin down. When things bug out, screenshots can’t even capture the issue and logs are indifferent, so it’s difficult to reach out with meaningful bug reports.

I’ve put it in the Wayland has serious bugs basket, and on that system I prioritise X11.

19

2 cents, may help narrow things down may throw them off. Glad X11 fixed it for you. I’ve got a new build (13600K, 4080S) and run into a similar issue with Total War: Warhammer 3 + discord. It’s the only game I play that does it, but it’s similar symptoms. If I’m playing TW:WH3 any active discord call will work as normal, but the discord gui will be frozen and unresponsive until I quit and restart it while I’m not in game. It’s been happening for quite a while (6m+). It doesn’t seem to mess with the rest of the system usually, sometimes it does.

Additionally I’ve been having some other issues with kde night light crashing my entire desktop and making it behave weirdly until a full restart. I’ve been unable to narrow that one down though. I suspect there’s a pertty serious bug related kwin-wayland and fullscreen rn.

20

@Mox’s comment actually reminds me of something you could try @SFoX.

Under a Wayland session, you might try disabling adaptive sync / variable refresh rate in Plasma’s display settings. I also disabled it on my monitors. That did eliminate some of the issues for me.