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 isolate the package that gave the issue. There was also an update to Garuda Rani that was warring, but no issues there.
I found that, if I update garuda-mokka 1.1.3-5 → 1.2.2-5, I get the issue. On garuda-linux’s git I’ve seen that in fact there was an update 3days ago.

I’ve searched with issues similar to this but no luck.

Do you know what could be the issue? Or if I had to do something.

Btw in the output of garuda-update, I see no issue related to garuda-mokka.

garuda-inxi below

System:
  Kernel: 6.15.8-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=98fa8dad-9bf2-450e-b763-0f919cae5ac7 rw 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 quiet
    resume=UUID=4a3cafc5-883a-4266-8a74-6717c3f51bf2 loglevel=3 ibt=off
  Desktop: KDE Plasma v: 6.4.3 tk: Qt v: N/A info: frameworks v: 6.16.0 wm: kwin_wayland
    with: krunner vt: 1 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
  Type: Desktop Mobo: Micro-Star model: MAG B650 TOMAHAWK WIFI (MS-7D75) v: 1.0
    serial: <superuser required> uuid: <superuser required> UEFI: American Megatrends LLC. v: 1.O0
    date: 06/24/2025
CPU:
  Info: model: AMD Ryzen 7 7700 bits: 64 type: MT MCP arch: Zen 4 gen: 4 level: v4 note: check
    built: 2022+ process: TSMC n5 (5nm) family: 0x19 (25) model-id: 0x61 (97) stepping: 2
    microcode: 0xA60120C
  Topology: cpus: 1x dies: 1 clusters: 1 cores: 8 threads: 16 tpc: 2 smt: enabled cache:
    L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB L2: 8 MiB desc: 8x1024 KiB L3: 32 MiB desc: 1x32 MiB
  Speed (MHz): avg: 3008 min/max: 430/5487 boost: enabled scaling: driver: amd-pstate-epp
    governor: performance cores: 1: 3008 2: 3008 3: 3008 4: 3008 5: 3008 6: 3008 7: 3008 8: 3008
    9: 3008 10: 3008 11: 3008 12: 3008 13: 3008 14: 3008 15: 3008 16: 3008 bogomips: 121600
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities: <filter>
Graphics:
  Device-1: NVIDIA GP106 [GeForce GTX 1060 6GB] vendor: Micro-Star MSI driver: nvidia v: 575.64.05
    alternate: nouveau,nvidia_drm non-free: 550-570.xx+ status: current (as of 2025-04;
    EOL~2026-12-xx) arch: Pascal code: GP10x process: TSMC 16nm built: 2016-2021 pcie: gen: 3
    speed: 8 GT/s lanes: 16 ports: active: none off: HDMI-A-1 empty: DP-1, DP-2, DP-3, DVI-D-1
    bus-ID: 01:00.0 chip-ID: 10de:1c03 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,nouveau alternate: fbdev,nv,vesa
    gpu: nvidia,nvidia-nvswitch display-ID: 0
  Monitor-1: HDMI-A-1 model: Samsung S34J55x serial: <filter> built: 2022 res: mode: 3440x1440
    hz: 75 scale: 100% (1) dpi: 110 gamma: 1.2 size: 797x333mm (31.38x13.11") diag: 864mm (34")
    modes: max: 3440x1440 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.05 glx-v: 1.4
    direct-render: yes renderer: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 memory: 5.86 GiB
    display-ID: :1.0
  API: Vulkan v: 1.4.321 layers: 7 device: 0 type: discrete-gpu name: NVIDIA GeForce GTX 1060 6GB
    driver: nvidia v: 575.64.05 device-ID: 10de:1c03 surfaces: N/A device: 1 type: cpu name: llvmpipe
    (LLVM 20.1.8 256 bits) driver: mesa llvmpipe v: 25.1.6-arch1.1 (LLVM 20.1.8)
    device-ID: 10005:0000 surfaces: N/A
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo de: kscreen-console,kscreen-doctor
    gpu: nvidia-settings,nvidia-smi wl: wayland-info x11: xdpyinfo, xprop, xrandr
Audio:
  Device-1: NVIDIA GP106 High Definition Audio vendor: Micro-Star MSI driver: snd_hda_intel
    v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 01:00.1 chip-ID: 10de:10f1 class-ID: 0403
  Device-2: Advanced Micro Devices [AMD] Family 17h/19h/1ah HD Audio vendor: Micro-Star MSI
    driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 11:00.6
    chip-ID: 1022:15e3 class-ID: 0403
  Device-3: Micro Star 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-6:5 chip-ID: 0db0:422d class-ID: 0300
  API: ALSA v: k6.15.8-zen1-1-zen status: kernel-api tools: N/A
  Server-1: PipeWire v: 1.4.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: Realtek RTL8125 2.5GbE vendor: Micro-Star MSI driver: r8169 v: kernel pcie: gen: 2
    speed: 5 GT/s lanes: 1 port: d000 bus-ID: 0c:00.0 chip-ID: 10ec:8125 class-ID: 0200
  IF: enp12s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Device-2: MEDIATEK MT7922 802.11ax PCI Express Wireless Network Adapter driver: mt7921e
    v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1 bus-ID: 0d:00.0 chip-ID: 14c3:0616 class-ID: 0280
  IF: wlp13s0 state: down mac: <filter>
  IF-ID-1: docker0 state: down mac: <filter>
  Info: services: NetworkManager, smbd, sshd, systemd-timesyncd, wpa_supplicant
