digiKam problem side effect - or maybe not

[rikona]

Hello Liam,

Tuesday, February 11, 2014, 11:31:34 AM, Liam wrote:

> On 11 February 2014 19:32, rikona <rikona at sonic.net> wrote:
>> digiKam is now working, but the konqueror problem is still there. In
>> trying to fix digiKam, I removed a number of files that looked like it
>> might help [but didn't]. Somewhere along the way what I did seemed to
>> have an effect on 'sudo konqueror' not working.
>>
>> I still can't fire up konq using gksu or sudo. This has worked OK for
>> a long time - just stopped. The only error msg is:
>>
>> "var/tmp/kdecache" is owned by uid 1001 instead of uid 0
>>
>> Even with digikam now running I still get the above error. After the
>> error, nothing happens. ^C exits when I get tired of waiting for
>> something...
>>
>> What does this mean, why is it, and what effect might it be having on
>> the konqueror problem?


> I think that this means that you have run Konqueror as root with
> `sudo` and it has saved some of its config files with root
> permissions.

Normally I do use gksu - I did try sudo when that didn't work [as it
used to work].

> Close all copies of Konqueror, then, as the root user, go and remove
> the file that it is complaining about.

> e.g.

> sudo rm var/tmp/kdecache

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.

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]?

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

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?

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

> After this, be sure to only use `gksu` to run it. This ensures your
> user's config files are not replaced or overwritten by root.

Normally I do use gksu, but nice to know a possible problem if I
don't.

Thanks...

-- 

 rikona