[SOLVED] KDE very slow to launch, remains slow for a while after booti

etteling · 2024-07-11 05:07:18

Hello

The last ~week or so I've been having an issue where KDE is verrry slow to load, like multiple minutes, and even once it has loaded, everything is very slow, in particular Firefox and Discord. About ten minutes after KDE loading it all seems mostly to have returned to normal (although also I am not launching new applications after that point really, or just here and there). Honestly I don't even really know where to start, because I can't think of anything I changed when it started. I have tried switching to the linux-lts kernel (from linux-zen), but it didn't make any difference.

This is the output of journalctl -b -p err

Jul 11 14:35:41 pigfriend kernel: iwlwifi 0000:00:14.3: WRT: Invalid buffer destination
Jul 11 14:35:39 pigfriend (udev-worker)[452]: event16: Failed to call EVIOCSKEYCODE with scan code 0x7c, and key code 190: Invalid argument
Jul 11 14:35:46 pigfriend kernel: iwlwifi 0000:00:14.3: WRT: Invalid buffer destination
Jul 11 14:38:28 pigfriend systemd[863]: Failed to start Splash screen shown during boot.
Jul 11 14:38:36 pigfriend org_kde_powerdevil[1223]: busno=4, sleep-multiplier =  2.00. Testing for supported feature 0x10 returned Error_Info[DDCRC_RETRIES in >
Jul 11 14:40:26 pigfriend akonadiserver[1628]: org.kde.pim.akonadiserver: Cannot connect to agent instance with identifier 'akonadi_akonotes_resource_0', error>
Jul 11 14:40:26 pigfriend akonadiserver[1628]: org.kde.pim.akonadiserver: Cannot connect to agent instance with identifier 'akonadi_akonotes_resource_0', error>

I have noticed my network connection being very slow on wifi as of maybe a month ago, but I have just been using ethernet.

Thank you very much in advance.

Last edited by etteling (2024-07-13 07:59:09)

seth · 2024-07-11 05:57:40

the output of journalctl -b -p err

Is almost always pointless.
Check the CPU and IO load during this, could be baloo (file indexer)

Is this on X11 or wayland? Same issue when you suspend the compositor?
To see whether the CPU is a bottleneck (could be frequencies next to load) you can run

time echo "scale=5000; a(1)*4" | bc -l

while slow and fast and compare the runtime (don't post the result of the calculation - it should look familiar…)

etteling · 2024-07-11 07:23:02

Ty! It's Wayland. It's all running fine now, but I will try that again later when I reboot (am just about to have dinner).

I have set up plasma widgets to report on CPU/memory/disk IO/network upload and download. They are always low %s, regardless of how slowly the system is running.

ETA: I've tried rebooting, and that command's output is broadly the same as it was when I was running it while everything was running more quickly. Within the range of 0m0.000s and 0m0.003s in all cases.

Last edited by etteling (2024-07-11 08:00:34)

seth · 2024-07-11 12:08:16

So not a CPU limitation.
Try the behavior on KDE/X11 and KDE/X11 w/ disabled compositor - and post the output of "qdbus org.kde.KWin /KWin supportInformation"
It might be an isssue w/ GPU shader generation (though not on every reboot?)

etteling · 2024-07-13 06:03:44

Thank you so much!

Logging into X11, there is no issue at all. This is the output of that command in X11: https://pastebin.com/bJ3JRqkR

Also, wrt "not on every reboot?" -- it is happening every reboot with Wayland, but it sorts itself out (mostly) eventually. There is still some slight lag in some applications, but for the most part after the first sort of 10-15 minutes after KDE has fully loaded, the system runs as expected. Although, I am in X11 now and I think I had stopped noticing the lag after the first 10-15 minutes because it does feel dramatically faster than it had been for the last week or so.

Last edited by etteling (2024-07-13 06:07:48)

seth · 2024-07-13 06:57:37

If you first log into an X11 session and then immediately out and into a wayland one, does the latter still show the symptoms?
Do you have the same problem w/ a single output?

Keep an eye on the GPU frequencies and power profiles, https://wiki.archlinux.org/title/AMDGPU#Overclocking and the following paragraphs, but radeontop/nvtop might do as well.

etteling · 2024-07-13 07:57:57

Oh wow, amazing. Yeah so long as I log in first to X11, then there are no issues when I launch Wayland. I am happy to consider this solved at this point, even though I don't know why it is happening still. But my issue is resolved. Thank you so much for all your time, seth.

seth · 2024-07-13 08:21:17

seth wrote:

Keep an eye on the GPU frequencies and power profiles, https://wiki.archlinux.org/title/AMDGPU#Overclocking and the following paragraphs, but radeontop/nvtop might do as well.

I could imagine that KDE/wayland doesn't cause it to step up sufficiently, then X11 kicks its butt and the subsequent wayland session benefits from that?

Arch Linux

#1 2024-07-11 05:07:18

[SOLVED] KDE very slow to launch, remains slow for a while after booti

#2 2024-07-11 05:57:40

Re: [SOLVED] KDE very slow to launch, remains slow for a while after booti

#3 2024-07-11 07:23:02

Re: [SOLVED] KDE very slow to launch, remains slow for a while after booti

#4 2024-07-11 12:08:16

Re: [SOLVED] KDE very slow to launch, remains slow for a while after booti

#5 2024-07-13 06:03:44

Re: [SOLVED] KDE very slow to launch, remains slow for a while after booti

#6 2024-07-13 06:57:37

Re: [SOLVED] KDE very slow to launch, remains slow for a while after booti

#7 2024-07-13 07:57:57

Re: [SOLVED] KDE very slow to launch, remains slow for a while after booti

#8 2024-07-13 08:21:17

Re: [SOLVED] KDE very slow to launch, remains slow for a while after booti

Board footer