Bluetooth:
  Device-1: MediaTek Wireless_Device driver: btusb v: 0.8 type: USB rev: 2.1 speed: 480 Mb/s
    lanes: 1 mode: 2.0 bus-ID: 1-7:8 chip-ID: 0e8d:0616 class-ID: e001 serial: <filter>
  Report: btmgmt ID: hci0 rfk-id: 0 state: up address: N/A
Drives:
  Local Storage: total: 2.75 TiB used: 184.45 GiB (6.5%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 990 PRO with Heatsink 1TB
    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: 6B2QJXD7 temp: 51.9 C scheme: GPT
  ID-2: /dev/nvme1n1 maj-min: 259:4 vendor: Samsung model: SSD 970 PRO 1TB size: 953.87 GiB
    block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter>
    fw-rev: 1B2QEXP7 temp: 39.9 C scheme: GPT
  ID-3: /dev/sda maj-min: 8:0 vendor: Western Digital model: WD10EZEX-08WN4A0 size: 931.51 GiB
    block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s tech: HDD rpm: 7200 serial: <filter>
    fw-rev: 1A02 scheme: GPT
Partition:
  ID-1: / raw-size: 897.66 GiB size: 897.66 GiB (100.00%) used: 184.45 GiB (20.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: 620 KiB (0.2%) fs: vfat
    dev: /dev/nvme0n1p1 maj-min: 259:1
  ID-3: /home raw-size: 897.66 GiB size: 897.66 GiB (100.00%) used: 184.45 GiB (20.5%) fs: btrfs
    dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-4: /var/log raw-size: 897.66 GiB size: 897.66 GiB (100.00%) used: 184.45 GiB (20.5%)
    fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-5: /var/tmp raw-size: 897.66 GiB size: 897.66 GiB (100.00%) used: 184.45 GiB (20.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: 30.94 GiB used: 195.9 MiB (0.6%) priority: 100 comp: zstd
    avail: lzo-rle,lzo,lz4,lz4hc,deflate,842 dev: /dev/zram0
  ID-2: swap-2 type: partition size: 33.56 GiB used: 0 KiB (0.0%) priority: -2
    dev: /dev/nvme0n1p3 maj-min: 259:3
Sensors:
  System Temperatures: cpu: 51.5 C mobo: 47.5 C
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 32 GiB note: est. available: 30.94 GiB used: 11.02 GiB (35.6%)
  Processes: 455 Power: uptime: 1h 27m states: freeze,mem,disk suspend: deep avail: s2idle
    wakeups: 0 hibernate: platform avail: shutdown, reboot, suspend, test_resume image: 12.29 GiB
    services: org_kde_powerdevil, power-profiles-daemon, upowerd Init: systemd v: 257
    default: graphical tool: systemctl
  Packages: pm: pacman pkgs: 1838 libs: 366 tools: octopi,pamac,paru Compilers: clang: 20.1.8
    gcc: 15.1.1 Client: Unknown Client: electron inxi: 3.3.38
Garuda (2.7.3-2):
  System install date:     2024-05-03
  Last full system update: 2025-07-24
  Is partially upgraded:   Yes
  Relevant software:       snapper NetworkManager dracut nvidia-dkms
  Windows dual boot:       Probably (Run as root to verify)
  Failed units:            

I might have missed something, to add to the Topic, but let me know.

Thanks for any suggestion.

1 Like

The SDDM theme is not showing at all?

There is an update related to that currently building, v1.2.3.
It forces Wayland on the SDDM screen, as Plasma uses Wayland by default now. It allows to use a different theme for Mokka.

I see you are on nvidia, I wonder if this was causing the blank screen you had.
All my tests are on AMD and I didn’t have a blank screen.

Wait for v1.2.3 to show up and see if that fixes it.

5 Likes

v1.2.3 is available.

7 Likes

I didn’t post about it because I have been so busy with work lately, however, assuming I’m correct, I had this problem happen recently. (Monday I think, and I do updates every day.) I just reverted back with the btrfs snapshots. I’ve been avoiding updating the hardware profiles packages because I thought those were the culprits, but it may be the mokka package because I avoided updating that too, to avoid a dependency loop, if I remember correctly.
I’m on AMD though. (Radeon RX 7900 XTX)

3 Likes

@FGD
No issue with v1.2.3.

Thanks a lot!

1 Like

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