Wayland issues with resolution/plasmashell

[brian]

I tried using a Wayland session on KDE 5 last fall and had this same issue and decided to wait for KDE 6 and better support before trying again.

When I log into an X11 session the shell opens correctly with the correct resolutions for my displays and everything is fine.

When I try the same thing with a Wayland session, the plasmashell doesn’t seem to load. There’s no widgets (taskbar, system tray, etc.), just my windows launched full screen at a really crappy resolution.

Wayland:

OS: Garuda Linux x86_64
Kernel: 6.7.8-zen1-1-zen
Uptime: 11 mins
Packages: 1862 (pacman)
Shell: bash 5.2.26
Resolution: 640x480
DE: Plasma 6.0.1
WM: kwin
WM Theme: Breeze
Theme: [Plasma], Sweet-Dark [GTK2/3]
Icons: [Plasma], breeze-dark [GTK2/3]
Terminal: konsole
Terminal Font: FiraCode Nerd Font Mono 12
CPU: 12th Gen Intel i7-12700K (20) @ 4.900GHz
GPU: NVIDIA GeForce RTX 3080 Ti
Memory: 4273MiB / 31902MiB

X11:

OS: Garuda Linux x86_64
Kernel: 6.7.8-zen1-1-zen
Uptime: 6 mins
Packages: 1862 (pacman)
Shell: bash 5.2.26
Resolution: 2560x1440, 3440x1440
DE: Plasma 6.0.1
WM: KWin
WM Theme: Breeze
Theme: [Plasma], Sweet-Dark [GTK2/3]
Icons: [Plasma], breeze-dark [GTK2/3]
Terminal: konsole
Terminal Font: FiraCode Nerd Font Mono 12
CPU: 12th Gen Intel i7-12700K (20) @ 4.900GHz
GPU: NVIDIA GeForce RTX 3080 Ti
Memory: 9077MiB / 31902MiB

I’m selecting KDE (Wayland) from the dropdown selection on the login screen. Searching for this issue hasn’t really found me any good results. If there’s any other settings or packages I’m missing, or articles I should look into, let me know.

I don’t mind if I have to do a fresh install if it comes down to it, was just trying to handle it via system updates first.

It’s a pain in the butt to get this information while in my Wayland session, but if there’s anything else I can add for debugging, please let me know. Thanks.

[Kayo]

@brian

if there’s anything else I can add

Could we get the output of garuda-inxi as requested by the template?

[filo]

It looks like you’re not alone.

KDE 6 only works on X11

So today the update to KDE 6 was pushed. After successful update I rebooted and logged into wayland session. Extremely slow with a lot of errors. For example: krunner failed to start error, ‘/’ file system not responding, mouse pointer does not move, it takes several minutes to launch anything, does not see my second monitor. Works great on X11, which is the output from because I can’t get the output from wayland. Thank you in advance for the help. System: Kernel: 6.7.8-zen1-1-zen arch: x86…

At least, an Nvidia GPU in common.
I guess you’ll have to wait…

[brian]

My apologies, here’s the output.

System:
  Kernel: 6.7.8-zen1-1-zen arch: x86_64 bits: 64
    compiler: gcc v: 13.2.1 clocksource: tsc avail: acpi_pm
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
    root=UUID=c140b002-e28d-4083-a150-ae19562001fd rw
    rootflags=subvol=@ quiet quiet rd.udev.log_priority=3
    vt.global_cursor_default=0
    resume=UUID=a515cfb2-63f6-4abb-9bde-b9daf61c375e
    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 with: krunner
    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 Z690-E GAMING WIFI
    v: Rev 1.xx serial: <superuser required> part-nu: SKU
    uuid: <superuser required>
    UEFI-[Legacy]: American Megatrends v: 0503
    date: 09/09/2021
Battery:
  ID-1: hidpp_battery_0 charge: 100% condition: N/A
    volts: 4.2 min: N/A model: Logitech G703 LIGHTSPEED
    Wireless Gaming Mouse w/ HERO type: N/A serial: <filter>
    status: full
CPU:
  Info: model: 12th Gen Intel Core i7-12700K 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: 12 mt: 8 tpc: 2 st: 4
    threads: 20 smt: enabled cache: L1: 1024 KiB desc: d-4x32
    KiB, 8x48 KiB; i-8x32 KiB, 4x64 KiB L2: 12 MiB
    desc: 8x1.2 MiB, 1x2 MiB L3: 25 MiB desc: 1x25 MiB
  Speed (MHz): avg: 1547 high: 2790
    min/max: 800/4900:5000:3800 scaling: driver: intel_pstate
    governor: powersave cores: 1: 800 2: 1200 3: 2508
    4: 2542 5: 2790 6: 800 7: 801 8: 1200 9: 2514 10: 1200
    11: 2536 12: 2579 13: 1200 14: 1236 15: 1300 16: 1200
    17: 1200 18: 1200 19: 947 20: 1200 bogomips: 144383
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1
    sse4_2 ssse3 vmx
  Vulnerabilities: <filter>
