Login screen SDDM not showing after reboot after an update

[Austin]

The login screen/display manager SDDM is not showing after reboot after an update

garuda-inxi from recovery mode

System:
  Kernel: 6.16.0-2-cachyos arch: x86_64 bits: 64 compiler: gcc v: 15.1.1 clocksource: tsc
    avail: hpet,acpi_pm parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-cachyos
    root=/dev/mapper/Linux-Root rw single rootflags=subvol=@
    vt.default_red=30,243,166,249,137,245,148,186,88,243,166,249,137,245,148,166
    vt.default_grn=30,139,227,226,180,194,226,194,91,139,227,226,180,194,226,173
    vt.default_blu=46,168,161,175,250,231,213,222,112,168,161,175,250,231,213,200
  Console: tty 1 DM: SDDM Distro: Garuda base: Arch Linux
Machine:
  Type: Laptop System: HP product: HP ProBook 445 14 inch G10 Notebook PC v: SBKPF,SBKPFV2
    serial: <superuser required> Chassis: type: 10 serial: <superuser required>
  Mobo: HP model: 8B5C v: KBC Version 53.33.00 serial: <superuser required> part-nu: B1RB5PC#ACJ
    uuid: <superuser required> UEFI: HP v: 78 Ver. 01.09.00 date: 01/14/2025
Battery:
  ID-1: BAT0 charge: 42.8 Wh (95.7%) condition: 44.7/51.3 Wh (87.2%) volts: 12.8 min: 11.6
    model: Hewlett-Packard Primary type: Li-ion serial: <filter> status: not charging cycles: 201
CPU:
  Info: model: AMD Ryzen 5 7530U with Radeon Graphics bits: 64 type: MT MCP arch: Zen 3 gen: 3
    level: v3 note: check built: 2021-22 process: TSMC n7 (7nm) family: 0x19 (25)
    model-id: 0x50 (80) stepping: 0 microcode: 0xA500012
  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: 16 MiB desc: 1x16 MiB
  Speed (MHz): avg: 1096 min/max: 411/4548 boost: enabled scaling: driver: amd-pstate-epp
    governor: performance cores: 1: 1096 2: 1096 3: 1096 4: 1096 5: 1096 6: 1096 7: 1096 8: 1096
    9: 1096 10: 1096 11: 1096 12: 1096 bogomips: 47906
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities: <filter>
Graphics:
  Device-1: Advanced Micro Devices [AMD/ATI] Barcelo vendor: Hewlett-Packard driver: amdgpu
    v: kernel arch: GCN-5 code: Vega process: GF 14nm built: 2017-20 pcie: gen: 3 speed: 8 GT/s
    lanes: 16 ports: active: eDP-1 empty: DP-1,DP-2,HDMI-A-1 bus-ID: 04:00.0 chip-ID: 1002:15e7
    class-ID: 0300 temp: 47.0 C
  Device-2: Cheng Uei Precision Industry (Foxlink) HP HD Camera driver: uvcvideo type: USB
    rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-4:2 chip-ID: 05c8:0b06 class-ID: fe01
    serial: <filter>
  Display: server: X.org v: 1.21.1.18 with: Xwayland v: 24.1.8 driver: X: loaded: amdgpu
    unloaded: modesetting alternate: fbdev,vesa dri: radeonsi gpu: amdgpu tty: 192x54
  Monitor-1: eDP-1 model: LG Display 0x0725 built: 2021 res: 1920x1080 dpi: 158 gamma: 1.2
    size: 309x174mm (12.17x6.85") diag: 355mm (14") ratio: 16:9 modes: max: 1920x1080 min: 640x480
  API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi device: 1 drv: swrast
    gbm: drv: radeonsi surfaceless: drv: radeonsi inactive: wayland,x11
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: mesa v: 25.1.6-cachyos1.3 note: console (EGL sourced)
    renderer: AMD Radeon Graphics (radeonsi renoir ACO DRM 3.64 6.16.0-2-cachyos), llvmpipe (LLVM
    20.1.8 256 bits)
  API: Vulkan v: 1.4.321 layers: 11 device: 0 type: integrated-gpu name: AMD Radeon Graphics
    (RADV RENOIR) driver: mesa radv v: 25.1.6-cachyos1.3 device-ID: 1002:15e7 surfaces: N/A
    device: 1 type: cpu name: llvmpipe (LLVM 20.1.8 256 bits) driver: mesa llvmpipe
    v: 25.1.6-cachyos1.3 (LLVM 20.1.8) device-ID: 10005:0000 surfaces: N/A
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo de: kscreen-console,kscreen-doctor
    gpu: corectrl,lact wl: wayland-info x11: xdpyinfo, xprop, xrandr
