[SOLVED] KDE Plasma starts delayed after update/services not reachable until it starts

Issues & Assistance
1

Hello!

I just updated my system and when I now login, Plasma does not start until a few minutes have passed. All programs that were open when I shut down the PC still start immediately, I can also access a terminal and issue commands. Most notably, mpd.service and mpd.socket are started and running (checked with systemctl status), but my client can only connect to it the moment Plasma starts up, which confuses me a whole lot and I cannot find a solution, so help and tips would be appreciated

The log from cachyos-bugreport.sh: 39be8bf

2

There is an option enabled on KDE Plasma by default is “Session Restore”, if you set it to “Start with an empty session”, it should fix one of your problems.

image
image1347Ă—429 37.5 KB

3

This helped on this end, thank you.

On the other problems:

I found out that the problem only happens on boot, if I log out and log in again everything functions as it should, task bar is there instantly, and my mpd client can connect to the socket immediately.

4

I’m glad it fixed one issue.

Can you check output for systemd-analyze and systemd-analyze blame, If they look normal.

You can try disabling plymouth and plashma splash screen. They might show any logs or warnings. Also, don’t forget to check if there is anything on Autostart from settings.

5

There were a few warnings in the startup screen, but they scrolled by way to fast to read them. :confused:

❯ systemd-analyze 
Startup finished in 14.865s (firmware) + 3.449s (loader) + 2.784s (kernel) + 3.348s (initrd) + 2min 5.703s (userspace) = 2min 30.151s 
graphical.target reached after 5.668s in userspace.

The 2,5 mins for userspace seem really long, I guess that’s where the problem lies?

❯ systemd-analyze blame
2min 129ms systemd-networkd-wait-online.service
   26.098s cachyos-rate-mirrors.service
   15.155s systemd-hostnamed.service
    4.770s dev-disk-by\x2dpath-pci\x2d0000:31:00.0\x2data\x2d6.0\x2dpart-by\x2dpartuuid-38eb990d\x2dba1d\x2d45d6\>
    4.770s sys-devices-pci0000:00-0000:00:08.3-0000:31:00.0-ata12-host11-target11:0:0-11:0:0:0-block-sdc-sdc1.dev>
    4.770s dev-disk-by\x2dpath-pci\x2d0000:31:00.0\x2data\x2d6.0\x2dpart-by\x2duuid-0035\x2dCD8F.device
    4.770s dev-disk-by\x2dpath-pci\x2d0000:31:00.0\x2data\x2d6.0\x2dpart-by\x2dpartnum-1.device
    4.770s dev-disk-by\x2did-wwn\x2d0x50026b7683fce573\x2dpart1.device
    4.770s dev-disk-by\x2dpartuuid-38eb990d\x2dba1d\x2d45d6\x2d8750\x2d91dba6b671e3.device
    4.770s dev-disk-by\x2dpath-pci\x2d0000:31:00.0\x2data\x2d6\x2dpart1.device
    4.770s dev-disk-by\x2did-ata\x2dKINGSTON_SUV500M8480G_50026B7683FCE573\x2dpart1.device
    4.770s dev-disk-by\x2dpath-pci\x2d0000:31:00.0\x2data\x2d6.0\x2dpart1.device
    4.770s dev-sdc1.device
    4.770s dev-disk-by\x2duuid-0035\x2dCD8F.device
    4.770s dev-disk-by\x2ddiskseq-3\x2dpart1.device
    4.757s dev-disk-by\x2dpath-pci\x2d0000:31:00.0\x2data\x2d6.0\x2dpart-by\x2duuid-C8F23C31F23C25DA.device
    4.757s dev-disk-by\x2dpath-pci\x2d0000:31:00.0\x2data\x2d6.0\x2dpart-by\x2dpartnum-3.device
    4.757s dev-disk-by\x2dlabel-Hass.device
    4.757s dev-disk-by\x2did-ata\x2dKINGSTON_SUV500M8480G_50026B7683FCE573\x2dpart3.device
    4.757s dev-disk-by\x2did-wwn\x2d0x50026b7683fce573\x2dpart3.device
    4.757s dev-disk-by\x2dpath-pci\x2d0000:31:00.0\x2data\x2d6.0\x2dpart-by\x2dpartuuid-c3ea0f72\x2d931a\x2d439d\>
    4.757s dev-disk-by\x2dpath-pci\x2d0000:31:00.0\x2data\x2d6\x2dpart3.device
    4.757s dev-disk-by\x2duuid-C8F23C31F23C25DA.device
    4.757s dev-disk-by\x2dpath-pci\x2d0000:31:00.0\x2data\x2d6.0\x2dpart-by\x2dlabel-Hass.device
    4.757s dev-disk-by\x2dpath-pci\x2d0000:31:00.0\x2data\x2d6.0\x2dpart-by\x2dpartlabel-Basic\x5cx20data\x5cx20p>
    4.757s dev-sdc3.device
    4.757s dev-disk-by\x2ddiskseq-3\x2dpart3.device
    4.757s dev-disk-by\x2dpath-pci\x2d0000:31:00.0\x2data\x2d6.0\x2dpart3.device
    4.757s sys-devices-pci0000:00-0000:00:08.3-0000:31:00.0-ata12-host11-target11:0:0-11:0:0:0-block-sdc-sdc3.dev>
    4.757s dev-disk-by\x2dpartuuid-c3ea0f72\x2d931a\x2d439d\x2d82d7\x2d1a60bdb5d986.device
    4.749s dev-disk-by\x2dpath-pci\x2d0000:31:00.0\x2data\x2d6\x2dpart2.device
    4.749s dev-disk-by\x2ddiskseq-3\x2dpart2.device
    4.749s dev-disk-by\x2did-wwn\x2d0x50026b7683fce573\x2dpart2.device
6

It looks like you have both systemd-networkd and NetworkManager enabled, disable systemd-networkd: sudo systemctl disable systemd-networkd

7

This solved the problem, now everything starts instantly and the mpd.socket also can be connected to immediately after logging in, thank you so much