Since nearly one week, I have some trouble with slow booting KDE.
If I restart my PC, it boots up fast till the login-screen.
After entering the credentials, it enter the WM and starts loading… I see the wallpaper (even if screens are switched [I have a dual-screen setup… left screen is right and opposite]). During this some Programms start (means… Linphone, Discord… and other apps (e.g. those who are not closed before last shutdown)… BUT the Plasma-Kicker keep on loading (stay’s invisible)
Till kicker is visible it takes round about 1,5 Minutes.
Even after this loading, I notice some delays.
If I press ALT+F2 (to open KRunner), the input-field show up immediately, but isn’t responsible for round about 20 - 30 Seconds. Same on starting Dolphin… I see the border of the Window, but it takes 20-30 Seconds to really load.
I wonder what the cause of this may be. Which logs can I check to find out what’s wrongs
I would suggest not starting with a saved session, because everything that Plasma has to autostart will be hogging up the CPU and taking CPU cycles away that Plasma itself needs for its initialization.
The second thing is that you probably won’t find anything meaningful in the logs about what is hogging your CPU when you log in — which is why it takes so long, i.e. something is getting stuck in the CPU. The best way of checking this would be through ksysguard or htop. Once you can identify the stuck process, it will become easier to troubleshoot this.
The third advice I will give you is that if you use baloo, have it index only the files but not their content. This can significantly influence the Plasma starting time.
One thing you could also try is create a second user account and see whether it exhibits the same symptoms. If it doesn’t, then the cause is to be found in your ~/.config, ~/.local/share and/or ~/.cache directories.
This gets my vote cause I currently have Garuda, Xero, and Big installed and want to add Manjaro. On all three I’ve noticed of late Discord, Telegram, Dolphin, and Stacer startup on their assigned desktops but it’s about a minute before I get the default panel and docks. Personally I think it’s something in Plasma itself causing the delay.
Well, there was a race condition in kactivitymanager upon initializing the desktop, but the update to Plasma 5.27.9 is said to have fixed that.
Either way, always make sure that your system is up to date — this is aimed more at @rethus than at yourself, of course, because you’ve been around these parts for a while already and you know the ropes.
I frequently visit this forum and I can assure you that there are many users who don’t regularly update their system. Just because it’s a rolling-release doesn’t mean the updates are automatically applied.
I’d created now a new Profile and login at it.
There is also a delay after bootup. Not as long as in my current profile, but much to long compared to earlier days where anything runs smooth.
That brings us back to having htop or something similar enough running at a tty to tell you what’s hogging the CPUs. And if you’re on wireless, then it may be that it’s trying to get a connection going from within your user account.
(Note: it’s called an account. “Profile” is Windows speak.)
I’ve done htop on tty3 and found nothing obvious that fully block the cpu.
BTW: I’ve logged in as root… or should I better do the HTOP with the same user as I’ll login with?
I thought… ok, let’s change the settings in Manjaro to start always with a new … clean session.
Then I’ve done a reboot (go for a coffe… so that the login-screen stay for a couple of minutes untouched).
Looks like you have a hardware failure going on. Your log is filled with dozens of repeated errors like this one below…
Nov 29 15:07:43 secondone kernel: sd 6:0:0:0: [sdc] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_OK
Nov 29 15:07:43 secondone kernel: sd 6:0:0:0: [sdc] Sense Key : Unit Attention [current]
Nov 29 15:07:43 secondone kernel: sd 6:0:0:0: [sdc] Add. Sense: Not ready to ready change, medium may have changed
Nov 29 15:07:51 secondone kernel: ..not responding...
The timestamps of those particular errors also clearly indicate that this failure is the cause of the delays. So, whatever /dev/sdc is, it’s da b0rk3n.
OK that certainly could explain the delay I get. I know my Ryzen 5 3600 is damaged . Still works but I see error messages during boot sometimes that seem to have to do with one or more damaged core. Luckily I just bought a 5700x to replace it. Just waiting to get a new mobo to go with it to be on the safe side.
. Still works but I see error messages during boot sometimes that seem to have to do with one or more damaged core. Luckily I just bought a 5700x to replace it. Just waiting to get a new mobo to go with it to be on the safe side.