-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA224 > On Mon, Oct 20, 2014 at 01:08:57AM +0200, Jagged O'Neill wrote: >> /var/tmp/kdecache-jagged/ksycoca, >> which exists, and is empty; it's a regular file, owned by jagged:users, > > Okay, shy and humble as I am --- but is there no one who has an idea > about what goes wrong? > > I mean, the name kbuildsycoca somehow implies that it writes the > file. It's fine that it also wants to read it, if necessary, but it > should figure when the file is empty and not just stop working... > regarding this behaviour I'm sure that it is a bug... > > Anyway --- if not via kbuildsycoca --- how do I otherwise populate > the file? > > Experts to the front please... thx I haven't experienced this which is why I haven't commented. That being said, you could try running kbuildsycoca --noincrememntal (as the user experiencing the problem) to fully regenerate the database and see if that helps. Tim -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iFYEARELAAYFAlRFfAIACgkQLaxZSoRZrGG6qADgygaC8mdu8b+tFaStdSLmOFjG SVAjnS8fpt2/sQDeONbpQqP6T1AqyNQ562YqtYeXC7DTZXmo1C8M+g== =4+dz -----END PGP SIGNATURE-----