plasmashell did not fully start & use 99% CPU

pogwizd · n00b Joined: 26 Mar 2006 Posts: 60 Location: Warszawa

Hi everyone,

I recently made an @world update of my system, which ended with the update of the whole plasma DE to version 6.1.4.
Since then, I have three problems (which are all related I think):
- I have no docker starting at all,
- I have no menu when right clicking on the desktop
- I have the "/usr/bin/plasmashell --no-respawn" PID stuck at nearly 100% the whole time the session is alive.

I tried to kill this plasmashell PID, but no success with that.

Here is a log of my plasmashell session

rab0171610 · Guru Joined: 24 Dec 2022 Posts: 420

It maybe some desktop settings leftover from KDE Plasma 5 that are no longer compatible with 6. To see if this is a likely, create a new user. Log in as that user, if the problem no longer appears, then it is likely a settings issue.

You can delete your cache. It should rebuild itself the next time you log back in. It is located at ~/.cache. Try logging out, logging into a TTY outside of the desktop and move or delete everything in that directory. Log back in to KDE to see if the issue still persists.

pogwizd · n00b Joined: 26 Mar 2006 Posts: 60 Location: Warszawa

Hi,

Indeed, I had to remove my enitre plasma configuration (just the cache did not sufice). So I had to redo it completely to have it as I wanted :cry:

Thanks rab0171610 for the advice,

I was just surpised, as with the previous version 6.1.x versions, I had no problems with the fact that I switched from plasma 5...

Now i have to see why I have non stop akonadi crashing, but that's another subject.

EDIT:
I must retract my previous result from this morning.

After loggin on again this afternoon, again I have the same problem. And this time I was starting from the clean plasma session on my account I started yesterday evening.
I really do not know, maybe some additional information is needed?

finoderi · Tux's lil' helper Joined: 29 Oct 2021 Posts: 75

latte-dock is not supported on Plasma 6. May be you have another dock, I don't know.

pogwizd · n00b Joined: 26 Mar 2006 Posts: 60 Location: Warszawa

No, that is not it, I do not use Latte

It's even masked on my system because tis is not supported by plasma 6, and will be removed:

finoderi · Tux's lil' helper Joined: 29 Oct 2021 Posts: 75

Yeah, latte-dock is a shitty piece of software anyway.

I can describe how I updated from Plasma 5 to 6.

1. I ran emerge command with --pretend, there were two blocks. I didn't feel like wasting time trying to resolve them manually.
2. So I edited out plasma packages from the world list. It's located in /var/lib/portage/world. I have pretty minimal KDE set up, so the list of packages I removed was rather short:

It's probably a good idea to make a backup of the world.

pogwizd · n00b Joined: 26 Mar 2006 Posts: 60 Location: Warszawa

Up until now, I had no problem with my switching to Plasma 6, I use it for 3 months now.

My Plasma installation is not that full, true, more than yours, but still:

pogwizd · n00b Joined: 26 Mar 2006 Posts: 60 Location: Warszawa

I tried the whole week to see where the problem is coming from, and here what's I managed to do so far:
1 - Deleting everything on my user account related to plasma (all plasma config. file, cache, and local file)
2 - Deleting everything on my user account related to the KDE-PIM suite (all config files, cacha, local, and purge of the akonadi db)
3 - Login to the account, and configuration plasma to my liking. - so far so good.
4 - Adding all my e-mail accounts. - Here we are still good.
5 - Adding my cardDav and calDav account (I have a local nextcloud server running). - and here the problems are starting.

So I guess the problem is not really with plasma itself, but with KDE-PIM and the calDav/cardDav functionality.

Since I configured those calDav/cardDav, everytime I boot my PC, I have a notification uppon startup that akonadi is performing some migration, but why, since it was a fresh db. For the moment my account start, but I wonder for how long...
The heck in that, is that after that, kmail does not show some subfolder in my IMAP accounts.