Plasma workspace freezing

Hello all,

I’m running KDE, Wayland and Nvidia drivers. (latest 555)
While working it’s very common for the UI to freeze, like pressing the hotkey for the start menu, it pops up but then it freezes. Sometimes it helps to trigger some form of refresh like windows key + D and it will unfreeze. (Not always)
It’s very hard to reproduce but now I have a 100% case which just requires KDEnlive.

When I render out a short video, a notification is presented with a progress bar. Once that is finished, the whole desktop is frozen. Ever application still works but everything that involves Plasma is dead. KRunner (alt + space) still works though but taskbar, startbar, top bar. All frozen.

Now I had my fair share of problems with KDE and Wayland, basically I never got it really working at an acceptable rate. I’ve tried to find similar topics and freezing is quite common but then they are related to KDE5, are years old, not about Wayland, etc…

I just wanna know if I’m the only one who has this problem because when I read about others experience, it seems so, although I find that very unlikely.

And apart from that, how do I go about solving this problem. Logs, debug, etc…

Thanks!

1 Like

Please post your garuda-inxi as requested by the template.

Switch to x11 and check if the same issues occur.

Welcome to the community :slight_smile:

1 Like
System:
Kernel: 6.9.6-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 14.1.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=2cc74576-73c7-40f6-9712-22d6c39083c5 rw rootflags=subvol=@
quiet resume=UUID=32afd744-3808-4486-852a-2d52cd7481ad loglevel=3 ibt=off
Desktop: KDE Plasma v: 6.1.1 tk: Qt v: N/A info: frameworks v: 6.3.0
wm: kwin_wayland vt: 1 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required>
Mobo: ASUSTeK model: ROG STRIX B550-F GAMING (WI-FI) v: Rev X.0x
serial: <superuser required> part-nu: SKU uuid: <superuser required>
UEFI: American Megatrends v: 3202 date: 06/15/2023
CPU:
Info: model: AMD Ryzen 9 5900X bits: 64 type: MT MCP arch: Zen 3+ gen: 4
level: v3 note: check built: 2022 process: TSMC n6 (7nm) family: 0x19 (25)
model-id: 0x21 (33) stepping: 0 microcode: 0xA201025
Topology: cpus: 1x cores: 12 tpc: 2 threads: 24 smt: enabled cache:
L1: 768 KiB desc: d-12x32 KiB; i-12x32 KiB L2: 6 MiB desc: 12x512 KiB
L3: 64 MiB desc: 2x32 MiB
Speed (MHz): avg: 3659 high: 3700 min/max: 2200/4950 boost: enabled
scaling: driver: acpi-cpufreq governor: performance cores: 1: 3644 2: 3597
3: 3700 4: 3700 5: 3600 6: 3700 7: 3700 8: 3700 9: 3700 10: 3700 11: 3700
12: 3700 13: 3599 14: 3700 15: 3700 16: 3599 17: 3700 18: 3600 19: 3600
20: 3597 21: 3599 22: 3600 23: 3700 24: 3700 bogomips: 177613
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities: <filter>
Graphics:
Device-1: NVIDIA AD103 [GeForce RTX 4080] vendor: Micro-Star MSI
driver: nvidia v: 555.58 alternate: nouveau,nvidia_drm non-free: 550.xx+
status: current (as of 2024-06) arch: Lovelace code: AD1xx
process: TSMC n4 (5nm) built: 2022+ pcie: gen: 4 speed: 16 GT/s lanes: 16
ports: active: none off: DP-1,HDMI-A-1 empty: DP-2,DP-3 bus-ID: 07:00.0
chip-ID: 10de:2704 class-ID: 0300
Display: wayland server: X.org v: 1.21.1.13 with: Xwayland v: 24.1.0
compositor: kwin_wayland driver: X: loaded: nvidia unloaded: modesetting
alternate: fbdev,nouveau,nv,vesa gpu: nvidia d-rect: 4480x1440
display-ID: 0
Monitor-1: DP-1 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: 555.58
glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce RTX 4080/PCIe/SSE2
memory: 15.62 GiB display-ID: :1.0
API: Vulkan v: 1.3.279 layers: 5 device: 0 type: discrete-gpu
name: NVIDIA GeForce RTX 4080 driver: nvidia v: 555.58 device-ID: 10de:2704
surfaces: xcb,xlib,wayland
Audio:
Device-1: NVIDIA vendor: Micro-Star MSI driver: snd_hda_intel v: kernel
pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 07:00.1 chip-ID: 10de:22bb
class-ID: 0403
Device-2: AMD Starship/Matisse HD Audio vendor: ASUSTeK
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 09:00.4 chip-ID: 1022:1487 class-ID: 0403
API: ALSA v: k6.9.6-zen1-1-zen status: kernel-api with: aoss
type: oss-emulator tools: N/A
Server-1: PipeWire v: 1.0.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 Wi-Fi 6 AX200 driver: iwlwifi v: kernel pcie: gen: 2
speed: 5 GT/s lanes: 1 bus-ID: 05:00.0 chip-ID: 8086:2723 class-ID: 0280
IF: wlp5s0 state: down mac: <filter>
Device-2: Intel Ethernet I225-V vendor: ASUSTeK driver: igc v: kernel
pcie: gen: 2 speed: 5 GT/s lanes: 1 port: N/A bus-ID: 06:00.0
chip-ID: 8086:15f3 class-ID: 0200
IF: enp6s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Info: services: NetworkManager, smbd, systemd-timesyncd
Bluetooth:
Device-1: Intel AX200 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-5:5 chip-ID: 8087:0029
class-ID: e001
Report: btmgmt ID: hci0 rfk-id: 2 state: down bt-service: enabled,running
rfk-block: hardware: no software: yes address: <filter> bt-v: 5.2 lmp-v: 11
status: discoverable: no pairing: no
Drives:
Local Storage: total: 11.6 TiB used: 198.95 GiB (1.7%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 990 PRO 2TB
size: 1.82 TiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: 4B2QJXD7 temp: 46.9 C
scheme: GPT
ID-2: /dev/sda maj-min: 8:0 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: 3B6Q scheme: MBR
ID-3: /dev/sdb maj-min: 8:16 vendor: Western Digital
model: WD60EFRX-68MYMN1 size: 5.46 TiB block-size: physical: 4096 B
logical: 512 B speed: 6.0 Gb/s tech: HDD rpm: 5700 serial: <filter>
fw-rev: 0A82 scheme: GPT
ID-4: /dev/sdc maj-min: 8:32 vendor: Samsung model: SSD 860 EVO 1TB
size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 4B6Q
ID-5: /dev/sdd maj-min: 8:48 vendor: Samsung model: SSD 830 Series
size: 238.47 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 3B1Q scheme: GPT
ID-6: /dev/sde maj-min: 8:64 vendor: Samsung model: SSD 870 EVO 2TB
size: 1.82 TiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 3B6Q scheme: GPT
ID-7: /dev/sdf maj-min: 8:80 vendor: Samsung model: SSD 860 EVO 1TB
size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 4B6Q scheme: GPT
Partition:
ID-1: / raw-size: 882.68 GiB size: 882.68 GiB (100.00%)
used: 198.95 GiB (22.5%) fs: btrfs dev: /dev/nvme0n1p7 maj-min: 259:7
ID-2: /boot/efi raw-size: 513 MiB size: 511.9 MiB (99.80%)
used: 588 KiB (0.1%) fs: vfat dev: /dev/nvme0n1p5 maj-min: 259:5
ID-3: /home raw-size: 882.68 GiB size: 882.68 GiB (100.00%)
used: 198.95 GiB (22.5%) fs: btrfs dev: /dev/nvme0n1p7 maj-min: 259:7
ID-4: /var/log raw-size: 882.68 GiB size: 882.68 GiB (100.00%)
used: 198.95 GiB (22.5%) fs: btrfs dev: /dev/nvme0n1p7 maj-min: 259:7
ID-5: /var/tmp raw-size: 882.68 GiB size: 882.68 GiB (100.00%)
used: 198.95 GiB (22.5%) fs: btrfs dev: /dev/nvme0n1p7 maj-min: 259:7
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 62.7 GiB used: 26 MiB (0.0%) priority: 100
comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 24 dev: /dev/zram0
ID-2: swap-2 type: partition size: 39.06 GiB used: 0 KiB (0.0%)
priority: -2 dev: /dev/nvme0n1p6 maj-min: 259:6
Sensors:
System Temperatures: cpu: 59.9 C mobo: N/A
Fan Speeds (rpm): N/A
Info:
Memory: total: 64 GiB note: est. available: 62.7 GiB used: 4.52 GiB (7.2%)
Processes: 491 Power: uptime: 0m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 25.04 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 256 default: graphical
tool: systemctl
Packages: pm: pacman pkgs: 1467 libs: 410 tools: octopi,paru,yay
Compilers: gcc: 14.1.1 Shell: garuda-inxi default: fish v: 3.7.1
running-in: konsole inxi: 3.3.35
Garuda (2.6.26-1):
System install date:     2024-06-19
Last full system update: 2024-06-29
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut
Windows dual boot:       Probably (Run as root to verify)
Failed units:

The problem is with Wayland. X11 runs fine.

Then use x11 :slight_smile:
Problems with nvidia and wayland are well known, there are several threads about it.

2 Likes

Hi. I just created an account since I was searching for this specific issue and landed here.
I am having the same issue. If X11 is the solution why is everyone ditching it for Wayland? Apologies if that comes off as snarky. It is a genuine question. It comes off as “My Mustang is stalling. The Prius doesn’t stall. Drive the Prius then”.
Yeah I get to work that way but it doesn’t fix the Mustang.

I would prefer figuring out why this is happening on Wayland and fixing it if possible. This only started happening about a week ago. I deleted my
plasma-org.kde.plasma.desktop-appletsrc file thinking that might fix it if it was a plasma issue but it still persists.

Here is my Inxi out:

System:
  Kernel: 6.9.7-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 14.1.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
    root=UUID=ff8ed01d-1967-471d-93db-e1dbc5051cd6 rw rootflags=subvol=@
    quiet resume=UUID=1aa6d8ea-345f-48ba-95bf-e8902f0e4894 loglevel=3 ibt=off
  Desktop: KDE Plasma v: 6.1.1 tk: Qt v: N/A info: frameworks v: 6.3.0
    wm: kwin_wayland vt: 1 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
  Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required>
  Mobo: ASUSTeK model: ROG CROSSHAIR VIII HERO (WI-FI) v: Rev X.0x
    serial: <superuser required> part-nu: SKU uuid: <superuser required>
    UEFI: American Megatrends v: 4805 date: 03/18/2024
CPU:
  Info: model: AMD Ryzen 9 3900X bits: 64 type: MT MCP arch: Zen 2 gen: 3
    level: v3 note: check built: 2020-22 process: TSMC n7 (7nm)
    family: 0x17 (23) model-id: 0x71 (113) stepping: 0 microcode: 0x8701033
  Topology: cpus: 1x cores: 12 tpc: 2 threads: 24 smt: enabled cache:
    L1: 768 KiB desc: d-12x32 KiB; i-12x32 KiB L2: 6 MiB desc: 12x512 KiB
    L3: 64 MiB desc: 4x16 MiB
  Speed (MHz): avg: 4100 high: 4111 min/max: 2200/5041 boost: disabled
    scaling: driver: acpi-cpufreq governor: performance cores: 1: 4099 2: 4100
    3: 4100 4: 4099 5: 4100 6: 4100 7: 4100 8: 4100 9: 4100 10: 4100 11: 4100
    12: 4100 13: 4100 14: 4111 15: 4100 16: 4100 17: 4100 18: 4100 19: 4100
    20: 4098 21: 4100 22: 4100 23: 4100 24: 4100 bogomips: 196807
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3
  Vulnerabilities: <filter>
Graphics:
  Device-1: NVIDIA TU104 [GeForce RTX 2070 SUPER] vendor: Micro-Star MSI
    driver: nvidia v: 555.42.02 alternate: nouveau,nvidia_drm non-free: 550.xx+
    status: current (as of 2024-06; EOL~2026-12-xx) arch: Turing code: TUxxx
    process: TSMC 12nm FF built: 2018-2022 pcie: gen: 3 speed: 8 GT/s
    lanes: 16 ports: active: none off: DP-1,HDMI-A-1 empty: DP-2,DP-3
    bus-ID: 0b:00.0 chip-ID: 10de:1e84 class-ID: 0300
  Device-2: HTC (High Tech ) Vive driver: uvcvideo type: USB rev: 2.0
    speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-2.3.1.2:11 chip-ID: 0bb4:2c87
    class-ID: 0e02
  Device-3: Logitech HD Webcam C615 driver: snd-usb-audio,uvcvideo type: USB
    rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 7-1:2 chip-ID: 046d:082c
    class-ID: 0e02 serial: <filter>
  Display: wayland server: X.org v: 1.21.1.13 with: Xwayland v: 24.1.0
    compositor: kwin_wayland driver: X: loaded: nvidia unloaded: modesetting
    alternate: fbdev,nouveau,nv,vesa gpu: nvidia display-ID: 0
  Monitor-1: DP-1 res: 3440x1440 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: 555.42.02
    glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce RTX 2070
    SUPER/PCIe/SSE2 memory: 7.81 GiB display-ID: :1.0
  API: Vulkan v: 1.3.279 layers: 11 device: 0 type: discrete-gpu name: NVIDIA
    GeForce RTX 2070 SUPER driver: nvidia v: 555.42.02 device-ID: 10de:1e84
    surfaces: xcb,xlib,wayland
Audio:
  Device-1: NVIDIA TU104 HD Audio vendor: Micro-Star MSI driver: snd_hda_intel
    v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 0b:00.1
    chip-ID: 10de:10f8 class-ID: 0403
  Device-2: AMD Starship/Matisse HD Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
    bus-ID: 0d:00.4 chip-ID: 1022:1487 class-ID: 0403
  Device-3: C-Media USB Audio Device
    driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 1.1 speed: 12 Mb/s
    lanes: 1 mode: 1.1 bus-ID: 3-2.3.1.4:12 chip-ID: 0d8c:0012 class-ID: 0300
  Device-4: Corsair VIRTUOSO SE Wireless Gaming Headset
    driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 2.0 speed: 12 Mb/s
    lanes: 1 mode: 1.1 bus-ID: 3-3:3 chip-ID: 1b1c:0a3e class-ID: 0300
    serial: <filter>
  Device-5: Logitech HD Webcam C615 driver: snd-usb-audio,uvcvideo type: USB
    rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 7-1:2 chip-ID: 046d:082c
    class-ID: 0e02 serial: <filter>
  API: ALSA v: k6.9.7-zen1-1-zen status: kernel-api with: aoss
    type: oss-emulator tools: N/A
  Server-1: PipeWire v: 1.2.0 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: Realtek RTL8125 2.5GbE vendor: ASUSTeK driver: r8169 v: kernel
    pcie: gen: 2 speed: 5 GT/s lanes: 1 port: e000 bus-ID: 05:00.0
    chip-ID: 10ec:8125 class-ID: 0200
  IF: enp5s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Device-2: Intel I211 Gigabit Network vendor: ASUSTeK driver: igb v: kernel
    pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: d000 bus-ID: 06:00.0
    chip-ID: 8086:1539 class-ID: 0200
  IF: enp6s0 state: down mac: <filter>
  Device-3: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel pcie: gen: 2
    speed: 5 GT/s lanes: 1 bus-ID: 07:00.0 chip-ID: 8086:2723 class-ID: 0280
  IF: wlp7s0 state: down mac: <filter>
  Device-4: Microsoft Xbox 360 Wireless Adapter driver: xpad type: USB
    rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 3-2.2:5
    chip-ID: 045e:0719 class-ID: ff00 serial: <filter>
  Info: services: NetworkManager, smbd, systemd-timesyncd
Bluetooth:
  Device-1: Intel AX200 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
    speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-6:5 chip-ID: 8087:0029
    class-ID: e001
  Report: btmgmt ID: hci0 rfk-id: 0 state: up address: N/A
  Report-ID: ID: hci1 rfk-id: 1 state: up address: N/A
Drives:
  Local Storage: total: 5.02 TiB used: 1.82 TiB (36.3%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:1 vendor: Corsair model: Force MP600
    size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: EGFM11.3 temp: 47.9 C
    scheme: GPT
  ID-2: /dev/nvme1n1 maj-min: 259:0 vendor: Intel model: SSDPEKKW512G7
    size: 476.94 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: PSF121C temp: 38.9 C
    scheme: GPT
  ID-3: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 830 Series
    size: 238.47 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    tech: SSD serial: <filter> fw-rev: 3B1Q scheme: GPT
  ID-4: /dev/sdb maj-min: 8:16 vendor: Seagate model: ST3750640NS
    size: 698.64 GiB block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s
    tech: N/A serial: <filter> fw-rev: K scheme: GPT
  ID-5: /dev/sdc maj-min: 8:32 vendor: Western Digital
    model: WD1001FALS-00J7B1 size: 931.51 GiB block-size: physical: 512 B
    logical: 512 B speed: 3.0 Gb/s tech: N/A serial: <filter> fw-rev: 0K05
    scheme: GPT
  ID-6: /dev/sdd maj-min: 8:48 vendor: Western Digital
    model: WD20EARX-00PASB0 size: 1.82 TiB block-size: physical: 512 B
    logical: 512 B type: USB rev: 3.0 spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1
    tech: N/A serial: <filter> fw-rev: 51.0 scheme: GPT
Partition:
  ID-1: / raw-size: 226.17 GiB size: 226.17 GiB (100.00%)
    used: 41.48 GiB (18.3%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:3
  ID-2: /boot/efi raw-size: 330 MiB size: 329.3 MiB (99.80%)
    used: 584 KiB (0.2%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:2
  ID-3: /home raw-size: 673.46 GiB size: 673.46 GiB (100.00%)
    used: 536.92 GiB (79.7%) fs: btrfs dev: /dev/nvme0n1p4 maj-min: 259:5
  ID-4: /var/log raw-size: 226.17 GiB size: 226.17 GiB (100.00%)
    used: 41.48 GiB (18.3%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:3
  ID-5: /var/tmp raw-size: 226.17 GiB size: 226.17 GiB (100.00%)
    used: 41.48 GiB (18.3%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:3
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
  ID-1: swap-1 type: zram size: 31.25 GiB used: 676.2 MiB (2.1%)
    priority: 100 comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 24
    dev: /dev/zram0
  ID-2: swap-2 type: partition size: 31.57 GiB used: 0 KiB (0.0%)
    priority: -2 dev: /dev/nvme0n1p3 maj-min: 259:4
Sensors:
  System Temperatures: cpu: 40.0 C mobo: 48.0 C
  Fan Speeds (rpm): cpu: 1016
Info:
  Memory: total: 32 GiB available: 31.25 GiB used: 5.48 GiB (17.5%)
  Processes: 555 Power: uptime: 28m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 12.46 GiB services: org_kde_powerdevil,
    power-profiles-daemon, upowerd Init: systemd v: 256 default: graphical
    tool: systemctl
  Packages: pm: pacman pkgs: 2004 libs: 574 tools: octopi,pamac,paru
    Compilers: clang: 17.0.6 gcc: 14.1.1 Shell: garuda-inxi default: fish
    v: 3.7.1 running-in: yakuake inxi: 3.3.35
Garuda (2.6.26-1):
  System install date:     2024-05-31
  Last full system update: 2024-06-30
  Is partially upgraded:   No
  Relevant software:       snapper NetworkManager dracut
  Windows dual boot:       Probably (Run as root to verify)
  Failed units:

Falling back to X11 is a workaround for folks who are stuck on Nvidia hardware. Outside of that group of users, the transition to Wayland seems to be going relatively well as far as I can tell.

Just anecdotally, many of us have been happily using Wayland for years.

This analogy isn’t quite right. Switching the display server protocol isn’t comparable to switching to a whole different car. It’s more like switching a single component in your car.

To straighten out your analogy, it would be more like there is a new high-performance air intake system available for Mustangs. It’s better than the old intake system so a lot of Mustang owners are switching.

However, you also installed a high-flow fuel pump on your Mustang. After some testing, it turns out when this component is combined with the new air intake system, the imbalance between the air and fuel mix causes the engine to run too rich and leads to stalling issues.

The manufacturers are aware of the issue and they are working on some changes that will allow the two components to be installed together, but that may take some time. The simplest solution in the meanwhile is to hold off on installing the new air intake system until it is compatible with your other custom components.

This is why:

You probably won’t be able to fix it unless you are a Nvidia developer. You could try your luck with the beta drivers or another kernel…but other than that you probably just need to wait for the issue to be addressed upstream.

4 Likes

And you paid how much for Plasma versus the Mustang?

Talk to the KDE developers, else you’re just pissin’ in the wind.

2 Likes