[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [digikam] [Bug 393068] digikam.coredb: Core database: Album library path from config file is empty. 
From:       arne anka <bugzilla_noreply () kde ! org>
Date:       2018-04-13 9:32:16
Message-ID: bug-393068-17878-uF4x6s10j3 () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=393068

--- Comment #2 from arne anka <kde-bugs@ginguppin.de> ---
as mentioned, I just hadn't used digikam for some time (about 6 months).
there was no dialog whatsoever, just something about looking for something and
the the error popup.

apparently you expect some sort of user action, but I never got anything beyond
the above and then the crash.

"I think that we can not solve the problem with such an old database."


it's not quite comprehensible for me how the database can be that old -- I use
debian/sid and update almost every day. looks like some sort of communication
trouble if you can make such large jumps without distributions noticing.

anyway: 
"The best way will be to create a new database."

care to elaborate? 

- how do I do that?
- what files need to be deleted/moved?
- what information will be lost?


digikam should do exactly that, shouldn't it?
notfiying me about the issue, offering to create a new db (and most
importantly, clearly stating the consequences - what information will be
lost?).
from your description I still don't understand why digikam fails to solve the
issue on its own.

Remember: didgikam doesn't even START! whatever needs to be done is obviously
more that digikam is able to handle and it doesn't tell me anything either.

-- 
You are receiving this mail because:
You are watching all bug changes.=
[prev in list] [next in list] [prev in thread] [next in thread]