Graphics:
  Device-1: NVIDIA GA102 [GeForce RTX 3080 Ti]
    vendor: eVga.com. 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: Ampere code: GAxxx process: TSMC n7 (7nm)
    built: 2020-2023 pcie: gen: 4 speed: 16 GT/s lanes: 16
    bus-ID: 01:00.0 chip-ID: 10de:2208 class-ID: 0300
  Device-2: Logitech HD Pro Webcam C920
    driver: snd-usb-audio,uvcvideo type: USB rev: 2.0
    speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-11.3.4.1:15
    chip-ID: 046d:082d class-ID: 0102 serial: <filter>
  Display: wayland server: X.org v: 1.21.1.11
    with: Xwayland v: 23.2.4 compositor: kwin_wayland driver:
    X: loaded: modesetting,nouveau,nvidia
    alternate: fbdev,nv,vesa gpu: nvidia display-ID: 0
  Monitor-1: Unknown-1 res: 640x480 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: kms_swrast
    surfaceless: drv: nvidia wayland: drv: zink x11:
    drv: zink inactive: device-1
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: mesa
    v: 24.0.2-arch1.1 glx-v: 1.4 direct-render: yes
    renderer: llvmpipe (LLVM 16.0.6 256 bits)
    device-ID: ffffffff:ffffffff memory: 30.42 GiB
    unified: yes display-ID: :1.0
  API: Vulkan v: 1.3.279 layers: 14 device: 0
    type: discrete-gpu name: NVIDIA GeForce RTX 3080 Ti
    driver: nvidia v: 550.54.14 device-ID: 10de:2208
    surfaces: xcb,xlib,wayland device: 1 type: cpu
    name: llvmpipe (LLVM 16.0.6 256 bits)
    driver: mesa llvmpipe v: 24.0.2-arch1.1 (LLVM 16.0.6)
    device-ID: 10005:0000 surfaces: xcb,xlib,wayland
Audio:
  Device-1: Intel Alder Lake-S HD Audio vendor: ASUSTeK
    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 GA102 High Definition Audio
    vendor: eVga.com. driver: snd_hda_intel v: kernel pcie:
    gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 01:00.1
    chip-ID: 10de:1aef class-ID: 0403
  Device-3: Logitech HD Pro Webcam C920
    driver: snd-usb-audio,uvcvideo type: USB rev: 2.0
    speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-11.3.4.1:15
    chip-ID: 046d:082d class-ID: 0102 serial: <filter>
  Device-4: SteelSeries ApS Arctis Pro Wireless
    driver: hid-generic,snd-usb-audio,usbhid type: USB
    rev: 1.1 speed: 12 Mb/s lanes: 1 mode: 1.1
    bus-ID: 1-11.3.4.3.3:18 chip-ID: 1038:1294
    class-ID: 0300
  Device-5: ASUSTek USB Audio
    driver: hid-generic,snd-usb-audio,usbhid type: USB
    rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0
    bus-ID: 1-4:2 chip-ID: 0b05:1996 class-ID: 0300
  API: ALSA v: k6.7.8-zen1-1-zen status: kernel-api
    with: aoss type: oss-emulator tools: N/A
  Server-1: 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 Wi-Fi 6E AX210/AX1675 2x2 [Typhoon Peak]
    driver: iwlwifi v: kernel pcie: gen: 2 speed: 5 GT/s
    lanes: 1 bus-ID: 05:00.0 chip-ID: 8086:2725
    class-ID: 0280
  IF: wlp5s0 state: up 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: 07:00.0 chip-ID: 8086:15f3
    class-ID: 0200
  IF: enp7s0 state: down mac: <filter>
  IF-ID-1: virbr0 state: up speed: 10000 Mbps
    duplex: unknown mac: <filter>
  IF-ID-2: vnet0 state: unknown speed: 10000 Mbps
    duplex: full mac: <filter>
  Info: services: NetworkManager, smbd, systemd-networkd,
    systemd-timesyncd, wpa_supplicant
Bluetooth:
  Device-1: Intel AX210 Bluetooth driver: btusb v: 0.8
    type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1
    bus-ID: 1-14:9 chip-ID: 8087:0032 class-ID: e001
  Report: btmgmt ID: hci0 rfk-id: 1 state: up
    address: <filter> bt-v: 5.3 lmp-v: 12 status:
    discoverable: no pairing: no class-ID: 6c0104
RAID:
  Hardware-1: Intel Volume Management Device NVMe RAID
    Controller driver: vmd v: 0.6 port: N/A bus-ID: 00:0e.0
    chip-ID: 8086:467f rev: class-ID: 0104
