Summary: | Collections on removable media does not work | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | Anders Lund <anderslund> |
Component: | Database-Media | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | caulier.gilles, lassi.login, metzpinguin |
Priority: | NOR | ||
Version: | 5.9.0 | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 7.5.0 |
Description
Anders Lund
2018-09-20 18:34:46 UTC
Activate the system file dialog in the digiKam settings->Miscellaneous. This does not work with the AppImage. Maik 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. If I try to add a collection on a network share, the behavior is the same, broken useless crab. Which version of digiKam do you use exactly? Which Linux desktop do you use? Maik 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 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. Anders, Which digiKam version do you use exactly ? Gilles Caulier 5.9.0 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 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
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. |