Upon restart of plasma-desktop I encountered the following output:


It points towards some serious instabilities. I have been searching for an idea of what to try to begin addressing the problem, but have hit a bit of a wall.

One suggestion was to remove and re-install akanodi, but this proved unwise as it threatens to break many other current running packages. Not really sure what more to try.

It all started with me trying to address the fact that my folder view widgets always move into a stack at the bottom right corner of my desktop upon reboot, so I thought maybe if i force a restart of the plasma-desktop service, it may save the locations properly into the config file, and encountered the fore-mentioned errors posted in the pastebin link above.

  • this almost certainly has nothing to do with akonadi. try this to restart the plasma desktop: kquitapp5 plasmashell && kstart plasmashell – cas Dec 31 '17 at 3:37
  • > kquitapp5 plasmashell && kstart plasmashell No command 'kquitapp5' found, did you mean: Command 'kquitapp' from package 'kde-runtime' (universe) kquitapp5: command not found – Bradley Elliott Dec 31 '17 at 7:10
  • dropping the '5' from 'kquitapp5' yielded: ~> kquitapp plasmashell && kstart plasmashell kquitapp(29943): "Application plasmashell could not be found using service org.kde.plasmashell and path /MainApplication." – Bradley Elliott Dec 31 '17 at 7:21
  • no idea, i don't use kde. that's what i found when i googled 'restart plasma desktop'. it seems that the page i found is obsolete now - the significant point seems to be using kstart to restart the plasma shell, whatever it's current name is. – cas Dec 31 '17 at 7:57
  • using kstart gave the same output, I started with akanodi as a possible cause of problems due to the last 4 lines of output: ProcessControl: Application 'akonadiserver' returned with exit code 255 (Unknown error) "akonadiserver" crashed too often and will not be restarted! plasma-desktop(2217)/libakonadi Akonadi::EntityTreeModelPrivate::finalCollectionFetchJobDone: "Unknown error." plasma-desktop(2217)/libakonadi Akonadi::EntityTreeModelPrivate::collectionFetchJobDone: Job error: "Unknown error." for collection: () – Bradley Elliott Dec 31 '17 at 9:00

On most distributions your login manager sets up your session. Simply killing plasma and restarting it isn't sufficient as this leaves your session (called ksm) in an already configured state. While what you probably should do is restart your session if you want to restart plasma you need to at least restart the shell.

kquitapp5 plasmashell && kstart5 plasmashell

Note that this will not be started by the session manager when you do this. Which leaves ksm in a weird state. You will have to stop plasmashell yourself before you end of your session.

  • kquitapp5 plasmashell && kstart plasmashell No command 'kquitapp5' found, did you mean: Command 'kquitapp' from package 'kde-runtime' (universe) kquitapp5: command not found – Bradley Elliott Dec 31 '17 at 19:41
  • also, more interested in tracking down the source of the errors, getting QBusErrors, akanodi errors, qt errors, missing paths, restarting plasma-desktop is just the action that revealed the underlying issues. see output @ pastebin.com/nSgv9WyG – Bradley Elliott Dec 31 '17 at 19:43

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.