digiKam problem side effect - or maybe not

[Liam Proven]

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.

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

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.

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