Drives:
  Local Storage: total: 1.82 TiB used: 521.4 GiB (28.0%)
  SMART Message: Unable to run smartctl. Root privileges
    required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung
    model: SSD 980 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: 5B2QGXA7 temp: 39.9 C
    scheme: MBR
Partition:
  ID-1: / raw-size: 1.79 TiB size: 1.79 TiB (100.00%)
    used: 521.4 GiB (28.5%) fs: btrfs dev: /dev/nvme0n1p1
    maj-min: 259:1
  ID-2: /home raw-size: 1.79 TiB size: 1.79 TiB (100.00%)
    used: 521.4 GiB (28.5%) fs: btrfs dev: /dev/nvme0n1p1
    maj-min: 259:1
  ID-3: /var/log raw-size: 1.79 TiB
    size: 1.79 TiB (100.00%) used: 521.4 GiB (28.5%) fs: btrfs
    dev: /dev/nvme0n1p1 maj-min: 259:1
  ID-4: /var/tmp raw-size: 1.79 TiB
    size: 1.79 TiB (100.00%) used: 521.4 GiB (28.5%) fs: btrfs
    dev: /dev/nvme0n1p1 maj-min: 259:1
Swap:
  Kernel: swappiness: 133 (default 60)
    cache-pressure: 100 (default) zswap: no
  ID-1: swap-1 type: partition size: 34.27 GiB
    used: 0 KiB (0.0%) priority: -2 dev: /dev/nvme0n1p2
    maj-min: 259:2
  ID-2: swap-2 type: zram size: 31.15 GiB
    used: 3 MiB (0.0%) priority: 100 comp: zstd
    avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 20
    dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 28.0 C mobo: N/A
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 32 GiB available: 31.16 GiB
    used: 9.3 GiB (29.8%)
  Processes: 444 Power: uptime: 6h 5m
    states: freeze,mem,disk suspend: deep avail: s2idle
    wakeups: 0 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 12.4 GiB
    services: org_kde_powerdevil, power-profiles-daemon,
    upowerd Init: systemd v: 255 default: graphical
    tool: systemctl
  Packages: pm: pacman pkgs: 1862 libs: 512
    tools: octopi,paru Compilers: gcc: 13.2.1
    Shell: garuda-inxi default: Bash v: 5.2.26
    running-in: konsole inxi: 3.3.33
Garuda (2.6.23-1):
  System install date:     2023-04-24
  Last full system update: 2024-03-06
  Is partially upgraded:   No
  Relevant software:       snapper NetworkManager dracut nvidia-dkms
  Windows dual boot:       <superuser required>
  Failed units:            systemd-networkd-wait-online.service 

I also luckily had GWE (GreenWithEnvy) opened this time from creating my forum account and getting the driver info and I saw this error message this time.

NV-CONTROL X extension not found

It was not possible to find the NVIDIA NV-CONTROL X extension on the current Display device.

Please make sure that the NVIDIA proprietary display drivers are installed and they support your current GPU 

So I’ll spend some time looking into that error more in the morning. I just wanted to get this posted since I forgot it from the template.

Edit: Looks like the above error might be a GWE only thing.

Edit 2: I found and ran this command in another post about Wayland and nVidia yesterday, but it didn’t do anything:

sudo cp /etc/default/grub /etc/default/grub.bak && sudo sed '/^GRUB_CMDLINE_LINUX_DEFAULT=/s/"$/ nvidia-drm.modeset=1 "/g' -i /etc/default/grub && sudo update-grub

But I manually went into the grub file and added the nvidia-drm.modeset and reboot and now I’m able to actually boot into Wayland at proper resolutions and with the KDE shell/widgets loading.

Thanks for the awesome experience so far with Garuda, and sorry for the post with my hiccup about getting Wayland running.

Fonts are a bit blurry in some areas, but I can live with that until I figure that out.

[Kayo]

@brian

Edit 2: I found and ran this command in another post about Wayland and nVidia yesterday, but it didn’t do anything:

sudo cp /etc/default/grub /etc/default/grub.bak && sudo sed '/^GRUB_CMDLINE_LINUX_DEFAULT=/s/"$/ nvidia-drm.modeset=1 "/g' -i /etc/default/grub && sudo update-grub

I’ve been seeing this more and more. @filo , I am thinking we should direct people to add the nvidia-drm.modeset=1 kernel parameter in the Garuda Boot Options program instead.

[filo]

Right. It is just that I have less and less time lately, so I entered into the bad habit of copy and paste my previous posts

[dr460nf1r3]

Gotta be efficient

[meanruse]

I have not run it, but by the look of it I’m not very convinced of that sed thing.
Won’t that blindly stick the new parameter at the end of the command line, even if there’s a comment?

[Kayo]

Might explain why that command only works for some people