digiKam problem side effect - or maybe not

[Liam Proven]

On 11 February 2014 22:29, rikona <rikona at sonic.net> wrote:
> Looking closer, this is a folder, user-owned, with files and
> sub-folders in it apparently associated with the few kde pgms I use.
> It's actually var/tmp/kdecache-rikona, and there are other folders for
> other users including var/tmp/kdecache-root [owned by root - only has
> icon-cache.kcache in it]]. I just left off the rikona part in my
> original email.

(!!!)

That's a crucial detail to leave off!

> If I remove kdecache-rikona, (1) will it mess up my other kde
> pgms, and (2) will it be safely recreated by running those pgms [or
> was the dir set up at install time]?

You might lose your local settings in them. Is that a problem?

> Sorry, but I tend to be a bit cautious... :-)

Not when it comes to leaving stuff out of a problem description you are posting!

> In the original error msg, it seemed to be complaining about
> ownership. Is it possible that the folder kdecache-root is the
> problem, perhaps created by running konq with sudo?
>
> If I change ownership of the folder kdecache-rikona to root, as it
> seems to want, will that make the contents inaccessible to the other
> kde pgms?

Root can access everything. Other users can't access root's stuff.

So, no.

> Is there an accessible creation-date that might tell me when these
> dirs/files were created? That might give a clue...

Yes. If you want to play detective, go ahead. My personal response
would be: nuke 'em.



-- 
Liam Proven * Profile: http://lproven.livejournal.com/profile
Email: lproven at cix.co.uk * GMail/G+/Twitter/Flickr/Facebook: lproven
MSN: lproven at hotmail.com * Skype/AIM/Yahoo/LinkedIn: liamproven
Tel: +44 20-8685-0498 * Cell: +44 7939-087884