Audio:
  Device-1: Advanced Micro Devices [AMD/ATI] Renoir Radeon High Definition Audio
    driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 04:00.1
    chip-ID: 1002:1637 class-ID: 0403
  Device-2: Advanced Micro Devices [AMD] Audio Coprocessor vendor: Hewlett-Packard driver: N/A
    alternate: snd_pci_acp3x, snd_rn_pci_acp3x, snd_pci_acp5x, snd_pci_acp6x, snd_acp_pci,
    snd_rpl_pci_acp6x, snd_pci_ps, snd_sof_amd_renoir, snd_sof_amd_rembrandt,
    snd_sof_amd_vangogh, snd_sof_amd_acp63, snd_sof_amd_acp70 pcie: gen: 3 speed: 8 GT/s lanes: 16
    bus-ID: 04:00.5 chip-ID: 1022:15e2 class-ID: 0480
  Device-3: Advanced Micro Devices [AMD] Family 17h/19h/1ah HD Audio vendor: Hewlett-Packard
    driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 04:00.6
    chip-ID: 1022:15e3 class-ID: 0403
  API: ALSA v: k6.16.0-2-cachyos status: kernel-api tools: N/A
  Server-1: PipeWire v: 1.4.7 status: off with: 1: pipewire-pulse status: off 2: wireplumber
    status: off 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: Hewlett-Packard
    driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: 3000 bus-ID: 01:00.0
    chip-ID: 10ec:8168 class-ID: 0200
  IF: enp1s0 state: down mac: <filter>
  Device-2: Realtek RTL8852CE PCIe 802.11ax Wireless Network vendor: Hewlett-Packard
    driver: rtw89_8852ce v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1 port: 2000 bus-ID: 02:00.0
    chip-ID: 10ec:c852 class-ID: 0280
  IF: wlp2s0 state: down mac: <filter>
  Info: services: systemd-timesyncd
