Tumbleweed plasma taking to long to login

Hello mates,

My first time on the Suse forum, and just 3 year using Linux as my daily OS on and main machine. I considered myself a noob.

I’m currently using Manjaro Plasma and playing with Suse Tumbleweed and Fedora on virtual machine to learn a little, but yesterday I build a new machine and decided to go with a fresh installation giving a try to Suse Tumbleweed due to better integration with BTRFS and auto snapshots. Everything seems to work fine except the loging time taking 22 seconds to load the desktop after the password is entered, it is too much and feels like and issue.

The Suse mascot on the start menu button is also missing plasma defaults is it’s place. Standard Dolphin is working correctly with dark theme, while File manager - Super User Mode shows white background and some dark areas making it hard to proper read information.

**Is there any know issue related to plasma loging ? How can I identify if is there issue with my machine? **

I tried to check system log, but the yast is very different compared to KSystemlog, so I wasn’t able to proper filter for error/critical/alert/emergency/warning

I download the ISO yesterday and proceed with installation today morning. The only thing I didn’t change from default was the SWAP partition that I select to not use, so I think it’s using swap file instead.

All my app / repo were installed correctly without any issue, this sentence consider also Flatpak ones.


Below my system information

Thank you in advance.

  Kernel: 6.2.8-1-default arch: x86_64 bits: 64 compiler: gcc v: 13.0.1
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.2.8-1-default
    root=UUID=3c28adf0-b172-4677-8554-027b0496259d splash=silent
    mitigations=auto quiet security=apparmor
  Desktop: KDE Plasma v: 5.27.3 tk: Qt v: 5.15.8 wm: kwin_x11 vt: 7 dm: SDDM
    Distro: openSUSE Tumbleweed 20230324
  Type: Desktop Mobo: MACHINIST model: E5-MR9A v: V1.0
    serial: <superuser required> UEFI: American Megatrends v: 5.11
    date: 10/25/2022
  Message: No system battery data found. Is one present?
  RAM: total: 31.18 GiB used: 2.23 GiB (7.2%)
  RAM Report: permissions: Unable to run dmidecode. Root privileges required.
  Info: model: Intel Xeon E5-2667 v4 bits: 64 type: MT MCP arch: Broadwell
    level: v3 note: check built: 2015-18 process: Intel 14nm family: 6
    model-id: 0x4F (79) stepping: 1 microcode: 0xB000038
  Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache:
    L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB L2: 2 MiB desc: 8x256 KiB L3: 25 MiB
    desc: 1x25 MiB
  Speed (MHz): avg: 1500 high: 3600 min/max: 1200/3600 scaling:
    driver: intel_cpufreq governor: schedutil cores: 1: 1200 2: 3600 3: 1200
    4: 1200 5: 1200 6: 3600 7: 1200 8: 1200 9: 1200 10: 1200 11: 1200 12: 1200
    13: 1200 14: 1200 15: 1200 16: 1200 bogomips: 102164
  Flags: 3dnowprefetch abm acpi adx aes aperfmperf apic arat arch_perfmon
    avx avx2 bmi1 bmi2 bts cat_l3 cdp_l3 clflush cmov constant_tsc cpuid
    cpuid_fault cqm cqm_llc cqm_mbm_local cqm_mbm_total cqm_occup_llc cx16 cx8
    dca de ds_cpl dtes64 dtherm dts epb ept ept_ad erms est f16c flexpriority
    flush_l1d fma fpu fsgsbase fxsr hle ht ibpb ibrs ida intel_ppin intel_pt
    invpcid invpcid_single lahf_lm lm mca mce md_clear mmx monitor movbe msr
    mtrr nonstop_tsc nopl nx pae pat pbe pcid pclmulqdq pdcm pdpe1gb pebs pge
    pln pni popcnt pse pse36 pti pts rdrand rdseed rdt_a rdtscp rep_good rtm
    sdbg sep smap smep smx ss ssbd sse sse2 sse4_1 sse4_2 ssse3 stibp syscall
    tm tm2 tpr_shadow tsc tsc_adjust tsc_deadline_timer vme vmx vnmi vpid
    x2apic xsave xsaveopt xtopology xtpr
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
  Type: retbleed status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
  Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, IBRS_FW,
    STIBP: conditional, RSB filling, PBRSB-eIBRS: Not affected
  Type: srbds status: Not affected
  Type: tsx_async_abort mitigation: Clear CPU buffers; SMT vulnerable
  Device-1: AMD Polaris 20 XL [Radeon RX 580 2048SP] driver: amdgpu v: kernel
    arch: GCN-4 code: Arctic Islands process: GF 14nm built: 2016-20 pcie: gen: 3
    speed: 8 GT/s lanes: 16 ports: active: HDMI-A-1 empty: DP-1,DP-2
    bus-ID: 03:00.0 chip-ID: 1002:6fdf class-ID: 0300 temp: 32.0 C
  Display: x11 server: X.Org v: 21.1.7 with: Xwayland v: 22.1.8
    compositor: kwin_x11 driver: X: loaded: modesetting unloaded: fbdev,vesa
    dri: radeonsi gpu: amdgpu display-ID: :0 screens: 1
  Screen-1: 0 s-res: 2560x1080 s-dpi: 96 s-size: 677x285mm (26.65x11.22")
    s-diag: 735mm (28.92")
  Monitor-1: HDMI-A-1 mapped: HDMI-1 model: LG (GoldStar) ULTRAWIDE
    serial: <filter> built: 2022 res: 2560x1080 hz: 60 dpi: 108 gamma: 1.2
    size: 601x254mm (23.66x10") diag: 652mm (25.7") modes: max: 2560x1080
    min: 640x480
  API: OpenGL v: 4.6 Mesa 23.0.0 renderer: AMD Radeon RX 580 2048SP
    (polaris10 LLVM 15.0.7 DRM 3.49 6.2.8-1-default) direct render: Yes
  Device-1: Intel 8 Series/C220 Series High Definition Audio
    driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:8c20
    class-ID: 0403
  Device-2: AMD Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590]
    driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
    bus-ID: 03:00.1 chip-ID: 1002:aaf0 class-ID: 0403
  Sound API: ALSA v: k6.2.8-1-default running: yes
  Sound Server-1: PulseAudio v: 16.1 running: no
  Sound Server-2: PipeWire v: 0.3.67 running: yes
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: d000
    bus-ID: 06:00.0 chip-ID: 10ec:8168 class-ID: 0200
  IF: enp6s0 state: up speed: 100 Mbps duplex: full mac: <filter>
  IP v4: <filter> type: dynamic noprefixroute scope: global
    broadcast: <filter>
  IP v6: <filter> type: temporary dynamic scope: global
  IP v6: <filter> type: mngtmpaddr noprefixroute scope: global
  IP v6: <filter> type: noprefixroute scope: link
  WAN IP: <filter>
  Message: No bluetooth data found.
  Message: No logical block device data found.
  Message: No RAID data found.
  Local Storage: total: 465.76 GiB used: 19.2 GiB (4.1%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Western Digital
    model: WD Blue SN570 500GB size: 465.76 GiB block-size: physical: 512 B
    logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter>
    rev: 234100WD temp: 30.9 C scheme: GPT
  Message: No optical or floppy data found.
  ID-1: / raw-size: 465.26 GiB size: 465.26 GiB (100.00%)
    used: 19.19 GiB (4.1%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
    label: N/A uuid: 3c28adf0-b172-4677-8554-027b0496259d
  ID-2: /.snapshots raw-size: 465.26 GiB size: 465.26 GiB (100.00%)
    used: 19.19 GiB (4.1%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
    label: N/A uuid: 3c28adf0-b172-4677-8554-027b0496259d
  ID-3: /boot/efi raw-size: 512 MiB size: 511 MiB (99.80%)
    used: 5.1 MiB (1.0%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1 label: N/A
    uuid: BCD5-FBB5
  ID-4: /boot/grub2/i386-pc raw-size: 465.26 GiB size: 465.26 GiB (100.00%)
    used: 19.19 GiB (4.1%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
    label: N/A uuid: 3c28adf0-b172-4677-8554-027b0496259d
  ID-5: /boot/grub2/x86_64-efi raw-size: 465.26 GiB
    size: 465.26 GiB (100.00%) used: 19.19 GiB (4.1%) fs: btrfs
    dev: /dev/nvme0n1p2 maj-min: 259:2 label: N/A
    uuid: 3c28adf0-b172-4677-8554-027b0496259d
  ID-6: /home raw-size: 465.26 GiB size: 465.26 GiB (100.00%)
    used: 19.19 GiB (4.1%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
    label: N/A uuid: 3c28adf0-b172-4677-8554-027b0496259d
  ID-7: /opt raw-size: 465.26 GiB size: 465.26 GiB (100.00%)
    used: 19.19 GiB (4.1%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
    label: N/A uuid: 3c28adf0-b172-4677-8554-027b0496259d
  ID-8: /root raw-size: 465.26 GiB size: 465.26 GiB (100.00%)
    used: 19.19 GiB (4.1%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
    label: N/A uuid: 3c28adf0-b172-4677-8554-027b0496259d
  ID-9: /srv raw-size: 465.26 GiB size: 465.26 GiB (100.00%)
    used: 19.19 GiB (4.1%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
    label: N/A uuid: 3c28adf0-b172-4677-8554-027b0496259d
  ID-10: /usr/local raw-size: 465.26 GiB size: 465.26 GiB (100.00%)
    used: 19.19 GiB (4.1%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
    label: N/A uuid: 3c28adf0-b172-4677-8554-027b0496259d
  ID-11: /var raw-size: 465.26 GiB size: 465.26 GiB (100.00%)
    used: 19.19 GiB (4.1%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
    label: N/A uuid: 3c28adf0-b172-4677-8554-027b0496259d
  Alert: No swap data was found.
  Message: No unmounted partitions found.
  Hub-1: 1-0:1 info: Full speed or root hub ports: 2 rev: 2.0 speed: 480 Mb/s
    chip-ID: 1d6b:0002 class-ID: 0900
  Hub-2: 1-1:2 info: Intel Integrated Rate Matching Hub ports: 8 rev: 2.0
    speed: 480 Mb/s chip-ID: 8087:8000 class-ID: 0900
  Hub-3: 2-0:1 info: Full speed or root hub ports: 2 rev: 2.0 speed: 480 Mb/s
    chip-ID: 1d6b:0002 class-ID: 0900
  Hub-4: 2-1:2 info: Intel Integrated Rate Matching Hub ports: 6 rev: 2.0
    speed: 480 Mb/s chip-ID: 8087:8008 class-ID: 0900
  Hub-5: 3-0:1 info: Hi-speed hub with single TT ports: 15 rev: 2.0
    speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900
  Device-1: 3-1:2 info: INSTANT USB GAMING MOUSE type: Mouse,Keyboard
    driver: hid-generic,usbhid interfaces: 2 rev: 1.1 speed: 1.5 Mb/s
    power: 100mA chip-ID: 30fa:1040 class-ID: 0300
  Device-2: 3-2:3 info: SINO WEALTH Gaming KB type: Keyboard,HID
    driver: hid-generic,usbhid interfaces: 2 rev: 1.1 speed: 12 Mb/s power: 500mA
    chip-ID: 258a:002a class-ID: 0300
  Hub-6: 4-0:1 info: Super-speed hub ports: 6 rev: 3.0 speed: 5 Gb/s
    chip-ID: 1d6b:0003 class-ID: 0900
  System Temperatures: cpu: 27.0 C mobo: N/A gpu: amdgpu temp: 32.0 C
  Fan Speeds (RPM): N/A gpu: amdgpu fan: 1344
  Processes: 338 Uptime: 0h 17m wakeups: 0 Init: systemd v: 253
  default: graphical tool: systemctl Compilers: gcc: N/A Packages: pm: rpm
  pkgs: N/A note: see --rpm tools: yast,zypper pm: flatpak pkgs: 25 Shell: Bash
  v: 5.2.15 running-in: konsole inxi: 3.3.23

Welcome to the forum, hope you enjoy your journey.

No idea what you mean by that, please describe what you expect and what you are seeing with abundant detail.

Since Super User Mode means running as root it probably takes theming from /root rather than your local user home. AFAIK Super User Mode is not well supported upstream, and I don’t run GUI as root (except YaST occasionally) so :person_shrugging: I avoid this by editing root files in the terminal.

Run and post these commands:

$ systemd-analyze 
$ systemd-analyze critical-chain 
$ systemd-analyze blame

Thank for helping me awerlang. Linux is always challenging but enjoying too.

it straight forward. The mascot for Suse is the chameleon so I was expecting to see the circumscribe chameleon in the start menu as you can see in the image below. I think I’m missing some tumbleweed animation too, I mentioning that because sometimes aesthetic issue can be a sing that something is wrong.

Starting computer from bios boot till login scree is vary fast. The part that consumes a lot of time during log in is just after password enter where I see I big plasma logo in a black background, before load the graphical desktop.

Startup finished in 1min 50.282s (firmware) + 4.697s (loader) + 604ms (kernel) + 3.884s (initrd) + 2.419s (userspace) = 2min 1.888s 
graphical.target reached after 2.419s in userspace.
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.

graphical.target @2.419s
└─multi-user.target @2.419s
  └─cron.service @2.419s
    └─postfix.service @1.773s +645ms
      └─network.target @1.770s
        └─NetworkManager.service @1.748s +21ms
          └─network-pre.target @1.724s
            └─firewalld.service @1.498s +225ms
              └─polkit.service @1.478s +18ms
                └─basic.target @1.467s
                  └─sockets.target @1.467s
                    └─pcscd.socket @1.467s
                      └─sysinit.target @1.464s
                        └─systemd-update-utmp.service @1.457s +7ms
                          └─auditd.service @1.421s +35ms
                            └─systemd-tmpfiles-setup.service @1.400s +17ms
                              └─local-fs.target @1.396s
                                └─run-credentials-systemd\x2dtmpfiles\x2dsetup.service.mount @1.407s
                                  └─local-fs-pre.target @389ms
                                    └─lvm2-monitor.service @313ms +76ms
                                      └─dm-event.socket @278ms
3.446s sys-devices-pci0000:00-0000:00:01.1-0000:02:00.0-nvme-nvme0-nvme0n1-nvme0n1p2.device
3.446s dev-disk-by\x2dpath-pci\x2d0000:02:00.0\x2dnvme\x2d1\x2dpart2.device
3.445s dev-disk-by\x2dpartuuid-d8e66114\x2d8aec\x2d4f28\x2d91eb\x2d4b245b4109a7.device
3.445s dev-disk-by\x2did-nvme\x2deui.e8238fa6bf530001001b448b453eda3e\x2dpart2.device
3.445s dev-disk-by\x2ddiskseq-1\x2dpart2.device
3.445s dev-disk-by\x2duuid-3c28adf0\x2db172\x2d4677\x2d8554\x2d027b0496259d.device
3.445s dev-disk-by\x2did-nvme\x2dWD_Blue_SN570_500GB_221362802746\x2dpart2.device
3.445s dev-nvme0n1p2.device
3.439s sys-devices-platform-serial8250-tty-ttyS1.device
3.439s dev-ttyS1.device
3.439s dev-ttyS14.device
3.439s sys-devices-platform-serial8250-tty-ttyS14.device
3.439s dev-ttyS10.device
3.439s sys-devices-platform-serial8250-tty-ttyS10.device
3.437s sys-devices-platform-serial8250-tty-ttyS13.device
3.437s dev-ttyS13.device
3.437s dev-ttyS15.device
3.437s sys-devices-platform-serial8250-tty-ttyS15.device
3.435s dev-ttyS12.device
3.435s sys-devices-platform-serial8250-tty-ttyS12.device
3.435s sys-devices-platform-serial8250-tty-ttyS16.device
3.435s dev-ttyS16.device
3.434s sys-devices-platform-serial8250-tty-ttyS11.device
3.434s dev-ttyS11.device
3.434s dev-ttyS17.device
3.434s sys-devices-platform-serial8250-tty-ttyS17.device
3.434s sys-devices-platform-serial8250-tty-ttyS2.device
3.434s dev-ttyS2.device
3.433s dev-ttyS19.device
3.433s sys-devices-platform-serial8250-tty-ttyS19.device
3.432s sys-devices-platform-serial8250-tty-ttyS21.device
3.432s dev-ttyS21.device
3.432s dev-ttyS24.device
3.432s sys-devices-platform-serial8250-tty-ttyS24.device
3.432s dev-ttyS18.device
3.432s sys-devices-platform-serial8250-tty-ttyS18.device
3.431s sys-devices-platform-serial8250-tty-ttyS26.device
3.431s dev-ttyS26.device
3.430s sys-devices-platform-serial8250-tty-ttyS20.device
3.430s dev-ttyS20.device
3.430s sys-devices-platform-serial8250-tty-ttyS23.device
3.430s dev-ttyS23.device

I also checked logout after everything was loaded and login again. The time to load desktop remain long > 22s.

The missing bit probably is switching to openSUSE global theme. Please double check that.

It reports firmware taking as long as 2 minutes alone :person_shrugging:
If it’s after logging in, I am not sure what it could be. It might be worth taking a look at display manager logs:

$ sudo journalctl -b | susepaste

Post a link to it here.

A troubleshooting step would be creating a new profile and logging into it.

One more check, logout and loging as root. The desktop load very fast as it should be. The chameleon mascot was loaded in the start menu and the tumbleweed animation loaded too. I changed the theme to dark mode and it fixed Dolphin super user background.

I have the impression that something went wrong during my user creation.

i’m using default Dark Theme. The image I post was from google to better illustrate.

Pasted as:

How many hours of uptime does this new installation on new PC with new user have? It may be some background task or tasks haven’t finished, and that after they have, time to desktop after login will normalize to a reasonable length. I don’t recall ever timing this interval, but I can imagine I’ve seen more then 20 seconds more times than just a few on my many installations across multiple PCs of various ages. Has that WD Blue ever been used before? What does it show on hdparm -t? Does smartctl give it an OK bill of health?

It has less them 2 hours, it’s a really new machine with fresh installation.

I checked again the root loging and it became issued too, as my user.

I create a new user called “teste” and everything works fine, made many login, logout and reboots.

Looks like selecting Dark theme is triggering the issue, but backing to light mode does not revert to the previous status. Need to see if this issue is from my ISO download, my installation, or Suse side.

See below

$ systemd-analyze

teste@localhost:~> systemd-analyze
Startup finished in 48min 6.796s (firmware) + 2.286s (loader) + 590ms (kernel) + 3.797s (initrd) + 2.621s (userspace) = 48min 16.092s
graphical.target reached after 2.620s in userspace.

Issued user (triggered from dark theme):
50.282s (firmware)

new user without changing theme
6.796s (firmware)

I just checked my SSD NMVE using GSmartControl and it passed.

smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.2.8-1-default] (SUSE RPM)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org

Model Number:                       WD Blue SN570 500GB
Serial Number:                      221362802746
Firmware Version:                   234100WD
PCI Vendor/Subsystem ID:            0x15b7
IEEE OUI Identifier:                0x001b44
Total NVM Capacity:                 500,107,862,016 [500 GB]
Unallocated NVM Capacity:           0
Controller ID:                      0
NVMe Version:                       1.4
Number of Namespaces:               1
Namespace 1 Size/Capacity:          500,107,862,016 [500 GB]
Namespace 1 Formatted LBA Size:     512
Namespace 1 IEEE EUI-64:            001b44 8b453eda3e
Local Time is:                      Mon Mar 27 00:32:22 2023 -03
Firmware Updates (0x14):            2 Slots, no Reset required
Optional Admin Commands (0x0017):   Security Format Frmw_DL Self_Test
Optional NVM Commands (0x005f):     Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat Timestmp
Log Page Attributes (0x1e):         Cmd_Eff_Lg Ext_Get_Lg Telmtry_Lg Pers_Ev_Lg
Maximum Data Transfer Size:         128 Pages
Warning  Comp. Temp. Threshold:     80 Celsius
Critical Comp. Temp. Threshold:     85 Celsius
Namespace 1 Features (0x02):        NA_Fields

Supported Power States
St Op     Max   Active     Idle   RL RT WL WT  Ent_Lat  Ex_Lat
 0 +     3.70W    3.10W       -    0  0  0  0        0       0
 1 +     2.70W    2.10W       -    0  0  0  0        0       0
 2 +     1.90W    1.80W       -    0  0  0  0        0       0
 3 -   0.0250W       -        -    3  3  3  3     3900   11000
 4 -   0.0050W       -        -    4  4  4  4     5000   44000

Supported LBA Sizes (NSID 0x1)
Id Fmt  Data  Metadt  Rel_Perf
 0 +     512       0         2
 1 -    4096       0         1

SMART overall-health self-assessment test result: PASSED

Breeze Dark is an upstream theme. Navigate to Appearance → Global Themes to find the openSUSE theme.

I don’t think I’ve ever seen as many as 5 minutes before, much less 48. There must be something big that didn’t or hasn’t yet finished initializing.

What follows is from a PC substantially older than yours:

# inxi -CGSMz
  Kernel: 6.2.6-1-default arch: x86_64 bits: 64 Console: pty pts/0
    Distro: openSUSE Tumbleweed 20230324
  Type: Desktop Mobo: BIOSTAR model: G31-M7 TE serial: N/A
    BIOS: American Megatrends v: 080014 date: 02/01/2010
  Info: dual core model: Intel Core2 Duo E7600 bits: 64 type: MCP cache:
    L2: 3 MiB
  Speed (MHz): avg: 1603 min/max: 1603/3066 cores: 1: 1603 2: 1603
  Device-1: AMD RV620 PRO [Radeon HD 3470] driver: radeon v: kernel
  Display: server: X.org v: with: Xwayland v: 22.1.8 driver: X:
    loaded: modesetting unloaded: fbdev,vesa gpu: radeon resolution:
    1: 2560x1440 2: 1680x1050
  API: OpenGL Message: GL data unavailable for root.
# systemd-analyze
Startup finished in 1.891s (kernel) + 3.840s (initrd) + 8.648s (userspace) = 14.381s
graphical.target reached after 8.604s in userspace.
# systemd-analyze critical-chain
graphical.target @8.604s
└─multi-user.target @8.602s
  └─cups.service @8.024s +576ms
    └─nss-user-lookup.target @5.337s
      └─nscd.service @5.147s +186ms
        └─basic.target @5.045s
          └─sockets.target @5.045s
            └─telnet.socket @5.045s
              └─sysinit.target @5.009s
                └─systemd-timesyncd.service @4.933s +75ms
                  └─systemd-tmpfiles-setup.service @4.829s +85ms
                    └─systemd-journal-flush.service @1.321s +3.494s
                      └─systemd-journald.service @1.233s +78ms
                        └─haveged.service @2.001s

The above is irrelevant output. What really matters is startup of graphical login. Journal of host erlangen:

karl@erlangen:~> journalctl --user --since 7:00 -g Started -o short-monotonic 
[58740.127749] erlangen systemd[21008]: Started Daily Cleanup of User's Temporary Directories.
[58740.132949] erlangen systemd[21008]: Started PipeWire Multimedia Service.
[58740.133557] erlangen systemd[21008]: Started Save jAlbum Project Files.
[58740.134192] erlangen systemd[21008]: Started Multimedia Service Session Manager.
[58740.142162] erlangen systemd[21008]: Started D-Bus User Message Bus.
[58740.581647] erlangen systemd[21008]: Started Baloo File Indexer Daemon.
[58740.593396] erlangen systemd[21008]: Started sandboxed app permission store.
[58740.594107] erlangen systemd[21008]: Started flatpak document portal service.
[58740.641016] erlangen systemd[21008]: Started KDE Config Module Initialization.
[58740.657155] erlangen systemd[21008]: Started Virtual filesystem service.
[58740.685957] erlangen systemd[21008]: Started Portal service (GTK/GNOME implementation).
[58740.740120] erlangen systemd[21008]: Started KDE Daemon.
[58740.788243] erlangen systemd[21008]: Started KDE Window Manager.
[58740.805660] erlangen systemd[21008]: Started KDE Global Shortcuts Server.
[58740.820420] erlangen systemd[21008]: Started KDE Session Management Server.
[58740.836934] erlangen systemd[21008]: Started User preferences database.
[58740.970289] erlangen systemd[21008]: Started KDE Plasma Workspace.
[58740.971171] erlangen systemd[21008]: Started Proxies GTK DBus menus to a Plasma readable format.
[58740.974612] erlangen systemd[21008]: Started Handle legacy xembed system tray icons.
[58740.995364] erlangen systemd[21008]: Started KActivityManager Activity manager Service.
[58741.083553] erlangen systemd[21008]: Started KDE PolicyKit Authentication Agent.
[58741.095666] erlangen systemd[21008]: Started Xdg Desktop Portal For KDE.
[58741.110719] erlangen systemd[21008]: Started Portal service.
[58741.220286] erlangen systemd[21008]: Started Powerdevil.
[58741.275880] erlangen systemd[21008]: Started Geoclue Demo agent.
[58741.275978] erlangen systemd[21008]: Started Accessibility.
[58741.276028] erlangen systemd[21008]: Started Calendar Reminders.
[58741.276076] erlangen systemd[21008]: Started Set KDE_FULL_SESSION=1.
[58741.289747] erlangen systemd[21008]: Started /usr/bin/kalendarac.
[58741.296559] erlangen systemd[21008]: Started KScreen.
[58741.473875] erlangen systemd[21008]: Started Firefox - Web Browser.
[58741.489723] erlangen systemd[21008]: Started Terminal - Super User Mode.
[58741.665816] erlangen systemd[21008]: Started KMail - Mail Client.
[58741.862061] erlangen systemd[21008]: Started PipeWire PulseAudio.

Total startup time of graphical login is 58741.86 - 58740.12 = 1.74 seconds.


Will see if any update can fix the issue, otherwise I going to proceed with new fresh installation again but checking ISO file integrity. I hope this can allow Tumbleweed to work fine on my machine, otherwise it might be an issue between my hardware and tumblweed that may not worth the investigation once it’s a single case.


I formatted the NVME, and proceed with new fresh installation, the ISO was previously checked for integrity, and the installation was done 100% offline with network disconnected. When the installation was complete, I just go to the settings and changed to Dark mode and reboot, as expected, the issues was triggered and start to slow the login.

Formatted again and stick with light theme doing some small stuffs with some reboots in between, no issue so far.

Formatted 3rd time and installed Fedora with Plasma, changed to Dark mode and no issue so far.

Note: Tumbleweed running on VM inside Manjaro works fine with dark mode.