With Plasma 6.4 released, if one does not have the new plasma-x11-session , they won’t be able to log in using X11:
Probably would be best to play it safe and install it with garuda-update to prevent issues on people that are still stuck using x11 for whatever reason.
(Maybe make it a hard dependency of a Plasma related Garuda package or some kind of tweak to garuda-update to identify KDE systems and fix?)
That would likely be the easiest solution. The question is how we’d go ahead and identify those systems 
I’m not sure whether there is an issue-free way to go ahead with this.
How about a notice pushed as Garuda maintenance notification instead (popping up in the system tray, linking to a forum thread in the maintenance section)?
System:
Kernel: 6.15.2-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 15.1.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=912594c8-56e7-4a2e-a0df-1bbc1dcf3d6a rw rootflags=subvol=@
quiet loglevel=3 ibt=off
Desktop: KDE Plasma v: 6.3.5 tk: Qt v: N/A info: frameworks v: 6.15.0
wm: kwin_x11 vt: 2 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required>
Mobo: ASUSTeK model: PRIME B550-PLUS v: Rev X.0x
serial: <superuser required> part-nu: SKU uuid: <superuser required>
UEFI: American Megatrends v: 3002 date: 02/23/2023
CPU:
Info: model: AMD Ryzen 5 5600X bits: 64 type: MT MCP arch: Zen 3+ gen: 3
level: v3 note: check built: 2022 process: TSMC n6 (7nm) family: 0x19 (25)
model-id: 0x21 (33) stepping: 2 microcode: 0xA201210
Topology: cpus: 1x dies: 1 clusters: 1 cores: 6 threads: 12 tpc: 2
smt: enabled cache: L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 3 MiB
desc: 6x512 KiB L3: 32 MiB desc: 1x32 MiB
Speed (MHz): avg: 1738 min/max: 561/4654 boost: enabled scaling:
driver: amd-pstate-epp governor: powersave cores: 1: 1738 2: 1738 3: 1738
4: 1738 5: 1738 6: 1738 7: 1738 8: 1738 9: 1738 10: 1738 11: 1738 12: 1738
bogomips: 88627
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities: <filter>
Graphics:
Device-1: NVIDIA AD104 [GeForce RTX 4070 SUPER] vendor: Micro-Star MSI
driver: nvidia v: 575.64 alternate: nouveau,nvidia_drm non-free: 550-570.xx+
status: current (as of 2025-04) 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 empty: DP-2,DP-3,HDMI-A-1 bus-ID: 07:00.0
chip-ID: 10de:2783 class-ID: 0300
Display: x11 server: X.Org v: 21.1.18 with: Xwayland v: 24.1.8
compositor: kwin_x11 driver: X: loaded: nvidia unloaded: modesetting,nouveau
alternate: fbdev,nv,vesa gpu: nvidia,nvidia-nvswitch display-ID: :0
screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 81 s-size: 602x331mm (23.70x13.03")
s-diag: 687mm (27.05")
Monitor-1: DP-1 mapped: DP-0 note: disabled model: YMC-70102 built: 2022
res: N/A dpi: 81 gamma: 1.2 size: 527x296mm (20.75x11.65") diag: 685mm (27")
ratio: 16:9 modes: max: 1920x1080 min: 640x480
API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia device: 2
drv: swrast gbm: drv: nvidia surfaceless: drv: nvidia x11: drv: nvidia
inactive: wayland,device-1
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 575.64
glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce RTX 4070
SUPER/PCIe/SSE2 memory: 11.71 GiB
API: Vulkan v: 1.4.313 layers: 15 device: 0 type: discrete-gpu name: NVIDIA
GeForce RTX 4070 SUPER driver: nvidia v: 575.64 device-ID: 10de:2783
surfaces: N/A device: 1 type: cpu name: llvmpipe (LLVM 20.1.6 256 bits)
driver: mesa llvmpipe v: 25.1.4-arch1.1 (LLVM 20.1.6)
device-ID: 10005:0000 surfaces: N/A
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor gpu: corectrl, nvidia-settings,
nvidia-smi wl: wayland-info x11: xdpyinfo, xprop, xrandr
Audio:
Device-1: NVIDIA AD104 High Definition Audio 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:22bc class-ID: 0403
Device-2: Advanced Micro Devices [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
Device-3: Turtle Beach Recon 60P driver: hid-generic,snd-usb-audio,usbhid
type: USB rev: 1.1 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-2:3
chip-ID: 10f5:0300 class-ID: 0300
API: ALSA v: k6.15.2-zen1-1-zen status: kernel-api with: aoss
type: oss-emulator tools: N/A
Server-1: PipeWire v: 1.4.5 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 RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
vendor: ASUSTeK RTL8111H driver: r8169 v: kernel pcie: gen: 1
speed: 2.5 GT/s lanes: 1 port: f000 bus-ID: 06:00.0 chip-ID: 10ec:8168
class-ID: 0200
IF: enp6s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Info: services: NetworkManager,systemd-timesyncd
Bluetooth:
Device-1: ASUSTek ASUS USB-BT500 driver: btusb v: 0.8 type: USB rev: 1.1
speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-10:7 chip-ID: 0b05:190e
class-ID: e001 serial: <filter>
Report: btmgmt ID: hci0 rfk-id: 0 state: up address: N/A
Drives:
Local Storage: total: 476.94 GiB used: 307.37 GiB (64.4%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 960 PRO 512GB
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: 1B6QCXP7 temp: 31.9 C
scheme: GPT
Partition:
ID-1: / raw-size: 476.64 GiB size: 476.64 GiB (100.00%)
used: 307.37 GiB (64.5%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 616 KiB (0.2%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
ID-3: /home raw-size: 476.64 GiB size: 476.64 GiB (100.00%)
used: 307.37 GiB (64.5%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-4: /var/log raw-size: 476.64 GiB size: 476.64 GiB (100.00%)
used: 307.37 GiB (64.5%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-5: /var/tmp raw-size: 476.64 GiB size: 476.64 GiB (100.00%)
used: 307.37 GiB (64.5%) 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: zram size: 31.22 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo-rle,lzo,lz4,lz4hc,deflate,842 dev: /dev/zram0
Sensors:
System Temperatures: cpu: 33.5 C mobo: N/A gpu: nvidia temp: 36 C
Fan Speeds (rpm): N/A gpu: nvidia fan: 0%
Info:
Memory: total: 32 GiB available: 31.22 GiB used: 5.12 GiB (16.4%)
Processes: 370 Power: uptime: 10m 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: 257 default: graphical
tool: systemctl
Packages: 1986 pm: pacman pkgs: 1969 libs: 578 tools: octopi,paru,yay
pm: flatpak pkgs: 17 Compilers: clang: 20.1.6 gcc: 15.1.1 Shell: garuda-inxi
default: fish v: 4.0.2 running-in: konsole inxi: 3.3.38
Garuda (2.7.2-1):
System install date: 2024-02-21
Last full system update: 2025-06-19
Is partially upgraded: No
Relevant software: snapper NetworkManager dracut nvidia-dkms
Windows dual boot: No/Undetected
I run certain apps on X11 that will not run in Wayland. If I manually update X11, will I always have to do this everytime KDE is updated?
That’s another good option. 
If you install plasma-x11-session you should be all set for when you need to use X11. This is probably because of the code split KDE has done recently. kwin X11 will be maintained until Plasma 7.
If this option is only good until KDE 7.0 I might be better off looking at replacing the apps I use with options that do work in Wayland. True, I could go with another Window Manager but I like KDE. Thanks!
Need to run this through @TNE still 
You have about 10 years before that give or take but cant hurt to look now.
It is merged. Criteria for triggering: installed kwin-x11 + plasma-desktop, but not plasma-x11-session.
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.