digiKam disaster

[rikona]

Hello Nils,

Monday, February 10, 2014, 10:19:41 PM, Nils wrote:

> Pete Smout wrote:
>> On Feb 11, 2014 1:48 AM, "rikona" <rikona at sonic.net> wrote:
>> > So, how can I get rid of this thing - completely - so another
>> > install
>> > would look like a brand-new install AND work corrrectly? Or,
>> > alternatively, is there some way to fix it so at least the program
>> > would work correctly? Any help on this would be greatly appreciated.
>> 
>> Sudo apt-get remove --purge digikam should remove program and all conf
>> files so when you re-install should be like first run!

> Reinstalling the application doesn't really help here. Usually the 
> configuration files are somewhere in $HOME. The package management 
> system leaves these files unchanged and only cares about files in system
> directories like "/usr", "/etc", "/var". In this case it is a KDE 
> application. Therefore it should be sufficient to remove the digikam 
> config files "$HOME/.kde/share/config/".

I removed files there - anything with 'digik'.

> As I don't use digikam, I can only guess the filename being
> "digikamrc".

Yep that too...

> Furthermore there could be additional files in
> "$HOME/.kde/share/apps/digikam/".

There were some there too, and in a few more places also.

> After removing these config files, it may be necessary to log out
> and log in again, but I'm not sure about that.

I haven't done that yet. That will have to wait a bit - I have 20+
things in process and don't want to lose those right now. I'll try it
in a bit...

Any idea why sudo konq just now stopped working? Just plain konq runs
fine but not under sudo/gksu. Could that be a clue to the digikam
problem?

-- 

 rikona