Bluetooth:
  Device-1: Realtek Bluetooth Radio driver: btusb v: 0.8 type: USB rev: 1.0 speed: 12 Mb/s
    lanes: 1 mode: 1.1 bus-ID: 1-3:3 chip-ID: 0bda:c85c 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: 187.03 GiB (39.2%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Micron model: MTFDKBA512QFM-1BD1AABHA
    size: 476.94 GiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 tech: SSD
    serial: <filter> fw-rev: HPSQ041 temp: 33.9 C scheme: GPT
Partition:
  ID-1: / raw-size: 64 GiB size: 64 GiB (100.00%) used: 37.12 GiB (58.0%) fs: btrfs dev: /dev/dm-0
    maj-min: 253:0 mapped: Linux-Root
  ID-2: /boot/efi raw-size: 384 MiB size: 383.2 MiB (99.80%) used: 640 KiB (0.2%) fs: vfat
    dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-3: /home raw-size: 64 GiB size: 64 GiB (100.00%) used: 37.12 GiB (58.0%) fs: btrfs
    dev: /dev/dm-0 maj-min: 253:0 mapped: Linux-Root
  ID-4: /var/log raw-size: 64 GiB size: 64 GiB (100.00%) used: 37.12 GiB (58.0%) fs: btrfs
    dev: /dev/dm-0 maj-min: 253:0 mapped: Linux-Root
  ID-5: /var/tmp raw-size: 64 GiB size: 64 GiB (100.00%) used: 37.12 GiB (58.0%) fs: btrfs
    dev: /dev/dm-0 maj-min: 253:0 mapped: Linux-Root
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
  ID-1: swap-1 type: zram size: 14.93 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: 46.8 C mobo: N/A gpu: amdgpu temp: 41.0 C
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 16 GiB note: est. available: 14.93 GiB used: 846.9 MiB (5.5%)
  Processes: 280 Power: uptime: 4m states: freeze,mem,disk suspend: s2idle wakeups: 0
    hibernate: platform avail: shutdown, reboot, suspend, test_resume image: 5.89 GiB Init: systemd
    v: 257 default: graphical tool: systemctl
  Packages: 1654 pm: pacman pkgs: 1633 libs: 374 tools: octopi,paru,yay pm: flatpak pkgs: 21
    Compilers: clang: 20.1.8 gcc: 15.1.1 Shell: garuda-inxi default: Bash v: 5.3.3 running-in: tty 1
    inxi: 3.3.38
Garuda (2.7.3-2):
  System install date:     2025-03-29
  Last full system update: 2025-07-30
  Is partially upgraded:   No
  Relevant software:       snapper dracut
  Windows dual boot:       Probably (Run as root to verify)
  Failed units:            

Here is a list of package that were updates:

ada 3.2.1-1.1 -> 3.2.7-1.1
archlinux-appstream-data 20250529-1 -> 20250730-1
bash 5.3.0-2 -> 5.3.3-2
binutils 2.44+r94+gfe459e33c676-2 -> 2.45-3
coin 4.0.4-1.1 -> 1:4.0.3-1.1
enchant 2.8.10-1.1 -> 2.8.12-1.1
fzf 0.64.0-1.1 -> 0.65.0-1.1
garuda-hardware-profile-standard 1.0.0-4 -> 1.1.0-1
garuda-hardware-profile-standard-x11 1.0.0-4 -> 1.1.0-1
garuda-hardware-tool 0.2.1-5 -> 0.2.1-6
garuda-mokka 1.1.3-5 -> 1.2.2-5
garuda-rani 3.1.1-3 -> 3.1.3-3
inkscape 1.4.2-5.1 -> 1.4.2-6.1
iproute2 6.15.0-1.1 -> 6.16.0-1.1
kwin-effect-rounded-corners-git 0.7.2.r66.gf2b3f7a-1 -> 0.8.0.r0.g20b6550-1
kwin-effects-forceblur 1.4.0-3.2 -> 1.5.0-1
lib32-libnghttp3 1.10.1-1 -> 1.11.0-1
lib32-pixman 0.46.2-1 -> 0.46.4-1
libheif 1.20.1-1.1 -> 1.20.1-2.1
libnghttp3 1.10.1-1.1 -> 1.11.0-1.1
linux-cachyos 6.15.8-2 -> 6.16.0-2
linux-cachyos-headers 6.15.8-2 -> 6.16.0-2
mpg123 1.33.0-1.1 -> 1.33.1-1.1
openexr 3.3.4-1.1 -> 3.3.5-1.1
openssh 10.0p1-3.1 -> 10.0p1-4.1
openucx 1.18.1-3.1 -> 1.18.1-4.1
packagekit-qt5 1.1.2-1 -> 1.1.3-1
pambase 20230918-2 -> 20250719-1
python-contourpy 1.3.2-1.1 -> 1.3.3-1.1
python-coverage 7.9.2-1.1 -> 7.10.0-1.1
python-kiwisolver 1.4.6-1.2 -> 1.4.7-1.1
python-lxml 6.0.0-1.1 -> 6.0.0-2.1
python-orjson 3.11.0-1.1 -> 3.11.1-1.1
python-pypdf 5.8.0-1 -> 5.9.0-1
qemu-audio-alsa 10.0.2-1 -> 10.0.3-1
qemu-audio-dbus 10.0.2-1 -> 10.0.3-1
qemu-audio-jack 10.0.2-1 -> 10.0.3-1
qemu-audio-oss 10.0.2-1 -> 10.0.3-1
qemu-audio-pa 10.0.2-1 -> 10.0.3-1
qemu-audio-pipewire 10.0.2-1 -> 10.0.3-1
qemu-audio-sdl 10.0.2-1 -> 10.0.3-1
qemu-audio-spice 10.0.2-1 -> 10.0.3-1
qemu-base 10.0.2-1 -> 10.0.3-1
qemu-block-curl 10.0.2-1 -> 10.0.3-1
qemu-block-dmg 10.0.2-1 -> 10.0.3-1
qemu-block-nfs 10.0.2-1 -> 10.0.3-1
qemu-block-ssh 10.0.2-1 -> 10.0.3-1
qemu-chardev-spice 10.0.2-1 -> 10.0.3-1
qemu-common 10.0.2-1 -> 10.0.3-1
qemu-desktop 10.0.2-1 -> 10.0.3-1
qemu-hw-display-qxl 10.0.2-1 -> 10.0.3-1
qemu-hw-display-virtio-gpu 10.0.2-1 -> 10.0.3-1
qemu-hw-display-virtio-gpu-gl 10.0.2-1 -> 10.0.3-1
qemu-hw-display-virtio-gpu-pci 10.0.2-1 -> 10.0.3-1
qemu-hw-display-virtio-gpu-pci-gl 10.0.2-1 -> 10.0.3-1
qemu-hw-display-virtio-gpu-pci-rutabaga 10.0.2-1 -> 10.0.3-1
qemu-hw-display-virtio-gpu-rutabaga 10.0.2-1 -> 10.0.3-1
qemu-hw-display-virtio-vga 10.0.2-1 -> 10.0.3-1
qemu-hw-display-virtio-vga-gl 10.0.2-1 -> 10.0.3-1
qemu-hw-display-virtio-vga-rutabaga 10.0.2-1 -> 10.0.3-1
qemu-hw-uefi-vars 10.0.2-1 -> 10.0.3-1
qemu-hw-usb-host 10.0.2-1 -> 10.0.3-1
qemu-hw-usb-redirect 10.0.2-1 -> 10.0.3-1
qemu-hw-usb-smartcard 10.0.2-1 -> 10.0.3-1
qemu-img 10.0.2-1 -> 10.0.3-1
qemu-system-x86 10.0.2-1 -> 10.0.3-1
qemu-system-x86-firmware 10.0.2-1 -> 10.0.3-1
qemu-ui-curses 10.0.2-1 -> 10.0.3-1
qemu-ui-dbus 10.0.2-1 -> 10.0.3-1
qemu-ui-egl-headless 10.0.2-1 -> 10.0.3-1
qemu-ui-gtk 10.0.2-1 -> 10.0.3-1
qemu-ui-opengl 10.0.2-1 -> 10.0.3-1
qemu-ui-sdl 10.0.2-1 -> 10.0.3-1
qemu-ui-spice-app 10.0.2-1 -> 10.0.3-1
qemu-ui-spice-core 10.0.2-1 -> 10.0.3-1
qemu-vhost-user-gpu 10.0.2-1 -> 10.0.3-1
slang 2.3.3-3.1 -> 2.3.3-4.1
spice 0.16.0-1.1 -> 0.16.0-2.1
systemd 257.7-1 -> 257.7-2
systemd-libs 257.7-1 -> 257.7-2
systemd-sysvcompat 257.7-1 -> 257.7-2
vde2 2.3.3-7.1 -> 2.3.3-8.1
waydroid-helper 0.1.2-1 -> 0.2.1-1
wolfssl 5.8.0-2 -> 5.8.2-1
zen-browser-bin 1.14.6b-1 -> 1.14.9b-1

I couldn’t find the culprit

Running startplasma-wayland in recovery mode gives me,

startplasmacompositor: Could not start D-Bus. Can you call qdbus?

It has been 3-4 days now, and I have been working on a restored snapshot.

The kernel and systemd upgrades don’t seem to be the issue.

Thank you in advance

Austin

[filo]

I suspect this one:

@Austin

garuda-mokka 1.1.3-5 → 1.2.2-5

because there were several SDDM configuration changes 3 days ago:

Commits · main · Garuda Linux 🦅 / Themes and Settings / Settings / Garuda...

I have no idea, and today I’m not at home to try/check. Maybe this one:

fix: SDDM conf files to support Wayland with new theme (4658576a) · Commits ·...

in the general.conf (since I see you’re on X11).
Edit: No, probably something else (but in that package upgrade), since I’ve just seen this other topic (on wayland):

Update of package garuda-mokka, no desktop at reboot

Hi guys, I’ve been using garuda-linux on this PC for about 2 years and it was a Dragonized version. At a certain point I switched to mokka theme following the post with the “how to” and I had NO issues and everything has been going fine. Yesterday morning, I tried to do a garuda-update -a and, after a reboot hours later, I got stuck at boot after grub with a simple “underscore” on screen. With Snapper, I went back and tried again using “garuda-update – --ignore pkg”, every time trying to iso…

Maybe that

CompositorCommand=kwin_wayland --no-lockscreen --no-global-shortcuts --locale1

?

[Austin]

Thank you, @filo, for pointing out the recent commits.
Thank you, @Kayo, for properly formatting my post.

The culprit was the addition of DisplayServer=wayland in /usr/lib/sddm/sddm.conf.d/general.conf

Commenting it out fixed the issue!

[Austin]

https://wiki.archlinux.org/title/SDDM#Configuration
Here it states that,

The default configuration file for SDDM can be found at /usr/lib/sddm/sddm.conf.d/default.conf. For any changes, create configuration file(s) in /etc/sddm.conf.d/.

I think changing the default configurations at /usr/lib/sddm/sddm.conf.d/default.conf caused the issue. You probably shouldn’t make any changes or additions in the /usr/lib/sddm/sddm.conf.d/ directory.

Also,
There is more relevant documentation here: https://wiki.archlinux.org/title/SDDM#Wayland

[FGD]

Precisely, the /usr/lib was the problem and in garuda-mokka v1.2.3 the file has been moved to /etc/sddm.conf.d.

Anyone using X11 might have problems, but in order to use the new Mokka SDDM Theme, Wayland needed to be forced at the SDDM configuration level.

The creator of the theme is looking into making this better.
Plasma is using Wayland by default.
If the theme does not display under X11, commenting out 1 or more of the below might fix the issue:

DisplayServer=wayland #Used to help force Wayland on certain themes
GreeterEnvironment=QT_WAYLAND_SHELL_INTEGRATION=layer-shell #Used to help force Wayland on certain themes

[Wayland]
CompositorCommand=kwin_wayland --drm --no-lockscreen --no-global-shortcuts --locale1 #Used to help force Wayland on certain themes

The file is /etc/sddm.conf.d/10-wayland.conf

It is also possible to use the old SDDM Theme, it’s still available (for now) in System Settings/Login Screen.

[Austin]

The new update pushed by the team has solved the issue — no need for changing anything now. It seems to have also solved some glitches in the Catppuccin-Mocha-Mauve theme that was there before.

[FGD]

@Austin

It seems to have also solved some glitches in the Catppuccin-Mocha-Mauve theme that was there before.

That’s great news, but hum, like what?

[Austin]

Whenever I clicked on input spaces like where you could type in your password or change your user (which is done by typing in this theme), the screen went completely dark, and then I would have to blindly type in my password and click Enter.

[FGD]

That’s the exact reason for all the recent changes.
The Catppuccin theme is not handling Wayland properly and the *.conf files needed to be edited (and located at the correct place).