Garuda Dragonized edition slow start up after login (splash screen)

Hi, I have been using the dragonized edition for quite some time (close to a year), it used to be super responsive right from logging in until a few months back. When I log in now, it takes close to 10 to 15 seconds to get to the Desktop (a spinning dragon will be shown until the DE loads). Even after I get the Desktop screen it takes 5 to 8 secs to load the dock etc. Any idea why I am facing such an issue or is it just the KDE startup time? Here is my garuda-inxi

Kernel: 5.18.12-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 12.1.0
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=c86ec1a0-7254-48c4-9823-df77cca3f8a9 rw [email protected]
quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
systemd.unified_cgroup_hierarchy=1 loglevel=3 ibt=off
Console: pty pts/1 wm: kwin_x11 DM: SDDM Distro: Garuda Linux
base: Arch Linux
Type: Laptop System: Acer product: Nitro AN515-52 v: V1.19 serial: <filter>
Mobo: CFL model: Freed_CFS v: V1.19 serial: <filter> UEFI: Insyde v: 1.19
date: 07/13/2018
ID-1: BAT1 charge: 32.3 Wh (100.0%) condition: 32.3/48.9 Wh (66.0%)
volts: 16.6 min: 15.2 model: LG PABAS0241231 type: Li-ion serial: <filter>
status: full
Info: model: Intel Core i7-8750H socket: U3E1 bits: 64 type: MT MCP
arch: Coffee Lake gen: core 8 built: 2018 process: Intel 14nm family: 6
model-id: 0x9E (158) stepping: 0xA (10) microcode: 0xF0
Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache:
L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 1.5 MiB desc: 6x256 KiB
L3: 9 MiB desc: 1x9 MiB
Speed (MHz): avg: 4091 high: 4102 min/max: 800/4100 scaling:
driver: intel_pstate governor: powersave volts: 1.2 V ext-clock: 100 MHz
cores: 1: 4101 2: 4102 3: 4101 4: 4083 5: 4100 6: 4100 7: 4099 8: 4101
9: 4100 10: 4029 11: 4085 12: 4098 bogomips: 52799
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Type: itlb_multihit status: KVM: VMX disabled
Type: l1tf
mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
Type: mds mitigation: Clear CPU buffers; SMT vulnerable
Type: meltdown mitigation: PTI
Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
Type: spec_store_bypass
mitigation: Speculative Store Bypass disabled via prctl
Type: spectre_v1
mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, IBRS_FW,
STIBP: conditional, RSB filling
Type: srbds mitigation: Microcode
Type: tsx_async_abort status: Not affected
Device-1: Intel CoffeeLake-H GT2 [UHD Graphics 630]
vendor: Acer Incorporated ALI driver: i915 v: kernel arch: Gen9.5
process: Intel 14nm built: 2016-20 ports: active: eDP-1 empty: none
bus-ID: 00:02.0 chip-ID: 8086:3e9b class-ID: 0300
Device-2: NVIDIA GP107M [GeForce GTX 1050 Ti Mobile]
vendor: Acer Incorporated ALI driver: nvidia v: 515.57
alternate: nouveau,nvidia_drm non-free: 515.xx+
status: current (as of 2022-06) arch: Pascal process: TSMC 16nm
built: 2016-21 pcie: gen: 1 speed: 2.5 GT/s lanes: 16 link-max: gen: 3
speed: 8 GT/s ports: active: none empty: HDMI-A-1 bus-ID: 01:00.0
chip-ID: 10de:1c8c class-ID: 0300
Device-3: Quanta HD Webcam type: USB driver: uvcvideo bus-ID: 1-5:3
chip-ID: 0408:a060 class-ID: 0e02 serial: <filter>
Display: x11 server: X.Org v: 21.1.4 with: Xwayland v: 22.1.3
compositor: kwin_x11 driver: X: loaded: modesetting,nvidia gpu: i915
display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22")
s-diag: 582mm (22.93")
Monitor-1: eDP-1 model: AU Optronics 0x61ed built: 2016 res: 1920x1080
hz: 60 dpi: 142 gamma: 1.2 size: 344x193mm (13.54x7.6") diag: 394mm (15.5")
ratio: 16:9 modes: 1920x1080
OpenGL: renderer: N/A v: N/A direct render: N/A
Device-1: Intel Cannon Lake PCH cAVS vendor: Acer Incorporated ALI
driver: snd_hda_intel v: kernel
alternate: snd_soc_skl,snd_sof_pci_intel_cnl bus-ID: 00:1f.3
chip-ID: 8086:a348 class-ID: 0403
Device-2: NVIDIA GP107GL High Definition Audio
vendor: Acer Incorporated ALI driver: snd_hda_intel v: kernel pcie:
speed: Unknown lanes: 63 link-max: gen: 6 speed: 64 GT/s bus-ID: 01:00.1
chip-ID: 10de:0fb9 class-ID: 0403
Sound Server-1: ALSA v: k5.18.12-zen1-1-zen running: yes
Sound Server-2: sndio v: N/A running: no
Sound Server-3: PulseAudio v: 16.1 running: no
Sound Server-4: PipeWire v: 0.3.55 running: yes
Device-1: Intel Cannon Lake PCH CNVi WiFi driver: iwlwifi v: kernel
bus-ID: 00:14.3 chip-ID: 8086:a370 class-ID: 0280
IF: wlp0s20f3 state: up mac: <filter>
Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: Acer Incorporated ALI driver: r8169 v: kernel pcie: gen: 1
speed: 2.5 GT/s lanes: 1 port: 3000 bus-ID: 06:00.1 chip-ID: 10ec:8168
class-ID: 0200
IF: enp6s0f1 state: down mac: <filter>
Device-1: Intel Bluetooth 9460/9560 Jefferson Peak (JfP) type: USB
driver: btusb v: 0.8 bus-ID: 1-14:4 chip-ID: 8087:0aaa class-ID: e001
Report: bt-adapter ID: hci0 rfk-id: 3 state: down
bt-service: enabled,running rfk-block: hardware: no software: yes
address: <filter>
Local Storage: total: 1.03 TiB used: 99.48 GiB (9.5%)
ID-1: /dev/sda maj-min: 8:0 vendor: SK Hynix model: HFS128G39TND-N210A
family: SATA SSDs size: 119.24 GiB block-size: physical: 4096 B
logical: 512 B sata: 3.1 speed: 6.0 Gb/s type: SSD serial: <filter>
rev: 1P10 temp: 39 C scheme: GPT
SMART: yes state: enabled health: PASSED on: 1y 252d 3h cycles: 5428
Pre-Fail: retired block: 100 threshold: 36
ID-2: /dev/sdb maj-min: 8:16 vendor: HGST (Hitachi)
model: HTS721010A9E630 family: Travelstar 7K1000 size: 931.51 GiB
block-size: physical: 4096 B logical: 512 B sata: 3.0 speed: 6.0 Gb/s
type: HDD rpm: 7200 serial: <filter> rev: A3J0 temp: 37 C scheme: GPT
SMART: yes state: enabled health: PASSED on: 1y 280d 15h cycles: 5378
ID-1: / raw-size: 149.91 GiB size: 149.91 GiB (100.00%)
used: 99.45 GiB (66.3%) fs: btrfs block-size: 4096 B dev: /dev/sdb3
maj-min: 8:19
ID-2: /boot/efi raw-size: 100 MiB size: 96 MiB (96.00%)
used: 31.8 MiB (33.2%) fs: vfat block-size: 512 B dev: /dev/sda2
maj-min: 8:2
ID-3: /home raw-size: 149.91 GiB size: 149.91 GiB (100.00%)
used: 99.45 GiB (66.3%) fs: btrfs block-size: 4096 B dev: /dev/sdb3
maj-min: 8:19
ID-4: /var/log raw-size: 149.91 GiB size: 149.91 GiB (100.00%)
used: 99.45 GiB (66.3%) fs: btrfs block-size: 4096 B dev: /dev/sdb3
maj-min: 8:19
ID-5: /var/tmp raw-size: 149.91 GiB size: 149.91 GiB (100.00%)
used: 99.45 GiB (66.3%) fs: btrfs block-size: 4096 B dev: /dev/sdb3
maj-min: 8:19
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: zram size: 15.47 GiB used: 2 MiB (0.0%) priority: 100
dev: /dev/zram0
ID-2: swap-2 type: partition size: 976 MiB used: 0 KiB (0.0%)
priority: -2 dev: /dev/sdb4 maj-min: 8:20
System Temperatures: cpu: 52.0 C pch: 56.0 C mobo: N/A
Fan Speeds (RPM): N/A
Processes: 323 Uptime: 45m wakeups: 1 Memory: 15.47 GiB
used: 3.53 GiB (22.8%) Init: systemd v: 251 default: graphical
tool: systemctl Compilers: gcc: 12.1.1 alt: 11 clang: 14.0.6 Packages: 1597
pacman: 1590 lib: 356 snap: 7 Shell: garuda-inxi (sudo) default: Bash
v: 5.1.16 running-in: konsole inxi: 3.3.19
Garuda (2.6.5-1):
System install date:     2022-05-16
Last full system update: 2022-07-18 ↻
Is partially upgraded:   No
Relevant software:       NetworkManager
Windows dual boot:       Yes
Snapshots:               Snapper
Failed units:

First reboot:

Then, I think you should start checking your

systemd-analyze blame
systemd-analyze critical-chain

Here are the outputs and quite interesting insights.

systemd-analyze : 
Startup finished in 3.395s (firmware) + 4.102s (loader) + 6.405s (kernel) + 8min 21.495s (userspace) = 8min 35
.399s reached after 59.291s in userspace.
systemd-analyze blame (top ones)
6min 43.789s linux-modules-cleanup.service
26.931s optimus-manager.service
24.632s snapd.service
14.526s ldconfig.service
10.592s dev-loop4.device
10.555s dev-sdb3.device
10.138s systemd-tmpfiles-setup.service
9.720s dev-loop3.device
8.495s dev-loop6.device
8.452s NetworkManager.service
7.870s systemd-journal-flush.service
7.745s ModemManager.service
7.648s dev-loop5.device
6.259s dev-loop9.device
5.204s dev-loop8.device
5.088s dev-loop2.device
5.075s polkit.service
4.917s avahi-daemon.service
4.915s bluetooth.service
4.912s dbus.service
4.912s libvirtd.service
4.907s systemd-logind.service
4.907s systemd-machined.service
4.841s dev-loop1.device
4.761s dev-loop7.device
4.104s udisks2.service
3.674s systemd-modules-load.service
systemd-analyze critical-chain

The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character. @59.291s
└─sddm-plymouth.service @59.291s
└─optimus-manager.service @32.359s +26.931s (blue)
└─ @32.351s
└─ @32.351s
└─systemd-oomd.socket @1min 8.590s
└─-.mount @3.281s
└─-.slice @3.281s

Sorry I did not reboot earlier, here are the output.

systemd-analyze : 
Startup finished in 3.410s (firmware) + 4.335s (loader) + 5.921s (kernel) + 2min 2.253s (userspace) = 2min 15.
921s reached after 2min 1.980s in userspace.
systemd-analyze blame : 

1min 31.526s ldconfig.service
14.582s optimus-manager.service
10.212s systemd-tmpfiles-setup.service
9.920s dev-sdb3.device
9.917s dev-loop7.device
9.870s snapd.service
8.947s dev-loop4.device
6.461s dev-loop8.device
6.145s dev-loop9.device
6.069s dev-loop6.device
5.365s systemd-journal-flush.service
4.794s packagekit.service
4.634s dev-loop2.device
3.840s dev-loop5.device
3.570s systemd-modules-load.service
3.520s dev-loop1.device
3.321s systemd-remount-fs.service
3.288s dev-loop0.device
3.247s dev-loop3.device
2.564s polkit.service
2.403s upower.service
2.371s [email protected]\x2duuid-B0D1\x2dE4E1.service
2.072s avahi-daemon.service
2.070s bluetooth.service
2.067s dbus.service
2.062s systemd-logind.service
2.062s systemd-machined.service
systemd-analyze critical-chain : 

The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character. @2min 1.980s
└─sddm-plymouth.service @2min 1.980s
└─optimus-manager.service @1min 47.396s +14.582s
└─ @1min 47.389s
└─ @1min 47.389s
└─snapd.socket @1min 47.388s +646us
└─ @1min 47.344s
└─systemd-update-done.service @1min 47.333s +10ms
└─ldconfig.service @15.805s +1min 31.526s
└─ @15.804s
└─boot-efi.mount @15.207s +597ms
└─[email protected]\x2duuid-B0D1\x2dE4E1.service @12.835s +2.371s
└─dev-disk-by\x2duuid-B0D1\x2dE4E1.device @12.834s
systemctl disable --now ldconfig.service
1 Like

Did that but I don't see any visual speed up in time as such.

Just a couple of ideas, not really suggestions.
Do you really need optimus-manager? I remember several suggestions from experienced team members here to try as much as possible to avoid it, leveraging on prime-run when you need your dGPU. This would remove:

Also, maybe something could be reduced here:

Maybe this is the fsck of your other (Windows?) disk /dev/sda? Maybe triggered via fstab?


Then you should look at the userspace values:

systemd-analyze --user critical-chain

My Crystal Ball :crystal_ball: says:

"Look into the auto starters path"

but I don't know what it means...
In any case, you have a long journey into the Journal World to do. Good luck, stranger!! :mage:


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