Bug 384849 - Database dropped when network collection not mounted
Summary: Database dropped when network collection not mounted
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Database-Media (show other bugs)
Version: 5.7.0
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-09-19 11:05 UTC by Unknown
Modified: 2017-11-11 22:53 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 5.8.0


Attachments
attachment-13843-0.html (2.17 KB, text/html)
2017-09-25 17:34 UTC, Unknown
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Unknown 2017-09-19 11:05:40 UTC
Incidentally it happens that I start digiKam while the network device containing my major collection is not mounted. Digikam removes whatever is not mounted from the list. Not from Settings | Condfigure Digikam | Collections. 
After mount, digiKam detects the collection is there, and starts a complete scan as if it is rebuilding the database. In my case over tens of thousands of images. Which takes at least an hour. This should not be necessary imho. I think it did not do so in version 4.x.
Comment 1 Unknown 2017-09-19 20:36:01 UTC
It's the July 2017 prerelease I was using. Replaced it by the Aug 27 version, but did not retry.

Theo
Comment 2 Unknown 2017-09-20 20:32:46 UTC
Same problem with the Aug 27 2017 release.
Comment 3 Maik Qualmann 2017-09-23 21:08:34 UTC
Problem is not reproducible here. The mount point has also been added as a network collection under digiKam?

Maik
Comment 4 Unknown 2017-09-25 17:33:59 UTC
Created attachment 108013 [details]
attachment-13843-0.html

Good question, Maik,

No it isn't. It's a local collection. When version 5 came, it seemed to
have lost everything in use until that moment. So I reconfigured. I may
have thought it made no difference. The file browsing menus are identical
anyway, asking for the mount point. Come to think of it, the mount point is
also a local directory, but when nothing mounted there, empty.

I will add a collection on removable shares, and when next remove the local
collection. Or should I remove it first and next add the network share?

Theo

Vriendelijke  groet,
Theo Groen

2017-09-23 23:08 GMT+02:00 Maik Qualmann <bugzilla_noreply@kde.org>:

> https://bugs.kde.org/show_bug.cgi?id=384849
>
> Maik Qualmann <metzpinguin@gmail.com> changed:
>
>            What    |Removed                     |Added
> ------------------------------------------------------------
> ----------------
>                  CC|                            |metzpinguin@gmail.com
>
> --- Comment #3 from Maik Qualmann <metzpinguin@gmail.com> ---
> Problem is not reproducible here. The mount point has also been added as a
> network collection under digiKam?
>
> Maik
>
> --
> You are receiving this mail because:
> You reported the bug.
>
Comment 5 Maik Qualmann 2017-09-25 17:50:04 UTC
If the collection is established under network, digiKam assumes that it is not always available. The thumbnails are retained when the network connection is lost. When trying to open an image, comes a tooltip that the connection to the network must be reconnected.

Maik
Comment 6 Unknown 2017-09-25 17:52:04 UTC
makes sense. What is the right order to fix it? +- or -+?
Theo
Comment 7 Unknown 2017-09-25 20:37:13 UTC
I made the change, photo's are there as usual. I trust the shares work now as intended.

Thanks a lot, especially for the quick help,
Theo
Comment 8 Unknown 2017-09-27 09:59:59 UTC
Checked database is still there. The pop-up on doubleclick stays too short to read. You need click and a half to read it.

Thanks again,
Theo