X11 removed from the sessions after my last Garuda-update

Issues & Assistance
1

Hello, so I recently updated my system with garuda-update after not being able to for a while because my network was having issues, but after the update I restarted my PC and when logging in my screen would go full black won’t respond to anything, I thought the update broke it but after checking in, the session was set to “Steam big picture” when I clicked on it to check the list, it shows me that I have two “Steam big picture” and Wayland, but no X11, any reason why that would happen?
Garuda-inxi:

System:
Kernel: 6.15.3-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=b8f55436-6379-4c35-b08e-eb4d2e1c60d3 rw rootflags=subvol=@
quiet loglevel=3 ibt=off
Desktop: KDE Plasma v: 6.4.0 tk: Qt v: N/A info: frameworks v: 6.15.0
wm: kwin_wayland vt: 1 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
Type: Desktop Mobo: ASUSTeK model: PRIME B450M-A v: Rev X.0x
serial: <superuser required> part-nu: SKU uuid: <superuser required>
UEFI: American Megatrends v: 2006 date: 11/13/2019
CPU:
Info: model: AMD Ryzen 5 3600 bits: 64 type: MT MCP arch: Zen 2 gen: 2
level: v3 note: check built: 2020-22 process: TSMC n7 (7nm)
family: 0x17 (23) model-id: 0x71 (113) stepping: 0 microcode: 0x8701034
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: 2x16 MiB
Speed (MHz): avg: 3579 min/max: 2200/4208 boost: enabled scaling:
driver: acpi-cpufreq governor: performance cores: 1: 3579 2: 3579 3: 3579
4: 3579 5: 3579 6: 3579 7: 3579 8: 3579 9: 3579 10: 3579 11: 3579 12: 3579
bogomips: 86232
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities: <filter>
Graphics:
Device-1: NVIDIA TU116 [GeForce GTX 1660 SUPER] vendor: PNY driver: nvidia
v: 575.64 alternate: nouveau,nvidia_drm non-free: 550-570.xx+ status: current
(as of 2025-04; 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: HDMI-A-1 empty: DP-1,DVI-D-1
bus-ID: 08:00.0 chip-ID: 10de:21c4 class-ID: 0300
Display: wayland server: X.org v: 1.21.1.18 with: Xwayland v: 24.1.8
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: Samsung S22F350 serial: <filter> built: 2020
res: mode: 1920x1080 hz: 60 scale: 100% (1) dpi: 102 gamma: 1.2
size: 477x268mm (18.78x10.55") diag: 547mm (21.5") 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 wayland: drv: nvidia
x11: drv: nvidia inactive: 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 GTX 1660
SUPER/PCIe/SSE2 memory: 5.86 GiB display-ID: :1.0
API: Vulkan v: 1.4.313 layers: 9 device: 0 type: discrete-gpu name: NVIDIA
GeForce GTX 1660 SUPER driver: nvidia v: 575.64 device-ID: 10de:21c4
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 TU116 High Definition Audio vendor: PNY
driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
bus-ID: 08:00.1 chip-ID: 10de:1aeb 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: 0a:00.4 chip-ID: 1022:1487 class-ID: 0403
API: ALSA v: k6.15.3-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: 07:00.0 chip-ID: 10ec:8168
class-ID: 0200
IF: enp7s0 state: up speed: 100 Mbps duplex: full mac: <filter>
Info: services: NetworkManager,systemd-timesyncd
Drives:
Local Storage: total: 476.94 GiB used: 872.83 GiB (183.0%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 model: SemsoTai SSD 512GB size: 476.94 GiB
block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s tech: SSD
serial: <filter> fw-rev: XKR scheme: GPT
Partition:
ID-1: / raw-size: 476.64 GiB size: 476.64 GiB (100.00%)
used: 436.41 GiB (91.6%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 616 KiB (0.2%) fs: vfat dev: /dev/sda1 maj-min: 8:1
ID-3: /home raw-size: 476.64 GiB size: 476.64 GiB (100.00%)
used: 436.41 GiB (91.6%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
ID-4: /var/log raw-size: 476.64 GiB size: 476.64 GiB (100.00%)
used: 436.41 GiB (91.6%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
ID-5: /var/tmp raw-size: 476.64 GiB size: 476.64 GiB (100.00%)
used: 436.41 GiB (91.6%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 31.27 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: 61.8 C mobo: 45.8 C
Fan Speeds (rpm): N/A
Info:
Memory: total: 32 GiB available: 31.27 GiB used: 5.69 GiB (18.2%)
Processes: 385 Power: uptime: 10m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 12.42 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 257 default: graphical
tool: systemctl
Packages: 1735 pm: pacman pkgs: 1725 libs: 495 tools: octopi,paru
pm: flatpak pkgs: 10 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:     2025-04-18
Last full system update: 2025-06-24
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut nvidia-dkms
Windows dual boot:       No/Undetected
Failed units:
2

Are you positively sure you updated with the garuda-update command?
The fix for this was already sent out:

If that didn’t work for some reason, install plasma-x11-session manually

4 Likes
3

Yeah after I made this post I tried to install plasma-x11-session manually right away and it installed kwin-x11 and plasma-desktop and I have X11 as a session again, but yes I am postive I updated using garuda-update, the only worth note I can give is that there has been a time of about 3 weeks since I last updated so that could be the issue but no I did not manually remove X11 or anything from my system for that matter and only updated using garuda-update

2 Likes
5

7 posts were split to a new topic: Black screen when signing into X11 KDE session

10

The only case in which x11 will be removed from your sessions list is if you don’t have kwin-x11 installed. The fix that people are talking about only stops you from having an unbootable session if you’ve already had kwin-x11 installed.

We are, in general, following the archlinux process of making Wayland the default behavior for KDE. This fix was only intended to prevent users from having a bricked (read: GUI-less) system.

If you want to keep/restore x11 functionality, you’ll have to install plasma-x11-session

3 Likes
11

I see, I was just wondering because I did not manually remove kwin-x11 myself and wasn’t sure if it was removed by the last update since only after I rebooted that it was gone so I went here to ask about it, thanks for the clarification.

12

You’ve probably never had kwin-x11 installed in the first place. The X11 Version of kwin was part of the original kwin package until recently. As Wayland is becoming the default in the Linux world, archlinux is starting to split those two packages (I assume that’s the reasoning at least!) so Wayland users don’t have to download x11 anymore.

4 Likes
14

This happened to me too, but I update frequently. I normally use Wayland, but I’ve got one game that needs X11 to work right.

Glad to have a solution.

1 Like
15

Yeah it is a bit weird, but harmless none the less, even though for my graphic card Wayland acts a bit wonky I can easily use it to get back X11 to use regularly since I am used to it

16

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.