My KDE install doesn't work well after an upgrade from frameworks 5.74 to 5.77: krunner doesn't give any selectable options, kmenu's application menu is empty, embedded konsoles do not start. As I thought it could be useful, i tried to run kbuildsycoca5, I cannot seem to run it successfully. I get:

Code: Select all

kbuildsycoca5
kbuildsycoca5 running...
kf.service.sycoca: Couldn't lock "/home/username/.cache/ksycoca5_nl-BE_jABT9uAdnn47BH0EKT84cdZB+ko=.lock"

That file doesn't exist. (I deleted all ‘ksycoca5_…=’ files in that directory, but that didn't change a thing.)

Does anyone know how I can get kbuildsycoca to run?

Hi!

Whats the folders permission? (`ls -ld ~/.config`) Does the logfile contain any remarkable errors?

koffeinfriedhof wrote:Whats the folders permission? (`ls -ld ~/.config`)

Code: Select all

drwxr-xr-x 1 username username 7284 15 jan 09:13 .config//

koffeinfriedhof wrote:Does the logfile contain any remarkable errors?

Lots of repetitions of

Code: Select all

plasmashell[118031]: kf.service.services: KServiceTypeTrader: serviceType "Application" not found
plasmashell[118031]: kf.service.sycoca: No ksycoca database available! Tried running kbuildsycoca5 ?
plasmashell[118031]: Could not open sycoca database, you must run kbuildsycoca first!
plasmashell[118031]: kf.service.sycoca: Couldn't lock "/home/username/.cache/ksycoca5_nl-BE_jABT9uAdnn47BH0EKT84cdZB+ko=.lock"
plasmashell[118031]: kf.service.sycoca: Couldn't lock "/home/username/.cache/ksycoca5_nl-BE_jABT9uAdnn47BH0EKT84cdZB+ko=.lock"

Sorry, it has to be `ls -ld ~/.cache` not config. Should have the same permissions as your config folder.

«could not lock» can have a lot of different causes, e.g. no write permission, already locked (should have been mentioned in log), incompatible filesystem or network mounted one (user mapping, etc.), …

koffeinfriedhof wrote:Sorry, it has to be `ls -ld ~/.cache` not config. Should have the same permissions as your config folder.

It was owned by root! (Why is a mystery to me…) After fixing that, things seem to be working as they should. Many thanks!

This is often a result of using sudo with gui tools. Thats why you should never start a graphical program using sudo.