[Digikam-devel] [digikam] [Bug 361339] New: Album auto-creation creates nameless subalbums and corrupts album hierarchy

via KDE Bugzilla bugzilla_noreply at kde.org
Sun Apr 3 12:46:58 BST 2016


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

            Bug ID: 361339
           Summary: Album auto-creation creates nameless subalbums and
                    corrupts album hierarchy
           Product: digikam
           Version: 5.0.0
          Platform: Compiled Sources
                OS: Linux
            Status: UNCONFIRMED
          Severity: major
          Priority: NOR
         Component: Import
          Assignee: digikam-devel at kde.org
          Reporter: kramski at web.de

I'm running 5.0.0beta5 (digikam-git r33955.9e7223e-1 from AUR) on Arch with a
MySQL backend.

Besides the wanted, correct date-based albums, importing new pictures with
"Auto-creation of albums" creates additional, nameless sub albums which seem to
contain duplicate pictures.

These "ghost albums" seem to have the same effective filesystem path as the
correct ones, so deleting them deletes the wanted subalbums and pictures as
well.

Opening such an album in filemanger reveals empty trailing path components,
e.g.: "/mnt/nas/sandl/bilder/Fotos/Maxi-Test/2016///".

My albums reside on NFS, but the problem exists for local collections as well.
It is also independent of the camera used and of the actual date format (can
also be reproduced with the default ISO format).

As a workaround: How can I get rid of subalbums in the folder pane without
deleting the pictures as well? (Sorry if that's FAQ, I'm quite new to Digikam).

Reproducible: Always

Steps to Reproduce:
1. Create a collection from some existing folder hierarchy (see screenshot 1)
2. Import some new picture which will autocreate new date based subalbums (see
screenshot 2)


Actual Results:  
Additional, nameless subalbums will be created (see screenshot 3)

Expected Results:  
Only the wanted, date based subalbums should be created.

-- 
You are receiving this mail because:
You are the assignee for the bug.



More information about the Digikam-devel mailing list