Bug 398885 - Collections on removable media does not work
Summary: Collections on removable media does not work
Status: RESOLVED WORKSFORME
Alias: None
Product: digikam
Classification: Applications
Component: Database-Media (show other bugs)
Version: 5.9.0
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-09-20 18:34 UTC by Anders Lund
Modified: 2022-11-15 09:21 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In: 7.5.0


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Anders Lund 2018-09-20 18:34:46 UTC
I have collections on various usb harddisks, but digikam is not handling this in a fashion that is even close to working.

If I plug the media in while digikam is running, it does not react at all. The collections are not visible when the disk is pluggen in.

If I plug the disk in, and then start digikam, it starts a process that takes near forever, recataloguing (I think) the collection.

This USED to work, but does not anymore.

Adding a collection on a removable media is not at all easy either, the file dialog offered does not know about removable media, and the only way is to browse to the mount directory. Please use a functional file dialog tor this purpose (ie the KDE one!)
Comment 1 Maik Qualmann 2018-09-20 19:28:10 UTC
Activate the system file dialog in the digiKam settings->Miscellaneous. This does not work with the AppImage.

Maik
Comment 2 Anders Lund 2018-09-20 20:05:24 UTC
This is what happens: I add a collection on a usb hd. Digikam scans for an hour. I unmount the disk, and digikam removes the entry from the Albums view. In the settings, the collection is now no longer listed under collections in removable media, but under local collections.
If I plug in the disk, nothing happens.
If I quit digikam and start it with the disk mounted, digikam scans for one hour. It is 100% broken.
Comment 3 Anders Lund 2018-09-20 20:08:59 UTC
If I try to add a collection on a network share, the behavior is the same, broken useless crab.
Comment 4 Maik Qualmann 2018-09-20 20:22:33 UTC
Which version of digiKam do you use exactly? Which Linux desktop do you use?

Maik
Comment 5 Maik Qualmann 2018-09-20 20:30:57 UTC
A test here under openSUSE Tumbleweed with digiKam from git/master (6.0.0-beta1) with a collection on a USB drive works here as expected. It is correctly indicated that the storage location is not available, it can be accessed immediately after mounting.

Maik
Comment 6 Anders Lund 2018-09-21 05:40:16 UTC
I'm on archlinux, fully updated, so digikam is latest release version.

It sounds encouraging that it works for you Maik. I have one suspicion about it, namely that it has to do with how media are recognized. Mine are listed as /dev/sd* in the mount list, but earlier they were listed by UUIDs. Maybe that is the root of the problem.
Comment 7 caulier.gilles 2018-09-22 07:15:35 UTC
Anders,
Which digiKam version do you use exactly ?

Gilles Caulier
Comment 8 Anders Lund 2018-09-22 12:26:57 UTC
5.9.0
Comment 9 caulier.gilles 2020-08-01 16:08:45 UTC
digiKam 7.0.0 stable release is now published and now available as FlatPak:

https://www.digikam.org/news/2020-07-19-7.0.0_release_announcement/

We need a fresh feedback on this file using this version.

Thanks in advance

Gilles Caulier
Comment 10 Anders Lund 2020-08-01 16:17:38 UTC
I have decided to not use digikam, as it deletes my files and apart from that 
is quite a monster loading a lot of unneeded code and providing much more 
features than I actually need.

--
lørdag den 1. august 2020 18.08.45 CEST skrev du:
> https://bugs.kde.org/show_bug.cgi?id=398885
> 
> --- Comment #9 from caulier.gilles@gmail.com ---
> digiKam 7.0.0 stable release is now published and now available as FlatPak:
> 
> https://www.digikam.org/news/2020-07-19-7.0.0_release_announcement/
> 
> We need a fresh feedback on this file using this version.
> 
> Thanks in advance
> 
> Gilles Caulier
Comment 11 Lassi 2022-11-15 09:21:32 UTC
I'm having this exact problem with Digikam v 7.8.0 on macOS 13.0.1.

(In reply to Anders Lund from comment #0)
> If I plug the media in while digikam is running, it does not react at all.
> The collections are not visible when the disk is pluggen in.
> 
> If I plug the disk in, and then start digikam, it starts a process that
> takes near forever, recataloguing (I think) the collection.